Still some boot problem

[fabs0028 at free.fr]

Hello
well my system is not far from being ready but i have another problem once more.
L4linux boots, it prints his messages and then it hangs and never go further,
here is the messages :



l4lx    | ======> L4Linux 2.6 starting... <========
l4lx    | Binary name: vmlinuz26
l4lx    | Kernel command line (3 args): ro root=/dev/VolGroup00/LogVol00 rhgb
l4lx    | My DMphys is at 07.00
l4lx    | My region mapper is at 0c.00
l4lx    | My code starts at 0x003ff000 and ends at 0x006d71a8 [2912 KiB].
l4lx    | Semaphore thread ID: 0c.01
l4lx    | Areas:
l4lx    | Text:     003ff000 - 005fc000 [2036kB] (a bit longer)
l4lx    | Data:     005fc000 - 0063d580 [261kB]
l4lx    | Initdata: 00640000 - 0066a000 [168kB]
l4lx    | BSS:      0066a008 - 006d71a8 [436kB]
l4lx    | l4lx_thread_create: Created thread 0c.03 (CLI SEM thread)
l4lx    | Using tamed mode.
l4lx    | l4lx_thread_create: Created thread 0c.04 (Linux server)
l4lx    | main thread will be 0c.04
l4lx    | l4env_register_pointer_section: addr = 3ff000 size = 2539520
l4lx    | with-init: virt: 0x003ff000 to 0x0066afff [2480 KiB]
l4lx    | Noncontinuous region for with-init
l4lx    | with-init: Number of physical regions: 4, 2539520 Bytes
l4lx    | with-init: 1: Phys: 0x01134000 to 0x011a7000, Size:  6061788
l4lx    | with-init: 2: Phys: 0x01417000 to 0x01500000, Size:  6061788
l4lx    | l4env_linux_startup thread 4.
l4lx    | with-init: 3: Phys: 0x01339000 to 0x01400000, Size:  6061788
l4lx    | with-init: 4: Phys: 0x012b7000 to 0x01300000, Size:  6061788
l4lx    | main thread: received startup message.
l4lx    | Main memory size: 32MB
l4lx    | Main thread running, waiting...
l4lx    | Mainmem DS id: 44
l4lx    | mainmem: virt: 0x006d8000 to 0x026d7fff [32768 KiB]
l4lx    | mainmem: Number of physical regions: 1, 33554432 Bytes
l4lx    | mainmem: 1: Phys: 0x030f0000 to 0x050f0000, Size:  6061522
l4lx    | Filling lower ptabs...
l4lx    | Done (886 entries).
l4lx    | l4x_setup_ti_thread_stack: ti = 0x905fe000
l4lx    | l4lx_thread_create: Created thread 0c.05 (IRQ0 (Timer))
l4lx    | DOpE is not registered at names!
l4lx    | l4x_setup_ti_thread_stack: ti = 0x906fe000
l4lx    | l4lx_thread_create: Created thread 0c.06 (IRQ17)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x907fe000
l4lx    | l4lx_thread_create: Created thread 0c.07 (IRQ16)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x908fe000
l4lx    | l4lx_thread_create: Created thread 0c.08 (IRQ15)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x909fe000
l4lx    | l4lx_thread_create: Created thread 0c.09 (IRQ14)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x90afe000
l4lx    | l4lx_thread_create: Created thread 0c.0a (IRQ13)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x90bfe000
l4lx    | l4lx_thread_create: Created thread 0c.0b (IRQ12)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x90cfe000
l4lx    | l4lx_thread_create: Created thread 0c.0c (IRQ11)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x90dfe000
l4lx    | l4lx_thread_create: Created thread 0c.0d (IRQ10)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x90efe000
l4lx    | l4lx_thread_create: Created thread 0c.0e (IRQ9)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x90ffe000
l4lx    | l4lx_thread_create: Created thread 0c.0f (IRQ8)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x910fe000
l4lx    | l4lx_thread_create: Created thread 0c.10 (IRQ7)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x911fe000
l4lx    | l4lx_thread_create: Created thread 0c.11 (IRQ6)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x912fe000
l4lx    | l4lx_thread_create: Created thread 0c.12 (IRQ5)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x913fe000
l4lx    | l4lx_thread_create: Created thread 0c.13 (IRQ3)
l4lx    | l4x_setup_ti_thread_stack: ti = 0x914fe000
l4lx    | l4lx_thread_create: Created thread 0c.14 (IRQ1)


and then nothing happens.

i feel a bit lost.

there is something else, the kernel calls printk but nothing appears on screen,
maybe it is just because the messages are not supposed to be printed but i
think it is weird.

It seems that the linux server has gone in l4x_blink and sleeps forever but i
can't find out where it come from (Is it possible to follow the execution with
jdb ?)

Thanx a lot for your help.

Fabien Chaillou