LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   Kernel panic - not syncing: No init found (https://www.linuxquestions.org/questions/linux-kernel-70/kernel-panic-not-syncing-no-init-found-613576/)

skibud2 01-14-2008 07:14 PM

Kernel panic - not syncing: No init found
 
Hi All,

I am building the 2.6.10 version of the kernel with a ramdisk (for
mips). When I build it with a gcc 3.4.3-glibc-2.3.6 toolchain, it
works find. When I build it with a gcc-4.2.2-glibc-2.7 toolchain I get
the following error:

Kernel panic - not syncing: No init found

Any suggestions? Note: the ramdisk images was built with Busybox (so
that can be the culprit). However, why would it work with the older
version of glibc? I am sure I am being stupid here; all help is appreciated!

Mike

skibud2 01-14-2008 09:18 PM

I am open to all suggestions: ie compile options etc.

Thanks!

jayeola 01-15-2008 04:29 AM

Sounds like you build your kernel to use an init but have not got one in your /boot directory. Here are the relevant lines in my .config.

grep -i init proj/build/kernel/linux-2.6.23.9/.config
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""

You may need to use mkinitrd.

arnabneogy 01-15-2008 06:22 AM

insert boot disk and start recovery of grub

DOTT.EVARISTI 01-15-2008 07:08 AM

Did you use Partimage ?
 
If you made a partimage image,you could restore it and everything would go ok

without becoming mad.

skibud2 01-15-2008 07:46 AM

This is a kernel image built for an embedded system. I have a very simple bootloader. The thing that is strange is that it works fine with the older toolchain but does not work with the newer one. Does anyone know any known issues there? I am using the same ramdisk for both.

skibud2 01-15-2008 08:18 AM

Just kidding .. Turns out it was one of my "simple" changes to the kernel sources. Hmmmm

delnortey 01-16-2008 11:31 PM

I had a similar problem with Fedora C5.
"Kernel Panic - not syncing: Attempted to kill init!"

This would occur randomly during boot up, but not usually
twice in a row.

I fixed it by updating the kernel to 2.6.20.


All times are GMT -5. The time now is 01:55 PM.