From: Grant Likely <grant.likely@secretlab.ca>
To: buildroot@busybox.net
Subject: [Buildroot] Filesystem problem
Date: Wed, 2 Jan 2008 11:54:55 -0700 [thread overview]
Message-ID: <fa686aa40801021054y64b480d0ldbb80ef2c98e5afa@mail.gmail.com> (raw)
In-Reply-To: <002e01c84d4c$11ff0cc0$35fd2640$@com>
On 1/2/08, mojtaba <kernelppc@gmail.com> wrote:
> Dear all,
>
> I am trying to boot a root file system build by buildroot. But I got this
> error" init has generated signal 11 but has no handler for it".
>
> My kernel version is 2.6.24-rc3
> My target system is PPC 405 (XILINX VIRTEX II pro)
> I am using the 26-12 snapshot of buildroot
>
<snip>
>
> mice: PS/2 mouse device common for all mice
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 76k init
> Warning: unable to open an initial console.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You probably don't have /dev/console in your root filesystem.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2008-01-02 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 14:30 [Buildroot] Filesystem problem mojtaba
2008-01-02 18:54 ` Grant Likely [this message]
2008-01-04 17:57 ` mojtaba
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=fa686aa40801021054y64b480d0ldbb80ef2c98e5afa@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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