From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel panic - not syncing: Attempted to kill init!
Date: Thu, 20 Aug 2009 00:13:42 +0200 [thread overview]
Message-ID: <20090819221342.GB19257@buzzloop.caiaq.de> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901BEA476@mi8nycmail19.Mi8.com>
On Wed, Aug 19, 2009 at 04:19:35PM -0400, H Hartley Sweeten wrote:
> On Wednesday, August 19, 2009 12:43 PM, Thomas Petazzoni wrote:
> >
> > Do you compile your kernel with Buildroot, or do you compile it
> > manually ? If compiled manually, is CONFIG_AEABI enabled in your kernel
> > configuration ?
>
> The kernel and rootfs are both created with Buildroot.
>
> For the kernel config I have:
>
> CONFIG_AEABI=y
> CONFIG_OABI_COMPAT=y
Just a side note: for performance reasons, you shouldn't enable
OABI_COMPAT unless you really can't know which binaries the kernel will
execute.
See http://wiki.debian.org/ArmEabiPort for some more details.
Other than that, your problem could also be related to VFP emulation
issues. I had such awhile back.
Daniel
next prev parent reply other threads:[~2009-08-19 22:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 18:32 [Buildroot] Kernel panic - not syncing: Attempted to kill init! H Hartley Sweeten
2009-08-19 19:42 ` Thomas Petazzoni
2009-08-19 20:19 ` H Hartley Sweeten
2009-08-19 21:30 ` Thomas Petazzoni
2009-08-19 22:28 ` H Hartley Sweeten
2009-08-20 2:29 ` H Hartley Sweeten
[not found] ` <48ab7e010908191938n3577c9eem76c04a5bb2f3bd20@mail.gmail.com>
2009-08-20 2:48 ` H Hartley Sweeten
2009-08-20 12:35 ` Thomas Petazzoni
2009-08-20 16:59 ` H Hartley Sweeten
2009-08-20 18:45 ` H Hartley Sweeten
2009-08-21 0:53 ` H Hartley Sweeten
2009-08-21 9:44 ` Thomas Petazzoni
2009-08-21 16:37 ` H Hartley Sweeten
2009-08-21 23:19 ` Thomas Petazzoni
2009-08-22 3:08 ` H Hartley Sweeten
2009-08-22 8:55 ` Thomas Petazzoni
2009-08-22 22:53 ` H Hartley Sweeten
2009-08-23 6:17 ` Thomas Petazzoni
2009-08-24 16:19 ` H Hartley Sweeten
2009-08-24 16:53 ` H Hartley Sweeten
2009-08-24 17:11 ` H Hartley Sweeten
2009-08-25 0:53 ` H Hartley Sweeten
2009-08-25 17:48 ` H Hartley Sweeten
2009-08-25 19:01 ` Bernhard Reutner-Fischer
2009-08-26 16:45 ` H Hartley Sweeten
2009-08-26 20:44 ` Peter Korsgaard
2009-08-26 21:50 ` H Hartley Sweeten
2009-08-27 7:49 ` Bernhard Reutner-Fischer
2009-08-28 23:09 ` H Hartley Sweeten
2009-08-30 11:03 ` Bernhard Reutner-Fischer
2009-09-10 23:57 ` H Hartley Sweeten
2009-09-11 10:34 ` Bernhard Reutner-Fischer
2009-09-11 22:04 ` H Hartley Sweeten
2009-09-12 6:02 ` Peter Korsgaard
2009-08-20 0:30 ` H Hartley Sweeten
2009-08-19 22:13 ` Daniel Mack [this message]
2009-08-19 22:19 ` H Hartley Sweeten
2009-08-20 8:56 ` Daniel Mack
-- strict thread matches above, loose matches on Subject: below --
2011-11-22 20:51 [Buildroot] equivalent of a 'make modules' Jeff Krasky
2011-12-01 22:56 ` [Buildroot] LIBFOO_SITE in .mk file Jeff Krasky
2011-12-02 7:50 ` Thomas De Schampheleire
2011-12-02 13:33 ` Michael S. Zick
2011-12-02 15:57 ` Jeff Krasky
2011-12-02 16:09 ` Quotient Remainder
2011-12-02 16:51 ` [Buildroot] Kernel panic - not syncing: Attempted to kill init! Jeff Krasky
2011-12-02 16:59 ` Jeff Krasky
2011-12-02 17:33 ` Tim Judd
2011-12-02 18:02 ` Jeff Krasky
2011-12-02 18:21 ` Aleksander Dutkowski
2011-12-02 18:30 ` Jeff Krasky
2011-12-03 0:25 ` Aleksander Dutkowski
2011-12-02 18:31 ` Tim Judd
2011-12-02 18:24 ` Tim Judd
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=20090819221342.GB19257@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--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