This list is intended for discussions about the L4 microkernel family and software running on top of L4.

headers sarita kale | 29 Jan 07:19 · /home/

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

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

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

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

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/16964e21bef27116

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.

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

Hi,

The NOVA project is happy to announce that there is a prerelease of the
NOVA microhypervisor available for download at http://www.hypervisor.org/
or http://os.inf.tu-dresden.de/~us15/nova/ under the terms of the
GNU Public License version 2.

NOVA is based on a modern microhypervisor written in C++ and assembler.
It currently supports x86-32 SMP platforms with hardware virtualization
features, such as Intel VT-x or AMD-V, and facilitates running multiple
unmodified guest operating systems in virtual machines with near-native
performance. On machines without VT-x or AMD-V, the functionality is
reduced to that of a microkernel.

Like third-generation microkernels, the NOVA microhypervisor uses a
capability-based authorization model and provides only basic mechanisms for
spatial and temporal isolation, scheduling, communication and delegation of
platform resources. Additional services are provided by an unprivileged
multi-server user environment running on top of the microhypervisor.

In NOVA, we implemented almost all of the virtualization functionality in a
deprivileged user-level virtual-machine monitor. This design choice improves
the overall security of the system, because exploitation of a bug in the
platform virtualization code only compromises the VMM and leaves the
remaining components unaffected.

Cheers,

	- Udo

_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

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

Hello all

I'm currently trying compil current Fiasco Kernel under Cygwin, 
unfortunatly I have a problem of compilation. when compiler try compil 
kip.cc I have an assembler message that said: Error: junk at the end of 
line, first unrecognized character is ','

Any Idea?

Thanks

Olivier

PS: my kip.cc

// AUTOMATICALLY GENERATED -- DO NOT EDIT!         -*- c++ -*-

#include "kip.h"
#include "kip_i.h"

#line 47 "/tudos/kernel/fiasco/src/abi/kip.cpp"

//============================================================================ 

#line 182 "/tudos/kernel/fiasco/src/abi/kip.cpp"

//---------------------------------------------------------------------------- 

#line 188 "/tudos/kernel/fiasco/src/abi/kip.cpp"

Kip *Kip::global_kip;
#line 192 "/tudos/kernel/fiasco/src/abi/kip.cpp"

asm(".section .initkip.version, \"a\", %progbits        \n"    \
   ".string \"" CONFIG_KERNEL_VERSION_STRING "\"       \n"    \
   ".previous                                          \n");
#line 196 "/tudos/kernel/fiasco/src/abi/kip.cpp"

asm(".section .initkip.features.fini, \"a\", %progbits  \n"    \
   ".string \"\"                                       \n"    \
   ".previous                                          \n");

#line 110 "/tudos/kernel/fiasco/src/abi/kip.cpp"

bool Kip::add_mem_region(Mem_desc const &md)
{
 Mem_desc *m = mem_descs();
 Mem_desc *end = m + num_mem_descs();
 for (;m<end;++m)
   {
     if (m->type() == Mem_desc::Undefined)
   {
     *m = md;
     return true;
   }
   }

 // Add mem region failed -- must be a Fiasco startup problem.  Bail out.
 assert (0);

 return false;
}

#line 130 "/tudos/kernel/fiasco/src/abi/kip.cpp"

Mem_region Kip::last_free() const
{
 Mem_desc const *m = mem_descs();
 Mem_desc const *const end = m + num_mem_descs();
 Mem_region r;
 r.start = 0;
 r.end   = 0;
 for (;m<end;++m)
   {
     Address s = m->start();
     Address e = m->end();

     // Speep out stupid descriptors (that have the end before the start)
     if (s>=e)
   {
     const_cast<Mem_desc*>(m)->type(Mem_desc::Undefined);
     continue;
   }

     if (m->is_virtual())    // skip virtual memory descriptors
   continue;

     switch (m->type())
   {
   case Mem_desc::Conventional:
     if (e>r.end)
       r.end = e;
     if (s>r.start)
       r.start = s;
     break;
   case Mem_desc::Reserved:
   case Mem_desc::Dedicated:
   case Mem_desc::Shared:
   case Mem_desc::Arch:
   case Mem_desc::Bootloader:
     if (e>=r.start && e<r.end)
       {
         r.start = e + 1;
       }
     if (s>=r.start && s<r.end)
       {
         r.end = s - 1;
       }
     break;
   default:
     break;
   }
   }
 return r;
}

3	February 2010
26	January 2010
20	December 2009
16	November 2009
25	October 2009
18	September 2009
27	August 2009
29	July 2009
21	June 2009
15	May 2009
96	April 2009
84	March 2009
49	February 2009
24	January 2009
25	December 2008
29	November 2008
66	October 2008
19	September 2008
13	August 2008
20	July 2008
35	June 2008
49	May 2008
37	April 2008
74	March 2008
17	February 2008
99	January 2008
17	December 2007
34	November 2007
39	October 2007
110	September 2007
79	August 2007
123	July 2007
73	June 2007
79	May 2007
52	April 2007
60	March 2007
29	February 2007
47	January 2007
80	December 2006
63	November 2006
49	October 2006
38	September 2006
113	August 2006
35	July 2006
68	June 2006
75	May 2006
39	April 2006
44	March 2006
20	February 2006
52	January 2006
27	December 2005
54	November 2005
70	October 2005
77	September 2005
74	August 2005
114	July 2005
182	June 2005
76	May 2005
26	April 2005
83	March 2005
105	February 2005
24	January 2005
13	December 2004
18	November 2004
27	October 2004
38	September 2004
8	August 2004
6	July 2004
10	June 2004
11	May 2004
1	March 2004
10	February 2004
27	January 2004

fiasco - related

Interrupt problems causing crash of network driver and Kernel panic?

DDE Linux26 in the Hurd

Call for participation to the Alt-OS devroom at FOSDEM (Extended deadline)

Re: l4-hackers Digest, Vol 80, Issue 11

Re: l4-hackers Digest, Vol 80, Issue 8

Re: l4-hackers Digest, Vol 80, Issue 6

Re: append a correct "root=" boot option. Kernel panic, can not find sda1 device

[ANNOUNCE] NOVA Microhypervisor 0.1 prerelease

Codezero Microkernel v0.2 Released

Problem compiling Fiasco Kernel (kip.cc)

Mon	Tue	Wed	Thu	Fri	Sat	Sun

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28