Kernel panic - not syncing: Attempted to kill init! (Embedded ARM Board)
Apologies for the duplicate post, I didn't see the embedded forum until after I posted the original.
I'm punting...I've been dealing with the same kernel panic at work for about a week and it's getting to me. I'm trying to get a small system built from scratch on an ARM development board. The kernel fails while trying to run init with the following error: Code:
eth0: link up
Now the host config:
Also, here's the param's uBoot is passing to the kernel: Code:
console=ttyS0,115200n8 What's really got me stumped is that there aren't any other errors. The panic doesn't give you much information by itself, but I got a lot of good info from this post. Since I never see the busybox load message and last successful message from the kernel is "Freeing init memory..", I'm not sure what's generating the panic. If I delete "init" from /sbin in the filesystem, I get the exact same kernel panic, which is odd because I would expect a warning like "init cannot be found". If, however, I add "init=/sbin/init" to the kernel params, I do get a warning similar to "specified init could not be executed, using default". This is also odd because I think /sbin/init IS the default. If I replace init after that, the warning dissapears, but I get the panic still. I've also tried replacing the busybox init with sysvinit, same panic...so I'm inclined to blame the kernel or something I've screwed up in /dev...or something else I'm missing. The only two entries I have in /dev are "console" and "null". I get a warning about "console" being missing if I remove them. I could also be network related. The filesystem seems to mount just fine, and I don't see any "NFS server not responding" errors...but init is the first binary run over the network, so it could still be a possibility. Please help. :) SOLVED. See the #4 post below... |
You kernel needs to have the following options built in
CONFIG_NFS_FS CONFIG_ROOT_NFS CONFIG_NET_ETHERNET CONFIG_IP_PNP CONFIG_IP_PNP_BOOTP your ethernet card driver. |
Network Settings
Quote:
|
Solved!
I rolled back the kernel version from 2.6.27.8 to 2.6.26.8...sysvinit came up just fine.
I'm not sure if I should report this as a bug or where to report it. Any thoughts? |
All times are GMT -5. The time now is 01:40 AM. |