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

Bernhard Reutner-Fischer rep.dot.nop at gmail.com
Thu Aug 27 07:49:57 UTC 2009

On Wed, Aug 26, 2009 at 05:50:55PM -0400, H Hartley Sweeten wrote:
>diff a/toolchain/external-toolchain/ext-tool.mk b/toolchain/external-toolchain/ext-tool.mk
>--- a/toolchain/external-toolchain/ext-tool.mk
>+++ b/toolchain/external-toolchain/ext-tool.mk
>@@ -205,12 +205,26 @@
> EXTERNAL_LIBS+=libstdc++.so
> endif
>-SYSROOT_DIR=$(shell LANG=C $(TARGET_CC) -v 2>&1 | grep ^Configured | tr " " "\n" | grep -- "--with-sysroot" | cut -f2 -d=)
>+# We need to pass the -march= option in order to get the correct
>+# multilib sysroot with CROSS-gcc -print-sysroot.
>+ifneq ($(CC_TARGET_ARCH_),)

Not that i'd care, but you should always check against (and of course
use) the full set of flags anyway.

>Every time I press Enter after that I get:
>sh (441): undefined instruction: pc=0007514c
>Code: e1530001 9a00006f e1110002 0a000071 (e16f2f13)
>Please press Enter to activate this console.
>I'm not sure how to figure out what the undefined instruction was but my
>guess is it's an ARMv5T instruction.  It seems like something in the busybox
>build did not honor the TARGET_CFLAGS that were setup for my build.
>TARGET_CFLAGS= -Os -mtune=arm920t -march=armv4t -mabi=aapcs-linux -msoft-float -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 --sysroot /home/bigguiness/buildroot/build_arm/staging_dir/
>Does anyone have any ideas on this?

see above. Sounds most likely like an incorrectly used toolchain. I'd
usually say that you should go bug the people who provide that
toolchain (or use the internal toolchain ;), but i'm pretty sure that
in this particular case you just use it incorrectly.

More information about the buildroot mailing list