[Buildroot] Kernel panic - not syncing: Attempted to kill init!

Jeff Krasky jeff.krasky at dspcg.com
Fri Dec 2 18:02:48 UTC 2011


> "Attempted to kill init" means the init process died.  Kernel must panic
because init cannot terminate.

> There's something preventing init from running, or it is dying during
execution.

> 

> Is your userland correctly have an init?  normally /sbin/init is called.
If your init is somewhere else, use

> the init= paramater to kernel append

 

How do I know where init is if I can't bring the board up and run any linux
commands?

 

>you may have a mounted jffs2 filesystem but not directly usable (think
squashfs), is it loaded to

> ramdisk?  if so, root=/dev/ram0 init=/sbin/init

 

When I successfully ran 2.6.33 built from Buildroot-2011.05, in U-boot the
setting for root was root=/dev/mtdblock1.  I am not sure what squashfs is.
How can the filesystem not be usable?

 

Thanks.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20111202/62bb2304/attachment-0002.html>


More information about the buildroot mailing list