AnsweredAssumed Answered

ltib L2.6.35_1.1.0_130130; kernel panic issue while trying to load from ram.

Question asked by Ijaz Fazily on Nov 2, 2015
Latest reply on Nov 6, 2015 by igorpadykov



We are getting the following issue while trying load the image from ram. I have checked the disk image and have found the file "init" in "/sbin". I have checked that the permissions are set to allow execution. I have also checked that busybox is present in /bin and that the permissions are set to allow execution.



setenv bootcmd 'bootm 0x42000000 0x42300000' ; setenv bootargs noinitrd console=ttyAM0,115200 root=/dev/ram init=/sbin/init rootfstype=ramdisk rw ramdisk_size=10000; boot

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:05:31 UTC (331)

VFS: Mounted root (ramdisk filesystem) on device 0:14.

Freeing init memory: 152K

Failed to execute /sbin/init.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance


[<c003212c>] (dump_backtrace+0x0/0x110) from [<c0367a94>] (dump_stack+0x18/0x1c)

r6:c004c9cc r5:c0026074 r4:c04b1500 r3:00000000

[<c0367a7c>] (dump_stack+0x0/0x1c) from [<c0367c7c>] (panic+0x74/0xf0)

[<c0367c08>] (panic+0x0/0xf0) from [<c0367a54>] (init_post+0xb4/0xdc)

r3:c7c24000 r2:c7da6b00 r1:c7da6c00 r0:c040f21e

[<c03679a0>] (init_post+0x0/0xdc) from [<c0008b00>] (kernel_init+0x12c/0x168)

r4:c0026074 r3:c7801080

[<c00089d4>] (kernel_init+0x0/0x168) from [<c004c9cc>] (do_exit+0x0/0x6b8)

r5:c00089d4 r4:00000000



But we were able to load the rootfs from nand with the following bootargs: setenv bootcmd 'bootm 0x42000000' ; setenv bootargs noinitrd console=ttyAM0,115200 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs ro gpmi; boot



Any suggestions would be really appreciated.




Thanks & Regards,

Ijaz Fazily