Still some boot problem

Adam Lackorzynski adam at os.inf.tu-dresden.de
Tue Jun 14 12:10:17 CEST 2005


On Tue Jun 14, 2005 at 11:44:45 +0200, fabs0028 at free.fr wrote:
> 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.

What do you use for output? DOpE, l4con or textmode? Looks like you have
neither l4con nor dope running, and no VGA support either so that
their's no output available.
Another possibility is to use the l4ser serial stub driver, and supply
console=ttyLv0 on the kernel command line. Then there should be the
normal kernel boot up output.

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

If it's in l4x_blink, it (probably) has panic'ed. Backtrace in jdb can
be done with the 'bt' command.




Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/




More information about the l4-hackers mailing list