Harald Fritzsche Harald.Fritzsche@mpd.de writes:
I found (i hope so) the reason for the kbd: sig_sched: invalid ext_preempter in L4-Linux, reported earlier.
In file : linux/arch/l4-i386/lib/task.c in function: start_linux_server_thread() is used the variable l4_threadid_t foo_id uninitialized. I set foo_id to L4_INVALID_ID and the sig_sched disappears. But i don't if this is intended from the authors.
Your fix is correct.
The problem occurred because I forgot to commit some patches before taking the snapshot. I've appended the patches (which include your fix) below.
[ from a different message: ]
The function rs_init() hangs during boot (the boot stops for ever). Or a function after this part of initialization. The last what i see is: tty0* ... is a 16550A.
If i disable the serial interface the boot goes on up to VFS mount and stops than.
This might be because the kernel debugger stub grabs irq 3 (the interrupt for COM2). Maybe Linux' serial driver waits for an interrupt that never arrives because L4Linux cannot attach to irq3.
Configuring out the serial driver is the correct solution when using a remote Gdb attached via a serial line. If you don't have a remote Gdb, try booting with the "-nokdb" kernel option and see if the problem goes away.
Michael
Dear Michael, Hello Hackers,
i have applied Michaels patch and fortunatly the message <KERNEL: no page fault handler ...> does never occur.
L4Linux boots now.
Thanks so far and congratulation for such a system (Linux on Fiasco).
startx or something else (xdm,kdm,X,...) scrambles the screen and blocks the keyboard. I assume that this is causes by the disabled serial interface and related IRQ's (i have configured out serial interface)?
Michael Hohmuth schrieb:
The function rs_init() hangs during boot (the boot stops for ever). Or a function after this part of initialization. The last what i see is: tty0* ... is a 16550A.
If i disable the serial interface the boot goes on up to VFS mount and stops than.
This might be because the kernel debugger stub grabs irq 3 (the interrupt for COM2). Maybe Linux' serial driver waits for an interrupt that never arrives because L4Linux cannot attach to irq3.
Configuring out the serial driver is the correct solution when using a remote Gdb attached via a serial line. If you don't have a remote Gdb, try booting with the "-nokdb" kernel option and see if the problem goes away.
Give me time to test your hints, but this evening i am visitingWagners Tannhaeuser in the Dresdner Semper Oper.
Michael
Thanks again and Best regards Harald Fritzsche
l4-hackers@os.inf.tu-dresden.de