- l4-hackers - example.com Site

Fiasco reserved memory area overlapping with bootloader area
by Christian Prochaska 14 Feb '10

14 Feb '10

Hello, I recently had the problem that a physical memory area reserved for Fiasco overlapped with a Bootloader area, resulting in one or possibly more corrupted boot modules. Apparently there was not enough physical memory available, but i would suggest that in this case Fiasco would print an error message and stop as soon as it knows about the overlap instead of further executing the corrupted modules. Christian [src] (17.00) jdb: kf KIP @ 0xf0001000 magic: L4�K version: 0x87004444 clock: 0000000000623d7c (6438268) freq_cpu: 2993136kHz freq_bus: 0kHz sigma0_ip: 00103de8 sigma0_sp: 002da720 sigma1_ip: 00000000 sigma1_sp: 00000000 root_ip: 010301dc root_sp: 00000000 Memory (max 30 descriptors): 1:phys [0000000000000000-000000000009fc00] Conventional 2:phys [0000000000100000-0000000003ff0000] Conventional 3:phys [0000000000001000-0000000000065000] Reserved 4:phys [000000000006a000-000000000006a400] Bootloader 5:phys [000000000009fc00-00000000000a0000] Arch 6:phys [00000000000e8000-0000000000100000] Arch 7:phys [0000000000100000-0000000000108400] Dedicated 8:phys [0000000001000000-0000000001065400] Bootloader 9:phys [00000000020de000-0000000003cef800] Bootloader 10:phys [0000000003ff0000-0000000004000000] Arch 11:phys [00000000fffc0000-0000000000000000] Arch 12:virt [0000000000000000-00000000c0000000] Conventional 13:phys [0000000003ad2000-0000000003ff0000] Reserved KIP syscalls via absolute stubs ipc: eacff000 id nearest: eacff100 fpage unmap: eacff200 thread switch: eacff300 thread schedule: eacff400 lthread ex regs: eacff500 task new: eacff600 user_ptr: 0x6a000 vhw_offset: 00000000 vkey_irq: 17 Kernel features: multi_irq exception_ipc segments pagerexregs deceit_bit_disables_switch abiver:9 io_prot utcb kip_syscalls thread_names

2 1

Interrupt problems causing crash of network driver and Kernel panic?
by Andreas Speier 08 Feb '10

08 Feb '10

Hi L4-Hackers, I got problem running L4Linux 2.6.29 on Fiasco with a time critical application (Asterisk). The main hardware components are an embedded board with 1GHz VIA C7 processor, 1GB of RAM and 2 network interface cards (VIA-Rhine, 3Com). The drivers are compiled into the L4Linux kernel. Running this application works fine until some more interrupt intensive process will be started. Then the VoIP communication (SIP) breaks down and I got the following output in /var/log/syslog: ################# Jan 28 08:24:58 TESTPC kernel: ------------[ cut here ]------------ Jan 28 08:24:58 TESTPC kernel: kernel BUG at /home/[...]/l4linux-2.6.29/net/core/dev.c:2625! Jan 28 08:24:58 TESTPC kernel: Trap: 6: 0000 [#1] Jan 28 08:24:58 TESTPC kernel: last sysfs file: Jan 28 08:24:58 TESTPC kernel: Modules linked in: Jan 28 08:24:58 TESTPC kernel: Jan 28 08:24:58 TESTPC kernel: Pid: 872, comm: find Not tainted (2.6.29-l4 #3) Jan 28 08:24:58 TESTPC kernel: EIP: ff04:[<0063c5bf>] EFLAGS: 00010246 CPU: 0 Jan 28 08:24:58 TESTPC kernel: EIP is at __napi_complete+0x2f/0x40 Jan 28 08:24:58 TESTPC kernel: EAX: 0092d45c EBX: 0092d45c ECX: 0092d45c EDX: 008aa40c Jan 28 08:24:58 TESTPC kernel: ESI: 00000001 EDI: 0092d45c EBP: b0afff14 ESP: b0afff0c Jan 28 08:24:58 TESTPC kernel: DS: 4000 ES: 7032 FS: 0023 GS: 0043 SS: 0023 Jan 28 08:24:58 TESTPC kernel: Process find (pid: 872, ti=b0afe000 task=0a5391b0 task.ti=0a564000) Jan 28 08:24:58 TESTPC kernel: Stack: Jan 28 08:24:58 TESTPC kernel: b0afff14 eacff011 b0afff24 0063dd25 0092d444 00000001 b0afff40 00640473 Jan 28 08:24:58 TESTPC kernel: 00000040 000107b2 00000040 00000000 0092d45c b0afff5c 006404ca 000107b4 Jan 28 08:24:58 TESTPC kernel: 0000012c 00000001 0000000c 00000100 b0afff74 0041afe7 0000000a 00000000 Jan 28 08:24:58 TESTPC kernel: Call Trace: Jan 28 08:24:58 TESTPC kernel: [<0063dd25>] ? napi_complete+0x25/0x40 Jan 28 08:24:58 TESTPC kernel: [<00640473>] ? process_backlog+0x93/0xa0 Jan 28 08:24:58 TESTPC kernel: [<006404ca>] ? net_rx_action+0x4a/0x100 Jan 28 08:24:58 TESTPC kernel: [<0041afe7>] ? __do_softirq+0x67/0x100 Jan 28 08:24:58 TESTPC kernel: [<0040bb05>] ? do_softirq+0x55/0x60 Jan 28 08:24:59 TESTPC kernel: [<0041af15>] ? irq_exit+0x35/0x40 Jan 28 08:24:59 TESTPC kernel: [<0040ba75>] ? do_IRQ+0x35/0x70 Jan 28 08:24:59 TESTPC kernel: [<00523ad5>] ? irq_dev_thread+0xf5/0x190 Jan 28 08:24:59 TESTPC kernel: Code: e5 f6 40 08 01 74 24 8b 40 20 85 c0 75 21 8b 11 8b 41 04 89 42 04 89 10 c7 41 04 00 02 20 00 c7 01 00 01 10 00 80 61 08 fe 5d c3 <0f> 0b eb fe 0f 0b eb fe 89 f6 8d bc 27 00 00 00 00 55 ba d0 00 Jan 28 08:24:59 TESTPC kernel: EIP: [<0063c5bf>] __napi_complete+0x2f/0x40 SS:ESP 0023:b0afff0c Jan 28 08:24:59 TESTPC kernel: ---[ end trace 5cee9576d4b98201 ]--- Jan 28 08:24:59 TESTPC kernel: Kernel panic - not syncing: Fatal exception in interrupt Jan 28 08:24:59 TESTPC kernel: panic: going to sleep forever, bye Jan 28 08:25:07 TESTPC kernel: ------------[ cut here ]------------ Jan 28 08:25:07 TESTPC kernel: WARNING: at /home/[...]/l4linux-2.6.29/net/sched/sch_generic.c:226 dev_watchdog+0x18e/0x1a0() Jan 28 08:25:07 TESTPC kernel: NETDEV WATCHDOG: eth0 (3c59x): transmit timed out Jan 28 08:25:07 TESTPC kernel: Modules linked in: Jan 28 08:25:07 TESTPC kernel: Pid: 0, comm: swapper Tainted: G D 2.6.29-l4 #3 Jan 28 08:25:07 TESTPC kernel: Call Trace: Jan 28 08:25:07 TESTPC kernel: [<00416bc6>] warn_slowpath+0x76/0x90 Jan 28 08:25:07 TESTPC kernel: [<006a0030>] ? xfrm4_mode_tunnel_output+0x50/0xf0 Jan 28 08:25:07 TESTPC kernel: [<004114fe>] ? __enqueue_entity+0x8e/0xb0 Jan 28 08:25:07 TESTPC kernel: [<0041156e>] ? enqueue_entity+0x4e/0x90 Jan 28 08:25:07 TESTPC kernel: [<00411500>] ? __enqueue_entity+0x90/0xb0 Jan 28 08:25:07 TESTPC kernel: [<0040242c>] ? l4x_global_restore_flags+0xc/0x40 Jan 28 08:25:07 TESTPC kernel: [<0041167f>] ? try_to_wake_up+0x8f/0xc0 Jan 28 08:25:07 TESTPC kernel: [<004116bb>] ? default_wake_function+0xb/0x10 Jan 28 08:25:07 TESTPC kernel: [<004273d1>] ? autoremove_wake_function+0x11/0x40 Jan 28 08:25:07 TESTPC kernel: [<0051f537>] ? strlcpy+0x17/0x50 Jan 28 08:25:07 TESTPC kernel: [<0064c1be>] dev_watchdog+0x18e/0x1a0 Jan 28 08:25:07 TESTPC kernel: [<00410078>] ? requeue_task_rt+0x18/0x90 Jan 28 08:25:07 TESTPC kernel: [<00402455>] ? l4x_global_restore_flags+0x35/0x40 Jan 28 08:25:07 TESTPC kernel: [<00424828>] ? __queue_work+0x38/0x40 Jan 28 08:25:07 TESTPC kernel: [<0041e50d>] run_timer_softirq+0x11d/0x170 Jan 28 08:25:07 TESTPC kernel: [<0064c030>] ? dev_watchdog+0x0/0x1a0 Jan 28 08:25:07 TESTPC kernel: [<0041afe7>] __do_softirq+0x67/0x100 Jan 28 08:25:07 TESTPC kernel: [<0040bb05>] do_softirq+0x55/0x60 Jan 28 08:25:07 TESTPC kernel: [<0041af15>] irq_exit+0x35/0x40 Jan 28 08:25:07 TESTPC kernel: [<0040ba75>] do_IRQ+0x35/0x70 Jan 28 08:25:07 TESTPC kernel: [<00523ef3>] timer_irq_thread+0x123/0x1a0 Jan 28 08:25:07 TESTPC kernel: ---[ end trace 5cee9576d4b98202 ]--- Jan 28 08:25:07 TESTPC kernel: eth0: transmit timed out, tx_status 00 status e681. Jan 28 08:25:07 TESTPC kernel: diagnostics: net 0cd2 media 8880 dma 0000003a fifo 8000 Jan 28 08:25:07 TESTPC kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Jan 28 08:25:07 TESTPC kernel: Flags; bus-master 1, dirty 612(4) current 612(4) Jan 28 08:25:07 TESTPC kernel: Transmit list 00000000 vs. 0ae83480. Jan 28 08:25:07 TESTPC kernel: 0: @0ae83200 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 1: @0ae832a0 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 2: @0ae83340 length 80000057 status 8c010057 Jan 28 08:25:07 TESTPC kernel: 3: @0ae833e0 length 80000057 status 8c010057 Jan 28 08:25:07 TESTPC kernel: 4: @0ae83480 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 5: @0ae83520 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 6: @0ae835c0 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 7: @0ae83660 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 8: @0ae83700 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 9: @0ae837a0 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 10: @0ae83840 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 11: @0ae838e0 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 12: @0ae83980 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 13: @0ae83a20 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 14: @0ae83ac0 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: 15: @0ae83b60 length 80000057 status 0c010057 Jan 28 08:25:07 TESTPC kernel: eth0: Resetting the Tx ring pointer. Jan 28 08:25:17 TESTPC kernel: eth0: transmit timed out, tx_status 00 status e681. Jan 28 08:25:17 TESTPC kernel: diagnostics: net 0cd2 media 8880 dma 0000003a fifo 8000 Jan 28 08:25:17 TESTPC kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Jan 28 08:25:17 TESTPC kernel: Flags; bus-master 1, dirty 628(4) current 628(4) Jan 28 08:25:17 TESTPC kernel: Transmit list 00000000 vs. 0ae83480. Jan 28 08:25:17 TESTPC kernel: 0: @0ae83200 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 1: @0ae832a0 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 2: @0ae83340 length 80000057 status 8c010057 Jan 28 08:25:17 TESTPC kernel: 3: @0ae833e0 length 80000057 status 8c010057 Jan 28 08:25:17 TESTPC kernel: 4: @0ae83480 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 5: @0ae83520 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 6: @0ae835c0 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 7: @0ae83660 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 8: @0ae83700 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 9: @0ae837a0 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 10: @0ae83840 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 11: @0ae838e0 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 12: @0ae83980 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 13: @0ae83a20 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 14: @0ae83ac0 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: 15: @0ae83b60 length 80000057 status 0c010057 Jan 28 08:25:17 TESTPC kernel: eth0: Resetting the Tx ring pointer. Jan 28 08:25:27 TESTPC kernel: eth0: transmit timed out, tx_status 00 status e681. Jan 28 08:25:27 TESTPC kernel: diagnostics: net 0cd2 media 8880 dma 0000003a fifo 8000 Jan 28 08:25:27 TESTPC kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Jan 28 08:25:27 TESTPC kernel: Flags; bus-master 1, dirty 644(4) current 644(4) Jan 28 08:25:27 TESTPC kernel: Transmit list 00000000 vs. 0ae83480. Jan 28 08:25:27 TESTPC kernel: 0: @0ae83200 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 1: @0ae832a0 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 2: @0ae83340 length 80000057 status 8c010057 Jan 28 08:25:27 TESTPC kernel: 3: @0ae833e0 length 80000057 status 8c010057 Jan 28 08:25:27 TESTPC kernel: 4: @0ae83480 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 5: @0ae83520 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 6: @0ae835c0 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 7: @0ae83660 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 8: @0ae83700 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 9: @0ae837a0 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 10: @0ae83840 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 11: @0ae838e0 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 12: @0ae83980 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 13: @0ae83a20 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 14: @0ae83ac0 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: 15: @0ae83b60 length 80000057 status 0c010057 Jan 28 08:25:27 TESTPC kernel: eth0: Resetting the Tx ring pointer. Jan 28 08:25:37 TESTPC kernel: eth0: transmit timed out, tx_status 00 status e681. Jan 28 08:25:37 TESTPC kernel: diagnostics: net 0cd2 media 8880 dma 0000003a fifo 8000 Jan 28 08:25:37 TESTPC kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Jan 28 08:25:37 TESTPC kernel: Flags; bus-master 1, dirty 660(4) current 660(4) Jan 28 08:25:37 TESTPC kernel: Transmit list 00000000 vs. 0ae83480. Jan 28 08:25:37 TESTPC kernel: 0: @0ae83200 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 1: @0ae832a0 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 2: @0ae83340 length 80000057 status 8c010057 Jan 28 08:25:37 TESTPC kernel: 3: @0ae833e0 length 80000057 status 8c010057 Jan 28 08:25:37 TESTPC kernel: 4: @0ae83480 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 5: @0ae83520 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 6: @0ae835c0 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 7: @0ae83660 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 8: @0ae83700 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 9: @0ae837a0 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 10: @0ae83840 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 11: @0ae838e0 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 12: @0ae83980 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 13: @0ae83a20 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 14: @0ae83ac0 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: 15: @0ae83b60 length 80000057 status 0c010057 Jan 28 08:25:37 TESTPC kernel: eth0: Resetting the Tx ring pointer. Jan 28 08:25:47 TESTPC kernel: eth0: transmit timed out, tx_status 00 status e681. Jan 28 08:25:47 TESTPC kernel: diagnostics: net 0cd2 media 8880 dma 0000003a fifo 8000 Jan 28 08:25:47 TESTPC kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Jan 28 08:25:47 TESTPC kernel: Flags; bus-master 1, dirty 676(4) current 676(4) Jan 28 08:25:47 TESTPC kernel: Transmit list 00000000 vs. 0ae83480. Jan 28 08:25:47 TESTPC kernel: 0: @0ae83200 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 1: @0ae832a0 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 2: @0ae83340 length 80000057 status 8c010057 Jan 28 08:25:47 TESTPC kernel: 3: @0ae833e0 length 80000057 status 8c010057 Jan 28 08:25:47 TESTPC kernel: 4: @0ae83480 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 5: @0ae83520 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 6: @0ae835c0 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 7: @0ae83660 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 8: @0ae83700 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 9: @0ae837a0 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 10: @0ae83840 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 11: @0ae838e0 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 12: @0ae83980 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 13: @0ae83a20 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 14: @0ae83ac0 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: 15: @0ae83b60 length 80000057 status 0c010057 Jan 28 08:25:47 TESTPC kernel: eth0: Resetting the Tx ring pointer. Jan 28 08:25:56 TESTPC kernel: eth0: transmit timed out, tx_status 00 status e681. Jan 28 08:25:56 TESTPC kernel: diagnostics: net 0cd2 media 8880 dma 0000003a fifo 8000 Jan 28 08:25:56 TESTPC kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Jan 28 08:25:56 TESTPC kernel: Flags; bus-master 1, dirty 692(4) current 692(4) Jan 28 08:25:56 TESTPC kernel: Transmit list 00000000 vs. 0ae83480. Jan 28 08:25:56 TESTPC kernel: 0: @0ae83200 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 1: @0ae832a0 length 8000002a status 0001002a Jan 28 08:25:56 TESTPC kernel: 2: @0ae83340 length 8000006a status 8c01006a Jan 28 08:25:56 TESTPC kernel: 3: @0ae833e0 length 80000057 status 8c010057 Jan 28 08:25:56 TESTPC kernel: 4: @0ae83480 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 5: @0ae83520 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 6: @0ae835c0 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 7: @0ae83660 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 8: @0ae83700 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 9: @0ae837a0 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 10: @0ae83840 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 11: @0ae838e0 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 12: @0ae83980 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 13: @0ae83a20 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 14: @0ae83ac0 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: 15: @0ae83b60 length 80000057 status 0c010057 Jan 28 08:25:56 TESTPC kernel: eth0: Resetting the Tx ring pointer. ################# I suppose this has something to do with interrupts that cannot be processed in time. Unfortunately I could not find any solution to that. I tested to rise the L4Linux priority, but this could not solve the problem. The configuration files look like the following: menu.lst: -------------------- title L4LX-TEST root (hd0,0) kernel /test/tcb/bootstrap -modaddr 0x02000000 module /test/tcb/fiasco -nokdb -serial_esc module /test/tcb/sigma0 module /test/tcb/roottask -configfile task modname "loader" allow_cli boot_priority 0x95 task modname "bmodfs" attached 4 modules module /test/tcb/roottask.config module /test/tcb/events module /test/tcb/names module /test/tcb/log module /test/tcb/dm_phys --isa=0x800000 -v -e module /test/tcb/simple_ts -t 300 module /test/tcb/rtc -v module /test/tcb/l4io module /test/tcb/l4dope vbeset 0x117 module /test/tcb/bmodfs module /test/tcb/libld-l4.s.so module /test/tcb/libloader.s.so module /test/l4lx/l4lx-net.cfg module /test/l4lx/l4lx-net module /test/tcb/loader --fprov=BMODFS l4lx-net.cfg roottask.config ------------------------- #!roottask task sigma0 boot_priority 0xA0 task roottask boot_priority 0xA0 task modname "rtc" allow_cli task modname "names" boot_priority 0xA0 task modname "dm_phys" boot_priority 0xA0 task modname "simple_ts" boot_priority 0xA0 task modname "l4io" allow_cli boot_priority 0xA0 task modname "loader" allow_cli boot_priority 0xA0 task modname "l4dope" allow_cli boot_priority 0xA0 task modname "bmodfs" boot_priority 0xA0 task modname "events" boot_priority 0xA0 task modname "l4lx-net" boot_priority 0xA0 l4lx-net.cfg ------------------ sleep 0 task "l4lx-net" "mem=160M root=1:0 root=/dev/hda2" allow_cli priority 0xE0 all_sects_writable I hope that someone in this list does have any idea why this error occurs, or some hint I can test to help solving it. Any good idea is welcome! Regards, Andreas

3 3

fiasco - related
by sarita kale 29 Jan '10

29 Jan '10

I have to select one of the micro-kernels for further development. I need answers to following questions to go forward: - What are the limitations/advantages of Fiasco, L4Ka: Pistachio and OKL4. Which one should I select? - Is Fiasco still alive? When I visit Fiasco http://os.inf.tu-dresden.de/fiasco/ site, last updated date is 26 Sep 2005 *Fiasco 1.2 released!* Do we have further releases or is it stopped? - Does anyone have performance figures of Fiasco, L4Ka: Pistachio and OKL4, based on which i can decide which micro-kernel to go for? - Does L4Linux work on OkL4, I read L4Linux runs of L4Ka: Pistachio, will it run as it is or we need to make some changes to it? Thanks Sarita

6 5

DDE Linux26 in the Hurd
by Da Zheng 29 Jan '10

29 Jan '10

Hello, I have managed to port DDE linux26 to the Hurd. At least it works with NIC drivers now. A few problems: 1. dde linux26 doesn't support multiple PCI buses. Unfortunately, my virtual machine has two PCI buses: bus 0 and bus 2. Now I have to hardcode the bus numbers in the code. Do you have plan to support multiple PCI buses? 2. DDE Linux26 doesn't support sound card drivers. Does DDE Linux26 support the block device and character device? Zheng Da

5 20

Call for participation to the Alt-OS devroom at FOSDEM (Extended deadline)
by François Revol 02 Jan '10

02 Jan '10

Hello, This year, the FOSDEM (in Brussels, 6-7th February 2010) will host the "Alt-OS" devroom on sunday from 9:00 to 17:00. This devroom is meant as a place for Free and OpenSource Alternative Operating System projects to share ideas and work on topics like: * distinguishing design and features, * device drivers and how to share them, * sharing code for internal components, * internal usage of other FOSS projects to build upon, * application portability, * interoperability, o file formats, o extended attributes... We are very interested to hear about your project on all those aspects, and of course we'd be happy to help you set up a hacking session or other form of gathering eventually, depending on the schedule. See the complete call for participation. http://groups.google.com/group/rosetta-os/browse_thread/thread/16964e21bef2… The deadline for the propositions for the Alt-OS devroom at FOSDEM has been extended to 2010-01-05, to allow at least one talk per project. The shedule must be sent rapidly to the FOSDEM team so we can't stretch it much more. François.

1 0

Re: l4-hackers Digest, Vol 80, Issue 11
by fang zhengshu 30 Dec '09

30 Dec '09

2009/12/29 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: Problems running l4-linux in VMWare with SCSI Discs > (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 28 Dec 2009 13:43:28 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: Problems running l4-linux in VMWare with SCSI Discs > Message-ID: <20091228124328.GB30342(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Sun Dec 27, 2009 at 12:40:11 +0800, fang zhengshu wrote: > > > scsi disk,and I try to create a ide disk ,then it can dectect the disk. > > so I think there is some problem with the vmware and the scsi. > > because I have enable the scsi disk. > > So do you have the appropriate SCSI driver in Linux enabled, i.e. the > (virtual) disk is detected? no,It can only detect the ide device.when I have a scsi disk and a ide cdrom, It can only test the ide cdrom. and when I create a ide disk,then it can detect the ide disk.but I have enable the scsi disk support. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 80, Issue 11 > ****************************************** > -- fang,

1 0

Re: l4-hackers Digest, Vol 80, Issue 8
by fang zhengshu 28 Dec '09

28 Dec '09

2009/12/26 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: l4-hackers Digest, Vol 80, Issue 6 (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 25 Dec 2009 17:24:48 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: l4-hackers Digest, Vol 80, Issue 6 > Message-ID: <20091225162448.GA18264(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Fri Dec 25, 2009 at 09:29:58 +0800, fang zhengshu wrote: > > I chage the command line "root=/dev/sda1" instead of "root=/dev/sda" > ,but > > there is still the error as the new attach! please look it. attach. > > > > > > > - the Linux booted only finds a VMware Virtual CDROM as hda, so there's > > > no sda device found, I'm not currently sure wheter VMware supports > > > SATA or not but you should make sure that VMware supplies a disk to > > > the guest, the Linux driver for that is compiled in and that the root= > > > option corresponds to that. > > > > > > > I'm sorry for not very clearly. If the VMware does not support the SATA, > how > > can it find the l4linux kernel and the other l4 modules??If you don't > agree , > > which must I select when configure the l4linux? > > Which type of disk did you configure in your VMware setup? > > scsi disk,and I try to create a ide disk ,then it can dectect the disk. so I think there is some problem with the vmware and the scsi. because I have enable the scsi disk. > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 80, Issue 8 > ***************************************** > -- fang,

3 2

Re: l4-hackers Digest, Vol 80, Issue 6
by fang zhengshu 25 Dec '09

25 Dec '09

2009/12/24 <l4-hackers-request(a)os.inf.tu-dresden.de> > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: append a correct "root=" boot option. Kernel panic, can > not find sda1 device (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 24 Dec 2009 11:37:08 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: append a correct "root=" boot option. Kernel panic, can > not find sda1 device > Message-ID: <20091224103708.GA23132(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Thu Dec 24, 2009 at 17:04:11 +0800, fang zhengshu wrote: > > the attach of the last email is the movie of booting l4linux through > serial > > +hardisk > > and I put an attach which is the picture of the error. > > Two things: > - in the video it has 3 kernel command line parameters, one being > root=/dev/sda (without a '1'), check your config file > I chage the command line "root=/dev/sda1" instead of "root=/dev/sda" ,but there is still the error as the new attach! please look it. attach. > - the Linux booted only finds a VMware Virtual CDROM as hda, so there's > no sda device found, I'm not currently sure wheter VMware supports > SATA or not but you should make sure that VMware supplies a disk to > the guest, the Linux driver for that is compiled in and that the root= > option corresponds to that. > I'm sorry for not very clearly. If the VMware does not support the SATA, how can it find the l4linux kernel and the other l4 modules？If you don't agree , which must I select when configure the l4linux? thank you. > > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 80, Issue 6 > ***************************************** > -- fang,

2 1

Re: append a correct "root=" boot option. Kernel panic, can not find sda1 device
by fang zhengshu 24 Dec '09

24 Dec '09

the attach of the last email is the movie of booting l4linux through serial +hardisk and I put an attach which is the picture of the error. any one can help me? thank you. 2009/12/24 fang zhengshu <fangzhsh07(a)gmail.com> > hi all, > I download the newest l4linux by using svn and use the x86-native_defconfig > to configure the l4linux > then modify some place: > process and the keyboard,vga > > then I can boot l4linux with the given drops-rd.rd through serial. > but when I use the same l4linux kernel to boot it on the national hardisk > throug serial. > I came across the following problem: > > Please append a correct "root=" boot option. Kernel panic - not syncing: > VFS: Unable to mount root fs on unknown-block(2,0) > I have enable the sata disk support! > I have following someone's step as the google: > > http://www.linuxquestions.org/questions/linux-kernel-70/kernel-panic-not-sy… > ... > but the error still exist! > > I do the things in vmware. > the menu.lst is: > > title l4linux26+serial > #my hardisk is /dev/sda1 > root (hd0,0) > kernel /boot/l4linux/bootstrap -serial -modaddr 0x02000000 > module /boot/l4linux/fiasco -nowait -nokdb -serial_esc \ > -comspeed 115200 -comport 1 > module /boot/l4linux/sigma0 > module /boot/l4linux/roottask task modname "bmodfs" attached 4 modules > module /boot/l4linux/names > module /boot/l4linux/log > module /boot/l4linux/dm_phys --isa=0x00800000 > module /boot/l4linux/simple_ts -t 300 > module /boot/l4linux/rtc > module /boot/l4linux/l4io > module /boot/l4linux/bmodfs > module /boot/l4linux/libld-l4.s.so > module /boot/l4linux/libloader.s.so > module /boot/l4linux/vmlinuzserial > module /boot/l4linux/l4linuxserial.cfg > module /boot/l4linux/loader --fprov=BMODFS l4linuxserial.cfg > > > the l4linuxserial.cfg is: > > modpath "(hd0,0)/boot/L4Linux" > task "vmlinuz" "earlyprintk=yes console=ttyLv0 init=/bin/sh mem=256M > l4ser.vkey_enable=1 root=/dev/sda1 ide_generic.probe_mask=0x3f" > all_sects_writable > allow_vga > > > thank you! > -- > fang, > > -- fang,

2 2

Codezero Microkernel v0.2 Released
by Bahadir Balban 07 Dec '09

07 Dec '09

I would like to announce that Codezero Microkernel v0.2 is released. On this release, the microkernel is now fully capability checked, and we introduced the notion of containers to provide isolated execution environments. Please see below for a brief description. 1.) Containers In Codezero containers provide the architectural infrastructure for isolation of execution environments. Each container is allocated with a set of address spaces, threads, and any other resource that would otherwise be globally available on the platform, such as virtual and physical memory. Using the simple notion of containers, it is possible to build any type of software design hierarchy. A hierarchical client/server design, or multi-threaded standalone applications are both possible scenarios. 2.) Capabilities Capabilities protect all resources maintained by the kernel. Currently, all system calls are protected by capabilities, except a few trivial ones that have been left out. Physical and virtual memory, typed memory pools, and inter-process communication are among other resources that are protected by capability checking. Capabilities build upon the foundation of containers, providing a fine-grained security architecture, inside and among container boundaries. We also introduced a capability control system call, by which the capabilities may be shared, granted and modified in different ways, enabling a highly flexible and configurable security architecture. 3.) Configuration We attempted to present the above two notions in an easily manageable kernel configuration system. Containers, their parameters and capabilities may be adjusted easily at configuration time, using our CML2-based kernel configuration system. We are aiming to evolve the L4 API into the future by feedback, hence this email post. Codezero Project is open with a GPLv3 license. If you are interested to learn more, download by: git-clone git://git.l4dev.org/codezero.git A useful jump-start guide: http://www.l4dev.org/doku.php?id=getting_started_quick API reference man pages: man -M codezero/docs/man pagename Thanks, -- Bahadir Balban

1 0