linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* RE: File system problem
@ 2008-01-03 23:57 Jean-Samuel Chenard
  2008-01-04 11:57 ` mojtaba
  0 siblings, 1 reply; 8+ messages in thread
From: Jean-Samuel Chenard @ 2008-01-03 23:57 UTC (permalink / raw)
  To: linuxppc-embedded, kernelppc

> Message: 9
> Date: Thu, 3 Jan 2008 18:00:14 +0100
> From: "mojtaba"
>
> Actually, I removed the console and null created by buildroot and create
> them manually using make node. This time the system freezes at this point=
.
> "Freeing unused kernel memory: 76k init"

Hi Mojtaba,

I just want to comment on your observation that the file size in /dev
was zero.  This is normal as the device files are 'special' since they
are a mean of abstracting the interface to the kernel.  I had to read
the online book listed below before I could understand the inner
workings of those special files.  If you plan on interfacing your FPGA
with the Linux Kernel, I suggest you read it too, as it is a very
insightful book:
http://lwn.net/Kernel/LDD3/

At this point, your system is not frozen, but your init script and
configuration files are probably not all correctly set.  You might
need to read some documentation about buildroot to see what its init
scripts are trying to do.

You might be missing a library or symlink (I got that problem in my
attempt to build the BusyBox root filesystem from scratch).  One way
to go at the problem is to pass the init=3D/bin/ash or something like
that to your kernel at the boot prompt (you could even make some
trivial 'hello world' program and pass it to the kernel as the init
process).  This way, you can dive right into a shell or your program
and avoid init and its configuration.

After some copying of required libraries in /lib (I'm using uClibc)
and the creation of the required symbolic links, I got my Busybox root
filesystem working on my ML-310 board.

Good luck!

Regards,

Jean-Samuel
--=20
Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montr=E9al, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

^ permalink raw reply	[flat|nested] 8+ messages in thread
* RE: File system problem
@ 2008-01-03  3:32 Jean-Samuel Chenard
  2008-01-03 15:57 ` mojtaba
  2008-01-03 17:00 ` mojtaba
  0 siblings, 2 replies; 8+ messages in thread
From: Jean-Samuel Chenard @ 2008-01-03  3:32 UTC (permalink / raw)
  To: linuxppc-embedded, kernelppc

> 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 26-12-2=
007
> 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.

Regards,

Jean-Samuel
--=20
Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montr=E9al, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

^ permalink raw reply	[flat|nested] 8+ messages in thread
* File system problem
@ 2008-01-02 18:50 mojtaba
  0 siblings, 0 replies; 8+ messages in thread
From: mojtaba @ 2008-01-02 18:50 UTC (permalink / raw)
  To: Linuxppc-embedded

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-2007
snapshot of buildroot.

This is what I get on terminal:

loaded at:     00400000 004CE1A0                                
board data at: 004CC120 004CC19C                                
relocated to:  0040405C 004040D8                                
zimage at:     00404E94 004CB08A                                
avail ram:     004CF000 10000000                                

Linux/PPC load: console=ttyS0,9600 root=/dev/xsa2 init=/bin/sh

Uncompressing Linux...done.                           
Now booting the kernel                      
Linux version 2.6.24-rc3 (mojtaba@ubuntu2) (gcc version 4.2.2) #1 Wed Jan 2
14:3

7:58 CET 2008             
Xilinx ML300 Reference System (Virtex-II Pro)

Zone PFN ranges:                
  DMA             0 ->    65536                               
  Normal      65536 ->    65536                               
  HighMem     655                
Movable zone start PFN for each node                                    
early_node_map[1] active PFN ranges                                   
    0:        0 ->    65536                           
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024

Kernel command line: console=ttyS0,9600 root=/dev/xsa2 init=/bin/sh

Xilinx INTC #0 at 0x41200000 mapped to 0xEF5FE000

PID hash table entries: 1024 (order: 10, 4096 bytes)

Console: colour dummy device 80x25                                  
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

Memory: 258048k available (1288k kernel code, 436k data, 76k init, 0k
highmem)

Mount-cache hash table entries: 512                                   
net_namespace: 64 bytes                       
NET: Registered protocol family 16                                  
sysctl table check failed: /kernel/l2cr .1.31 Missing strategy

Call Trace:           
[cfc1fe20] [c0008148] show_stack+0x58/0x188 (unreliable)

[cfc1fe68] [c0038908] set_fail+0x50/0x68

[cfc1fe80] [c0038f7c] sysctl_check_table+0x65c/0x6ac

[cfc1fee8] [c0038f8c] sysctl_check_table+0x66c/0x6ac

[cfc1ff50] [c0026c58] register_sysctl_table+0x64/0xb4

[cfc1ff68] [c019ed4c] register_ppc_htab_sysctl+0x18/0x2c
[cfc1ff70] [c019b228] kernel_init+0x104/0x290 [cfc1fff0] [c0004af8]
kernel_thread+0x44/0x60 io scheduler noop registered io scheduler
anticipatory registered io scheduler deadline registered io scheduler cfq
registered (default) Generic RTC Driver v1.07 Macintosh non-volatile memory
driver v1.1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x40401003 (irq = 2) is a 16550A console [ttyS0]
enabled xsysace xsysace.0: Xilinx SystemACE revision 1.0.12 xsysace
xsysace.0: capacity: 1981728 sectors
 xsa: xsa1 xsa2 xsa3
Xilinx SystemACE device driver, major=254
i8042.c: No controller found.
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.
init has generated signal 11 but has no handler for it Kernel panic - not
syncing: Attempted to kill init!
Rebooting in 180 seconds..


Regards,
Mojtaba

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2008-01-04 11:56 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-03 23:57 File system problem Jean-Samuel Chenard
2008-01-04 11:57 ` mojtaba
  -- strict thread matches above, loose matches on Subject: below --
2008-01-03  3:32 Jean-Samuel Chenard
2008-01-03 15:57 ` mojtaba
2008-01-03 17:27   ` Grant Likely
2008-01-03 17:00 ` mojtaba
2008-01-03 17:33   ` Grant Likely
2008-01-02 18:50 mojtaba

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).