From: Gaye Abdoulaye Walsimou <walsimou@walsimou.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel panic - not syncing: Attempted to kill init!: at boot time
Date: Thu, 22 Jan 2009 20:10:50 +0100 [thread overview]
Message-ID: <4978C4BA.3030805@walsimou.com> (raw)
In-Reply-To: <C171323BB93CB94897E300CBB6D4537F17D80301@CLMSG-01.ad.cirrus.com>
Austin, Brian wrote:
> It's not quite that we aren't inspired. It seems to be a common problem.
> Usually it's from either EABI/OABI conflicts with the kernel and your ramdisk, or something broken in the build with busybox itself.
>
> Have you run 'file' on your init or busybox binary?
>
>
Austin,
Toolchain #1:
kernel header linux-2.6.28.1, gcc-4.3.2, binutils-2.9, uclibc-0.9.30
Toolchain #1:
kernel header linux-2.6.27.10, gcc-4.2.4, binutils-2.9, uclibc-0.9.30
busybox which generates a kernel panic:
file /nfsroot/bin/busybox
/nfsroot/bin/busybox: setuid ELF 32-bit LSB executable, MIPS, MIPS32
rel2 version 1 (SYSV), dynamically linked (uses shared libs), stripped
build with toolchain #1
file /var/lib/tftpboot/vmlinux
/var/lib/tftpboot/vmlinux: ELF 32-bit LSB executable, MIPS, MIPS32
version 1 (SYSV), statically linked, not stripped
build with toolchain #1
Working busybox:
bin/busybox: setuid ELF 32-bit LSB executable, MIPS, MIPS32 version 1
(SYSV), dynamically linked (uses shared libs), stripped
build with toolchain #2
I'm a bit confused, I've set mips32r2 in buildroot for toolchain #1 and
for toolchain #2.
Thanks for your answer.
Regards
prev parent reply other threads:[~2009-01-22 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 23:04 [Buildroot] Kernel panic - not syncing: Attempted to kill init!: at boot time Gaye Abdoulaye Walsimou
2009-01-22 17:20 ` Gaye Abdoulaye Walsimou
2009-01-22 17:23 ` Austin, Brian
2009-01-22 19:10 ` Gaye Abdoulaye Walsimou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4978C4BA.3030805@walsimou.com \
--to=walsimou@walsimou.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox