Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

[Adigarla Bhargav]

Hi,

     I am facing an issue while booting minimal rootfs from sd card to armv5 board. i am getting kernel panic.

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

Please help me regarding this issue.

Thanks & Regards

Bhargav

[Anil Kumar Pugalia]

Multiple possibilities - a couple of them being:

+ Corrupt SD Card

+ init not finding its needed libraries. Check using ldd on the init executable, what all libraries does it need, and have you put all those. There could be a chain of dependencies.

Regards
Anil

Passion: http://sysplay.in (Playing with Systems)

--
You received this message because you are subscribed to the Google Groups "SysPlay's Inside Linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Adigarla Bhargav]

Hi Anil,

            Thanks for your response. I had simple init file. Same file system is working with NFS. Please find below init file.

#!/bin/busybox sh

/bin/busybox --install -s

mount -t proc none /proc

mount -t sysfs none /sys

echo /sbin/mdev > /proc/sys/kernel/hotplug

/sbin/mdev -s

mknod /dev/ttyO0 c 5 0

echo "just printing this line"

exec /bin/sh 

Thanks & Regards

Bhargav

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "SysPlay's Inside Linux" group.

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux+unsubscribe@googlegroups.com.

[Anil Kumar Pugalia]

Then, possibly some SD card problem. Try booting w/ NFS and then mounting the SD card file system.

Regards
Anil

Passion: http://sysplay.in (Playing with Systems)

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.

[Adigarla Bhargav]

Hi Anil,

I Tried booting with NFS and mounted sd card file system. It's mounting. But not mounting directly from SD card.

Thanks & Regards

Bhargav

[Anil Kumar Pugalia]

Try running the SD card's init script after mounting the SD card file system.

Also try doing a chroot to the SD card file system and then running the init script.

Post your results.

Regards
Anil

Passion: http://sysplay.in (Playing with Systems)

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.

[Adigarla Bhargav]

Hi Anil, 

I tried  running the SD card's init script after mounting the SD card file system.Please find below result.

/ # mount -t ext4 /dev/mmcblk0p2 /appmount/

EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

/ # 

/ # 

/ # 

/ # 

/ # ls

appmount  dev       init      linuxrc   root      sys       usr

bin       etc       lib       proc      sbin      tmp

/ # cd /appmount/

/appmount # ls

appmount    etc         lost+found  sbin        usr

bin         init        proc        sys

dev         lib         root        tmp

/appmount # ./init 

mount: mounting none on /proc failed: Device or resource busy

mount: mounting none on /sys failed: Device or resource busy

mknod: /dev/ttyO0: File exists

/bin/sh: can't access tty; job control turned off

Thanks & Regards

Bhargav

[Anil Kumar Pugalia]

What about trying after a chroot /appmount?

Regards
Anil

Passion: http://sysplay.in (Playing with Systems)

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.

[Adigarla Bhargav]

Hi Anil,

             I tried following. please find below.

/ # chroot /appmount

chroot: can't execute '/bin/sh': No such file or directory.

Thanks & Regards

Bhargav

[Anil Kumar Pugalia]

Try to debug a bit on the lines of errors you are getting and then give us some inputs, like why is chroot failing - use man pages, google, ...

Otherwise, we are like struggling in dark, as we do not have access to your system.

Basically, try verfiying your SD card file system from various possible ways.

Regards
Anil

Passion: http://sysplay.in (Playing with Systems)

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.

[sudip midya]

no /bin/sh file?

[Adigarla Bhargav]

Hi Anil, 

              I tried prebuilt filesystem and flashed with ext3. Getting shell for the first time with following errors. second time mounting is failed.(sd card corrupted after this). 

EXT4-fs error (device mmcblk0p2): ext4_lookup:1584: inode #40562: comm swapper: deleted inode referenced: 40633

Starting init: /sbin/init exists but couldn't execute it (error -117)

/bin/sh: can't access tty; job control turned off

EXT4-fs error (device mmcblk0p2): ext4_iget:4173: inode #40689: comm sh: bad extra_isize (57200 != 256)

EXT4-fs error (device mmcblk0p2): ext4_iget:4173: inode #40689: comm sh: bad extra_isize (57200 != 256)

random: nonblocking pool is initialized

/ # 

/ # 

sudip, there is no bin/sh file in busybox.

Thanks & Regards

Bhargav

[Anil Kumar Pugalia]

These again points to SD card corruption. Try running fsck on the sdcard, or try with another SD card.

Because of the corruption anything weird/random could happen and it would be difficult to debug.

And even in busybox, /bin/sh should be there (may be link to busybox), as you yourself are calling that in your init script. If it is not there, again something corrupt - fix it.

Regards
Anil

Passion: http://sysplay.in (Playing with Systems)

To unsubscribe from this group and stop receiving emails from it, send an email to inside_linux...@googlegroups.com.