From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: i.MX35 Kernel without ARM EABI support cannot execute init
Date: Sat, 22 Aug 2009 00:07:55 +0530 [thread overview]
Message-ID: <20090821183754.GA3017@debian> (raw)
In-Reply-To: <1250865435.17931.20.camel@wks02-lin.nanotronic.local>
On Fri, Aug 21, 2009 at 04:37:15PM +0200, hoefle marco wrote:
> When trying to boot the i.MX35 Kernel (with ARM EABI or without, the
> kernel panic remains exactly the same) using the emdebian rootfs I get
> this:
>
> Kernel panic - not syncing: Attempted to kill init!
If you build your kernel with CONFIG_DEBUG_USER=y and pass in
"user_debug=31" on your kernel command line, you'll get some info on why
init is being killed.
Rabin
next prev parent reply other threads:[~2009-08-21 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 14:37 i.MX35 Kernel without ARM EABI support cannot execute init hoefle marco
2009-08-21 16:12 ` Hector Oron
2009-08-21 15:32 ` Bill Gatliff
2009-08-21 16:57 ` H Hartley Sweeten
2009-08-21 18:37 ` Rabin Vincent [this message]
2009-08-24 10:17 ` Robert Schwebel
2009-08-24 10:53 ` hoefle marco
2009-08-24 10:57 ` Robert Schwebel
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 9:59 hoefle marco
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=20090821183754.GA3017@debian \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).