File system problem

mojtaba kernelppc at
Fri Jan 4 02:57:30 EST 2008

Thank you very much for your answers.

But I have both console and null in /dev.

-rw-rw-rw- 1 mojtaba mojtaba    0 2007-12-26 15:50 console
-rw-rw-rw- 1 mojtaba mojtaba    0 2007-12-26 15:50 null

They have been created by buildroot. Do I need to create them manually?
Actually the size of both of them is 0 and both are empty files. Is that a

Thank you in advance and best regards,

-----Original Message-----
From: jsamch at [mailto:jsamch at] On Behalf Of Jean-Samuel
Sent: Thursday, January 03, 2008 4:33 AM
To: linuxppc-embedded at; kernelppc at
Subject: RE: File system problem

> Date: Wed, 2 Jan 2008 19:50:13 +0100
> From: "mojtaba"
> 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
> snapshot of buildroot.
[ ... ]
> Warning: unable to open an initial console.
> init has generated signal 11 but has no handler for it Kernel panic - not

Hi Mojtaba,

I got a similar error on my ML-310 when I tried a new root filesystem.
 As far as I recall, I needed to make sure that two entries existed in
/dev, namely:

crw-------    1 root     root       5,   1 Jan  1 05:18 console
crw-rw----    1 root     root       1,   3 Dec 10  2007 null

I think that you are missing /dev/console and then init cannot run
since it has nowhere to put its standard output.

You can make those by mounting your CF card on your development host
and (as root) make the nodes:

# mknod -m 660 /dev/console c 5 1
# mknod -m 660 /dev/null c 1 3

In my case, I use the UartLite (ttyUL0) serial port driver, but I'm
pretty sure this is going to fix the problem you are observing.


Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montréal, QC, CANADA
Web Page:

More information about the Linuxppc-embedded mailing list