In august, I tested L4Linux on PC, and everything was working fine with L4Linux-2.6.17. Now, I get the snapshots of 20061116, and rebuild everything. The L4Linux kernel is now 2.6.18. The build is ok, but I can't start it under Fiasco.
Here is the log :
Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Sat Nov 11 18:26:23 2006 compiled with gcc 3.4.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off
Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:4:9:0) Model: Pentium 4E (Prescott/Nocona) at 2793 MHz
64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 16 KB L1 D Cache (8-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line)
Freeing init code/data: 20480 bytes (5 pages)
SIGMA0: Hello! ... ... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled!
Of course, I have the exception_ipc feature enabled in Fiasco !!!
If I rebuild L4Linux-2.6.17, with the L4Env from 20061116, and try to start it under Fiasco, there is no problem ...
On Fri Dec 01, 2006 at 17:55:47 +0100, FERANDELLE Pascal wrote:
In august, I tested L4Linux on PC, and everything was working fine with L4Linux-2.6.17. Now, I get the snapshots of 20061116, and rebuild everything. The L4Linux kernel is now 2.6.18. The build is ok, but I can't start it under Fiasco.
Here is the log :
Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Sat Nov 11 18:26:23 2006 compiled with gcc 3.4.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off
Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:4:9:0) Model: Pentium 4E (Prescott/Nocona) at 2793 MHz
64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 16 KB L1 D Cache (8-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line)
Freeing init code/data: 20480 bytes (5 pages)
SIGMA0: Hello! ... ... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled!
Of course, I have the exception_ipc feature enabled in Fiasco !!!
By any chance, do you have CONFIG_REGPARM enabled? Disable it. (I recently added a check for that config option...)
Adam
... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled!
Of course, I have the exception_ipc feature enabled in Fiasco !!!
By any chance, do you have CONFIG_REGPARM enabled? Disable it. (I recently added a check for that config option...)
I disable it, in both Fiasco and L4Linux, and now L4Linux is starting. But, it panics ... Here is the end of the log on the serial line :
... Kernel command line: earlyprintk=yes mem=64M load_ramdisk=1 ramdisk_size=16384 r oot=/dev/ram l4env_rd=test-rd.rd Initializing CPU#0 l4lx_irq_init: l4lx_irq_max = 18 PID hash table entries: 512 (order: 9, 2048 bytes) l4lx_irq_timer_startup(0) l4lx | l4lx_thread_create: Created thread 0e.05 (timer.i0) timer_irq_thread: Starting timer IRQ thread. disabling early console l4lx | l4lx_thread_create: Created thread 0e.06 (Idler) l4lx | Starting L4FB via CON con | vc_loop(): vc[1] running as B.07 l4lx | l4lx_thread_create: Created thread 0e.07 (L4ConInput) con | vc_open_out(): vc[1] 1024x768@16, gmode:0x35 l4lx | l4fbcon: 1024x750 2bypp, size: 1540096 l4lx | l4lx_thread_create: Created thread 0e.08 (CON refresher) l4lx | l4lx_thread_create: Created thread 0e.09 (IRQ8) l4lx | panic: going to sleep forever, bye
and on my graphical console :
... EFLAGS : 00013202 (2.6.18-l4 #3) EIP is at flush_kernel_map+0x9/0x10 Call Trace : Global_flush_tlb agp_backend_initialize pci_enable_device agp_add_bridge __pci_device_probe driver_probe_device agp_intel_init do_initcalls register_irq_proc do_quotactl init_irq_proc init kernel_thread_start ret_kernel_thread_start Code : EIP : [<00411c09>] flush_kernel_map+0x9/0x10 SS :ESP 0023 :0080de44 Kernel panic not syncing : Attempted to kill init !
On Mon Dec 04, 2006 at 16:14:17 +0100, FERANDELLE Pascal wrote:
... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled!
Of course, I have the exception_ipc feature enabled in Fiasco !!!
By any chance, do you have CONFIG_REGPARM enabled? Disable it. (I recently added a check for that config option...)
I disable it, in both Fiasco and L4Linux, and now L4Linux is starting. But, it panics ... Here is the end of the log on the serial line :
... Kernel command line: earlyprintk=yes mem=64M load_ramdisk=1 ramdisk_size=16384 r oot=/dev/ram l4env_rd=test-rd.rd Initializing CPU#0 l4lx_irq_init: l4lx_irq_max = 18 PID hash table entries: 512 (order: 9, 2048 bytes) l4lx_irq_timer_startup(0) l4lx | l4lx_thread_create: Created thread 0e.05 (timer.i0) timer_irq_thread: Starting timer IRQ thread. disabling early console l4lx | l4lx_thread_create: Created thread 0e.06 (Idler) l4lx | Starting L4FB via CON con | vc_loop(): vc[1] running as B.07 l4lx | l4lx_thread_create: Created thread 0e.07 (L4ConInput) con | vc_open_out(): vc[1] 1024x768@16, gmode:0x35 l4lx | l4fbcon: 1024x750 2bypp, size: 1540096 l4lx | l4lx_thread_create: Created thread 0e.08 (CON refresher) l4lx | l4lx_thread_create: Created thread 0e.09 (IRQ8) l4lx | panic: going to sleep forever, bye
and on my graphical console :
... EFLAGS : 00013202 (2.6.18-l4 #3) EIP is at flush_kernel_map+0x9/0x10 Call Trace : Global_flush_tlb agp_backend_initialize pci_enable_device agp_add_bridge
Do not enable AGP, I think that's the culprit.
Adam
l4-hackers@os.inf.tu-dresden.de