On Tue, 10 Jun 2014 05:45:56 -0700 (PDT) [email protected] wrote: > I have the absolutely same problem:
Yes, the problem looks essentially the same as experienced by the previous reporter. Looks like you both are using some broken or misleading u-boot and kernel compilation instructions instead of the instructions provided at the linux-sunxi wiki. Please help us to identify its origin. > U-Boot SPL 2014.04-10684-g765936d (Jun 10 2014 - 12:26:32) > Board: Cubieboard > DRAM: 1024 MiB > CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2 > spl: not an uImage at 1600 > > > U-Boot 2014.04-10684-g765936d (Jun 10 2014 - 12:26:32) Allwinner Technology > > CPU: Allwinner A10 (SUN4I) > Board: Cubieboard > I2C: ready > DRAM: 1 GiB > MMC: SUNXI SD/MMC: 0 > In: serial > Out: serial > Err: serial > Net: emac > Hit any key to stop autoboot: 0 > ** Unrecognized filesystem type ** > ** File not found uEnv.txt ** > ** Unrecognized filesystem type ** > 335 bytes read in 136 ms (2 KiB/s) > Jumping to boot.scr > ## Executing script at 44000000 > ** Unrecognized filesystem type ** > 335 bytes read in 125 ms (2 KiB/s) > ** Unrecognized filesystem type ** > ** File not found uImage ** > ## Booting kernel from Legacy Image at 48000000 ... > Image Name: Linux-3.4.90-00253-ge37d760 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 4367320 Bytes = 4.2 MiB > Load Address: 40008000 > Entry Point: 40008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK Based on this log, script.bin is apparently never loaded to RAM. > Starting kernel ... > > <6>Booting Linux on physical CPU 0 > <6>Initializing cgroup subsys cpuset > <5>Linux version 3.4.90-00253-ge37d760 (vlad@pkgdev) (gcc version 4.9.1 > 20140505 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.05 - Linaro GCC > 2014.05) ) #1 PREEMPT Tue Jun 10 13:09:07 EEST 2014 > CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d > CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [...] > [<c0298ca8>] (strncmp+0x10/0x7c) from [<c002985c>] > (script_parser_fetch+0x6c/0x184) > [<c002985c>] (script_parser_fetch+0x6c/0x184) from [<c07cfe8c>] > (usb_manager_init+0xa0/0x510) > [<c07cfe8c>] (usb_manager_init+0xa0/0x510) from [<c0008658>] > (do_one_initcall+0x114/0x16c) > [<c0008658>] (do_one_initcall+0x114/0x16c) from [<c07b7958>] > (kernel_init+0x17c/0x214) > [<c07b7958>] (kernel_init+0x17c/0x214) from [<c000fcf0>] > (kernel_thread_exit+0x0/0x8) > <0>Code: e3520000 0a00001a e52de004 e281e001 (e5d1c000) > <4>---[ end trace f4041c5a663b1fd2 ]--- > <0>Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b And here we go again. The script parser apparently can't parse the missing or garbage data without oopsing. Maybe it could be improved to detect this situation and provide a more comprehensive and user friendly fatal error message. -- Best regards, Siarhei Siamashka -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
