From: Paulo Marques <pmarques@grupopie.com>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.8-rc4 "Kernel panic: Attempted to kill init!" - after replacing /fadsroot on the Linux NFSserver with the one from Arabella cdr om
Date: Wed, 29 Sep 2004 11:46:14 +0100 [thread overview]
Message-ID: <415A9276.4060009@grupopie.com> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF0A6471D6@whq-msgusr-02.pit.comms.marconi.com>
Povolotsky, Alexander wrote:
> Hi,
>
> I have built (cross-compiled for ppc 82xx) Linux 2.6.8-rc4 kernel and am
> trying to boot it on PQ2FADS-VR
>
>
>>I am getting: "Kernel panic: Attempted to kill init!" - after replacing
>>/fadsroot (with the BusyBox) on the remote Linux NFS server with the newer
>>one from the new version of the Arabella cdrom.
>
> Is it software or hardware (bad memory ?) issue ?
This seems to be more userspace related than kernel related, so this is
probably the wrong mailing list. Anyway, check that:
- busybox is statically linked or that you have the necessary
libraries in the library path. (you can check this with "ldd busybox")
- busybox is marked executable
- busybox is compiled for the right processor
- check that the init= parameter points to the right executable
- if you have another ppc machine, try a "chroot <dir> busybox" and
see if it executes or why it doesn't
I hope this helps,
--
Paulo Marques - www.grupopie.com
To err is human, but to really foul things up requires a computer.
Farmers' Almanac, 1978
prev parent reply other threads:[~2004-09-29 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 20:20 Linux 2.6.8-rc4 "Kernel panic: Attempted to kill init!" - after replacing /fadsroot on the Linux NFSserver with the one from Arabella cdr om Povolotsky, Alexander
2004-09-29 10:46 ` Paulo Marques [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=415A9276.4060009@grupopie.com \
--to=pmarques@grupopie.com \
--cc=Alexander.Povolotsky@marconi.com \
--cc=linux-kernel@vger.kernel.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