- l4-hackers - OS Site

Build Issues
by Michael J. Emswiler 17 Jun '06

17 Jun '06

Hi, I am trying to follow the directions (which may be old?) on the Fiasco site for building. (I am attempting to build a full DROP system eventually.) I am running OpenSuse 10.1, and have installed GCC 3.4.6 specifically for this purpose. After restructuring my dev area, I am building out of usr/src/drops. I have checked out the latest versions of l4 and l4linux-2.6 (even tried the hello alias.) For some reason, I can't seem to get past a missing configure in the tool/dice subdirectory. Can anyone clue me in as to how to generate this file properly? I start in usr/src/drops, create a bin directory to receive the output, type make -C l4 config and point DROPS_STDDIR to /usr/src/drops/bin, then I check the Linux-2.6 kernel sources available, and the default path appears correct ($(L4DIR)/../l4linux-2.6) and Save the configuration. Subsequently, I cd directly into l4 and try a simple make. It then asks for me to always provide O=.../builddir -- is this the same dir I provide in the config Target Path for DROPS_STDDIR ? So after doing that, it wants me to run config again ... so I do and set the paths all over again. After that, it gets through the bootstrap step in dice, but fails because ./configure does not exist. I am sure I am doing something stupid or missing a vital stip. Any tips would be appreciated. Thanks, MikeE

2 1

Multiprocessor Fiasco? Drops on Pistachio?
by Michael J. Emswiler 16 Jun '06

16 Jun '06

Hi, I was wondering if anyone was working on either of the following scenarios: 1. EM64T or AMD64 multiprocessor support for Fiasco 2. Running the DROPS OS on top of multiprocessor Pistachio I am interested in this functionality, would like to not duplicate any existing work, and would like to contribute to these areas if there are already folks working on this. Thanks, MikeE

1 0

Please Ignore: Building with GCC 4.1
by Michael J. Emswiler 16 Jun '06

16 Jun '06

It looks like i am just missing packages... please ignore the following email! Is anyone working on a GCC 4.x port? Or should i attempt to install 3.4.x side-by-side with 4.1? I am running OpenSuse 10.1 with GCC 4.1.0 on an Athlon I checked out the l4 tree from CVS and tried make -C l4 config O=./bin and get the following errors: make: Entering directory `/home/memswiler/Projects/Emswiler/Drops/l4' make -C ./tool/config make[1]: Entering directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config' make -C lxdialog lxdialog make[2]: Entering directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config/lxdialog' gcc -DLOCALE -MD -DCURSES_LOC="<curses.h>" -c -o checklist.o checklist.c In file included from checklist.c:24: dialog.h:29:20: error: curses.h: No such file or directory In file included from checklist.c:24: dialog.h:127: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘use_colors’ dialog.h:128: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘use_shadow’ dialog.h:130: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘attributes’ dialog.h:143: error: expected ‘)’ before ‘*’ token dialog.h:146: error: expected ‘)’ before ‘*’ token dialog.h:147: error: expected ‘)’ before ‘*’ token dialog.h:148: error: expected ‘)’ before ‘*’ token dialog.h:150: error: expected ‘)’ before ‘*’ token checklist.c:32: error: expected ‘)’ before ‘*’ token checklist.c:64: error: expected ‘)’ before ‘*’ token checklist.c:103: error: expected ‘)’ before ‘*’ token checklist.c: In function ‘dialog_checklist’: checklist.c:126: error: ‘WINDOW’ undeclared (first use in this function) checklist.c:126: error: (Each undeclared identifier is reported only once checklist.c:126: error: for each function it appears in.) checklist.c:126: error: ‘dialog’ undeclared (first use in this function) checklist.c:126: error: ‘list’ undeclared (first use in this function) checklist.c:133: warning: incompatible implicit declaration of built-in function ‘fprintf’ checklist.c:133: error: ‘stderr’ undeclared (first use in this function) checklist.c:148: error: ‘COLS’ undeclared (first use in this function) checklist.c:149: error: ‘LINES’ undeclared (first use in this function) checklist.c:151: error: ‘stdscr’ undeclared (first use in this function) checklist.c:154: error: ‘TRUE’ undeclared (first use in this function) checklist.c:156: error: ‘attributes’ undeclared (first use in this function) checklist.c:231: error: ‘KEY_UP’ undeclared (first use in this function) checklist.c:231: error: ‘KEY_DOWN’ undeclared (first use in this function) checklist.c:241: error: ‘FALSE’ undeclared (first use in this function) checklist.c:270: error: called object ‘scroll’ is not a function checklist.c:309: error: ‘KEY_LEFT’ undeclared (first use in this function) checklist.c:310: error: ‘KEY_RIGHT’ undeclared (first use in this function) checklist.c:343: warning: incompatible implicit declaration of built-in function ‘fprintf’ checklist.c:345: warning: incompatible implicit declaration of built-in function ‘fprintf’ make[2]: *** [checklist.o] Error 1 make[2]: Leaving directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config/lxdialog' make[1]: *** [lxdialog/lxdialog] Error 2 make[1]: Leaving directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config' make: *** [tool/config/lxdialog/lxdialog] Error 2

1 0

Building with GCC 4.1
by Michael J. Emswiler 16 Jun '06

16 Jun '06

Is anyone working on a GCC 4.x port? Or should i attempt to install 3.4.x side-by-side with 4.1? I am running OpenSuse 10.1 with GCC 4.1.0 on an Athlon I checked out the l4 tree from CVS and tried make -C l4 config O=./bin and get the following errors: make: Entering directory `/home/memswiler/Projects/Emswiler/Drops/l4' make -C ./tool/config make[1]: Entering directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config' make -C lxdialog lxdialog make[2]: Entering directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config/lxdialog' gcc -DLOCALE -MD -DCURSES_LOC="<curses.h>" -c -o checklist.o checklist.c In file included from checklist.c:24: dialog.h:29:20: error: curses.h: No such file or directory In file included from checklist.c:24: dialog.h:127: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘use_colors’ dialog.h:128: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘use_shadow’ dialog.h:130: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘attributes’ dialog.h:143: error: expected ‘)’ before ‘*’ token dialog.h:146: error: expected ‘)’ before ‘*’ token dialog.h:147: error: expected ‘)’ before ‘*’ token dialog.h:148: error: expected ‘)’ before ‘*’ token dialog.h:150: error: expected ‘)’ before ‘*’ token checklist.c:32: error: expected ‘)’ before ‘*’ token checklist.c:64: error: expected ‘)’ before ‘*’ token checklist.c:103: error: expected ‘)’ before ‘*’ token checklist.c: In function ‘dialog_checklist’: checklist.c:126: error: ‘WINDOW’ undeclared (first use in this function) checklist.c:126: error: (Each undeclared identifier is reported only once checklist.c:126: error: for each function it appears in.) checklist.c:126: error: ‘dialog’ undeclared (first use in this function) checklist.c:126: error: ‘list’ undeclared (first use in this function) checklist.c:133: warning: incompatible implicit declaration of built-in function ‘fprintf’ checklist.c:133: error: ‘stderr’ undeclared (first use in this function) checklist.c:148: error: ‘COLS’ undeclared (first use in this function) checklist.c:149: error: ‘LINES’ undeclared (first use in this function) checklist.c:151: error: ‘stdscr’ undeclared (first use in this function) checklist.c:154: error: ‘TRUE’ undeclared (first use in this function) checklist.c:156: error: ‘attributes’ undeclared (first use in this function) checklist.c:231: error: ‘KEY_UP’ undeclared (first use in this function) checklist.c:231: error: ‘KEY_DOWN’ undeclared (first use in this function) checklist.c:241: error: ‘FALSE’ undeclared (first use in this function) checklist.c:270: error: called object ‘scroll’ is not a function checklist.c:309: error: ‘KEY_LEFT’ undeclared (first use in this function) checklist.c:310: error: ‘KEY_RIGHT’ undeclared (first use in this function) checklist.c:343: warning: incompatible implicit declaration of built-in function ‘fprintf’ checklist.c:345: warning: incompatible implicit declaration of built-in function ‘fprintf’ make[2]: *** [checklist.o] Error 1 make[2]: Leaving directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config/lxdialog' make[1]: *** [lxdialog/lxdialog] Error 2 make[1]: Leaving directory `/home/memswiler/Projects/Emswiler/Drops/l4/tool/config' make: *** [tool/config/lxdialog/lxdialog] Error 2

1 0

Re: not enough modules for loading L4Linux-2.6 on the Fiasco
by chenggh 14 Jun '06

14 Jun '06

On Tuesday 13 June 2006 15:17, Bjoern Doebel wrote: > Hi, > > > Grub: > > title fiasco_L4Linux-2.6 > > kernel (hd0,1)/boot/fiasco_L4/bootstrap > > modaddr 0x06000000 > > module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc > > -comspeed 115200 -comport 1 > > module (hd0,1)/boot/fiasco_L4/sigma0 > > module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" module > > module module module module module > > Try > > module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" attached 1 > modules > > here. I modify the roottask line as this: module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" module So the grub is like this: # L4Linux bootable over Fiasco title fiasco_L4Linux-2.6 kernel (hd0,1)/boot/fiasco_L4/bootstrap modaddr 0x06000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" module module (hd0,1)/boot/fiasco_L4/events module (hd0,1)/boot/fiasco_L4/names -events module (hd0,1)/boot/fiasco_L4/log module (hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events module (hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events module (hd0,1)/boot/fiasco_L4/rtc --events module (hd0,1)/boot/fiasco_L4/l4io -noirq --events module (hd0,1)/boot/fiasco_L4/l4exec --events # module (hd0,1)/boot/faisco_L4/con -l4io -cpuload --events # module (hd0,1)/boot/fiasco_L4/tftp -i module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/libloader.s.so module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26 The minicom log is like this: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) 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: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427936kB ( 418MB) received RAM from Sigma0 23232kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:1 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 12 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074ac99d ] entry at 000690b4 via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) #0e: loading "(hd0,1)/boot/fiasco_L4/libloader.s.so" from [074ad000-07550661] to [00000000-00021e1d] Roottask: cannot load binary because address at 00000000 not free loaded module: [074ad000-07550661) (hd0,1)/boot/fiasco_L4/libloader.s.so overlaps with: [00000000-00001000) BIOS area Roottask boot panic: can't allocate page at 0x00000000: owned by #01 [Esc] reboot, [k] kdebug, [m] memory map, [r] region map Rebooting... it is unlucky. Later I used the five module again in the grub it is like this: Grub: title fiasco_L4Linux-2.6 kernel (hd0,1)/boot/fiasco_L4/bootstrap modaddr 0x06000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" module module module module module module (hd0,1)/boot/fiasco_L4/events module (hd0,1)/boot/fiasco_L4/names -events module (hd0,1)/boot/fiasco_L4/log module (hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events module (hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events module (hd0,1)/boot/fiasco_L4/rtc --events module (hd0,1)/boot/fiasco_L4/l4io -noirq --events module (hd0,1)/boot/fiasco_L4/l4exec --events # module (hd0,1)/boot/faisco_L4/con -l4io -cpuload --events # module (hd0,1)/boot/fiasco_L4/tftp -i module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/libloader.s.so module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26 The minicom log is like this: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) 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: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 427936kB ( 418MB) received RAM from Sigma0 23232kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:4 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 12 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074ac99d ] passing module (hd0,1)/boot/fiasco_L4/libloader.s.so [ 074ad000-07550661 ] passing module (hd0,1)/boot/fiasco_L4/loader [ 07551000-076356f5 ] Roottask boot warning: task configured to use modules, but there are not enough modules for loading --> not passing [Return] continue, [Esc] reboot, [k] kdebug, [m] memory map, [r] region map entry at 00069144 via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. DMphys | [8.0] dm_phys/server/src/main.c:115:__get_num(): DMphys | Error: DMphys: invalid number: 'sa=0x00800000'! DMphys | [8.0] dm_phys/server/src/main.c:153:__pool_config(): DMphys | Error: DMphys: invalid size for pool 7: sa=0x00800000! rtc | Date:14.06.2006 Time:21:15:57 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x0013a000 0 12 MAPPED DMphys | 0x0013a000-0x001d2000 -- -- DENIED DMphys | 0x001d2000-0x002d0000 0 12 MAPPED DMphys | 0x002d0000-0x002e4000 -- -- DENIED DMphys | 0x002e4000-0x00400000 0 12 MAPPED DMphys | 0x00400000-0x0043c000 -- -- DENIED DMphys | 0x0043c000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bf1000 -- -- DENIED DMphys | 0x00bf1000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108b000 -- -- DENIED DMphys | 0x0108b000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114e000 -- -- DENIED DMphys | 0x0114e000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01258000 -- -- DENIED DMphys | 0x01258000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01416000 -- -- DENIED DMphys | 0x01416000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154e000 -- -- DENIED DMphys | 0x0154e000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x066b2000 0 12 MAPPED DMphys | 0x066b2000-0x07636000 -- -- DENIED DMphys | 0x07636000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b875000 0 12 MAPPED DMphys | 0x1b875000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 431896KB total, 431896KB free, 32KB reserved DMphys | 0x00100000-0x0013a000 ( 232KB, 0MB) DMphys | 0x001d2000-0x002d0000 ( 1016KB, 1MB) DMphys | 0x002e4000-0x00400000 ( 1136KB, 1MB) DMphys | 0x0043c000-0x00b80000 ( 7440KB, 7MB) DMphys | 0x00bf1000-0x01080000 ( 4668KB, 5MB) DMphys | 0x0108b000-0x01100000 ( 468KB, 0MB) DMphys | 0x0114e000-0x01220000 ( 840KB, 1MB) DMphys | 0x01258000-0x01400000 ( 1696KB, 2MB) DMphys | 0x01416000-0x01500000 ( 936KB, 1MB) DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) DMphys | 0x0154e000-0x066b2000 ( 83344KB, 81MB) DMphys | 0x07636000-0x1b875000 (329980KB, 322MB) bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/fiasco_L4/vmlinuz26" (14315kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/libloader.s.so" (654kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26" (9 bmodfs : 14kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec11ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec120000-ec13ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec160000-ec1600ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec161000-ec1617ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec162000-ec1620ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d01f : Intel Corp. 82544GC Gigabit Ethernet Controller (Copper io : ) io | d400-d4ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d800-d87f : VIA Technologies, Inc. IEEE 1394 Host Controller io | dc00-dc1f : VIA Technologies, Inc. USB io | e000-e01f : VIA Technologies, Inc. USB (#2) io | e400-e41f : VIA Technologies, Inc. USB (#3) io | e800-e80f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | ec00-ecff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler Please help me! Chenggh

2 1

Re: The "region overlap" problem in the L4/Fiasco hello example
by chenggh 14 Jun '06

14 Jun '06

On Tuesday 13 June 2006 19:25, Ronald Aigner wrote: > chenggh wrote on 13.06.2006 09:15 this: > > Hi,everyone: > > When I boot the hello example in the L4/Fiasco. there is a "region > > overlap" in the booting information. I don't why it could be like this. > > The grub configuration and the error information is following: > > > > Grub: > > title fiasco_hello_new > > kernel (hd0,1)/boot/fiasco_hello_new/bootstrap -comport 1 -serial > > modaddr 0x06000000 ? > > > module (hd0,1)/boot/fiasco_hello_new/main -nokdb > > module (hd0,1)/boot/fiasco_hello_new/sigma0 > > module (hd0,1)/boot/fiasco_hello_new/roottask > > module (hd0,1)/boot/fiasco_hello_new/hello > > > > minicom_log: > > L4 Bootstrapper > > Loading (hd0,1)/boot/fiasco_hello_new/main > > Kernel at 00002000-0038f408 > > Detected new-style DD-L4(v2)/Fiasco x86 > > Loading (hd0,1)/boot/fiasco_hello_new/sigma0 > > Loading (hd0,1)/boot/fiasco_hello_new/roottask > > loaded module section: [0028d000-00324e13) .Roottask syms/lines > > (copy) overlaps with: [00300000-0038f408) > > (hd0,1)/boot/fiasco_hello_new/main > > [00002000-0005ae70) (hd0,1)/boot/fiasco_hello_new/main > > [0005b000-0005fcfd) (hd0,1)/boot/fiasco_hello_new/main > > [00090000-0009432d) (hd0,1)/boot/fiasco_hello_new/sigma0 > > [00095340-00096824) (hd0,1)/boot/fiasco_hello_new/sigma0 > > [0009f000-00100000) BIOS area > > [00100000-0010dc04) bootstrap > > [0013f000-0028ccb0) Modules Memory > > [00300000-0038f408) (hd0,1)/boot/fiasco_hello_new/main > > [1dff0000-ffffffff) Deep Space > > region overlap > > > > Thanks! > > Cheng > > HTH, Ron. The hello example is ok. Thank you ! Cheng

1 0

not enough modules for loading L4Linux-2.6 on the Fiasco
by chenggh 13 Jun '06

13 Jun '06

Hi,everyone: when I boot L4Linux-2.6 on the Fiasco the booting information says there is not enough modules for loading. my configuration and error information are following: Grub: title fiasco_L4Linux-2.6 kernel (hd0,1)/boot/fiasco_L4/bootstrap modaddr 0x06000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/roottask task modname "bmodfs" module module module module module module module (hd0,1)/boot/fiasco_L4/events module (hd0,1)/boot/fiasco_L4/names -events module (hd0,1)/boot/fiasco_L4/log module (hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events module (hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events module (hd0,1)/boot/fiasco_L4/rtc --events module (hd0,1)/boot/fiasco_L4/l4io -noirq --events module (hd0,1)/boot/fiasco_L4/l4exec --events # module (hd0,1)/boot/faisco_L4/con -l4io -cpuload --events # module (hd0,1)/boot/fiasco_L4/tftp -i module (hd0,1)/boot/fiasco_L4/bmodfs --events module (hd0,1)/boot/fiasco_L4/vmlinuz26 module (hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26 Minicom_log: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.6 for AMD Athlon Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_LIST_ALLOC_SANITY is on CONFIG_BEFORE_IRET_SANITY is on CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) 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: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 188kB for maintenance structures. Roottask. 491071kB ( 479MB) total RAM (reported by bootloader) 428592kB ( 419MB) received RAM from Sigma0 22576kB ( 23MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:6 Symbols at [1b956000-1b95b000] (20kB), lines at [1b944000-1b956000] (72kB) Roottask: Loading 11 modules. #05: loading "(hd0,1)/boot/fiasco_L4/events" from [0612b000-06174e2f] to [01540000-0154ab9d][0154b000-0154d954] entry at 00061078 via trampoline page code symbols at [1b942000-1b944000] (8kB), lines at [1b93a000-1b942000] (32kB) #06: loading "(hd0,1)/boot/fiasco_L4/names -events" from [06175000-061b9ca6] to [002d0000-002d784a][002d8000-002e4000] entry at 00062080 via trampoline page code symbols at [1b938000-1b93a000] (8kB), lines at [1b931000-1b938000] (28kB) #07: loading "(hd0,1)/boot/fiasco_L4/log" from [061ba000-061fd64c] to [00400000-004080aa][00409000-0043b8b0] entry at 00063074 via trampoline page code symbols at [1b92f000-1b931000] (8kB), lines at [1b928000-1b92f000] (28kB) #08: loading "(hd0,1)/boot/fiasco_L4/dm_phys -isa=0x00800000 -v --events" from [061fe000-0627ab68] to [01500000-01513aea][01514000-0151e000] entry at 00064094 via trampoline page code symbols at [1b924000-1b928000] (16kB), lines at [1b916000-1b924000] (56kB) #09: loading "(hd0,1)/boot/fiasco_L4/simple_ts -t 300 --events" from [0627b000-062c5fd2] to [01400000-0140910a][0140a000-01415bf0] entry at 0006508c via trampoline page code symbols at [1b913000-1b916000] (12kB), lines at [1b90b000-1b913000] (32kB) #0a: loading "(hd0,1)/boot/fiasco_L4/rtc --events" from [062c6000-062fbfd8] to [01080000-01085960][01086000-0108b000] entry at 0006607c via trampoline page code symbols at [1b909000-1b90b000] (8kB), lines at [1b903000-1b909000] (24kB) #0b: loading "(hd0,1)/boot/fiasco_L4/l4io -noirq --events" from [062fc000-064e5299] to [00b80000-00ba436a][00ba5000-00bf1000] entry at 00067084 via trampoline page code symbols at [1b8cb000-1b903000] (224kB), lines at [1b8b1000-1b8cb000] (104kB) #0c: loading "(hd0,1)/boot/fiasco_L4/l4exec --events" from [064e6000-0660ffd9] to [01100000-0112bb8a][0112c000-0114e000] entry at 00068080 via trampoline page code symbols at [1b8a9000-1b8b1000] (32kB), lines at [1b88c000-1b8a9000] (116kB) #0d: loading "(hd0,1)/boot/fiasco_L4/bmodfs --events" from [06610000-066b110a] to [01220000-0123706a][01238000-01258000] passing module (hd0,1)/boot/fiasco_L4/vmlinuz26 [ 066b2000-074ac99d ] passing module (hd0,1)/boot/fiasco_L4/loader [ 074ad000-075916f5 ] Roottask boot warning: task configured to use modules, but there are not enough modules for loading --> not passing [Return] continue, [Esc] reboot, [k] kdebug, [m] memory map, [r] region map entry at 0006913c via trampoline page code symbols at [1b887000-1b88c000] (20kB), lines at [1b875000-1b887000] (72kB) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. DMphys | [8.0] dm_phys/server/src/main.c:115:__get_num(): DMphys | Error: DMphys: invalid number: 'sa=0x00800000'! DMphys | [8.0] dm_phys/server/src/main.c:153:__pool_config(): DMphys | Error: DMphys: invalid size for pool 7: sa=0x00800000! rtc | Date:13.06.2006 Time:14:38:43 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x1dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x1dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x0013a000 0 12 MAPPED DMphys | 0x0013a000-0x001d2000 -- -- DENIED DMphys | 0x001d2000-0x002d0000 0 12 MAPPED DMphys | 0x002d0000-0x002e4000 -- -- DENIED DMphys | 0x002e4000-0x00400000 0 12 MAPPED DMphys | 0x00400000-0x0043c000 -- -- DENIED DMphys | 0x0043c000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bf1000 -- -- DENIED DMphys | 0x00bf1000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108b000 -- -- DENIED DMphys | 0x0108b000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x0114e000 -- -- DENIED DMphys | 0x0114e000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01258000 -- -- DENIED DMphys | 0x01258000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01416000 -- -- DENIED DMphys | 0x01416000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0154e000 -- -- DENIED DMphys | 0x0154e000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x066b2000 0 12 MAPPED DMphys | 0x066b2000-0x07592000 -- -- DENIED DMphys | 0x07592000-0x07800000 0 12 MAPPED DMphys | 0x07800000-0x1b800000 0 22 MAPPED DMphys | 0x1b800000-0x1b875000 0 12 MAPPED DMphys | 0x1b875000-0x1dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 432552KB total, 432552KB free, 32KB reserved DMphys | 0x00100000-0x0013a000 ( 232KB, 0MB) DMphys | 0x001d2000-0x002d0000 ( 1016KB, 1MB) DMphys | 0x002e4000-0x00400000 ( 1136KB, 1MB) DMphys | 0x0043c000-0x00b80000 ( 7440KB, 7MB) DMphys | 0x00bf1000-0x01080000 ( 4668KB, 5MB) DMphys | 0x0108b000-0x01100000 ( 468KB, 0MB) DMphys | 0x0114e000-0x01220000 ( 840KB, 1MB) DMphys | 0x01258000-0x01400000 ( 1696KB, 2MB) DMphys | 0x01416000-0x01500000 ( 936KB, 1MB) DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) DMphys | 0x0154e000-0x066b2000 ( 83344KB, 81MB) DMphys | 0x07592000-0x1b875000 (330636KB, 323MB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | e0000000-e7ffffff : PCI Bus #01 io | e0000000-e7ffffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | e8000000-ebffffff : VIA Technologies, Inc. VT8375 [KM266/KL266] Hos io : t Bridge io | ec000000-ec0fffff : PCI Bus #01 io | ec000000-ec07ffff : S3 Inc. VT8375 [ProSavage8 KM266/KL266] io | ec100000-ec11ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec120000-ec13ffff : Intel Corp. 82544GC Gigabit Ethernet Controller io : (Copper) io | ec160000-ec1600ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io : 8139C+ io | ec161000-ec1617ff : VIA Technologies, Inc. IEEE 1394 Host Controlle io : r io | ec162000-ec1620ff : VIA Technologies, Inc. USB 2.0 io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d01f : Intel Corp. 82544GC Gigabit Ethernet Controller (Copper io : ) io | d400-d4ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io | d800-d87f : VIA Technologies, Inc. IEEE 1394 Host Controller io | dc00-dc1f : VIA Technologies, Inc. USB io | e000-e01f : VIA Technologies, Inc. USB (#2) io | e400-e41f : VIA Technologies, Inc. USB (#3) io | e800-e80f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | ec00-ecff : VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Control io : ler bmodfs | Passed the following modules: bmodfs | module "(hd0,1)/boot/fiasco_L4/vmlinuz26" (14315kB) bmodfs | module "(hd0,1)/boot/fiasco_L4/loader --fprov=BMODFS vmlinuz26" (9 bmodfs : 14kB) I don't know I have which module to be missed. Please help me to check it! Thank you! Cheng

2 1

The booting error of L4Linux-2.6 on fiasco
by chenggh 09 Jun '06

09 Jun '06

Hi: When i booting the L4Linux-2.6 on fiasco , the error information is as following: Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.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: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 188kB for maintenance structures. Roottask. SIGMA0: can't handle d1=0xe0000040, d2=0x0 from thread=4.00 Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Jun 1 13:35:11 2006 compiled with gcc 3.3.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: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 2002 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 188kB for maintenance structures. Roottask. SIGMA0: can't handle d1=0xe0000040, d2=0x0 from thread=4.00 then the machine is dead and my menu.lst about this part is as following: # L4Linux bootable over Fiasco title fiasco_L4Linux-2.6 kernel (hd0,1)/boot/fiasco_L4/bootstrap -roottask -sigma0 task modname "L4Linux task" modaddr 0x02000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/roottask -sigma0 module (hd0,1)/boot/fiasco_L4/names module (hd0,1)/boot/fiasco_L4/log module (hd0,1)/boot/fiasco_L4/dm_phys module (hd0,1)/boot/fiasco_L4/simple_ts -t 300 module (hd0,1)/boot/fiasco_L4/rtc module (hd0,1)/boot/fiasco_L4/l4io -noirq module (hd0,1)/boot/fiasco_L4/tftp -i module (hd0,1)/boot/fiasco_L4/l4exec module (hd0,1)/boot/fiasco_L4/loader (hd0,1)/boot/fiasco_L4/vmlinuz26 Please help me. Thank you! Cheng

2 1

another FLIPS build problem
by David Silcott 08 Jun '06

08 Jun '06

Hello all, Ok, I've pointed to my Linux 2.4 source tree ( tried both 2.4.27 and 2.4.28) and I have tried gcc 3.3 and 3.4 And each time I am getting the error below.... Any suggestions?? David ===================================== ... Compiling flips-server.o LD_PRELOAD=/RESEARCH/l4test/l4/tool/gendep/libgendep.so GENDEP_TARGET=flips-server.o GENDEP_BINARY=cc1 gcc -c -D__KERNEL__ -DDDE_LINUX -DRAM_BASE=0x0 -DUSE_UCLIBC=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I../../../server/lib-linux/include -I../../../server/lib-lxdrv/include -I../../../server/include -I../../../../../include/x86/l4/dde_linux -I/RESEARCH/drops1/include/x86/l4/dde_linux -I/usr/src/linux-2.4/include -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/RESEARCH/drops1/include/x86/l4v2 -I../../../../../include/l4v2 -I/RESEARCH/drops1/include/l4v2 -I../../../../../include/x86 -I/RESEARCH/drops1/include/x86 -I../../../../../include -I/RESEARCH/drops1/include -nostdinc -I../../../../../include/x86/uclibc -I../../../../../include/uclibc -I../../../../../include/uclibc++ -I/RESEARCH/drops1/include/x86/uclibc -I/RESEARCH/drops1/include/uclibc -I/RESEARCH/drops1/include/uclibc++ -I/usr/lib/gcc-lib/i486-linux-gnu/3.3.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -fno-common /RESEARCH/l4test/l4/pkg/flips/idl/OBJ-x86-l4v2/flips-server.c -o flips-server.o ==> Linking flips LD_PRELOAD=/RESEARCH/l4test/l4/tool/gendep/libgendep.so GENDEP_TARGET=flips GENDEP_BINARY=ld gcc -o flips ../../../../../lib/x86_586/crt0.o server.o main.o notify.o flips-server.o -Ttext=0x01900000 -L../../../server/lib-linux/src/OBJ-x86_586-l4v2 -L../../../server/lib-ore/src/OBJ-x86_586-l4v2 -L../../../server/lib-lxdrv/src/OBJ-x86_586-l4v2 -L../../../../../lib/x86_586/l4v2 -L/RESEARCH/drops1/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/RESEARCH/drops1/lib/x86_586 -L../../../../../lib -L/RESEARCH/drops1/lib -T../../../../../lib/x86_586/main_stat.ld -lsocket_linux.o -llinux.o -ldde_linux -lio -lomega0 -llist_alloc -ll4vfs_network_server-server -ll4vfs_select -ll4vfs_select_notify-server -lflips_l4vfs_server -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot.o -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/libgcc.a -luc_c -ll4sys -Ttext=0x01900000 -Wl,-gc-sections -Wl,--warn-common ../../../server/lib-linux/src/OBJ-x86_586-l4v2/liblinux.o.a: In function `net_device_init':/usr/src/linux-2.4/drivers/net/setup.c:167: undefined reference to `netlink_proto_init' collect2: ld returned 1 exit status make[3]: *** [flips] Error 1 make[3]: Leaving directory `/RESEARCH/l4test/l4/pkg/flips/server/src/OBJ-x86_586-l4v2' make[2]: *** [OBJ-x86_586-l4v2] Error 2 make[2]: Leaving directory `/RESEARCH/l4test/l4/pkg/flips/server/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/RESEARCH/l4test/l4/pkg/flips/server' make: *** [server] Error 2 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 6

Re: building l4env (fuxfprov error)
by David Silcott 08 Jun '06

08 Jun '06

--- David Silcott <lava_patch(a)yahoo.com> wrote: > Hello again > > I after managing to checkout the flips and ore > packages I am getting the error below. > > Currently I am trying to find the solution to the > problem but I would appreciate any help which would > speed up the process :-) > > Thanks > David > I think I got this error because I didn't not point to the linux 2.4 source tree. Error is no where to be found since I did that :). David __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

building l4env (fuxfprov error)
by David Silcott 06 Jun '06

06 Jun '06

Hello again I after managing to checkout the flips and ore packages I am getting the error below. Currently I am trying to find the solution to the problem but I would appreciate any help which would speed up the process :-) Thanks David === Building servers, examples of "lxfuxlibc" === PWD=/RESEARCH/l4env/l4/pkg/lxfuxlibc make -C lxfuxlibc all -o lib -o include -o idl make[2]: Entering directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc' test -f server/broken -o -f server/obsolete || \ if [ -f server/Makefile ] ; then PWD=/RESEARCH/l4env/l4/pkg/lxfuxlibc/server make -C server ; fi make[3]: Entering directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc/server' test -f fuxfprov/broken -o -f fuxfprov/obsolete || \ if [ -f fuxfprov/Makefile ] ; then PWD=/RESEARCH/l4env/l4/pkg/lxfuxlibc/server/fuxfprov make -C fuxfprov ; fi make[4]: Entering directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc/server/fuxfprov' PWD=/RESEARCH/l4env/l4/pkg/lxfuxlibc/server/fuxfprov/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc/server/fuxfprov/OBJ-x86_586-l4v2' ==> Linking fuxfprov LD_PRELOAD=/RESEARCH/l4env/l4/tool/gendep/libgendep.so GENDEP_TARGET=fuxfprov GENDEP_BINARY=ld gcc -o fuxfprov ../../../../../lib/x86_586/crt0.o -L../../../.. /../lib/x86_586/l4v2 -L/RESEARCH/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/RESEARCH/drops/lib/x86_586 -L../../../../../lib -L/RESEARCH/drops/lib -T. ./../../../../lib/x86_586/main_stat.ld -lclxfux.o -ll4z -lstdio_zlib_ux -lgeneric_fprov-server -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot.o -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdl ib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple _sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a -luc_c -ll4sys -Wl,-gc-se ctions -Wl,--warn-common ../../../../../lib/x86_586/l4v2/libl4env.a(startup.o): In function `__startup_main':/RESEARCH/l4env/l4/pkg/l4env/lib/src/startup.c:78: undefined reference to `mai n' collect2: ld returned 1 exit status make[5]: *** [fuxfprov] Error 1 make[5]: Leaving directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc/server/fuxfprov/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc/server/fuxfprov' make[3]: *** [fuxfprov] Error 2 make[3]: Leaving directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc/server' make[2]: *** [server] Error 2 make[2]: Leaving directory `/RESEARCH/l4env/l4/pkg/lxfuxlibc' make[1]: *** [lxfuxlibc.bin] Error 2 make[1]: Leaving directory `/RESEARCH/l4env/l4/pkg' make: *** [pkg] Error 2 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

l4vfs, flips
by David Silcott 06 Jun '06

06 Jun '06

Hello Christian I am currently trying to port a network server to L4 and I am attempting to use flips in order to enable communication across the network. I am getting the following message after running *make* in the pkg directory. I have tried to check out the l4vfs package but it is not available. Any suggestions will be greatly appreciated. David ^^^^^^^^^^^^^MAKE RESULTS BELOW^^^^^^^^^^^^^^^^^^^ make: Circular dde_linux.headers <- l4con.bin dependency dropped. === Building IDL & includes of "dde_linux" === PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux make -C dde_linux include make[1]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' test -f include/broken -o -f include/obsolete || \ if [ -f include/Makefile ] ; then PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux/include make -C include ; fi make[2]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[2]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[1]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux make -C dde_linux idl make[1]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' test -f include/broken -o -f include/obsolete || \ if [ -f include/Makefile ] ; then PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux/include make -C include ; fi make[2]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[2]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[1]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' make: *** No rule to make target `l4vfs.headers', needed by `flips.headers'. Stop.

2 1

unable to compile flips
by David Silcott 06 Jun '06

06 Jun '06

Hello all I am trying to port a network server to L4 and I have checked out the flips and dde modules using cvs. However when I run make withing my pkg directory I get the message below. I've tried checking out l4vfs in an attempt to solve the problem but with no success. Am I doing something wrong?? David ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ make: Circular dde_linux.headers <- l4con.bin dependency dropped. === Building IDL & includes of "dde_linux" === PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux make -C dde_linux include make[1]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' test -f include/broken -o -f include/obsolete || \ if [ -f include/Makefile ] ; then PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux/include make -C include ; fi make[2]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[2]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[1]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux make -C dde_linux idl make[1]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' test -f include/broken -o -f include/obsolete || \ if [ -f include/Makefile ] ; then PWD=/RESEARCH/L4oskit/l4/pkg/dde_linux/include make -C include ; fi make[2]: Entering directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[2]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux/include' make[1]: Leaving directory `/RESEARCH/L4oskit/l4/pkg/dde_linux' make: *** No rule to make target `l4vfs.headers', needed by `flips.headers'. Stop. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Re: ore with fiasco-ux
by Hieb,Jeffrey Lloyd 02 Jun '06

02 Jun '06

Thanks, that helped alot on the L4 ore side. Arping seems to run fine now except that packets seem not to be making it to and from the host network . Do I need to configure something for the tunnel for fiasco-ux ?? Thanks, Jeff ----- Original Message ----- From: "Bjoern Doebel" <doebel(a)os.inf.tu-dresden.de> To: "Jeff Hieb" <j_hieb(a)insightbb.com> Cc: <l4-hackers(a)os.inf.tu-dresden.de> Sent: Wednesday, May 31, 2006 4:58 AM Subject: Re: ore with fiasco-ux > Hello, > >> When I run under fiasco-ux: >> >> ./fiasco -N -s -l names -l dm_phys -l log -l "l4io --noirq" -l ore -l >> ore_test_arping > > First, please add "-n9" to your command line. This enables task 9 (ore) > to execute native system calls using int80. > >> ore | main(): Initialized 1 network devices. >> ore | Device = lo, IRQ = 0, MAC = 00:00:00:00:00:00 > > There should be 2 network devices: lo and eth0. The arping test tries to > open eth0 and this fails because of the missing device. > > Please do a "make cleanall" in your l4/pkg/ore directory. > Then "make config" in l4/pkg/ore/server and configure the server to run > with Fiasco UX only. Thereafter rebuild the ORe directory. This will > compile the ux_net driver into the ORe server, which in turn will > provide an eth0 interface. > > Note that "make cleanall" also erases configuration files. A subsequent > "make" will use the default config from l4/pkg/ore/server/defconfig. By > default this builds ORe with a real network driver again. If you are > only using UX, you might copy your .config to defconfig so that "make > cleanall && make" builds ORe for UX. > > So far > Bjoern

4 4

Fiaco and ARM
by Christian Roepke 01 Jun '06

01 Jun '06

Hi, now I try to compile Fiasco for ARM926. It seems that a file is missed ? ... Preprocessing globals make[2]: *** No rule to make target `config-arm-isg.cpp', needed by `auto/stamp-config.ready'. Stop. make[2]: Leaving directory `...l4/kernel/fiasco/build' make[1]: *** [create-sources] Error 2 make[1]: Leaving directory `...l4/kernel/fiasco/build' make: *** [all] Error 2 Hans -- Hans Christian Röpke Network Administration Applied Data Security Group Ruhr-Universität Bochum, IC 4/42 Universitätsstrasse 150 44780 Bochum, Germany http://www.prosec.rub.de

2 1

DROPS and ARM
by Christian Roepke 01 Jun '06

01 Jun '06

Hi, I try to compile DROPS for an ARM processor. So I compiled my own cross compiler arm-unknown-linux-uclibc-gcc (I used Gentoo's cross-toolchain generator crossdev). l4/tool/ compiled correctly, but l4/pkg/ NOT :-( I get this message: === Building IDL & includes of "l4io" === PWD=.../l4/pkg/l4io make -C l4io include make[1]: Entering directory `.../l4/pkg/l4io' Makefile:8: *** Wrong gcc major version "" - use 3.x for l4io. Stop. make[1]: Leaving directory `.../l4/pkg/l4io' make: *** [l4io.headers] Error 2 But I use GCC 3.3.6. See the version output: l4/pkg $ arm-unknown-linux-uclibc-gcc --version arm-unknown-linux-uclibc-gcc (GCC) 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8) Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. What is going wrong here? Thanks, Hans -- Hans Christian Röpke Network Administration Applied Data Security Group Ruhr-Universität Bochum, IC 4/42 Universitätsstrasse 150 44780 Bochum, Germany http://www.prosec.rub.de

2 1

ore with fiasco-ux
by Jeff Hieb 31 May '06

31 May '06

Hello, I am having trouble getting the ore arping test to work under fiasco or fiasco-ux. When I run under fiasco-ux: ./fiasco -N -s -l names -l dm_phys -l log -l "l4io --noirq" -l ore -l ore_test_arping Roottask. Found Fiasco-UX. 64512kB ( 63MB) total RAM (reported by bootloader) 57208kB ( 56MB) received RAM from Sigma0 7628kB ( 8MB) reserved RAM for RMGR Received no I/O ports Attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 A B C D E F ] Roottask: Loading 6 modules. #05: loading "names" from [0399a000-039e0a2a] to [002d0000-002d774a][002d8000-002e4000] entry at 0000c060 via trampoline page code symbols at [039ee000-039f0000] (8kB), lines at [039e7000-039ee000] (28kB) #06: loading "dm_phys" from [0391c000-039996f4] to [01500000-0151304a][01514000-0151e000] entry at 0000d060 via trampoline page code symbols at [039e3000-039e7000] (16kB), lines at [039d5000-039e3000] (56kB) #07: loading "log" from [038d9000-0391b69c] to [00400000-00407eaa][00408000-0043a890] entry at 0000e05c via trampoline page code symbols at [039d3000-039d5000] (8kB), lines at [039cc000-039d3000] (28kB) #08: loading "l4io --noirq" from [036f0000-038d8801] to [00b80000-00ba32ce][00ba4000-00bf0000] entry at 0000f068 via trampoline page code symbols at [03994000-039cc000] (224kB), lines at [0397a000-03994000] (104kB) #09: loading "ore" from [034bf000-036ef46b] to [01800000-0182f3e6][01830000-01865000] entry at 0001005c via trampoline page code symbols at [03972000-0397a000] (32kB), lines at [0394e000-03972000] (144kB) #0a: loading "ore_test_arping" from [03411000-034be85e] to [00980000-0099872e][00999000-009b9000] entry at 00011068 via trampoline page code symbols at [03949000-0394e000] (20kB), lines at [03936000-03949000] (76kB) io | do_args(): Disabling internal IRQ handling. arping | main(): Hello from the ORe arping shared memory client arping | main(): string ipc receive arping | main(): sending with string ipc arping | l4ore_open(): called ore | l4dde_mm_init(): Using ... ore | 16 MB at 0x00100000 (vmem) ore | 16 MB in 1 regions (kmem) ore | device lo entered promiscuous mode ore | main(): Initialized 1 network devices. ore | Device = lo, IRQ = 0, MAC = 00:00:00:00:00:00 ore | main(): Registering at names... ore | main(): Ready for service. arping | ore_lookup_server(): ORe = 9.02 arping | l4ore_open(): descriptor: 0 arping | ore_do_open(): called ore | [9.2] ore/server/src/clients.c:208:setup_connection(): ore | Error: no device found. arping | ore_do_open(): opened. worker = 7FF.7F arping | [A.2] ore/lib/client/lib.c:153:l4ore_open(): arping | Error: ore_open() returned INVALID_ID arping | main(): opened eth0: -1 for 00:00:00:00:00:00 arping | [A.2] ore/examples/arping/main.c:243:main(): arping | Error: could not open eth0! arping | arping | Exiting with 1 Would appreciate any suggestions Thanks Jeff

2 1

NICTA's virtualised Linux faster than native on L4-embedded
by Gernot Heiser 31 May '06

31 May '06

NICTA's ERTOS team is proud to release LMBench performance figures for Wombat, our architecture-independent para-virtualized Linux running on L4-embedded/Iguana. The benchmarks show that Wombat's context-switching overheads are up to thirty times lower than those of native Linux on an XScale processor. This result, which is due to Wombat benefiting from the fast-context-switching support provided by NICTA's L4-embedded, demonstrates that L4-embedded/Iguana is the leading high-performance microkernel and embedded virtualisation technology, particularly on ARM processors. For details see http://ertos.nicta.com.au/news/home.pml#v-gt-r Gernot

1 0

sigma1
by Luke A. Guest 26 May '06

26 May '06

Hi, I've just started to look at L4 and I'm using L4ka::Pistachio as a starting point. I'm trying to read as much as possible and have found a reference to sigma1, but no docs on it. Can anyone elaborate on what this is for? Thanks, Luke.

5 7

test
by Luke A. Guest 20 May '06

20 May '06

please ignore

1 0

DoS problem still existing?
by Robert Kaiser 19 May '06

19 May '06

Hello L4 Hackers, a long time ago (*), Jochen Liedtke described a potential denial-of-service attack against the L4 kernel by -IIRC- requesting a huge number of mappings, thereby exhausting kernel memory. Does this issue still exist in the current L4 implementations or has it been solved (How?). Kind Regards Rob (*) see http://i30www.ira.uka.de/research/documents/l4ka/preventing-denial-of-servi… -- Robert Kaiser <rkaiser(a)sysgo.com> SYSGO AG Tel.: +49-6136-9948-0 Am Pfaffenstein 14 Fax: +49-6136-9948-10 55270 Klein-Winternheim http://www.sysgo.com

2 1

con-ux bug?
by Wei Shen 12 May '06

12 May '06

Hi, I run con-ux with: ./fiasco -G 800x600@16 -m 128 -l names -l dm_phys -l con-ux The output is: >*con | Using fast memcpy. >*con | Character size is 8x14, font has 256 characters >*con | VESA reports 800x600@16 1600bpl (0000) [4096kB] >*con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 > ... .... >*con | Mapping I/O UX video mem c0000000 => 00400000+000000 [4096kB] >*con | Using MMXEXT for colorspace transform >KERNEL: 7.2 (tcb=201c1000) killed: >Unhandled trap >EAX 00000025 EBX 0000122b ECX 0000000a EDX 00000000 >ESI 00000320 EDI 00b0d73c EBP 012ffda8 ESP 012ffda4 >EIP 00b0dc7f EFLAGS 00200206 >CS 0002 SS 007b DS 007b ES 007b FS 0000 GS 0000 >trap 13 (General Protection), error 00000402, from user mode >(internal event regarding IDT gate descriptor no. 0x80) The backtrace: >main // l4con/server/src/main.c >do_switch >vc_clear // vc.c >vc_fill >pslim_fill // pslim.c >sw_fill In "sw_fill", "vc->do_drty" equals 11589436, which seems invalid. Maybe, it should be NULL? Maybe, we should add "new->do_drty = fg_do_drty;" to line 402 in main.c? Regards, Wei

3 8

L4Linux freezes
by Vilmos Nebehaj 12 May '06

12 May '06

Hi, I've compiled and installed Fiasco and L4Linux-2.6 and it works, except that when I start a simple test program that creates lots of pthreads, the whole L4Linux task freezes (simply pthread_create() a thousand threads after each other is enough to reproduce the problem). I can ping the machine from another host, but can't login through ssh, the console becomes totally unresponsive, etc. At the same time, the following message appears in the log: simplets| ERROR: task #23 doesn't match: client 10.03, owner 0.0 l4lx | l4ts_create_task(): failed (server=7.00, ret=-3, exc=0) Other L4 tasks continue running uncluttered. Do you have an idea why this happens? Is this a bug in Fiasco, or is it a misconfiguration problem? -vili

2 2

Re: TCP/IP between L4Linux and L4 task
by Bjoern Doebel 11 May '06

11 May '06

2 1

Re: TCP/IP between L4Linux and L4 task
by Stefan Scheler 11 May '06

11 May '06

Hi, > Sure. Both, L4Linux and your app need to be compiled without native > hardware support. Instead, use a software network switch like the one > provided by l4/pkg/ore. L4Linux needs to compiled with the ORe driver > and your app needs to send/receive packets through ORe. Well, sounds good. So I'm currently trying to integrate the latest e1000 driver (v7.0.33) into ORe as my e1000 adapter is not supported by the current one but encountered the following problem: The updated driver wants to alloc some pages using alloc_page(). This results in a undefined reference to "_alloc_pages" when linking ore: ==> Linking ore LD_PRELOAD=/home/sts/L4_full/l4/tool/gendep/libgendep.so GENDEP_TARGET=ore GENDEP_BINARY=ld gcc -o ore ../../../../../lib/x86_586/crt0.o main.o openclose.o clients.o recv.o send.o netdevice.o irq_handling.o rxtx_string.o debug.o util.o events.o checksum.o xmit_lock.o worker.o local_deliver.o dummy_dsi.o -Wl,--whole-archive ../../../server/lib/net/OBJ-x86_586-l4v2/liblinuxnetdrv.a -Wl,--no-whole-archive -Ttext=0x01800000 -L../../../server/lib/linuxemul/OBJ-x86_586-l4v2 -L../../../../../lib/x86_586/l4v2 -L/home/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/drops/lib/x86_586 -L../../../../../lib -L/home/drops/lib -T../../../../../lib/x86_586/main_stat.ld -llinuxemul -levents -llinuxnetdrv -ldde_linux -lomega0 -lio -ll4rm -lore_server-worker -lore_server -lore_notify -llist_alloc -lparsecmdline /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libgcc.a -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot.o -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libgcc.a -luc_c -ll4sys -Ttext=0x01800000 -Wl,-gc-sections -Wl,--warn-common ../../../server/lib/net/OBJ-x86_586-l4v2/liblinuxnetdrv.a(e1000_main.o): In function `e1000_alloc_rx_buffers_ps': /home/sts/L4_full/l4/pkg/ore/server/lib/net/OBJ-x86_586-l4v2/../../../../server/include/linux_headers/linux/mm.h:454: undefined reference to `_alloc_pages' collect2: ld returned 1 exit status I suppose I have to link something else? Any hints appreciated. BTW is ORe an acronym for something? What does it stand for? Stefan

3 4

[Fwd: Re: TCP/IP between L4Linux and L4 task]
by Bjoern Doebel 11 May '06

11 May '06

3 4

Re: Fiasco hello world problem..
by raghavendra pai 11 May '06

11 May '06

---------------------------------------------------------------------- Message: 1 Date: Mon, 8 May 2006 13:48:25 +0200 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> Subject: Re: Fiasco hello world problem.. To: l4-hackers(a)os.inf.tu-dresden.de Message-ID: <20060508114825.GI1784(a)os.inf.tu-dresden.de> Content-Type: text/plain; charset=iso-8859-1 On Mon May 08, 2006 at 15:04:27 +0530, raghavendra pai wrote: > I was trying to run hello world program in Fiasco . > I downloaded the hello world from the CVS and did the steps as given in > the site. > > http://os.inf.tu-dresden.de/fiasco/use.html > > but I was trying to boot using my pc the hello world program . > the grub entry in grub.conf file was > > title hello world > module /fiasco-boot/main -nokdb > module /fiasco-boot/sigma0 > module /fiasco-boot/roottask > module /fiasco-boot/hello > > When i booted it the following was displayed > > Booting "Hello World" > module /fiasco/main -nokdb > > Error No:20 Multiboot kernel must be loaded before modules.. > > What is the cause of error.. >You forgot 'kernel bootstrap', i.e. the grub entry needs to look like: >title hello world > kernel /fiasco-boot/bootstrap > module /fiasco-boot/main -nokdb > module /fiasco-boot/sigma0 > module /fiasco-boot/roottask > module /fiasco-boot/hello I tried to locate the bootstrap file and i got this much entry /root/l4/l4/kernel/fiasco/build/.bootstrap.cc.d /root/l4/l4/kernel/fiasco/build/bootstrap.o /root/l4/l4/kernel/fiasco/src/boot/amd64/bootstrap.cc /root/l4/l4/kernel/fiasco/src/boot/amd64/bootstrap.ld /root/l4/l4/kernel/fiasco/src/boot/ia32/bootstrap.cc /root/l4/l4/kernel/fiasco/src/boot/ia32/bootstrap.ld /root/l4/l4/kernel/fiasco/src/kern/arm/bootstrap.cpp /root/l4/l4/kernel/fiasco/src/test/boottask/bootstrap-boottask.cc /root/l4/l4/tool/dice/bootstrap /root/l4/my/build/dir/.bootstrap.cc.d /root/l4/my/build/dir/bootstrap.o which of the one is to be copied into /fiasco-boot folder . I tried using /root/l4/l4/tool/dice/bootstrap but it tells no file is there Wht is the problem ? Am i entered the wrong Regards Pai

2 4

RE: L4Env and L4 version X.2.
by Volkmar Uhlig 11 May '06

11 May '06

> -----Original Message----- > From: Adam Lackorzynski > Sent: Wednesday, May 10, 2006 7:14 PM > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: L4Env and L4 version X.2. > > On Thu May 04, 2006 at 18:26:56 -0500, sethb wrote: > > Is there ongoing work to port L4Env to L4 version X.2? > > None that I know of. > > > How much work would it be? > > Quite a bit, I guess. If you have an IDL compiler you can > then go through every module and port it over, probably > redesigning some parts of it. The X.2 interface was designed such that a mapping of V2 -> X.2 is possible via wrapper functions. The fixed thread/task model can be emulated and ex-regs etc can be mapped as well. Main problem is the IDL compiler; not sure if Dice supports X.2... Ron? - Volkmar

3 2

L4Env and L4 version X.2.
by sethb 11 May '06

11 May '06

Hello Everyone, Is there ongoing work to port L4Env to L4 version X.2? How much work would it be? Thanks, Seth

3 2

The question about flexpage
by 강후영 11 May '06

11 May '06

HI! I have some questions about flexpage. What i want to do is to share memory between L4linux "A" and L4linux "B". So i tried to use flexpage method but this method is not available. Another tests sharing memory between L4linux "A" and L4 server are good work with flexpage. Is it possible to share memory between between L4linux "A" and L4linux "B"? best regards.

2 1

TCP/IP between L4Linux and L4 task
by Stefan Scheler 10 May '06

10 May '06

Hello, is it possible to connect from an L4Linux process to a FLIPS-based L4 task using TCP/IP? And if so, how? Thanks, Stefan

1 0

Fiasco hello world problem..
by raghavendra pai 08 May '06

08 May '06

Hi , I was trying to run hello world program in Fiasco . I downloaded the hello world from the CVS and did the steps as given in the site. http://os.inf.tu-dresden.de/fiasco/use.html but I was trying to boot using my pc the hello world program . the grub entry in grub.conf file was title hello world module /fiasco-boot/main -nokdb module /fiasco-boot/sigma0 module /fiasco-boot/roottask module /fiasco-boot/hello When i booted it the following was displayed Booting "Hello World" module /fiasco/main -nokdb Error No:20 Multiboot kernel must be loaded before modules.. What is the cause of error.. Regards Pai..

2 1

[EMSCB] L4Linux
by Oskar Senft 05 May '06

05 May '06

Hi! Nachdem alles lief habe ich nochmal ein Update der DROPS-Sourcen gemacht und bekomme jetzt folgenden Fehler beim Starten von L4Linux: l4lx | l4x_hybrid_return: Invalid hybrid return for 13.00 (0x00823630, d, 18 l4lx : e, 1, 804ba5e, eacff102)! l4lx | l4x_hybrid_return: Currently running: 00.00 Siehe auch angehängtes Logfile. Was ist denn diesmal falsch? Viele Grüße Oskar. PS: Sorry, irgendwie ging die Mail bei mir nicht richtig raus; falls doch: sorry für das Doppel-Posting! l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (osk@gamma) (gcc version 3.3.6) #1 Fri May 5 l4lx : 09:58:11 CEST 2006 l4lx | Binary name: vmlinuz26-l4linux-2.6.15-svpnserver l4lx | Kernel command line (8 args): mem=20M noreplacement root=1:0 load_ram l4lx : disk=1 ramdisk_size=15000 l4env_rd=svpn-ramdisk.gz panicblink=0 lang= l4lx : de l4lx | Image: 00400000 - 0072e000 [3256 KiB]. l4lx | Areas: Text: 00400000 - 00645000 [2324kB] (a bit longer) l4lx | Data: 00645000 - 00690520 [301kB] l4lx | Initdata: 00694000 - 006c2000 [184kB] l4lx | BSS: 006c2000 - 0072c0a0 [424kB] l4lx | l4lx_thread_create: Created thread 0f.03 (server) l4lx | l4env_linux_startup thread 3. l4lx | main thread will be 0f.03 l4lx | l4env_register_pointer_section: addr = 00692000 size = 638976 l4lx | sec-w-init: virt: 0x00692000 to 0x0072dfff [624 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 638976 Bytes l4lx | sec-w-init: 1: Phys: 0x001d4000 to 0x001df000, Size: 45056 l4lx | sec-w-init: 2: Phys: 0x0146f000 to 0x01500000, Size: 593920 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 20MB l4lx | Main memory: virt: 0x00800000 to 0x01bfffff [20480 KiB] l4lx | Main memory: Number of physical regions: 1, 20971520 Bytes l4lx | Main memory: 1: Phys: 0x03000000 to 0x04400000, Size: 20971520 l4lx | Filling lower ptabs... l4lx | Done (1069 entries). l4lx | l4env_rd_path: svpn-ramdisk.gz l4lx | Loading: svpn-ramdisk.gz l4lx | INITRD: Size of RAMdisk is 5015KiB l4lx | RAMdisk from 01c00000 to 020e5c00 [5015KiB] l4lx | l4lx_thread_create: Created thread 0f.04 (timer.i0) l4lx | l4lx_thread_create: Created thread 0f.05 (Idler) l4lx | l4x_hybrid_return: Invalid hybrid return for 13.00 (0x00823630, d, 18 l4lx : e, 1, 804ba5e, eacff102)! l4lx | l4x_hybrid_return: Currently running: 00.00

5 6

[EMSCB] L4Linux
by Oskar Senft 05 May '06

05 May '06

Hi! Nachdem alles lief habe ich nochmal ein Update der DROPS-Sourcen gemacht und bekomme jetzt folgenden Fehler beim Starten von L4Linux: l4lx | l4x_hybrid_return: Invalid hybrid return for 13.00 (0x00823630, d, 18 l4lx : e, 1, 804ba5e, eacff102)! l4lx | l4x_hybrid_return: Currently running: 00.00 Siehe auch angehängtes Logfile. Was ist denn diesmal falsch? Viele Grüße Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 500 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.16-l4 (osk@gamma) (gcc version 3.3.6) #1 Fri May 5 l4lx : 09:58:11 CEST 2006 l4lx | Binary name: vmlinuz26-l4linux-2.6.15-svpnserver l4lx | Kernel command line (8 args): mem=20M noreplacement root=1:0 load_ram l4lx : disk=1 ramdisk_size=15000 l4env_rd=svpn-ramdisk.gz panicblink=0 lang= l4lx : de l4lx | Image: 00400000 - 0072e000 [3256 KiB]. l4lx | Areas: Text: 00400000 - 00645000 [2324kB] (a bit longer) l4lx | Data: 00645000 - 00690520 [301kB] l4lx | Initdata: 00694000 - 006c2000 [184kB] l4lx | BSS: 006c2000 - 0072c0a0 [424kB] l4lx | l4lx_thread_create: Created thread 0f.03 (server) l4lx | l4env_linux_startup thread 3. l4lx | main thread will be 0f.03 l4lx | l4env_register_pointer_section: addr = 00692000 size = 638976 l4lx | sec-w-init: virt: 0x00692000 to 0x0072dfff [624 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 638976 Bytes l4lx | sec-w-init: 1: Phys: 0x001d4000 to 0x001df000, Size: 45056 l4lx | sec-w-init: 2: Phys: 0x0146f000 to 0x01500000, Size: 593920 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 20MB l4lx | Main memory: virt: 0x00800000 to 0x01bfffff [20480 KiB] l4lx | Main memory: Number of physical regions: 1, 20971520 Bytes l4lx | Main memory: 1: Phys: 0x03000000 to 0x04400000, Size: 20971520 l4lx | Filling lower ptabs... l4lx | Done (1069 entries). l4lx | l4env_rd_path: svpn-ramdisk.gz l4lx | Loading: svpn-ramdisk.gz l4lx | INITRD: Size of RAMdisk is 5015KiB l4lx | RAMdisk from 01c00000 to 020e5c00 [5015KiB] l4lx | l4lx_thread_create: Created thread 0f.04 (timer.i0) l4lx | l4lx_thread_create: Created thread 0f.05 (Idler) l4lx | l4x_hybrid_return: Invalid hybrid return for 13.00 (0x00823630, d, 18 l4lx : e, 1, 804ba5e, eacff102)! l4lx | l4x_hybrid_return: Currently running: 00.00

1 0

error build docs?
by Colin Burgess 05 May '06

05 May '06

What verison of latex do I need to build the docs? My suse 10 system seems to have pdfeTeX installed as latex, and this spits out a lot of errors... Thanks, Colin

2 2

[EMSCB] L4Linux + IPC
by Oskar Senft 03 May '06

03 May '06

Hi all! We are using different Deamons running in L4Linux providing IPC services to other L4 task. With the most current DROPS CVS checkout, the L4Linux user processes freeze completely, as soon as an IPC call is executed which causes the process to sleep (eg. DICE IPC server loop). The L4Linux kernel seems to run, as it answers Ethernet/IP "ping" requests. A connection to a running SSH daemon no longer is possible and active SSH connection freeze, too. => Only L4Linux userland processes are frozen ?!? This did not happen with other version of L4Linux (eg. from January) and does not depend on the program we run in L4Linux - it happens with different applications that provide IPC services. Is this a problem with our settings for L4Env / L4Linux? Or could it be a bug in L4Linux? Do you have a test program that should run? Regards Oskar.

5 8

MIKES 2006 - Call for Papers
by Ihor Kuz 03 May '06

03 May '06

Call for Papers: MIKES 2006 First International Workshop on MicroKernels for Embedded Systems To be held on August 15 2006, in Sydney, Australia, co-located with the 12th IEEE RTCSA (http://www.rtcsa.org). Microkernels and microkernel-based operating systems are experiencing an increased popularity in the field of embedded systems. Despite a period of low popularity a decade ago, there is a new realisation, in academia and industry, of the usefulness of microkernels. This is especially true in the embedded systems domain where the reduced size and increased dependability of microkernel-based systems have made them particularly attractive. The MIKES workshop will bring together researchers and developers from industry and academia to discuss: * emerging novel concepts, * analysis approaches, and * case studies in the area of microkernels. MIKES 2006 seeks papers that describe original research in the area of microkernels. This includes but is not limited to: * case studies * real-time behaviour * temporal analysis * formal/functional verification * portability * API proposals * security and safety Papers describing new ideas, promising approaches, experiences with practical systems are considered particularly appropriate. Papers will be 6 pages in IEEE conference paper format. Papers should be submitted electronically at http://www.easychair.org/MIKES2006/ in PDF or postscript format. The material must be unpublished and not under submission elsewhere. Proceedings will be published as a technical report by National ICT Australia (NICTA). IMPORTANT DATES Please note the submission deadline has been pushed back to disentangle it from concurrent deadlines. Submissions deadlines: May 20th Notification of acceptance: June 12th Camera ready papers: July 7th ORGANISERS Gernot Heiser, NICTA/UNSW, Australia Stefan M. Petters, NICTA/UNSW, Australia Ihor Kuz, NICTA/UNSW, Australia PROGRAM COMMITTEE Kevin Elphinstone, UNSW, Australia (chair) Andrew Tannenbaum, Vrije Universiteit, Amsterdam, Netherlands Gerwin Klein, NICTA/UNSW, Australia Hermann Haertig, TU Dresden, Germany Jonathan S. Shapiro, The Johns Hopkins University, USA Neil Audsley, University of York, UK Sebastian Schoenberg, Intel, Hillsboro, USA Volkmar Uhlig, IBM Watson, USA RELATED EVENTS Also of interest to some attendees of MIKES might be the International Workshop on System Verification (http://www.cse.unsw.edu.au/~formalmethods/events/svws-06/) being held in Sydney (just before MIKES and RTCSA) on August 7 and 8, 2006.

1 0

Getting Started...
by Colin Burgess 25 Apr '06

25 Apr '06

Hi All, I tried following the build instructions for building L4-Linux 2.6 but to no avail. I am running Suse Linux 2.6.13-15.8-default I checked out l4linux-2.6-env, and typed make config, and selected a DROPS_DIR of /home/cburgess/drops I then typed make and it eventually failed to find l4/sys/types.h trying to build log-server Are there other modules I need to checkout? Do I also need the l4linux-2.6 module, and should it be in the same toplevel dir as the l4linux-2.6-env module? Thanks, Colin

3 4

About l4.sec schedule
by Wei Shen 24 Apr '06

24 Apr '06

Hi, Is there any schedule for the first release of l4.sec kernel? Maybe, in several months? Or before the end of this year? How do you consider the compatibility of l4.sec and l4env? Thanks, Wei

1 0

fiasco-ux does not build
by Stefan Scheler 21 Apr '06

21 Apr '06

Hello, I get the following error building fiasco-ux: ==> Linking kernel.image /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ld: errno: TLS definition in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a(errno.o) section .tbss mismatches non-TLS reference in boot_info-ux.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [kernel.image] Error 1 make[2]: Leaving directory `/home/sts/hellomodule/l4/kernel/fiasco/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/sts/hellomodule/l4/kernel/fiasco/build' make: *** [all] Error 2 Real: 91.12s User: 74.26s System: 11.10s Percent: 93% Cmd: make So is this an gcc, glibc or binutils issue in the first place? And which versions are supposed to be able to build fiasco-ux? I'm using binutils 2.16.92 and glibc 2.4 and various gcc versions btw. Thanks in advance Stefan

2 5

L4Linux booting failed
by chenggh04＠st.lzu.edu.cn 18 Apr '06

18 Apr '06

Hi: I compile the L4Linux with plain mode! But when I boot L4Linux it is wrong. The information is as following: RNGR: Stage1 loading (hd0,1)/boot/fiasco_L4/sigma0 loading kernel (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -compseed The module 00:00300000-00390408: (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial overlaps with module loaded by bootloader at 00100000-001caec0: RMGR 00:0020f000-002661ac: (hd0,1)/boot/fiasco_L4/main -nowait 01:00267000-00275925: (hd0,1)/boot/fiasc_L4/sigma0 ==>02:00276000-004d8950: (hd0,1)/boot/fiasco_L4/vmlinuz.V2 no-scroll no 03:00409000-014d9000:(hd0,1)/boot/fiasco_L4/drops-rd.rd The reason for this error message is that the modules as loaded by GRUB Interface with their final position as defined by the linker. Most often you can solve this problem by inserting the command "modaddr 0x02000000" immediately as next line after the "kernel=" line of you menu.lst. Note that you have to use a special version of GRUB which is avaiable from http://os.inf.tu-dresden.de/drops/download.html The grub about L4Linux is : title fiasco_L4Linux root (hd0,1) kernel (hd0,1)/boot/fiasco_L4/rmgr -sigma0 task modname "vmlinuz" module modaddr 0x02000000 module (hd0,1)/boot/fiasco_L4/main -nowait -nokdb -serial_esc -comspee d 115200 -comport 1 module (hd0,1)/boot/fiasco_L4/sigma0 module (hd0,1)/boot/fiasco_L4/vmlinuz.V2 no-scroll no-hlt l4irqack=lin ux load_ramdisk=1 ramdisk_size=16384 root=/dev/ram module (hd0,1)/boot/fiasco_L4/drops-rd.rd I don't know what is wrong! Please help me! Thank you!

3 2

Strange L4Linux behavior
by Jugwan Eom 14 Apr '06

14 Apr '06

Hi, L4Linux fails to run correctly with the SCSI and network device under heavy load. My system has a Adaptec AIC7902 SCSI adapter (one SCSI hard disk is connected) and a E1000 network adapter. When the two devices is used at the same time under heavy load (some benchmarks to SCSI disk and transferring files using ftp), SCSI adapter driver prints error message and dumps device's status. and then system is not work. Actually, this error doesn't happen immediately after using the two devices. It works during some seconds (about 10~20secs). I could not capture all the message by SCSI adapter driver printed on console because it is very fast and vast. Anyway, the message means "PCI interrupt error". In L4Linux, the two devices share same IRQ number. IMHO, this is one of the source of this behavior. To use SCSI in L4Linux, I use dm_phys with '--isa=0x00800000' option. Two different IRQ handling methods (one thread per IRQ and multiple IRQs) got the same result. Is there anyone can help me? Regards, -- Jugwan Eom

2 3

Fwd: attempted fix for asm in oskit cpuid.c
by spooq 12 Apr '06

12 Apr '06

*sigh* ---------- Forwarded message ---------- From: spooq <spoooq(a)gmail.com> Date: Apr 11, 2006 11:12 PM Subject: Re: attempted fix for asm in oskit cpuid.c To: Ronald Aigner <ra3(a)os.inf.tu-dresden.de> I see dietlibc's printf is not given a good review on http://www.and.org/vstr/printf_comparison... On 4/11/06, spooq <spoooq(a)gmail.com> wrote: > Ok, I'll start using one of those. Is there any real difference between the two? > > Id also like to know what would need to be done to port L4Env to a new > arm-based arch, eg video card driver (not supported by existing linux > driver), touchscreen, mmu. Is there a list somewhere of interfaces > that need to be implemented? > > btw, just spooq is fine > > -- > spooq > > On 4/11/06, Ronald Aigner <ra3(a)os.inf.tu-dresden.de> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hello spoo(o)q, > > > > spooq wrote on 10.04.2006 19:36 this: > > > I tried to fix some errors in cpuid.c ... wouldnt rely on it, my asms > > > not very good and I havent tested it beyond seeing that it compiles. > > > Basically it just makes the asm respect gcc using the ebx as a pic > > > reg. Not sure about the \n\t stuff, it made it work tho. > > Nice job. However, oskit is no longer supported as a libc for L4Env > > applications. Please use either dietlibc or uclibc. > > > > Thanks, keep it up. > > Ron. > > - -- > > Mit freundlichen Gruessen / with regards > > ra3 @ inf.tu-dresden.de > > http://os.inf.tu-dresden.de/~ra3/ > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.2.2 (GNU/Linux) > > > > iD8DBQFEPCGivCdOf9l7ipgRAv9RAKCEMCFLEx1o0ehBLG+f5J+6I9/dIgCgwjdV > > SzC8KfKBWcPvexF8A8vzadw= > > =1wJw > > -----END PGP SIGNATURE----- > > >

3 2

Re: Fwd: attempted fix for asm in oskit cpuid.c
by spooq 12 Apr '06

12 Apr '06

I think this list needs to be fixing its reply-tos... I wasnt the only one caught by it... On 4/12/06, Steffen Liebergeld <s1010824(a)inf.tu-dresden.de> wrote: > On Tue, 11 Apr 2006 23:14:08 +0100, spooq <spoooq(a)gmail.com> said: > > *sigh* ---------- Forwarded message ---------- From: spooq > > <spoooq(a)gmail.com> Date: Apr 11, 2006 11:12 PM Subject: Re: > > attempted fix for asm in oskit cpuid.c To: Ronald Aigner > > <ra3(a)os.inf.tu-dresden.de> > > > > I see dietlibc's printf is not given a good review on > > http://www.and.org/vstr/printf_comparison... > > That comparison is very old, and they tested version 0.22 of > dietlibc. The current version is 0.29 (have a look at > http://www.fefe.de/dietlibc/). > > -- > Microsoft is simply one example of a proprietary software developer, a > software developer that tries to subjugate users to keep them divided > and helpless. -- Richard M. Stallman >

2 1

attempted fix for asm in oskit cpuid.c
by spooq 11 Apr '06

11 Apr '06

Hello list, I tried to fix some errors in cpuid.c ... wouldnt rely on it, my asms not very good and I havent tested it beyond seeing that it compiles. Basically it just makes the asm respect gcc using the ebx as a pic reg. Not sure about the \n\t stuff, it made it work tho. --- virgin_code/oskit/libkern/x86/cpuid.c 2006-04-02 15:41:55.000000000 +0000 +++ cpuid.c 2006-04-10 17:14:57.000000000 +0000 @@ -39,12 +39,17 @@ unsigned i; cicount++; - asm volatile("cpuid" + asm volatile( + "movl %%ebx, %%edi\n\t" + "cpuid\n\t" + "movl %1, %%ebx\n\t" + "movl %%edi, %%ebx\n\t" : "=a" (ci[0]), - "=b" (ci[1]), + "=r" (ci[1]), "=c" (ci[2]), "=d" (ci[3]) - : "a" (2)); + : "a" (2) + : "edi"); for (i = 0; i < 4; i++) { @@ -90,21 +95,29 @@ * CPUID is supported, so use it. * First get the vendor ID string. */ - asm volatile("cpuid" + asm volatile( + "movl %%ebx, %%edi\n\t" + "cpuid\n\t" + "movl %1, %%ebx\n\t" + "movl %%edi, %%ebx\n\t" : "=a" (highest_val), - "=b" (*((int*)(out_id->vendor_id+0))), + "=r" (*((int*)(out_id->vendor_id+0))), "=d" (*((int*)(out_id->vendor_id+4))), "=c" (*((int*)(out_id->vendor_id+8))) - : "a" (0)); + : "a" (0) + : "edi"); /* Now the feature information. */ if (highest_val >= 1) { - asm volatile("cpuid" - : "=a" (*((int*)out_id)), - "=d" (out_id->feature_flags) - : "a" (1) - : "ebx", "ecx"); + asm volatile( + "movl %%ebx, %%edi\n\t" + "cpuid\n\t" + "movl %%edi, %%ebx\n\t" + : "=a" (*((int*)out_id)), + "=d" (out_id->feature_flags) + : "a" (1) + : "ecx","edi"); } /* Cache and TLB information. */ -- spooq

2 1

Static Linux kernel, anyone?
by Stefan Schulz 09 Apr '06

09 Apr '06

Hi there I am currently trying to build a static linux kernel (one usable without libloader). I have read the earlier thread in this mailing list, but have run into some problems. I tried adding libraries to fix undefined references, since merely adding the static dependencies of libloader.s.so did not work. Finally, i hit upon references such as __l4sys_abs_ipc_fixup, which frankly looks like something i should not have to care about. ;) A quick scan through the libraries also seemed to indicate that it isn't even exported by any library. So, what am i doing so fundamentally wrong? Is there a way to build a static linux binary, or is it just intrinsically tied to the loader?

2 1

L4Linux and AMD64
by Zephiris 09 Apr '06

09 Apr '06

I haven't been looking around at things very long, but I was noticing, while Fiasco largely supports AMD64 processors in 64-bit mode, L4Linux appears to specifically avoid it. I couldn't find any references for this, will it ever be supported? It's something I was excited about/meaning to try, but as my system is setup with 64-bit binaries in mind, it looks like the only way to test it would be for L4Linux to support that.

2 1

Re: Building the environment fails
by Alexander Boettcher 05 Apr '06

05 Apr '06

1 0

Re: Building the environment fails
by Alexander Boettcher 05 Apr '06

05 Apr '06

1 0

Building the environment fails
by Stefan Schulz 05 Apr '06

05 Apr '06

Sorry for using this ML as my personal helpdesk, but i believe there is a problem in the build process for l4env. I checked the current version out from CVS, and used "make config" to configure. While "make" was running, the process failed with ... Compiling ARCH-all/libc/misc/internals/__uClibc_main.o LD_PRELOAD=/l4/tmp/l4/tool/gendep/libgendep.so GENDEP_TARGET=ARCH-all/libc/misc/internals/__uClibc_main.o GENDEP_BINARY=cc1 gcc -c -nostdinc -include ../../../lib/uclibc/ARCH-all/include/libc-symbols.h -DNDEBUG -D_LIBC -DSTATIC -DSYSTEM_x86_586 -DARCH_x86 -DCPUTYPE_586 -DL4API_ -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I../ARCH-x86/include -I../ARCH-all/include -I../../../../../include/x86 -I../../../../../include -I/usr/lib/gcc/i686-pc-linux-gnu/3.4.5/include -fno-builtin -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -fno-common /l4/tmp/l4/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/internals/__uClibc_main.c -o ARCH-all/libc/misc/internals/__uClibc_main.o /l4/tmp/l4/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/internals/__uClibc_main.c:2:49: l4/sys/consts.h: No such file or directory /l4/tmp/l4/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/internals/__uClibc_main.c:15: error: `L4_PAGESIZE' undeclared here (not in a function) make[4]: *** [ARCH-all/libc/misc/internals/__uClibc_main.o] Error 1 make[4]: Leaving directory `/l4/tmp/l4/pkg/uclibc/lib/uclibc/OBJ-x86_586' make[3]: *** [OBJ-x86_586] Error 2 make[3]: Leaving directory `/l4/tmp/l4/pkg/uclibc/lib/uclibc' make[2]: *** [virt_dep] Error 2 make[2]: Leaving directory `/l4/tmp/l4/pkg/uclibc' make[1]: *** [uclibc.headers] Error 2 make[1]: Leaving directory `/l4/tmp/l4/pkg' make: *** [pkg] Error 2 Even if i "fixed" this error (by manually defining L4_PAGESIZE", similar problems crept up all over the build, far too many to manually fix. I tried this build on an IBM T43, using current sources, gcc3.4.5 and make 3.80 Is the build process really broken, or am i doing something wrong?

1 0

Make hello stops with an error
by Ricard de Benito Panillo 05 Apr '06

05 Apr '06

Hi, the following error arises making 'hello': cc1: note: obsolete option -I- used, please use -iquote instead In file included from ../libkern/x86/base_cpu_init.c:22: ../flux/x86/base_trap.h:105: error: array type has incomplete element type make[3]: *** [base_cpu_init.o] Error 1 gcc version 4.0.2 20051125 (Red Hat 4.0.2-8) on Fedora Core 4 Any hint? it seems that the compiler versions is newer than expected. Best regards, Ricard de Benito

2 1

I have new problem!
by chenggh04＠st.lzu.edu.cn 04 Apr '06

04 Apr '06

>Can you please give more details on what you did? I cannot really say >anything helpful on a generic "it doesn't work" statement. Thank adam lackorzynski(<adam(a)os.inf.tu-dresden.de>) for your help. Now I resolve last problem and the compilation fiasco in slackware (last time is debian) is ok. The execution of hello example is also good! Now I am ready for experiencing the fiasco-ux. I compile the package but runs badly. The error information is as follows: Fiasco-UX on Linux 2.4.31 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00094e60 [sigma0-ux] Failed to open file: roottask But according to the instructions of Fiasco-ux website the information should be like this: Fiasco-UX on Linux 2.4.31 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00070000-0x000955c0 [sigma0-ux] Loading Module 0x00100000-0x001b9ce0 [rmgr-ux] ... The addresses of the sigma0-ux are different! My configuration of fiasco is as follows: Target System Options >(UX) Target Platform (IA-32) Target CPU Family (K7) Target processor >(L4V2) Kernel ABI Version [ ] TCB size of 4k [ ] Fine-grained CPU time [Y] Graphical console (requires SDL library!) [Y] Network support Kernel Debugging >[Y] Generate inline code [ ] Do not compile assertions [Y] Compile without frame pointer [ ] Measure stack depth of threads [ ] Sanity checks in low level allocator [ ] Sanity checks at syscall entry/exit [Y] Compile with gstabs+ debugging information [Y] JDB kernel debugger [ ] JDB extended logging [ ] JDB accounting [ ] Miscellaneous JDB modules (ANY) Runtime warning level Compiling and Building >gcc C compiler g++ C++ compiler [ ] Verbose build process [ ] Do additional checks at build time and then make VERBOSE=@ according to the instruction of Fiasco-ux website but I don't find the option "Assembler IPC shortcut" . Please help me! Cheng

4 3

Why don't I have /bin/ directory in L4
by chenggh04＠st.lzu.edu.cn 03 Apr '06

03 Apr '06

Hi,Everybody: I am a beginner for L4. when I compile the L4 without any errors but finally I don't have the bin directory which inlcudes hello, rmgr and sigma0. Maybe I think there is lack of some packages in my install package. But the package is downloaded from the Fiasco official WebSite. I don't know why! Please help me! Chenggh

2 1

Lovelace Web-Site
by Frederic BOYER 30 Mar '06

30 Mar '06

By the way, Lovelace has now a little web-site (I've just began to do it) and there is a mailing list. Please visit The Lovelace web-site. http://lovelace.rochebrune.org Regards, Frédéric. "This message, including any attachments may contain confidential and privileged material; it is intended only for the person to whom it is addressed. Its contents do not constitute a commitment by Credit Agricole Cheuvreux except where provided for in a written agreement. Credit Agricole Cheuvreux assumes no liability or responsibility for the consequences arising out of a delay and/or loss in transit of this message, or for corruption or other error(s) arising in its transmission and for any misuse or fraudulent use which may be made thereof. If you are not the intended recipient, please contact us and abstain from any disclosure, use or dissemination. To the extent that this message contains research information and/or recommendations, these are provided on the same basis as Credit Agricole Cheuvreux's published research and the recipient must have regard to all disclosures and disclaimers contained therein."

2 1

L4Linux without libloader?
by Daniel Vandersee 23 Mar '06

23 Mar '06

Hi there, is it possible to compile L4Linux without the need of libloader.s.so (e.g. by using other libs) to have it statically linked? Thanks, Daniel

4 7

Reloading L4Linux problem
by Jugwan Eom 17 Mar '06

17 Mar '06

Hi. I encountered problems reloading L4Linux. After shutdown loaded L4Linux, I tried reloading the L4Linux (same configuration) using 'l' command in l4con but it didn't work(network device probe failed, lost ide disk interrupt). During booting L4linux showed "irq_thread: RMGR denied IRQ 14: code 0x1". Because I use l4con, I can see the system memory on bottom right. After shutdown loaded L4Linux, it still shows the same value before. Using 'a' command in l4con memory region used by previous L4Linux seem to be still allocated. IMHO, this is the source to fail to reloading L4Linux. Because memory region by used L4Linux includes the DMA region, reloading L4Linux cannot control the system device. Is this a bug in L4Linux or other L4Env server? Also, see the attached log. Best regards, -- Jugwan Eom

4 7

What is trampoline.S for?
by BVK Groups 17 Mar '06

17 Mar '06

Hi, Whenever i try to start executing first thread in a new address space, its pager is receiving pagefault (at 0x0000002b), eventhough none of the mapped code touches that place. Why is it? I found out that CHACMOS is mapping trampoline.S at that address. I What is this trampoline.S is for? I tried to understand trampoline.S code, but i couldn't. I didnt find any FAQ entry regarding this. Can anyone please help me here? NOTE: I am using pistachio-0.4 Thanks, -bvk

4 4

Announce: OS Group of TU Dresden (TUD:OS) releases Live-Demo CD
by Norman Feske 13 Mar '06

13 Mar '06

The OS Group of Technische Universität Dresden (TUD:OS) has released a live demo CD of our operating system project. Some highlights of the Demo CD include a new approach for securing graphical user interfaces called Nitpicker, multiple L4Linux kernels running at the same time on top of a L4/Fiasco, a survey on our reuse of device drivers on the TUD:OS platform, native Qt-applications, the DOpE windowing system and a prototype of a secure E-commerce application based on TUD:OS. More information, an ISO image, and screenshots are available at the demo CD website: http://demo.tudos.org Norman Feske TU Dresden Operating Systems Group

1 0

some weird performance result
by Sungkwan Heo 11 Mar '06

11 Mar '06

Hi all, I measured network I/O performance of native Linux-2.4 and Fiasco-1.2+L4Linux-2.4 using the netperf benchmark. The TCP streaming test results are following: Recv Socket Size bytes: Linux = 87380, L4Linux = 87380 Send Socket Size bytes: Linux = 16384, L4Linux = 16384 Send Message Size bytes: Linux = 16384, L4Linux=16384 Elapsed Time secs: Linux = 10.002, L4Linux = 10.002 Throughput MBytes/s: Linux = 11.22, L4Linux = 11.206 Utilization Send local % S: Linux = 11.359, L4Linux = 4.35 ... The last 2 lines indicates the network I/O throughput and CPU utilization for the network I/O. One weird thing is the L4Linux CPU utilization. It spent much less CPU cycles than the native Linux did. In my humble opinion, it is normal case because the L4 Fiasco schedules the L4Linux application (netperf) as a L4 process and L4Linux kernel doesn't have correct CPU usage information of the application. Is it correct?

2 1

config for 2 L4Linux instances
by Sungkwan Heo 11 Mar '06

11 Mar '06

Hi all, Is there anyone who succeeded in running multiple L4Linux (2.4 or 2.6) instances on native fiasco, not fiasco-ux? If so, could I share the configuration and howto? Especially, I want to boot L4Linux-2.4 mounting root disk partition where RedHat 9.0 is already installed. I expect that another L4Linux-2.4 image can be loaded MODFS or TFTP. However I can't figure out how I can setup my L4 box to load any application that I want from where I want. Another issue is the second L4Linux need another root partition or not. Is it possible to the first L4Linux use hard disk partition and the second one use ramdrive? And as far as I know, the main purpose of fiasco-ux is just emulation and not real solution that has similiar architecture to WMware. right?

2 1

Update on NICTA's secure embedded L4 project
by Kevin Elphinstone 10 Mar '06

10 Mar '06

Hi All, I'm please to announce the release of more information on the secure embedded L4 (seL4) project, including a reference manual of the experimental kernel API. You can get more info on the project's web page at http://www.ertos.nicta.com.au/research/sel4/ cheers - Kevin Dr. Kevin Elphinstone Senior Researcher and seL4 Project Leader National ICT Australia

1 0

L4.Sec Implementation
by Anton Soppelsa 08 Mar '06

08 Mar '06

Hi, My name is Anton Soppelsa and I'm doing a PhD course at the "Istituto Gas Ionizzati" (Ionized Gas Institute) in Padova (Italy). I am a control system engineer and at the moment I'm involved in some work with a Motorola mv5500 Single Board Computer installed in a VME rack. As I am a free software supporter and I don't like too much our working developing platform as is based on the proprietary VxWorks operative system. For this reason I am interested in GPL-ed real time operative systems. I read the specification of the L4.Sec system, but unfortunately I am not able to fully understand the concept of capability space. Probably this happens because I am one of those that need to see how things are made to catch the concept of what they really are. Even if I don't think, at this moment, that L4.Sec is exactly what I need (because speed is my real priority), I'm anyway curious about how it works. So if your new project is at a point where you actually have some structures, or classes implementing the capability space, will your team be so kind to send me that piece of code? I will read it with interest in my spare time. Many thanks, Anton

2 2

L4::Pistachio ARM GNU toolchain
by Shakthi Kannan 08 Mar '06

08 Mar '06

Greetings! I have downloaded pistachio-0.4.tar.bz2. I would like to know which GNU ARM toolchain needs to be used to cross-compile the above for ARM. Thanks, SK -- Shakthi Kannan, MS Software Engineer, Hexaware Technologies [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

l4linux-2.6 build error
by Sungkwan Heo 07 Mar '06

07 Mar '06

Hi all, Though I had some hard time to run l4linux-2.6, I still get build error. When I build l4linux-2.6, the following error occured. As far as I know, a global variable (xtime) was defined twice. First, l4/pkg/generic_io/lib/clientlib/ARCH-x86/io_info.S Second, some header file included in l4linux-2.6/kernel/sysctl.c Any suggestion will help me much! $ cd l4linux-2.6 $ make menuconfig ... $ make ... CC arch/l4/l4lxlib/l4env/task.o CC arch/l4/l4lxlib/l4env/thread.o AR arch/l4/l4lxlib/l4env/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 /home/drops/l4linux-2.6-env/l4/lib/x86_586/l4v2/libio.a(io_info.o)(.ros pace+0xc): In function `xtime': : multiple definition of `xtime' kernel/built-in.o(.bss+0x9650):/home/drops/l4linux-2.6-env/l4linux-2.6/ kernel/sysctl.c:1666: first defined here make: *** [.tmp_vmlinux1] Error 1 $

2 4

make hello stops with an error
by Delitsyn Igor 03 Mar '06

03 Mar '06

Hi, I try to compile L4 kernel on x86 just to start with, but ¨make hello¨ results in an error in linking as follows: /usr/bin/ld: cannot find -lroot.o I was unable to locate this module manually. Any ideas? Thanks for taking a look at it. Best regards, Igor

3 2

Re: PowerPC interrupt setup
by Kay-Uwe.Genz 03 Mar '06

03 Mar '06

Hi Joshua, hi @ all, I start this year with first experiments in implementation of an kernel (based on L4.X2) on PowerPC, mostly to learn more about PowerPC/HW and design philosophies. So I read your posting with attention and have some questions ... and hope your answers would made it easier for my to understand. You recommend "enabling virtual addressing immediatly". Did I understand it right, that you use virtual memory in kernel mode? Is this only for protection or means this, the kernel memory is vitual? There are other kernels using virtual memory in kernel mode? My design doesn't have a kernel section in the tasks address space (on 32 bit machines a task is 4GB). I agonise to solve some of the problems with this design. In the case StringItems used to send Msg's from one space to another (means copy the information in the kernel) the message buffer on both sides can scattered and located across page bounderies. Handling this seems easier if the kernel has the same view to memory and pionters to memory regions (buffers) but this destroy my approach of lockfreeness, because the String Buffers in different tasks can by overlap or locate at the same virtual adress. (The sendphase of StringItems should by interruptable and at any time it should by possible to handle as much as possible StrinItem sends in the same time.) Handling this in kernel with the view of real memory avoid overlapping buffer regions from different threads. Do you see the issue like I and is there a solution I didn't see? As I see on the homepage, the kernel runs on a G3 (aka PPC750). So you use the normal hardware table search? Thanks for helping. Regards Kay-Uwe. Am 07.02.2006 um 17:35 schrieb Joshua LeVasseur: > > The PowerPC jumps to predefined code locations when delivering > interrupts and traps, starting at 0x100 (with virtual addressing > disabled). You only need to install code at those locations; > PowerPC has no interrupt descriptors. I recommend enabling virtual > addressing immediately, even while handling page faults; I've seen > other kernels implement excessive logic in assembler, executing in > physical mode; that isn't necessary. I enable virtual addressing > within 19 or so instructions. > > Maybe try volume 3 here: > http://www-128.ibm.com/developerworks/eserver/articles/archguide.html > I've never read those documents; I used the 603 architecture manual > when porting L4Ka::Pistachio. > > Consider reading about how I made my L4Ka::Pistachio PowerPC > implementation frigging fast: > http://l4ka.org/projects/pistachio/powerpc/ppc.pdf > It covers: > - Fast system calls (without wasting a register for a system call > number, unlike all other kernels out there that I've seen) > - Fast address space ID management (the way ASIDs were meant to be > managed on the PowerPC, and again, the other kernels out there are > doing it wrong) > - Fast page hash management. Most kernels perform O(n) searches > through the page hash when manually locating an entry. I instead > perform O(1) lookups. > > I recommend that you avoid looking at open source kernels for > guidance. They don't push the limits of PowerPC. > > -Josh > > > > On Feb 7, 2006, at 16:18, Matthias Lange wrote: > >> Hi, >> >> I am stuck with porting the Fiasco microkernel to PowerPC. I can't >> find any clear documentation about how to setup a interrupt >> description table. So, these are my questions: >> >> 1. How is an interrupt descriptor formed on PowerPC? How does it >> look? >> 2. Where (in memory) do I need to store these descriptors? >> >> The IBM PowerPC Programming Manual gives me a good overview but no >> information on how to implement it. Can someone please point me to >> some meaningful documentation? >> >> Regards, >> >> Matthias. >> > > >

2 2

trying to launch a server
by Xavier Grave 28 Feb '06

28 Feb '06

Hi all, Always playing with an OS implementation in Ada, I would like to launch a task in an new address space. I have read the example from l4uman-x2.pdf but threse is still some questions for me : - I need to send the task an instruction pointer and stack pointer but in which address space ? - does l4 translate it for me ? - I got a start address (I fink hardware address) from boot info for the server I want to launch does this pointer need translation ? Thanks in advance for any answer (or full example :) xavier PS: I have read part of the iguana code, but it is two much complicated for me for the moment...

1 0

Question about UTCB
by Jonathan S. Shapiro 24 Feb '06

24 Feb '06

This is a naive, simple question -- I looked in the reference manual and the answer did not jump out at me. When a process is preempted, where are its registers stored? Are the stored in the UTCB, or are they stored in some data structure that is only accessible to the kernel? Thanks shap

3 5

are there any more detailed document?
by Liu Jian 17 Feb '06

17 Feb '06

Hi all, I find the course "Microkernel Construction" is a good choice to newmen to Fiasco. If there was any detailed document about the design of Fiasco with it, it will be wonderful. If you know such documents, pls let me known and I will appreciate your direction. Moreover, I plan to give a series of seminars about Fiasco in our group based on the course documents. I also wonder how the teachers at Dresden to carry out the curse. cheers:) Liu Jian

1 0

PowerPC interrupt setup
by Matthias Lange 08 Feb '06

08 Feb '06

Hi, I am stuck with porting the Fiasco microkernel to PowerPC. I can't find any clear documentation about how to setup a interrupt description table. So, these are my questions: 1. How is an interrupt descriptor formed on PowerPC? How does it look? 2. Where (in memory) do I need to store these descriptors? The IBM PowerPC Programming Manual gives me a good overview but no information on how to implement it. Can someone please point me to some meaningful documentation? Regards, Matthias.

3 2

Ore on Intel Pro/1000
by Michael Scheibel 07 Feb '06

07 Feb '06

Hello list, I am running Ore on native HW and Intel(R) PRO/1000 Network Connection. Ore seems to recognize the network card correctly but quits when I try to setup eth0. L4Linux error message: eth0: Overwriting IRQ type for IRQ 0 with l4ore type! eth0: request_irq(0, ...) failed. Any hint highly appreciated. Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel(a)sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.

3 6

Fiasco and L4Linux for ARM926 (Nokia770)
by Delitsyn Igor 07 Feb '06

07 Feb '06

Hi fellow L4 hackers, We´d like to port Fiasco kernal to ARM926 processor, which is used in Nokia770 internet tablet device. Later we plan to run L4Linux on the device as well. We would really appreciate any recommendations from you on how to proceed and links to necessary resources, especially from those who made the porting to SA1110 and PXA. Best regards, Igor

3 2

Ada L4
by Frederic BOYER 03 Feb '06

03 Feb '06

Hi L4'er ... We have began to rewrite a L4 lib with Ada and by now : - We have all L4 types (threads, ...) - We make system calls - We Allocate memory - We have a minimal support exceptions. Currently we are working on tasks. We'd like to get a little help from L4 teams in order to make our OS design. If some peoples in the L4 team have some experience with L4, please contact me. Regards, Frédéric. "This message, including any attachments may contain confidential and privileged material; it is intended only for the person to whom it is addressed. Its contents do not constitute a commitment by Credit Agricole Cheuvreux except where provided for in a written agreement. Credit Agricole Cheuvreux assumes no liability or responsibility for the consequences arising out of a delay and/or loss in transit of this message, or for corruption or other error(s) arising in its transmission and for any misuse or fraudulent use which may be made thereof. If you are not the intended recipient, please contact us and abstain from any disclosure, use or dissemination. To the extent that this message contains research information and/or recommendations, these are provided on the same basis as Credit Agricole Cheuvreux's published research and the recipient must have regard to all disclosures and disclaimers contained therein."

1 0

SPEC CPU 2000 Benchmarks
by Julian Grizzard 31 Jan '06

31 Jan '06

Hi all, Does anyone have any recent SPEC 2000 benchmarks comparing Linux to L4Linux running on Fiasco? I'm getting surprisingly high results running on a Pentium IV 2.53 GHz forcing memory to be 256M in both systems. I haven't even tweaked all the performance critical options in L4 to the "off" state yet. Thanks! Julian

4 5

gdb remote debugging + shared video ram question
by s6994440＠mail.inf.tu-dresden.de 30 Jan '06

30 Jan '06

Hello, I'm a l4 beginner. So I have 2 questions to standard issues (guess) . 1.: I followed the Building & Using Fiasco html to the debugging point. - I removed the -nowait Kerneloption - I edited the .gdbinit file with > file ../build_x862/kernel.image (current compiled kernel) > target remote /dev/ttyS0 (debugging on COM1) - When fiasco comes up, I start gdb and immediatly after that my testmachine reboots, when it comes back up everytime i type c in my host debugger it reboots again. - When I use > file ../build_x86/kernel.image, a kernelimage I built some time ago, gdb says > 0x00000000 in ?? () and again, when I press c it reboots. - There was no KDB::Init- Message at all. - I expected the kernel to continue normal operation like with the "nowait" option after pressing c in the debugger..., Am I wrong ? - Kernelconfiguration in globalconfig.out - My menu.lst: 38 title fiasco 39 kernel $(P)/bootstrap 40 modaddr 0x02000000 41 module $(PF)/fiasco-o -comport 1 -comspeed 115200 42 module $(P)/sigma0 43 module $(P)/roottask 2.: My testmachine is an Advantech PCM 5820. It shares the video mem with normal RAM. When I boot up DOpE I get several error messages (see file error.txt) The following lines put L4io about my video: io | 40800000-40ffffff : Cyrix Corporation 5530 Video [Kahlua] io | WARNING: Cannot handle memory 40800000-40ffffff for device 1078:0104 So I guess it couldn't get the RAM it wanted to ? When I tried to boot up with L4Con these messages appeared : con | Mapping I/O video mem 40800000 => 00400000+000000 [4096kB] con | [8.2] l4con/server/src/con_hw/iomem.c:61:map_io_mem(): con | I/O video memory address is below 2GB (0x80000000), con | don't know how to map it as device super I/O page. So I guess my video mem is mapped to 0x00400000 via Hardware ? DM_Phys has allocated this AREA (0x00400000-0x00800000). So I tried to reserve this area with its --reserve option. Plus I dissabled L4log for the moment because it was mapped into the AREA by the roottask. But it didn't help, maybe already sigma0 has this area, so i cannot be remapped ?! So I read a little along the source of sigma0, but didn't find anything yet... Hopefully you can help me ?! Thanks, Marcus

2 1

problems with drops <math.h> and '-lm' linkage
by Vladimir Nikolov 30 Jan '06

30 Jan '06

Hello, I have problems with drops and the std C mathematical library. For my project, I am working on a package which is linked against a static user-library. This library on itslef uses <math.h>, e.g. the functions sin, cos, pow, a.s.o. ..., and is linked by gcc with "-lm". When linking the executable of the package without including "-lm" in "LIBS" of the package Makefile, simmilar output messages are generated: ../../../../../lib/x86_586/l4v2/my-user-lib.a(src_file.o): In function `myFunc': src_file.c:(.text+0x466): undefined reference to `log' src_file.o:(.text+0x477): undefined reference to `log' src_file.o:(.text+0x490): undefined reference to `pow' src_file.o:(.text+0x490): undefined reference to `sqrt' src_file.o:(.text+0x490): undefined reference to `cos' src_file.o:(.text+0x525): undefined reference to `__assert_fail' ... I am linking in "l4env_freebsd" mode and the appropiate user-library is found, as I assume by the output message, but not the implementation of the <math.h> functions, which should come with a libm.a ... Linking with "-lm" in the freebsd mode sends the following output: ../../../../../lib/x86_586/l4v2/my-user-lib.a(src_file.o): In function `myFunc': src_file.c:(.text+0x525): undefined reference to `__assert_fail' /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o): In function `__kernel_standard': : undefined reference to `__errno_location' /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o): In function `__kernel_standard': : undefined reference to `__errno_location' /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o): In function `__kernel_standard': : undefined reference to `__errno_location' /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o): In function `__kernel_standard': : undefined reference to `__errno_location' /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o): In function `__kernel_standard': : undefined reference to `__errno_location' /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o):: more undefined references to `__errno_location' follow /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/../../../libm.a(k_standard.o): In function `__kernel_standard': : undefined reference to `__assert_fail' collect2: ld returned 1 exit status Does anyone have any solution for this problem? I thought about searching another math library, which does not use standard C math functions and trying to compile it as a library in a drops package by including 'lib.mk' in the appropiate Makefile. I am not really shure, if this would really solve my problem, or just keep me fighting with other incompatibility problems. Is there no other possibility to use mathematical functions in any drops application, or perhaps another linkage concept or configuration? I hope for some replies ;-) Vladimir

2 2

hello and question from a l4 beginner
by Xavier Grave 26 Jan '06

26 Jan '06

Hi everybody, I have just discovered l4 because I have started to translate a simple OS in Ada (SOS from http://sos.enix.org), and now I would like to develop an Ada interface to L4. Actually I have compiled pistachio and I run a very simple Ada executable on top of it. There something strange with my executable : it sends page fault error to sigma0 (label 0xffe5 and 0xffe2) even before I start to execute code... Does somebody have an idea ? Thanks in advance, xavier

2 5

Instances of lazy scheduling and timeslice donation in L4 implementations
by Sergio Ruocco 25 Jan '06

25 Jan '06

According to Gernot's "Inside L4/MIPS" Version 2.19 of January 30, 2001 https://www.ertos.nicta.com.au/publications/papers/Heiser:IL4.abstract.pml Section 2.1.2 (page 7): Time-slice donation can happen in one of two ways: • explicitly via the thread switch system call. This call donates the remainder of the caller’s current time [...] • implicitly via IPC. IPC operations are often accompanied by a context switch from the sender to the receiver, in which case the sender’s current time slice is implicitly donated to the receiver. and Section 5.2.3: " The other point to note is that, while the sender thread is put into the busy list to allow it to be scheduled again, the context switch to the receiver is actually performed without any scheduling (lazy scheduling [Lie93]). The receiver simply continues in the remainder of the sender’s time slice. This is an instance of time-slice donation in L4." I assume that the above described cases still hold for most, if not all, the current L4 implementation(s). The IPC time-slice donation is a classic optimisation, and ThreadSwitch() is part of the L4 specification. I have few Qs: 1) Besides the ones above, are there in the current L4 implementations other instances of: 1.1) time-slice donation ? 1.2) lazy-scheduling ? 2) If yes, do they affect or are affected in special ways by [kernel] interrupt threads ? (I think not, but with implementation/optimisations you never know...) Thanks Sergio -- -- http://www.cse.unsw.edu.au/~sruocco/ ERTOS Researcher Lecturer National ICT Australia Ltd. University of New South Wales This email and any attachments are confidential. They may contain legally privileged information or copyright material. You should not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. This notice should not be removed.

6 19

log_net does not work
by Arthur Mielimonka 24 Jan '06

24 Jan '06

Hi, To analyze real-time processes I collect data in memory and after completition I want to transfer the data via the log_net server. For this reason, I compiled the package log_net with INITDRV(vortex) (network card is a 3com905). Compiling works fine, but I get this error message on startup: log | Initializing device ... log | BIOS mapped to 0xe0000 log | pcibios_init : OSKIT PCI BIOS revision 1.0 log | PCI: Probing PCI hardware log | pci: out of memory log | scsi : 0 hosts log | scsi : detected total log | [6.1] log_net/server/src/tcpip.c:100:init_ethernet(): log | Error: Error initializing etherdriver vortex. log | log | Probing devices... log | Probing done. log | Current hardware tree: log | Initializing network code... log | can't allocate callout queue! log | log | Backtrace: fp=37164c log | 00355524 0034bcff 0034bb8f 003332f5 0032f13a 00301042 00300c20 log | Exited with return code 1. log | Looping forever... My GRUB Menu: title RTXviDE standalone log to network (131.188.36.186) kernel /drops/l4/bin/x86_586/l4v2/rmgr -sigma0 modaddr 0x02000000 module /drops/l4/kernel/fiasco/build/main -noserial -nowait -nokdb module /drops/l4/bin/x86_586/l4v2/sigma0 module /drops/l4/bin/x86_586/l4v2/names module /drops/l4/bin/x86_586/l4v2/log_net -net -local -ip 131.188.36.186 -verbos e -buffer 4096 module /drops/l4/bin/x86_586/l4v2/dm_phys module /drops/l4/bin/x86_586/l4v2/simple_ts module /drops/l4/bin/x86_586/l4v2/RTXviDE -type 0 -w 176 -h 144 -frames 381 Thanks for help, Arthur

1 0

Ada on L4 questions ...
by Frederic BOYER 23 Jan '06

23 Jan '06

Hi L4 Teams ... Have somebody got any experience with Ada in the L4 teams I've got a few question about the design of an Ada on L4 based operating system (specialy how to impléments Ada Task, Memory and Exception on top of L4) thanks, Regards, Frédéric BOYER. Lovelace Team. "This message, including any attachments may contain confidential and privileged material; it is intended only for the person to whom it is addressed. Its contents do not constitute a commitment by Credit Agricole Cheuvreux except where provided for in a written agreement. Credit Agricole Cheuvreux assumes no liability or responsibility for the consequences arising out of a delay and/or loss in transit of this message, or for corruption or other error(s) arising in its transmission and for any misuse or fraudulent use which may be made thereof. If you are not the intended recipient, please contact us and abstain from any disclosure, use or dissemination. To the extent that this message contains research information and/or recommendations, these are provided on the same basis as Credit Agricole Cheuvreux's published research and the recipient must have regard to all disclosures and disclaimers contained therein."

1 0

Instances of lazy scheduling and timeslice donation in L4 implementations
by Sergio Ruocco 20 Jan '06

20 Jan '06

According to Gernot's "Inside L4/MIPS" Version 2.19 of January 30, 2001 https://www.ertos.nicta.com.au/publications/papers/Heiser:IL4.abstract.pml Section 2.1.2 (page 7): Time-slice donation can happen in one of two ways: • explicitly via the thread switch system call. This call donates the remainder of the caller’s current time [...] • implicitly via IPC. IPC operations are often accompanied by a context switch from the sender to the receiver, in which case the sender’s current time slice is implicitly donated to the receiver. and Section 5.2.3: " The other point to note is that, while the sender thread is put into the busy list to allow it to be scheduled again, the context switch to the receiver is actually performed without any scheduling (lazy scheduling [Lie93]). The receiver simply continues in the remainder of the sender’s time slice. This is an instance of time-slice donation in L4." I assume that the above described cases still hold for most, if not all, the current L4 implementation(s). The IPC time-slice donation is a classic optimisation, and ThreadSwitch() is part of the L4 specification. I have few Qs: 1) Besides the ones above, are there in the current L4 implementations other instances of: 1.1) time-slice donation ? 1.2) lazy-scheduling ? 2) If yes, do they affect or are affected in special ways by [kernel] interrupt threads ? (I think not, but with implementation/optimisations you never know...) Thanks Sergio -- -- http://www.cse.unsw.edu.au/~sruocco/ ERTOS Researcher Lecturer National ICT Australia Ltd. University of New South Wales This email and any attachments are confidential. They may contain legally privileged information or copyright material. You should not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages. We do not accept liability in connection with computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment. This notice should not be removed.

1 0

a error when compling fiasco-1.2
by Liu Jian 18 Jan '06

18 Jan '06

Hi All, there is a error when compling fiasco-1.2 on my pc. I do it following the course "Microkernel Construction Exercises": 1)Download and extract the Fiasco kernel from here <http://os.inf.tu-dresden.de/fiasco/download/fiasco-1.2.tar.gz>. 2)Switch to the directory *fiasco-1.2/l4/kernel/fiasco/* and create a build directory using *make BUILDDIR=build_ux**. 3)Run *make config* in this build directory and select UX as target platform (in 'Target System Options'). Leave the configuration menu with 'x'. 4)Build the kernel using *make*. The error as following: ........ ........ ... Making thread-msg-ux.o ... Making thread-log.o ... Making thread-debug.o ... Making kernel_thread.o /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:104: error: parse error before `)' token /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ISO C++ forbids declaration of `init_switch_time' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1039: error: candidate is: void Context::init_switch_time() /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1039: error: candidate is: void Context::init_switch_time() /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: declaration of `int Context::init_switch_time()' outside of class is not definition /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:117: error: ISO C++ forbids declaration of `init_workload' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:119: error: parse error before `while' /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ISO C++ forbids declaration of `puts' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ` int puts' redeclared as different kind of symbol /usr/include/stdio.h:589: error: previous declaration of `int puts(const char*) ' /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: invalid conversion from `const char*' to `int' /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:127: error: ISO C++ forbids declaration of `ready_dequeue' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: ISO C++ forbids declaration of `sched' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp: In function `int sched()': /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: parse error before `->' token /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:129: error: ISO C++ forbids declaration of `ready_enqueue' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:131: error: ISO C++ forbids declaration of `kill_all' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: ISO C++ forbids declaration of `threading_system_active' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: conflicting types for `int Helping_lock::threading_system_active' auto/helping_lock.h:24: error: previous declaration as `bool Helping_lock::threading_system_active' /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ISO C++ forbids declaration of `exit' with no type /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ` int exit' redeclared as different kind of symbol /usr/include/stdlib.h:640: error: previous declaration of `void exit(int)' /home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/src/kern/kernel_thread.cpp:136: error: parse error before `}' token make[3]: *** [kernel_thread.o] Error 1 make[3]: Leaving directory `/home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/build' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/ljian/L4/Fiasco/curses/practise/fiasco-1.2/l4/kernel/fiasco/build' make: *** [build] Error 2 btw: I use gentoo Cheers:) Liu Jian

3 2

L4Linux (dm_phys?) problem
by Jugwan Eom 12 Jan '06

12 Jan '06

Hello, I have a problem with runnig L4Linux. On both native and ux, the error is similar. (see the following log) Before this problem happened, I didn't any problem. IMHO, dm_phys seems to be the source of this error. I tried different mode (uclibc, dietlibc) with the same error. Best regards, Jugwan 1) On ux ---------------------------------------------------------------------------------------------------------------------- zugwan@getgid:~/boot/l4.oskit/runux$ ./lx con /home/zugwan/boot/l4.oskit/fiasco/fiasco -m 256 -symbols /home/zugwan/boot/l4.oskit/fiasco/Symbols -lines /home/zugwan/boot/l4.oskit/fiasco/Lines -rmgr /home/zugwan/boot/l4.oskit/l4v2/rmgr-ux -symbols -lines -sigma0 /home/zugwan/boot/l4.oskit/l4v2/sigma0-ux -fb_program /home/zugwan/boot/l4.oskit/fiasco/ux_con -irq0 /home/zugwan/boot/l4.oskit/fiasco/irq0 -t 32768 -G 640x480@16 -l /home/zugwan/boot/l4.oskit/l4v2/names -l /home/zugwan/boot/l4.oskit/l4v2/log -l /home/zugwan/boot/l4.oskit/l4v2/dm_phys -l /home/zugwan/boot/l4.oskit/l4v2/simple_ts -l /home/zugwan/boot/l4.oskit/l4v2/fuxfprov -n9 -l /home/zugwan/boot/l4.oskit/l4v2/rtc-ux -n10 -l /home/zugwan/boot/l4.oskit/l4v2/l4exec -l /home/zugwan/boot/l4.oskit/l4v2/con-ux -n12 -l /home/zugwan/boot/l4.oskit/l4v2/loader /home/zugwan/boot/l4.oskit/l4v2/run /home/zugwan/boot/l4.oskit/cfg/l4linux26.ux Fiasco-UX on Linux 2.6.11 (i686) Native Syscall Map: 0x1600 Mapped 256 MB Memory + 4096 KB Framebuffer + 4 MB Input Area on FD 3 Loading Module 0x00090000-0x00095060 [/home/zugwan/boot/l4.oskit/l4v2/sigma0-ux] Loading Module 0x00100000-0x001c6220 [/home/zugwan/boot/l4.oskit/l4v2/rmgr-ux] Copying Module 0x0ea66000-0x0ea84685 [/home/zugwan/boot/l4.oskit/fiasco/Symbols] Copying Module 0x0ea33000-0x0ea65cdd [/home/zugwan/boot/l4.oskit/fiasco/Lines] Copying Module 0x0ea07000-0x0ea32a7e [/home/zugwan/boot/l4.oskit/l4v2/names] Copying Module 0x0e9df000-0x0ea066c1 [/home/zugwan/boot/l4.oskit/l4v2/log] Copying Module 0x0e97d000-0x0e9de1fb [/home/zugwan/boot/l4.oskit/l4v2/dm_phys] Copying Module 0x0e94d000-0x0e97cd2b [/home/zugwan/boot/l4.oskit/l4v2/simple_ts] Copying Module 0x0e8a4000-0x0e94cdc1 [/home/zugwan/boot/l4.oskit/l4v2/fuxfprov] Copying Module 0x0e880000-0x0e8a345d [/home/zugwan/boot/l4.oskit/l4v2/rtc-ux] Copying Module 0x0e784000-0x0e87fcfa [/home/zugwan/boot/l4.oskit/l4v2/l4exec] Copying Module 0x0e6b1000-0x0e783b26 [/home/zugwan/boot/l4.oskit/l4v2/con-ux] Copying Module 0x0e5ea000-0x0e6b0c9a [/home/zugwan/boot/l4.oskit/l4v2/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Dec 22 23:02:20 2005 compiled with gcc 3.4.4 for Intel Pentium Starting Framebuffer: 640x480@16 CPU: GenuineIntel (F:4:1:0) Model: Pentium 4E (Prescott/Nocona) at 3190 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K \uffff-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: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 68kB for maintenance structures. RMGR: Hello! running on Fiasco bootloader loaded 9 modules at 0e5ea000-0ea84686 L4 symbols at 0e5cb000-0e5e9687 (121kB), lines at 0e598000-0e5cacdd (203kB) total RAM size = 261120 KB (reported by bootloader) received 239296 KB RAM from sigma0 1128 KB reserved for RMGR received no I/O ports attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 a b c d e f ] RMGR: Starting tasks. #05: loading "/home/zugwan/boot/l4.oskit/l4v2/names " from 0ea07000-0ea32a7e to [ 00240000-00246812 00247000-00253000 ] starting at entry 00240000 via trampoline page code 0000c46c symbols at 0ea86000-0ea88000 (8kB), lines at 0ea81000-0ea86000 (20kB) #06: loading "/home/zugwan/boot/l4.oskit/l4v2/log" from 0e9df000-0ea066c1 to [ 00400000-00406c31 00407000-00439510 ] starting at entry 00400000 via trampoline page code 0000d468 symbols at 0ea7f000-0ea81000 (8kB), lines at 0ea7a000-0ea7f000 (20kB) #07: loading "/home/zugwan/boot/l4.oskit/l4v2/dm_phys " from 0e97d000-0e9de1fb to [ 01500000-01511ca2 01512000-015193d0 ] starting at entry 01500000 via trampoline page code 0000e470 symbols at 0ea76000-0ea7a000 (16kB), lines at 0ea6a000-0ea76000 (48kB) #08: loading "/home/zugwan/boot/l4.oskit/l4v2/simple_ts " from 0e94d000-0e97cd2b to [ 01400000-01407ede 01408000-01413830 ] starting at entry 01400000 via trampoline page code 0000f470 symbols at 0ea68000-0ea6a000 (8kB), lines at 0ea62000-0ea68000 (24kB) #09: loading "/home/zugwan/boot/l4.oskit/l4v2/fuxfprov" from 0e8a4000-0e94cdc1 to [ 00500000-00521d4a 00522000-0053e000 ] starting at entry 00500000 via trampoline page code 00010470 symbols at 0ea5d000-0ea62000 (20kB), lines at 0ea4a000-0ea5d000 (76kB) #0a: loading "/home/zugwan/boot/l4.oskit/l4v2/rtc-ux" from 0e880000-0e8a345d to [ 01080000-01084abd 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 0001146c symbols at 0ea48000-0ea4a000 (8kB), lines at 0ea44000-0ea48000 (16kB) #0b: loading "/home/zugwan/boot/l4.oskit/l4v2/l4exec" from 0e784000-0e87fcfa to [ 01100000-01127ec2 01128000-01132000 ] starting at entry 01100000 via trampoline page code 0001246c symbols at 0ea3c000-0ea44000 (32kB), lines at 0ea24000-0ea3c000 (96kB) #0c: loading "/home/zugwan/boot/l4.oskit/l4v2/con-ux " from 0e6b1000-0e783b26 to [ 00b00000-00b242da 00b25000-00b30000 ] starting at entry 00b00000 via trampoline page code 0001346c symbols at 0ea1d000-0ea24000 (28kB), lines at 0ea05000-0ea1d000 (96kB) #0d: loading "/home/zugwan/boot/l4.oskit/l4v2/loader /home/zugwan/boot/l4.oskit/l4v2/run /home/zugwan/boot/l4.oskit/cfg/l4linux26.ux" from 0e5ea000-0e6b0c9a to [ 01300000-013253f6 01326000-01338000 ] starting at entry 01300000 via trampoline page code 000144bc symbols at 0e9ff000-0ea05000 (24kB), lines at 0e9e9000-0e9ff000 (88kB) simplets| Configured for 64 tasks. DMphys | (0x000161f8-0x000181f8),(0x00016258-0x00020000),(0x00102000-0x00103 DMphys : 000) DMphys | [7.0] dm_phys/server/src/pages.c:249:__add_area(): DMphys | DMphys: new area overlaps existing area! --PANIC, 'g' for exit-------------------------------ESP:01513ab0 EIP:01502146 (7.00) jdb: ^ Exiting, wait... 2) On native -------------------------------------------------------------------------------------------------------------------- RMGR: Stage1 Using extended multiboot info loading (hd1,0)/oskit/l4/v2/sigma0 loading kernel (hd1,0)/oskit/l4/v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 kernel at 00001000-003906a4 detected new-style DD-L4(v2)/Fiasco configuring sigma0: 00090000-00096000, start: 00090000 reserve modules memory range: 02055000-0455ec9b starting kernel (hd1,0)/oskit/l4/v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 proto=0x101fc0 @ 0x0030090c Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Dec 22 23:02:20 2005 compiled with gcc 3.4.4 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 CPU: GenuineIntel (F:4:8:0) Model: Pentium 4E (Prescott/Nocona) at 3190 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K \uffff-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! Found Fiasco: KIP syscalls: no. Allocated 107kB for maintenance structures. RMGR: Stage2 running on Fiasco bootloader loaded 17 modules at 02065000-0455ec9b total RAM size = 158270 KB (reported by bootloader) received 144292 KB RAM from sigma0 812 KB reserved for RMGR My symbols at 08e6c000-08e6f000 (12kB), lines at 08e60000-08e6c000 (48kB) received no I/O ports attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f ] RMGR: Parsing the config options of command line. configured task 0x0c: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:10 small:ff ] log_mask: 00000000, log_types: 00000000 RMGR: Starting tasks. #05: loading "(hd1,0)/oskit/l4/v2/names" from 02065000-02090a7e to [ 00240000-00246812 00247000-00253000 ] starting at entry 00240000 via trampoline page code 00056460 symbols at 08e5e000-08e60000 (8kB), lines at 08e59000-08e5e000 (20kB) #06: loading "(hd1,0)/oskit/l4/v2/log" from 02091000-020b86c1 to [ 00400000-00406c31 00407000-00439510 ] starting at entry 00400000 via trampoline page code 0005745c symbols at 08e57000-08e59000 (8kB), lines at 08e52000-08e57000 (20kB) #07: loading "(hd1,0)/oskit/l4/v2/dm_phys --isa=0x00800000 -v" from 020b9000-0211a1fb to [ 01500000-01511ca2 01512000-015193d0 ] starting at entry 01500000 via trampoline page code 00058474 symbols at 08e4e000-08e52000 (16kB), lines at 08e42000-08e4e000 (48kB) #08: loading "(hd1,0)/oskit/l4/v2/simple_ts -t 380" from 0211b000-0214ad2b to [ 01400000-01407ede 01408000-01413830 ] starting at entry 01400000 via trampoline page code 0005946c symbols at 08e40000-08e42000 (8kB), lines at 08e3a000-08e40000 (24kB) #09: loading "(hd1,0)/oskit/l4/v2/rtc" from 0214b000-0216ceca to [ 01080000-01084b69 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 0005a45c symbols at 08e38000-08e3a000 (8kB), lines at 08e34000-08e38000 (16kB) #0a: loading "(hd1,0)/oskit/l4/v2/l4io" from 0216d000-0233e01b to [ 00b80000-00ba237e 00ba3000-00bd7000 ] starting at entry 00b80000 via trampoline page code 0005b460 symbols at 08dfc000-08e34000 (224kB), lines at 08de5000-08dfc000 (92kB) #0b: loading "(hd1,0)/oskit/l4/v2/omega0 --l4io" from 0233f000-02374bd0 to [ 00360000-003683d5 00369000-0038257c ] starting at entry 00360000 via trampoline page code 0005c468 symbols at 08de3000-08de5000 (8kB), lines at 08ddc000-08de3000 (28kB) #0c: loading "(hd1,0)/oskit/l4/v2/bmodfs" from 02375000-0240047f to [ 01220000-0123634c 01237000-0123f000 ] passing module (hd1,0)/oskit/l4/v2/libloader.s.so [ 02401000-0248de37 ] passing module (hd0,0)/l4/cfg/run.bmodfs.cfg [ 0248e000-0248e078 ] passing module (hd1,0)/oskit/l4/v2/run [ 0248f000-024dc6e7 ] passing module (hd1,0)/oskit/l4/lx/vmlinuz26 [ 024dd000-0322576b ] passing module (hd0,0)/l4/cfg/lx/l4linux26_rd.cfg [ 03226000-0322609b ] passing module (hd0,0)/l4/rd/rd1 [ 03227000-04227000 ] starting at entry 01220000 via trampoline page code 0005d460 symbols at 08dd7000-08ddc000 (20kB), lines at 08dc8000-08dd7000 (60kB) #13: loading "(hd1,0)/oskit/l4/v2/l4exec" from 04227000-04322cfa to [ 01100000-01127ec2 01128000-01132000 ] starting at entry 01100000 via trampoline page code 0005e460 symbols at 08dc0000-08dc8000 (32kB), lines at 08da8000-08dc0000 (96kB) #14: loading "(hd1,0)/oskit/l4/v2/con --l4io" from 04323000-04497302 to [ 00b00000-00b4e4ba 00b4f000-00b61000 ] starting at entry 00b00000 via trampoline page code 0005f464 symbols at 08d9b000-08da8000 (52kB), lines at 08d69000-08d9b000 (200kB) #15: loading "(hd1,0)/oskit/l4/v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26 _rd.cfg" from 04498000-0455ec9a to [ 01300000-013253f6 01326000-01338000 ] starting at entry 01300000 via trampoline page code 00060490 symbols at 08d63000-08d69000 (24kB), lines at 08d4d000-08d63000 (88kB) DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x09af0000 (from L4 kernel info page) DMphys | using 0x00100000-0x09af0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00119000 7 12 MAPPED DMphys | 0x00119000-0x00193000 -- -- DENIED DMphys | 0x00193000-0x00240000 7 12 MAPPED DMphys | 0x00240000-0x00253000 -- -- DENIED DMphys | 0x00253000-0x00360000 7 12 MAPPED DMphys | 0x00360000-0x00383000 -- -- DENIED DMphys | 0x00383000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009ea000 7 12 MAPPED DMphys | 0x009ea000-0x00b00000 0 12 MAPPED DMphys | 0x00b00000-0x00b61000 -- -- DENIED DMphys | 0x00b61000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00bd7000 -- -- DENIED DMphys | 0x00bd7000-0x00c00000 0 12 MAPPED DMphys | 0x00c00000-0x01000000 0 22 MAPPED DMphys | 0x01000000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01100000 0 12 MAPPED DMphys | 0x01100000-0x01132000 -- -- DENIED DMphys | 0x01132000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x0123f000 -- -- DENIED DMphys | 0x0123f000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01338000 -- -- DENIED DMphys | 0x01338000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01414000 -- -- DENIED DMphys | 0x01414000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151a000 -- -- RESERVED DMphys | 0x0151a000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x02400000 0 22 MAPPED DMphys | 0x02400000-0x02401000 0 12 MAPPED DMphys | 0x02401000-0x04227000 -- -- DENIED DMphys | 0x04227000-0x04400000 0 12 MAPPED DMphys | 0x04400000-0x08c00000 0 22 MAPPED DMphys | 0x08c00000-0x08d4d000 0 12 MAPPED DMphys | 0x08d4d000-0x09af0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 102160KB total, 102160KB free, 32KB reserved DMphys | 0x009ea000-0x00b00000 ( 1112KB, 1MB) DMphys | 0x00b61000-0x00b80000 ( 124KB, 0MB) DMphys | 0x00bd7000-0x01080000 ( 4772KB, 5MB) DMphys | 0x0108a000-0x01100000 ( 472KB, 0MB) DMphys | 0x01132000-0x01220000 ( 952KB, 1MB) DMphys | 0x0123f000-0x01300000 ( 772KB, 1MB) DMphys | 0x01338000-0x01400000 ( 800KB, 1MB) DMphys | 0x01414000-0x01500000 ( 944KB, 1MB) DMphys | 0x0151a000-0x02401000 ( 15260KB, 15MB) DMphys | 0x04227000-0x08d4d000 ( 76952KB, 75MB) DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00119000 ( 100KB, 0MB) DMphys | 0x00193000-0x00240000 ( 692KB, 1MB) DMphys | 0x00253000-0x00360000 ( 1076KB, 1MB) DMphys | 0x00383000-0x00400000 ( 500KB, 0MB) DMphys | 0x0043a000-0x009ea000 ( 5824KB, 6MB) simplets| Configured for 380 tasks. rtc | Date:26.12.2005 Time:16:48:44 RMGR: task a.00 at 00b99b61 is trying to get page 00100000 allocated by task 7 ---------------------------------------------------------IP: 0011b7fa --double page fault (4.00) jdb:

3 8

l4linux-2.6 compilation: acpi problems: undefined reference *acpi*
by Konstantinos Pachopoulos 11 Jan '06

11 Jan '06

Hi, it seems like there are some acpi problems: ------------------------------------ ..... drivers/built-in.o(.init.text+0x52c0): In function `display_to_var': /usr/src/l4linux/l4linux-2.6/drivers/video/console/fbcon.c:749: undefined refere nce to `acpi_ht' drivers/built-in.o(.init.text+0x52ca):/usr/src/l4linux/l4linux-2.6/drivers/video /console/fbcon.c:750: undefined reference to `acpi_pci_disabled' drivers/built-in.o(.init.text+0x52d4):/usr/src/l4linux/l4linux-2.6/drivers/video /console/fbcon.c:752: undefined reference to `acpi_noirq' drivers/built-in.o(.init.text+0x5b5d): In function `acpi_pci_root_init': /usr/src/l4linux/l4linux-2.6/drivers/acpi/pci_root.c:347: undefined reference to `acpi_pci_disabled' drivers/built-in.o(.init.text+0x5cc1): In function `irqrouter_init_sysfs': /usr/src/l4linux/l4linux-2.6/drivers/acpi/pci_link.c: undefined reference to `ac pi_noirq' drivers/built-in.o(.init.text+0x5ced): In function `acpi_pci_link_init': /usr/src/l4linux/l4linux-2.6/drivers/acpi/pci_link.c: undefined reference to `ac pi_noirq' arch/l4/pci/built-in.o(.text+0x45a): In function `get_base_addr': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/mmconfig.c:27: undefined reference to `pci_mmcfg_config' arch/l4/pci/built-in.o(.text+0x464):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/m mconfig.c:27: undefined reference to `pci_mmcfg_config_num' arch/l4/pci/built-in.o(.text+0x15d3): In function `pcibios_penalize_isa_irq': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:1078: undefined reference to `a cpi_noirq' arch/l4/pci/built-in.o(.text+0x164e): In function `pirq_enable_irq': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c: undefined reference to `mp_irq _entries' arch/l4/pci/built-in.o(.text+0x165c):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/ irq.c: undefined reference to `skip_ioapic_setup' arch/l4/pci/built-in.o(.text+0x1666):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/ irq.c: undefined reference to `io_apic_irqs' arch/l4/pci/built-in.o(.text+0x16dd): In function `pcibios_fixup_irqs': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:922: undefined reference to `IO _APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.text+0x1728):/usr/src/l4linux/l4linux-2.6/arch/i386/pci/ irq.c:932: undefined reference to `IO_APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.init.text+0x71d): In function `pci_mmcfg_init': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/mmconfig.c:124: undefined reference t o `acpi_parse_mcfg' arch/l4/pci/built-in.o(.init.text+0x72a):/usr/src/l4linux/l4linux-2.6/arch/i386/ pci/mmconfig.c:125: undefined reference to `pci_mmcfg_config_num' arch/l4/pci/built-in.o(.init.text+0x734):/usr/src/l4linux/l4linux-2.6/arch/i386/ pci/mmconfig.c:125: undefined reference to `pci_mmcfg_config' arch/l4/pci/built-in.o(.init.text+0xeb0): In function `pci_acpi_init': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/acpi.c:40: undefined reference to `ac pi_noirq' arch/l4/pci/built-in.o(.init.text+0xf22): In function `pirq_sis_set': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c: undefined reference to `acpi_i oapic' arch/l4/pci/built-in.o(.init.text+0xf2b):/usr/src/l4linux/l4linux-2.6/arch/i386/ pci/irq.c: undefined reference to `print_IO_APIC' arch/l4/pci/built-in.o(.init.text+0x171b): In function `pcibios_fixup_irqs': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:932: undefined reference to `mp _irq_entries' arch/l4/pci/built-in.o(.init.text+0x1727):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:932: undefined reference to `skip_ioapic_setup' arch/l4/pci/built-in.o(.init.text+0x1730):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:932: undefined reference to `io_apic_irqs' arch/l4/pci/built-in.o(.init.text+0x1760):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:938: undefined reference to `IO_APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.init.text+0x17fa): In function `pci_vector_resources': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:1168: undefined reference to `I O_APIC_get_PCI_irq_vector' arch/l4/pci/built-in.o(.init.text+0x1957): In function `pcibios_irq_init': /usr/src/l4linux/l4linux-2.6/arch/i386/pci/irq.c:1048: undefined reference to `m p_irq_entries' arch/l4/pci/built-in.o(.init.text+0x1960):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:1048: undefined reference to `skip_ioapic_setup' arch/l4/pci/built-in.o(.init.text+0x196a):/usr/src/l4linux/l4linux-2.6/arch/i386 /pci/irq.c:1048: undefined reference to `io_apic_irqs' arch/l4/pci/built-in.o(.init.text+0x1e2f): In function `pcibios_setup': /usr/src/l4linux/l4linux-2.6/include/asm-l4/i386-arch/asm/acpi.h:149: undefined reference to `acpi_noirq' make: *** [.tmp_vmlinux1] Error 1 kastor:/usr/src/l4linux/l4linux-2.6# -------------------------------------- Any ideas? Thanks ___________________________________________________________ NEW Yahoo! Cars - sell your car and browse thousands of new and used cars online! http://uk.cars.yahoo.com/

2 1

grub-0.97 problem
by Der Herr Hofrat 05 Jan '06

05 Jan '06

HI ! Not to far into l4 yet - so this is most likely quite basic. trying to get L4Linux-2.6 to boot from hard disk. To get it to boot the docs say to use the modified grub - first shot was the grub cvs version - but that does not compile with gcc 3.3.6 (looks like it compiles up to gcc 3.2.X only - so next show was the patched grub-0.97 with the diff from ~adam/grub/ (patch < grub-0.97-os.diff) recompiled (./configure, make) and installed it(make install, grub-install /dev/hda) - booting gives me: GNU GRUB version 0.97-os.1 (640K lower / 228288K upper memory) followed by the menu - so I guess it worked. But if I use any of the features (i.e. set VAR := VAL, reference as $(VAL) ) it does not seem to know of these extensions ? the following is a part of my menu.lst: <snip> set P := (hd0,1)/usr/src/l4/l4/bin/x86_586/l4v2/ set C := (hd0,1)/usr/src/l4/cfg set L := (hd0,1)/usr/src/l4/l4linux/ # For booting GNU/Linux title GNU/Linux kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 read-only title The "hello" program kernel $(P)/rmgr -sigma0 module $(P)/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 0 module $(P)/sigma0 module $(P)/hello title The "hello2" program kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 0 module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 module /usr/src/l4/l4/bin/x86_586/l4v2/hello <snip> The target "hello" fails with <snip> kernel $(P)/rmgr -sigma0 Error 1: Filename must be either an absolute pathname or blocklist Press any key to continue... <snip> The target "hello2" loads as expected (it fails for other reasons later though) <snip> kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 [Multiboot-elf, <0x100000:0x20e40:0x0>, <0x121e40:0x483c:0xa4784>, shtab=0x1 cb2f8, entry=0x100000] module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comsp eed 115200 -comport 0 [Multiboot-module @ 0x20f000, 0x56ea4 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 [Multiboot-module @ 0x266000, 0x10211 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/hello [Multiboot-module @ 0x277000, 0xa884 bytes] <snip> I'm excluding hardware problems as the demo-CD version works fine - so its something thats wrong in this menu.lst ? I also tried removing the (hd0,1) from the settings as I did not have that in the hardcoded modules - so using: set P := /usr/src/l4/l4/bin/x86_586/l4v2/ but that did not change anything. regarding booting of linux - with all paths absolute due to the above problem: <menu.lst> title L4Linux 2.6 kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 task modname "bmodfs" module module module module module module boot_priority 0xA8 modaddr 0x02000000 module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -serial_esc -comspeed 115200 -comport 0 module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 module /usr/src/l4/l4/bin/x86_586/l4v2/names module /usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0 module /usr/src/l4/l4/bin/x86_586/l4v2/dm_phys module /usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380 module /usr/src/l4/l4/bin/x86_586/l4v2/rtc module /usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq module /usr/src/l4/l4/bin/x86_586/l4v2/bmodfs module /usr/src/l4/l4/bin/x86_586/l4v2/libloader.s.so module /usr/src/l4/cfg/run.bmodfs.cfg module /usr/src/l4/l4/bin/x86_586/l4v2/run module /usr/src/l4/l4linux-2.6/vmlinuz26 module /usr/src/l4/cfg/l4linux26.cfg module /usr/src/l4/l4/bin/x86_586/l4v2/l4exec module /usr/src/l4/l4/bin/x86_586/l4v2/con --l4io module /usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26.cfg <snip> I get the following output when booting: <snip> Booting 'L4Linux 2.6 ' kernel /usr/src/l4/l4/bin/x86_586/l4v2/rmgr -sigma0 -serial -comport=1 task mod name "bmodfs" module module module module module module module task modname "l4 dope" boot_priority 0xA8 [Multiboot-elf, <0x100000:0x20e40:0x0>, <0x121e40:0x483c:0xa4784>, shtab=0x1 cb2f8, entry=0x100000] modaddr 0x02000000 Setting module load address to 0x2000000 module /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comsp eed 115200 -comport 1 [Multiboot-module @ 0x2000000, 0x56ea4 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 [Multiboot-module @ 0x2057000, 0x10211 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/names [Multiboot-module @ 0x2068000, 0x2ab0e bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0 [Multiboot-module @ 0x2093000, 0x27a40 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/dm_phys [Multiboot-module @ 0x20bb000, 0x622a7 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380 [Multiboot-module @ 0x211e000, 0x2ffac bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/rtc [Multiboot-module @ 0x214e000, 0x2138b bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq [Multiboot-module @ 0x2170000, 0x1da7d1 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/bmodfs [Multiboot-module @ 0x234b000, 0x8f715 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/libloader.s.so [Multiboot-module @ 0x23db000, 0x8ec94 bytes] module /usr/src/l4/cfg/run.bmodfs.cfg [Multiboot-module @ 0x246a000, 0x78 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/run [Multiboot-module @ 0x246b000, 0x51d69 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/con_demo2 [Multiboot-module @ 0x24bd000, 0x8a3eb bytes] module /usr/src/l4/l4linux-2.6/vmlinuz26 [Multiboot-module @ 0x2548000, 0xda1d5a bytes] module /usr/src/l4/cfg/l4linux26.cfg [Multiboot-module @ 0x32ea000, 0x73 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/l4exec [Multiboot-module @ 0x32eb000, 0x103b97 bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/con --l4io [Multiboot-module @ 0x33ef000, 0x17531e bytes] module /usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4l inux26.cfg [Multiboot-module @ 0x3565000, 0xcf4e3 bytes] RMGR: Stage1 loading /usr/src/l4/l4/bin/x86_586/l4v2/sigma0 loading kernel /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 kernel at 00001000-003906a4 detected new-style DD-L4(v2)/Fiasco configuring sigma0: 00090000-00096000, start: 00090000 reserve modules memory range: 02057000-036344e4 starting kernel /usr/src/l4/l4/bin/x86_586/l4v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 proto=0x101f20 @ 0x0030097c Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Dec 22 23:02:20 2005 compiled with gcc 3.3.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_NDEBUG is off Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling CPU: AuthenticAMD (6:8:1:0) Model: Duron (Applebred) at 1601 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 64 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 124kB for maintenance structures. RMGR: Stage2 running on Fiasco bootloader loaded 16 modules at 02068000-036344e4 total RAM size = 228928 KB (reported by bootloader) received 209268 KB RAM from sigma0 816 KB reserved for RMGR My symbols at 0cde3000-0cde6000 (12kB), lines at 0cdd6000-0cde3000 (52kB) received no I/O ports attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 a b c d e f ] RMGR: Parsing the config options of command line. configured task 0x0b: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:10 small:ff ] WARNING: couldn't find modname l4dope, only storing it's quota configured task 0x15: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:a8 small:ff ] log_mask: 00000000, log_types: 00000000 RMGR: Starting tasks. #05: loading "/usr/src/l4/l4/bin/x86_586/l4v2/names" from 02068000-02092b0e to [ 00240000-002467d2 00247000-00253000 ] starting at entry 00240000 via trampoline page code 0005916c symbols at 0cdd4000-0cdd6000 (8kB), lines at 0cdcf000-0cdd4000 (20kB) #06: loading "/usr/src/l4/l4/bin/x86_586/l4v2/log --prio 0xA1 --buffer 0" from 02093000-020baa40 to [ 00400000-00406d01 00407000-00439510 ] starting at entry 00400000 via trampoline page code 0005a180 symbols at 0cdcd000-0cdcf000 (8kB), lines at 0cdc8000-0cdcd000 (20kB) #07: loading "/usr/src/l4/l4/bin/x86_586/l4v2/dm_phys" from 020bb000-0211d2a7 to [ 01500000-0151239a 01513000-0151a410 ] starting at entry 01500000 via trampoline page code 0005b16c symbols at 0cdc4000-0cdc8000 (16kB), lines at 0cdb8000-0cdc4000 (48kB) #08: loading "/usr/src/l4/l4/bin/x86_586/l4v2/simple_ts -t 380" from 0211e000-0214dfac to [ 01400000-01407ffa 01408000-01413850 ] starting at entry 01400000 via trampoline page code 0005c178 symbols at 0cdb6000-0cdb8000 (8kB), lines at 0cdb0000-0cdb6000 (24kB) #09: loading "/usr/src/l4/l4/bin/x86_586/l4v2/rtc" from 0214e000-0216f38b to [ 01080000-01084b19 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 0005d168 symbols at 0cdae000-0cdb0000 (8kB), lines at 0cdaa000-0cdae000 (16kB) #0a: loading "/usr/src/l4/l4/bin/x86_586/l4v2/l4io --noirq" from 02170000-0234a7d1 to [ 00b80000-00ba322b 00ba4000-00bd8000 ] starting at entry 00b80000 via trampoline page code 0005e174 symbols at 0cd73000-0cdaa000 (220kB), lines at 0cd5d000-0cd73000 (88kB) #0b: loading "/usr/src/l4/l4/bin/x86_586/l4v2/bmodfs" from 0234b000-023da715 to [ 01220000-01236d6c 01237000-0123f000 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/liblo [ 023db000-02469c94 ] passing module /usr/src/l4/cfg/run.bmodfs.cfg [ 0246a000-0246a078 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/run [ 0246b000-024bcd69 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/con_d [ 024bd000-025473eb ] passing module /usr/src/l4/l4linux-2.6/vmlinuz26 [ 02548000-032e9d5a ] passing module /usr/src/l4/cfg/l4linux26.cfg [ 032ea000-032ea073 ] passing module /usr/src/l4/l4/bin/x86_586/l4v2/l4exe [ 032eb000-033eeb97 ] starting at entry 01220000 via trampoline page code 0005f16c symbols at 0cd58000-0cd5d000 (20kB), lines at 0cd49000-0cd58000 (60kB) #13: loading "/usr/src/l4/l4/bin/x86_586/l4v2/con --l4io" from 033ef000-0356431e to [ 00b00000-00b4efab 00b4f000-00b61000 ] starting at entry 00b00000 via trampoline page code 00060170 symbols at 0cd3b000-0cd49000 (56kB), lines at 0cd0d000-0cd3b000 (184kB) #14: loading "/usr/src/l4/l4/bin/x86_586/l4v2/loader --fprov=BMODFS run.bmodfs.cfg l4linux26.cfg" from 03565000-036344e3 to [ 01300000-013265cb 01327000-01339000 ] starting at entry 01300000 via trampoline page code 00061198 symbols at 0cd07000-0cd0d000 (24kB), lines at 0ccf2000-0cd07000 (84kB) simplets| Configured for 380 tasks. rtc | Date:04.01.2006 Time:11:00:09 RMGR: task a.00 at 00b99c57 is trying to get page 00100000 allocated by task 7 ---------------------------------------------------------IP: 0011c6c1 --double page fault (4.00) jdb: ^ Return reboots, "k" enters L4 kernel debugger... Rebooting. <snip> Any hint on what I've messed up - also pointers on how to get usable debug infos out of such a situation would be appreciated - I did fine some short l4_install.notes describing setup of hello + L4Linux but they seem to be a bit out of date. My suspicion is that the grub is not correctly patched and thus these problems... thx ! hofrat

2 2

Re: L4Linux (dm_phys?) problem
by Jugwan Eom 29 Dec '05

29 Dec '05

Oh, I had many many many mistake. :( This is the right image.

1 0

Dataspaces mappings for L4Linux
by Julian Grizzard 21 Dec '05

21 Dec '05

All, I'm running Fiasco on i386 with L4Linux 2.6. Is there an easy way to find out where all L4Linux DMphys DS's are mapped in its virtual memory? My goal is to get the entire mapping of DS's to virtual memory location in L4Linux. I am able to get some of these mappings from the dump-l4 example and from data printed out from L4Linux. However, I don't know where all DS's are mapped (e.g. "L4thread stack"...). Here's some specific questions I am trying to answer: 1) Where is "L4RM heap" mapped? 2) Where are "syms vmlinux" and "lines vmlinux" mapped? 3) Where is "L4thread TCB table" mapped? 4) Where are the "L4thread stack" DS's mapped? 5) Where is "Ghost page 1" mapped? What is that DS by the way? 6) There seems to be some DS's for L4Linux that are created by the loader and there is also the "L4Linux main memory" DS. Are there any other mappings in L4Linux's virtual memory? Thanks! Julian

2 1

wrong gcc major version "2"- use 3.x for l4io
by Konstantinos Pachopoulos 21 Dec '05

21 Dec '05

Hi, issuing a "make" in /usr/src/l4linux/l4, i end up with this error: ----------------------------------------------------- ===Building IDL & includes of "l4io"=== PWD= /usr/src/l4linux/l4/pkg/l4io make -C l4io idl make[2]: Entering directory '/usr/src/l4linux/l4/pkg/l4io' Makefile:8: ***Wrong gcc major version "2"- use 3.x for l4io. Stop. make[2]: Leaving directory '/usr/src/l4linux/l4/pkg/l4io' make[1]: ***[l4io.headers] Error 2 make[1]: Leaving directory '/usr/src/l4linux/l4/pkg' make: ***[pkg] Error 2 kastor:/usr/src/l4linux/l4# ----------------------------------------------------- I use gcc-2.95 for this. However, using gcc-3.3, i ended up with exactly the same error. Having problems using byacc, i changed the conf file and now i use bison, without any problems from this point. I am using the latest sources from CVS- downloaded yesterday in fact. Any ideas about the l4io problem? Thanks, Kostas ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com

2 1

Is it a problem to use l4env_freebsd - mode?
by Arthur Mielimonka 21 Dec '05

21 Dec '05

Hello, I was told recently that you are currently in the process of dumping oskit in favor of uclibc or dietlibc. For my work, I need the log_net server which only compiles with oskit. So I cannot abandon it. Are they any problems or reasons why one shouldn't use oskit? Is it possilble to use a mixed configuration (e.g. compile log_net with oskit and own packages with dietlibc and use them together)? Thanks, Arthur

6 5

Track Program_Counter(PC)/regs of L4Linux Task
by Julian Grizzard 19 Dec '05

19 Dec '05

All, I am currently running L4Linux2.6.14 on the Fiasco l4v2 microkernel using i386 arch with mostly default configurations. I need the ability to track the program counter and registers of all threads in the L4Linux task. Here's exactly what I would like to be able to do from a monitoring L4 task: -Obtain the PC/regs for the first thread (thread 0) for L4Linux just before the thread executes it's first instruction. It would be nice to make the thread wait for a signal before beginning execution. -Obtain the PC/regs for any additional thread created or any thread moved for L4Linux (i.e. from a l4_thread_ex_regs call) just before that thread executes. Again, it would be nice to make that thread wait for a signal before beginning its execution. -Randomly preemptively obtain the PC/regs for all threads of L4Linux. -Obtain the PC/regs for all threads of L4Linux on demand. -Receive notification of thread exit for all threads of L4Linux. There are a few items that I do not yet fully understand that *may* make matters more difficult: -The setup code executing in libloader.s.so. -Trampoline code There are a few assumptions I am willing to have for initial testing to make the development easier: -Assume Task number of L4Linux is known by the microkernel (i.e. hard code it in). -Assume Task number of monitoring thread is known by the microkernel. As a first crack, I have added some code to the microkernel to print out information on the L4Linux task, to see if that information would be good to transfer to the monitoring task. Below is a summary of things I have tried and results seen: MODIFICATION #1 l4/kernel/fiasco/src/kern/context.cpp Context::schedule() Goal: Track current PC of L4Linux threads ======================= ... /* in the for loop */ Sys_task_new_frame *regs = sys_frame_cast<Sys_task_new_frame>(next_to_run->regs()); L4_uid id = regs->dst(); if (id.task() == 0xC) // hard coded task of L4Linux { unsigned int ip = next_to_run->regs()->ip(); unsigned int sp = next_to_run->regs()->sp(); printf("task: %d.%d @ ip: %08x sp: %08x\n", id.task(), id.lthread(), ip, sp); } ... ======================= Results: task: 12.3 @ ip: 004ccb0b sp: b00fff80 task: 12.3 @ ip: 004cd303 sp: b01fff7c task: 12.4 @ ip: 004cca9d sp: b00fff80 task: 12.5 @ ip: 00402ae6 sp: 00657f50 ======================= Notes: 004ccb0b - right after an 'int 0x30' in timer_irq_thread 004cd303 - right after an 'int 0x30' in irq_thread_hw 004cca9d - right after an 'int 0x30' in timer_irq_thread 00402ae6 - right after an 'int 0x30' in l4x_idle MODIFICATION #2 l4/kernel/fiasco/src/kern/thread-syscall.cpp Thread::sys_task_new() Goal: Track starting PC of main L4Linux thread (i.e. thread 0) ======================= ... /* near tail of for loop, just before return */ if (taskno == 0xC) // hard coded L4Linux task ID { printf("new task: %d @ ip: %08x sp: %08x\n", taskno, regs->ip(), regs->sp()); } ======================= Results: new task: 12 @ ip: 00015ea0 sp: 00008f6c ======================= Notes: 00015ea0 - part of the libloader.s.so code MODIFICATION #3 l4/kernel/fiasco/src/kern/thread-syscall.cpp Thread::sys_thread_ex_regs() Goal: Track PC entry of new L4Linux threads ======================= ... if (!dst->exists()) { unsigned int task_num = dst_id.task(); unsigned int lthread_num = regs->thread(); new_thread = true; check (new (dst_id) Thread (dst_task, dst_id, sched()->prio(), mcp()) == dst); if (taskno == 0xC) { printf("new thread: %d.%d @ ip: %08x sp: %08x\n", task_num, lthread_num, regs->ip(), regs->sp()); } } else { unsigned int task_num = dst_id.task(); unsigned int lthread_num = regs->thread(); if (taskno == 0xC) { printf("modified thread: %d.%d @ ip: %08x sp: %08x\n", task_num, lthread_num, regs->ip(), regs->sp()); } } ... ======================= Results: modified thread: 12.0 @ ip: ffffffff sp: ffffffff modified thread: 12.0 @ ip: ffffffff sp: ffffffff new thread: 12.1 @ ip: 0001ac10 sp: afe00000 new thread: 12.2 @ ip: 0001ac10 sp: aff00000 modified thread: 12.2 @ ip: ffffffff sp: ffffffff new thread: 12.3 @ ip: 0001ac10 sp: 00657ff8 modified thread: 12.3 @ ip: ffffffff sp: ffffffff new thread: 12.4 @ ip: 0001ac10 sp: b0100000 modified thread: 12.3 @ ip: ffffffff sp: ffffffff new thread: 12.5 @ ip: 0001ac10 sp: b0200000 modified thread: 12.3 @ ip: ffffffff sp: ffffffff new thread: 12.6 @ ip: 0001ac10 sp: b0300000 new thread: 12.7 @ ip: 0001ac10 sp: b0400000 ======================= Notes: 0001ac10 - part of the libloader.s.so code ffffffff - not really useful. wrong data perhaps. QUESTIONS: GENERAL QUESTIONS -Is there any easy to delay execution of newly created threads, both new task thread 0 and additional threads? -Is there an easy way to randomly interrupt L4Linux threads to check their PC value? -Do any L4Linux threads exit? MODIFICATION #1 -Seems like threads resume execution right after an interrupt. I don't see threads getting preempted in the middle of servicing a system call, for example. Any ideas why not? Further, is there one thread dedicated to handling system calls? -Is there any better way to track where all the L4Linux threads are? Maybe somewhere else besides the scheduler? Are any other classes/functions helpful to get this information? MODIFICATION #2 -I believe this is working correctly. See anything wrong here? MODIFICATION #3 -I would like to catch all instances of creating new threads for L4Linux. Will this current approach work, or is it not correct? If my implementation is correct: -Why are L4Linux threads getting modified? -Any idea why my ip and sp values are 0xffffffff for modified threads? -Looks like all new threads start at the same place. How would they distinguish from one another in terms of functionality? Is that encoded in their stack (e.g. when they issue a 'ret', they'll return to different locations or maybe arguments to their function are on the stack?) Any other comments you have would also be appreciated. Thanks! Julian

3 7

Postdoc position at Nijmegen (ROBIN project on OS verification)
by Erik Poll 15 Dec '05

15 Dec '05

(Apologies for multiple copies) The SoS (Security of Systems) group at the Radboud University of Nijmegen in the Netherlands has a vacancy for a postdoc for a 2-year period starting February 1 2006. The vacancy is in the EU project ROBIN (Robust Open Infrastructure), which is a joint project in collaboration with TU Dresden (more specifically Hermann Härtig's operating systems group), ST Micro Electronics and Secunet. The goal of the ROBIN project is to develop a robust platform (Operating System kernel) that can host legacy operating systems and their applications, but that is small enough (in the order of 50-100k lines of code) to apply rigorous formal analysis and construction techniques. The kernel of the robust platform will be written in C++ (with very small parts in assembly). The work in Nijmegen concentrates on the formal specification and verification of key security properties of the kernel. The objectives are to develop, evaluate and assess tool-supported formal methods for the specification and verification of low level systems code, especially operating-system kernel source-code. The aim is not a full verification of the kernel, but rather to show a perspective of what can be achieved with formal methods. A starting point for this work is the VFiasco project at TU Dresden. We are looking for candidates with a recent PhD in Computing Science, a strong background in formal methods, and an interest in applying formal methods to low-level system programs, such as operating system kernels. Experience with (interactive) theorem provers, program verification, or static analysis is a pré, as is an interest in security. You'll be collaborating with a second postdoc working on this project in Nijmegen for two years, Hendrik Tews, who'll be joining the SoS group starting February 2006. Pre-tax salary starts at 2625,- euro per month, but can be more depending on experience. For more info, contact Erik Poll <erikpoll(a)cs.ru.nl> or Hendrik Tews <tews(a)tcs.inf.tu-dresden.de>. The ROBIN project proposal is available on request from either Erik or Hendrik. You can apply by sending a letter of motivation and a detailed cv (preferably in PDF format) and contact details of at least two references to Erik Poll <erikpoll(a)cs.ru.nl> by January 2, 2006. Relevant links: - SoS group at Nijmegen: http://www.cs.ru.nl/sos - VFiasco project at Dresden: http://os.inf.tu-dresden.de/vfiasco/

1 0

L4Linux-2.6.14 perfomance question
by Der Herr Hofrat 12 Dec '05

12 Dec '05

HI ! I'm very new to L4Linux so my question might be obvious - anyway did not find anything directly related in the archive. For a start I did a quick performance comparison using lmbench-3.0. This comparison is based on the L4Linux-2.6 running a debina ramdisk lmbench-3.0 vs Linux-2.6.14 running from harddisk (though data files were in tempfs in both cases - so the HD should not really have much of an impact). L4Linux Linux 2.6.14 com lat.: (us) lat_pipe 14.1-14.5 2.0 lat_fifo 13.9-14.6 2.2 lat_unix 19.4-19.5 3.2 lat_sem 3.5 0.6 lat_proc: (us) fork 805-1249 80-82 exec 3124-3784 212-230 shell 9992-9997 2480-2592 tlb: 7,8,32 always 32 bw com: (MB/s) bw_pipe 921-958 1338-1352 bw_unix 429-753 1122-1138 lat mem: oopses under L4Linux - no results bw_mem: (MB/s) bcopy 3856-4066 5056-5080 rdwr 11937-13242 16052 syscall: (us) null 2.4-2.8 0.13 read 2.6-3.3 0.26-0.31 stat 4.4-4.9 0.89 open 6.5-8.1 1.16-1.39 The thing that supprises me is that the performance variation is much higher than on regular linux - in both cases the system was idle except for lmbench running, so I'm excluding any syslog parties or cron jobs fireing at inconvenient times (i.e bandwidth of UNIX sockets has a variance of almost 50% ?). Generally the performance difference is much larger than I would have expected, especially also in areas where I don't quite understand where the u-kenrel can impact the Linux system (i.e. bcopy, memory read-write) Are these values in the usual range or did I screw up fundamentally ? thx ! Prof. Nicholas Mc Guire University of Lanzhou Distributed & Embedded System Lab http://dslab.lzu.edu.cn School of Information Science and Engeneering mcguire(a)lzu.edu.cn Tianshui South Road 222. Lanzhou 730000 .P.R.China Tel:+86-931-8912025 Fax:+86-931-8912022 Lichtensteinstr. 31, Mistelbach A-2130 Austria Tel:+43-2572-201082 Fax:+43-2572-201084

2 1

Compiling fiasco for ARM
by Marko Wolf 07 Dec '05

07 Dec '05

Hi there! I tried to compile your current CVS Fiasco with the SA1100 ARM CPU target with all other options at default. I used the, at www.arm.com officially mentioned, GNU Toolchain for ARM Processors from www.codesourcery.com. Both target platform versions arm-bare-gcc-3.4.4 (target platform bare metal) and arm-linux-gcc-3.4.4 (target platform linux) fail at final linking with the attached error message. Maybe, I'm using the wrong arm-linux-compiler. What am I doing wrong? Are other mandatory configuration settings? What ARM compiler are you using? Best regards Marko ######### with arm-bare-gcc-3.4.4 ########## ==> Linking fiasco.image arm-linux-ld: Warning: size of symbol `__DTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(_ctors.o) arm-linux-ld: Warning: size of symbol `__CTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(_ctors.o) arm-linux-ld: section .excp [c0026000 -> c002697f] overlaps section .bss._ZGVZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026000 -> c0026003] arm-linux-ld: section .bss._ZZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026004 -> c0026027] overlaps section .excp [c0026000 -> c002697f] uart_console.o: In function `uart_console_init_stage1()':uart_console.cc: (.text._Z24uart_console_init_stage1v+0x88): undefined reference to `__aeabi_atexit' kernel_uart.o: In function `Kernel_uart::uart()':kernel_uart.cc: (.text._ZN11Kernel_uart4uartEv+0x3c): undefined reference to `__aeabi_atexit' kernel_console.o: In function `Kconsole::console()':kernel_console.cc: (.text._ZN8Kconsole7consoleEv+0x50): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD1Ev+0xe4): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD2Ev+0xe4): undefined reference to `__aeabi_atexit' mapdb.o:mapdb.cc:(.text._ZN5Mapdb4freeEP7Mapping+0x270): more undefined references to `__aeabi_atexit' follow /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(unwind-arm.o): In function `get_eit_entry':unwind-arm.c:(.text+0x45c): undefined reference to `__exidx_start' :unwind-arm.c:(.text+0x460): undefined reference to `__exidx_end' /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(unwind-arm.o): In function `unwind_phase2':unwind-arm.c:(.text+0x4c8): undefined reference to `abort' /opt/arm-bare-gcc-3.4.4/bin/../lib/gcc/arm-none-eabi/3.4.4/libgcc.a(unwind-arm.o): In function `__gnu_Unwind_Resume':unwind-arm.c:(.text+0x6f4): undefined reference to `abort' make[3]: *** [fiasco.image] Fehler 1 ######### with arm-linux-gcc-3.4.4 ########## ==> Linking fiasco.image arm-linux-ld: Warning: size of symbol `__CTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_ctors.oS) arm-linux-ld: Warning: size of symbol `__DTOR_LIST__' changed from 4 in libc.a(construction.o) to 8 in /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_ctors.oS) arm-linux-ld: section .excp [c0026000 -> c002697f] overlaps section .bss._ZGVZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026000 -> c0026003] arm-linux-ld: section .bss._ZZN23mapping_tree_allocators8instanceEvE15tree_allocators [c0026004 -> c0026027] overlaps section .excp [c0026000 -> c002697f] uart_console.o: In function `uart_console_init_stage1()':uart_console.cc: (.text._Z24uart_console_init_stage1v+0x80): undefined reference to `__aeabi_atexit' kernel_uart.o: In function `Kernel_uart::uart()':kernel_uart.cc: (.text._ZN11Kernel_uart4uartEv+0x38): undefined reference to `__aeabi_atexit' kernel_console.o: In function `Kconsole::console()':kernel_console.cc: (.text._ZN8Kconsole7consoleEv+0x4c): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD1Ev+0xd8): undefined reference to `__aeabi_atexit' mapdb.o: In function `Mapdb::~Mapdb()':mapdb.cc:(.text._ZN5MapdbD2Ev+0xd8): undefined reference to `__aeabi_atexit' mapdb.o:mapdb.cc:(.text._ZN5Mapdb4freeEP7Mapping+0x13c): more undefined references to `__aeabi_atexit' follow /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_divdi3.oS): (.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' /opt/arm-linux-gcc-3.4.4/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.4/libgcc.a(_udivdi3.oS): (.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' make[3]: *** [fiasco.image] Fehler 1

2 3

fprintf(stderr, ...) fails
by Arthur Mielimonka 29 Nov '05

29 Nov '05

Hello, for my project I'm using sources, which heavily make use of code like this: fprintf (stderr, "...."); Even if compiling works fine, the executions of the program failes with the following error message, when the program reaches the respective code: Program| OSKit support: using 4096KB at 0x00100000 as heap Program| Program| Exiting with rc=-2147467262 No error occurs on printf("..") - commands. I am using the "l4env_freebsd" mode, but even in "l4env" mode an (another) error occurs. I'm starting fiasco-ux with the command: ./fiasco-ux -m 256 -l names -l name_server -l dm_phys -l log -l simple_ts -l Program Thanks for any help, Arthur

3 4

dde_linux26 down_trylock bug
by Wei Shen 28 Nov '05

28 Nov '05

Hi, In dde_linux26/include/ARCH-x86/asm/semaphore.h: static inline int down_trylock(struct semaphore * sem) { return l4semaphore_try_down(&sem->l4_sema); } It seems incorrect. Maybe it should be: static inline int down_trylock(struct semaphore * sem) { return (l4semaphore_try_down(&sem->l4_sema) != 1); } Regards, Wei

2 1

Failed Assertion @ auto/kmem.h:162
by Julian Grizzard 27 Nov '05

27 Nov '05

All, I'm upgrading my Fiasco/L4Linux setup to the latest CVS version. My machine is a Pentium IV with 1 Gig RAM. Using the same configuration that worked before, I've run into an assertion problem when the system boots with the latest CVS. Below is the contents of menu.lst, L4 kernel configuration (globalconfig.out), and the boot log showing the assertion error. Further, I cannot enter the kernel debugger with "k"; instead, the offending address changes to 0xf0014fc7 with the same assertion thus failing to enter the debugger. Any idea what is wrong? Thanks! Julian ################ menu.lst ################## title L4Linux-2.6 root (hd0,0) kernel /boot/l4/rmgr -sigma0 task modname "bmodfs" module module module modaddr 0x02000000 module /boot/l4/main -nokdb -nowait -serial -comport 1 module /boot/l4/sigma0 module /boot/l4/names module /boot/l4/log module /boot/l4/dm_phys module /boot/l4/simple_ts -t 300 #module /boot/l4/rtc module /boot/l4/l4io --noirq module /boot/l4/l4exec module /boot/l4/bmodfs module /boot/l4/libloader.s.so module /boot/l4/run-script module /boot/vmlinuz26 module /boot/l4/loader --fprov=BMODFS run-script ############## /boot/l4/run-script ############### sleep 2 task "vmlinuz26" "noreplacement mem=64M root=/dev/hda1" ################ globalconfig.out ################ # # Automatically generated, don't edit # # Generated on: linux1 # At: Thu, 24 Nov 2005 18:22:02 +0000 # Linux version 2.6.8-2-686 (horms(a)tabatha.lab.ultramonkey.org) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Thu May 19 17:53:30 JST 2005 # # Main menu # CONFIG_EXPERIMENTAL=y # # Target System Options # # # Target Platform # CONFIG_PF_PC=y CONFIG_PF_UX=n CONFIG_PF_SA1100=n CONFIG_PF_XSCALE=n CONFIG_PF_ISG=n # # Target CPU Family # CONFIG_IA32=y CONFIG_ARM=n CONFIG_AMD64=n # # Target processor # CONFIG_IA32_486=n CONFIG_IA32_586=n CONFIG_IA32_686=n CONFIG_IA32_P2=n CONFIG_IA32_P3=n CONFIG_IA32_P4=y CONFIG_IA32_PM=n CONFIG_IA32_K6=n CONFIG_IA32_K7=n CONFIG_IA32_K8=n # # Target processor # CONFIG_AMD64_K8=n CONFIG_REGPARM3=y # # Kernel Options # # # Kernel ABI Version # CONFIG_ABI_V2=y CONFIG_ABI_X0=n # # ABI Extensions # CONFIG_DECEIT_BIT_DISABLES_SWITCH=y CONFIG_KIP_SYSCALLS=n CONFIG_MULTI_IRQ_ATTACH=n CONFIG_EXCEPTION_IPC=y CONFIG_SYSCALL_ITER=y CONFIG_HANDLE_SEGMENTS=y CONFIG_LOCAL_IPC=n CONFIG_ACTIVATION_IPC=n CONFIG_PL0_HACK=n CONFIG_ASSEMBLER_IPC_SHORTCUT=n CONFIG_SMALL_SPACES=n CONFIG_CONTEXT_4K=y # # Scheduling Timer # CONFIG_SCHED_PIT=y CONFIG_SCHED_RTC=n CONFIG_SCHED_APIC=n CONFIG_ONE_SHOT=n CONFIG_SYNC_TSC=n CONFIG_FINE_GRAINED_CPUTIME=n CONFIG_IO_PROT=n CONFIG_UX_CON=n CONFIG_UX_NET=n # # Kernel Debugging # CONFIG_INLINE=y CONFIG_NDEBUG=n CONFIG_PROFILE=n CONFIG_NO_FRAME_PTR=n CONFIG_STACK_DEPTH=n CONFIG_LIST_ALLOC_SANITY=n CONFIG_BEFORE_IRET_SANITY=n CONFIG_GSTABS=y CONFIG_POWERSAVE_GETCHAR=y CONFIG_SERIAL=y CONFIG_KDB=y CONFIG_JDB=y CONFIG_JDB_LOGGING=n CONFIG_JDB_ACCOUNTING=n CONFIG_JDB_MISC=n CONFIG_WATCHDOG=y # # Runtime warning level # CONFIG_WARN_NONE=n CONFIG_WARN_ANY=y # # Compiling and Building # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_VERBOSE=n CONFIG_MAINTAINER_MODE=n # # Derived symbols # CONFIG_BIT32=y CONFIG_XARCH="ia32" CONFIG_IA32_TARGET="Intel Pentium 4" CONFIG_WARN_LEVEL=2 CONFIG_BIT64=n CONFIG_PERF_CNT=y CONFIG_ABI="v2" # # That's all, folks! ################# BOOT LOG ################# [Multiboot-elf, <0x100000:0x20e18:0x0>, <0x121e20:0x49fc:0xa4784>, shtab=0x1 cb2f8, entry=0x100000] modaddr 0x02000000 Setting module load address to 0x2000000 module /boot/l4/main -nokdb -nowait -serial -comport 1 [Multiboot-module @ 0x2000000, 0x591ac bytes] module /boot/l4/sigma0 [Multiboot-module @ 0x205a000, 0xe94b bytes] module /boot/l4/names [Multiboot-module @ 0x2069000, 0x2a831 bytes] module /boot/l4/log [Multiboot-module @ 0x2094000, 0x26a93 bytes] module /boot/l4/dm_phys [Multiboot-module @ 0x20bb000, 0x5f2b2 bytes] module /boot/l4/simple_ts -t 300 [Multiboot-module @ 0x211b000, 0x2ef4f bytes] module /boot/l4/l4io --noirq [Multiboot-module @ 0x214a000, 0x1d1360 bytes] module /boot/l4/l4exec [Multiboot-module @ 0x231c000, 0xf4b72 bytes] module /boot/l4/bmodfs [Multiboot-module @ 0x2411000, 0x88b4c bytes] module /boot/l4/libloader.s.so [Multiboot-module @ 0x249a000, 0x88c3f bytes] module /boot/l4/run-script [Multiboot-module @ 0x2523000, 0x40 bytes] module /boot/vmlinuz26 [Multiboot-module @ 0x2524000, 0xd967f6 bytes] module /boot/l4/loader --fprov=BMODFS run-script [Multiboot-module @ 0x32bb000, 0xc8ed6 bytes] Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Tue Nov 22 22:45:10 2005 compiled with gcc 3.3.5 for Intel Pentium 4 Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling CPU: GenuineIntel (F:2:7:9) Model: Pentium 4 (Northwood/Prestonia) at 2519 MHz 128 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 8 KB L1 D Cache (4-way associative, 64 bytes per line) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) Assertion failed: 'Mem_layout::Tcbs_end == Mem_layout::Tcbs + (Config::thread_block_size * Config::max_threads())' in auto/kmem.h:162 at f0007cb1 Return reboots, "k" enters L4 kernel debugger... <k> Assertion failed: 'Mem_layout::Tcbs_end == Mem_layout::Tcbs + (Config::thread_block_size * Config::max_threads())' in auto/kmem.h:162 at f0014fc7 Return reboots, "k" enters L4 kernel debugger...

2 2

L4Linux on fiasco UX problem
by Jugwan Eom 24 Nov '05

24 Nov '05

Hi, I tried runnig L4Linux on fiasco UX but it didn't work. I enabled three options for the L4Linux. (Exception IPC / Inter-task ex-regs syscall / Handle and preserve segments) I have no idea why l4linux causes the trap. Anyone could help me? Followings are log and disassembling of vmlinux. Thanks in advance. ------------------------------------------------------------------------------------ $ ./lx con /home/zugwan/boot/fiasco_ux/fiasco -m 256 -symbols /home/zugwan/boot/fiasco_ux/Symbols -lines /home/zugwan/boot/fiasco_ux/Lines -rmgr /home/zugwan/boot/l4bin/rmgr-ux -symbols -lines -sigma0 /home/zugwan/boot/l4bin/sigma0-ux -fb_program /home/zugwan/boot/fiasco_ux/ux_con -irq0 /home/zugwan/boot/fiasco_ux/irq0 -t 32768 -G 640x480@16 -l /home/zugwan/boot/l4bin/names -l /home/zugwan/boot/l4bin/log -l /home/zugwan/boot/l4bin/dm_phys -l /home/zugwan/boot/l4bin/simple_ts -l /home/zugwan/boot/l4bin/fuxfprov -n9 -l /home/zugwan/boot/l4bin/rtc-ux -n10 -l /home/zugwan/boot/l4bin/l4exec -l /home/zugwan/boot/l4bin/con-ux -n12 -l /home/zugwan/boot/l4bin/loader /home/zugwan/boot/l4bin/run /home/zugwan/boot/cfg/l4linux26.ux Fiasco-UX on Linux 2.6.10-5-386 (i686) Native Syscall Map: 0x1600 Mapped 256 MB Memory + 4096 KB Framebuffer + 4 MB Input Area on FD 3 Loading Module 0x00090000-0x00094dc0 [/home/zugwan/boot/l4bin/sigma0-ux] Loading Module 0x00100000-0x001c61c0 [/home/zugwan/boot/l4bin/rmgr-ux] Copying Module 0x0ea66000-0x0ea843d6 [/home/zugwan/boot/fiasco_ux/Symbols] Copying Module 0x0ea33000-0x0ea6518f [/home/zugwan/boot/fiasco_ux/Lines] Copying Module 0x0ea08000-0x0ea327ac [/home/zugwan/boot/l4bin/names] Copying Module 0x0e9e1000-0x0ea0745f [/home/zugwan/boot/l4bin/log] Copying Module 0x0e982000-0x0e9e000d [/home/zugwan/boot/l4bin/dm_phys] Copying Module 0x0e953000-0x0e981b65 [/home/zugwan/boot/l4bin/simple_ts] Copying Module 0x0e8b1000-0x0e95281f [/home/zugwan/boot/l4bin/fuxfprov] Copying Module 0x0e88e000-0x0e8b0273 [/home/zugwan/boot/l4bin/rtc-ux] Copying Module 0x0e7a1000-0x0e88dd64 [/home/zugwan/boot/l4bin/l4exec] Copying Module 0x0e6d9000-0x0e7a0c7f [/home/zugwan/boot/l4bin/con-ux] Copying Module 0x0e619000-0x0e6d8a04 [/home/zugwan/boot/l4bin/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Nov 24 08:46:52 2005 compiled with gcc 3.4.4 for Intel Pentium Starting Framebuffer: 640x480@16 CPU: GenuineIntel (F:4:1:0) Model: Pentium 4E (Prescott/Nocona) at 3190 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K \uffff-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: 24576 bytes (6 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 68kB for maintenance structures. RMGR: Hello! running on Fiasco bootloader loaded 9 modules at 0e619000-0ea843d7 L4 symbols at 0e5fa000-0e6183d8 (120kB), lines at 0e5c7000-0e5f918f (200kB) total RAM size = 261120 KB (reported by bootloader) received 239300 KB RAM from sigma0 1128 KB reserved for RMGR received no I/O ports attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 a b c d e f ] RMGR: Starting tasks. #05: loading "/home/zugwan/boot/l4bin/names " from 0ea08000-0ea327ac to [ 00240000-002467ea 00247000-00253000 ] starting at entry 00240000 via trampoline page code 0000c464 symbols at 0ea86000-0ea88000 (8kB), lines at 0ea81000-0ea86000 (20kB) #06: loading "/home/zugwan/boot/l4bin/log" from 0e9e1000-0ea0745f to [ 00400000-00406c11 00407000-00439510 ] starting at entry 00400000 via trampoline page code 0000d460 symbols at 0ea7f000-0ea81000 (8kB), lines at 0ea7a000-0ea7f000 (20kB) #07: loading "/home/zugwan/boot/l4bin/dm_phys " from 0e982000-0e9e000d to [ 01500000-01511baa 01512000-015193d0 ] starting at entry 01500000 via trampoline page code 0000e468 symbols at 0ea76000-0ea7a000 (16kB), lines at 0ea6a000-0ea76000 (48kB) #08: loading "/home/zugwan/boot/l4bin/simple_ts " from 0e953000-0e981b65 to [ 01400000-01407ede 01408000-01413830 ] starting at entry 01400000 via trampoline page code 0000f468 symbols at 0ea68000-0ea6a000 (8kB), lines at 0ea62000-0ea68000 (24kB) #09: loading "/home/zugwan/boot/l4bin/fuxfprov" from 0e8b1000-0e95281f to [ 00500000-00521c96 00522000-0053e000 ] starting at entry 00500000 via trampoline page code 00010468 symbols at 0ea5d000-0ea62000 (20kB), lines at 0ea4a000-0ea5d000 (76kB) #0a: loading "/home/zugwan/boot/l4bin/rtc-ux" from 0e88e000-0e8b0273 to [ 01080000-01084abd 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 00011464 symbols at 0ea48000-0ea4a000 (8kB), lines at 0ea44000-0ea48000 (16kB) #0b: loading "/home/zugwan/boot/l4bin/l4exec" from 0e7a1000-0e88dd64 to [ 01100000-01127dee 01128000-01132000 ] starting at entry 01100000 via trampoline page code 00012464 symbols at 0ea3c000-0ea44000 (32kB), lines at 0ea24000-0ea3c000 (96kB) #0c: loading "/home/zugwan/boot/l4bin/con-ux " from 0e6d9000-0e7a0c7f to [ 00b00000-00b23fe2 00b24000-00b2f000 ] starting at entry 00b00000 via trampoline page code 00013464 symbols at 0ea1d000-0ea24000 (28kB), lines at 0ea05000-0ea1d000 (96kB) #0d: loading "/home/zugwan/boot/l4bin/loader /home/zugwan/boot/l4bin/run /home/zugwan/boot/cfg/l4linux26.ux" from 0e619000-0e6d8a04 to [ 01300000-01325306 01326000-01338000 ] starting at entry 01300000 via trampoline page code 000144a4 symbols at 0e9ff000-0ea05000 (24kB), lines at 0e9e9000-0e9ff000 (88kB) simplets| Configured for 64 tasks. fuxfprov| OSKit support: using 128KB at 0x00100000 as heap (growing) fuxfprov| File provider started, registered as 9.02 exec | OSKit support: using 4096KB at 0x00400000 as heap (growing) con | OSKit support: using 128KB at 0x00100000 as heap con | Character size is 8x14, font has 256 characters con | VESA reports 640x480@16 1280bpl (0000) [4096kB] con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 con | Found Fiasco/UX con | Found VHW descriptor, provider is 24195 con | Mapping I/O UX video mem c0000000 => 00400000+000000 [4096kB] con | Using MMXEXT for colorspace transform con | map_inputmemory: paddr = 0xc0400000 con | Input memory page mapped to 0x00c00000 loader | OSKit support: using 128KB at 0x00100000 as heap loader | Can't map tbuf status page (map=00004000, error=00 result=00004000) con | Started input interrupt thread C.03! con | Running as C.02. Video mode is 640x480@16. fuxfprov| open "/home/zugwan/boot/l4bin/run" by D.02 loader | "/home/zugwan/boot/l4bin/run" is a valid binary image loader | Setting libpath to /home/zugwan/boot/l4bin/ exec | run: Loading exec | run: Merging psec 01312000-01314000 with psec 0130d000-01313000 exec | run: Saved 14133 bytes of symbols exec | libloader.s.so: Loading fuxfprov| open "/home/zugwan/boot/l4bin//libloader.s.so" by B.02 exec | libloader.s.so: Saved 21533 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 00004ff0 => 00014ff0 exec | libloader.s.so: Setting section flag 0800 exec | run: Setting section flag 0800 loader | run: Starting l4env-style application loader | run,#e: Starting at l4loader_init (000156a0) exec | run: Linking exec | run: Relocating entry 01300000 => 01300000 exec | run: Packed 25941 bytes of symbols exec | run: Packed 96567 bytes of lines loader | run,#e: Continue at l4env_init (000156b0, libloader.s.so) fuxfprov| open "/home/zugwan/boot/cfg/l4linux26.ux" by D.02 loader | sleeping for 1000 ms run | OSKit support: using 256KB at 0x00040000 as heap (growing) con | vc_loop(): vc[1] running as C.04 con | vc_open_out(): vc[1] 640x480@16, gmode:0x15 run | contxt_init(): 640x462, cols:80, lines:33, sb_lines:1033 fuxfprov| open "/home/zugwan/boot/lx/vmlinuz26.ux" by D.02 exec | vmlinuz26.ux: Loading exec | vmlinuz26.ux: Interpreter section found, contains "/usr/lib/libc.so.1 exec : " exec | vmlinuz26.ux: Saved 756346 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 00004ff0 => 00014ff0 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26.ux: Setting section flag 0800 loader | vmlinuz26.ux: Starting l4env-style application loader | vmlinuz26.ux,#f: Starting at l4loader_init (000156a0) exec | vmlinuz26.ux: Linking exec | vmlinuz26.ux: Relocating entry 00400000 => 00400000 exec | vmlinuz26.ux: Packed 600616 bytes of symbols exec | vmlinuz26.ux: Packed 1616968 bytes of lines loader | vmlinuz26.ux,#f: Continue at l4env_init (000156b0, libloader.s.so) l4lx | crt0_construction called. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Binary name: vmlinuz26.ux l4lx | Kernel command line (8 args): mem=44M noreplacement root=1:0 load_ram l4lx : disk=1 ramdisk_size=16384 l4env_rd=/home/zugwan/boot/rd/rd1 panicblin l4lx : k=0 lang=us l4lx | Image: 00400000 - 0068a1a0 [2600 KiB]. l4lx | Areas: Text: 00400000 - 005b5000 [1748kB] (a bit longer) l4lx | Data: 005b5000 - 005f04cc [237kB] l4lx | Initdata: 005f4000 - 00618000 [144kB] l4lx | BSS: 00618008 - 0068a1a0 [456kB] l4lx | l4lx_thread_create: Created thread 0f.03 (server) l4lx | main thread will be 0f.03 l4lx | l4env_register_pointer_section: addr = 005f2000 size = 159744 l4lx | sec-w-init: virt: 0x005f2000 to 0x00618fff [156 KiB] l4lx | sec-w-init: Number of physical regions: 1, 159744 Bytes l4lx | sec-w-init: 1: Phys: 0x00f69000 to 0x00f90000, Size: 159744 l4lx | l4env_linux_startup thread 3. l4lx | main thread: received startup message. l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 44MB l4lx | Main memory: virt: 0x00800000 to 0x033fffff [45056 KiB] l4lx | Main memory: Number of physical regions: 1, 46137344 Bytes l4lx | Main memory: 1: Phys: 0x0b800000 to 0x0e400000, Size: 46137344 l4lx | Filling lower ptabs... l4lx | Main thread running, waiting... l4lx | Done (1263 entries). l4lx | l4env_rd_path: /home/zugwan/boot/rd/rd1 l4lx | Loading: /home/zugwan/boot/rd/rd1 fuxfprov| open "/home/zugwan/boot/rd/rd1" by F.03 l4lx | INITRD: Size of RAMdisk is 16384KiB l4lx | RAMdisk from 03400000 to 04400000 [16384KiB] l4lx | l4lx_thread_create: Created thread 0f.04 (timer.i0) KERNEL: f.3 (tcb=00000000203c1800) killed: Unhandled trap ip:60965b EAX 00000001 EBX 00000001 ECX 0107fe80 EDX 00000cfb ESI 00000000 EDI 00828000 EBP 00829fa4 ESP 00829f98 EIP 0060965b EFLAGS 00010046 CS 0002 SS 007b DS 007b ES 007b FS 0000 GS 0007 trap 13 (General Protection), error 00000000, from user mode (internal event regarding GDT entry no. 0x00) --------------------------------------------------------------------------------------------------- /home/zugwan/l4/l4linux-2.6/vmlinux: file format elf32-i386 Disassembly of section .text: Disassembly of section .plt: Disassembly of section .init.text: 006095db <pci_sanity_check+0x3b>: pci_sanity_check(): /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:193 6095db: 83 c4 18 add $0x18,%esp 6095de: 85 c0 test %eax,%eax 6095e0: 75 e4 jne 6095c6 <pci_sanity_check+0x26> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:195 6095e2: 8b 45 f0 mov 0xfffffff0(%ebp),%eax 6095e5: 3d 00 06 00 00 cmp $0x600,%eax 6095ea: 0f 94 c2 sete %dl 6095ed: 3d 00 03 00 00 cmp $0x300,%eax 6095f2: 0f 94 c0 sete %al 6095f5: 09 d0 or %edx,%eax 6095f7: a8 01 test $0x1,%al 6095f9: 75 2c jne 609627 <pci_sanity_check+0x87> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:198 6095fb: 56 push %esi 6095fc: 6a 02 push $0x2 6095fe: 6a 00 push $0x0 609600: 53 push %ebx 609601: 6a 00 push $0x0 609603: 6a 00 push $0x0 609605: ff 17 call *(%edi) 609607: 83 c4 18 add $0x18,%esp 60960a: 85 c0 test %eax,%eax 60960c: 75 b8 jne 6095c6 <pci_sanity_check+0x26> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:200 60960e: 8b 45 f0 mov 0xfffffff0(%ebp),%eax 609611: 3d 86 80 00 00 cmp $0x8086,%eax 609616: 0f 94 c2 sete %dl 609619: 3d 11 0e 00 00 cmp $0xe11,%eax 60961e: 0f 94 c0 sete %al 609621: 09 d0 or %edx,%eax 609623: a8 01 test $0x1,%al 609625: 74 9f je 6095c6 <pci_sanity_check+0x26> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:201 609627: b8 01 00 00 00 mov $0x1,%eax /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:206 60962c: 8d 65 f4 lea 0xfffffff4(%ebp),%esp 60962f: 5b pop %ebx 609630: 5e pop %esi 609631: 5f pop %edi 609632: 5d pop %ebp 609633: c3 ret /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:205 609634: 31 c0 xor %eax,%eax 609636: eb f4 jmp 60962c <pci_sanity_check+0x8c> 609638: 90 nop 609639: 8d b4 26 00 00 00 00 lea 0x0(%esi),%esi 00609640 <pci_check_type1>: pci_check_type1(): /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:209 609640: 55 push %ebp 609641: 89 e5 mov %esp,%ebp 609643: 56 push %esi 609644: 53 push %ebx 609645: 51 push %ecx /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:214 609646: e8 a5 7c df ff call 4012f0 <l4x_local_save_flags> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:212 60964b: 31 f6 xor %esi,%esi /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:214 60964d: 89 c3 mov %eax,%ebx 60964f: e8 7c 7c df ff call 4012d0 <l4x_local_irq_disable> /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:395 609654: b0 01 mov $0x1,%al 609656: ba fb 0c 00 00 mov $0xcfb,%edx 60965b: ee out %al,(%dx) /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:397 60965c: b2 f8 mov $0xf8,%dl 60965e: ed in (%dx),%eax 60965f: 89 45 f4 mov %eax,0xfffffff4(%ebp) 609662: b8 00 00 00 80 mov $0x80000000,%eax 609667: ef out %eax,(%dx) 609668: ed in (%dx),%eax 609669: 3d 00 00 00 80 cmp $0x80000000,%eax 60966e: 74 20 je 609690 <pci_check_type1+0x50> 609670: ba f8 0c 00 00 mov $0xcf8,%edx 609675: 8b 45 f4 mov 0xfffffff4(%ebp),%eax 609678: ef out %eax,(%dx) /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:223 609679: 53 push %ebx 60967a: e8 81 7c df ff call 401300 <l4x_local_irq_restore> 60967f: 58 pop %eax /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:226 609680: 8d 65 f8 lea 0xfffffff8(%ebp),%esp 609683: 89 f0 mov %esi,%eax 609685: 5b pop %ebx 609686: 5e pop %esi 609687: 5d pop %ebp 609688: c3 ret 609689: 8d b4 26 00 00 00 00 lea 0x0(%esi),%esi /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:397 609690: 68 58 82 5c 00 push $0x5c8258 609695: e8 06 ff ff ff call 6095a0 <pci_sanity_check> 60969a: 5a pop %edx 60969b: 85 c0 test %eax,%eax 60969d: 74 d1 je 609670 <pci_check_type1+0x30> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:220 60969f: 66 be 01 00 mov $0x1,%si 6096a3: eb cb jmp 609670 <pci_check_type1+0x30> 6096a5: 8d 74 26 00 lea 0x0(%esi),%esi 6096a9: 8d bc 27 00 00 00 00 lea 0x0(%edi),%edi 006096b0 <pci_check_type2>: pci_check_type2(): /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:229 6096b0: 55 push %ebp 6096b1: 89 e5 mov %esp,%ebp 6096b3: 57 push %edi 6096b4: 56 push %esi 6096b5: 53 push %ebx /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:233 6096b6: e8 35 7c df ff call 4012f0 <l4x_local_save_flags> /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:231 6096bb: 31 f6 xor %esi,%esi /home/zugwan/l4/l4linux-2.6/arch/l4/pci/../../i386/pci/direct.c:233 6096bd: 89 c3 mov %eax,%ebx 6096bf: e8 0c 7c df ff call 4012d0 <l4x_local_irq_disable> /home/zugwan/l4/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h:395 6096c4: 31 c0 xor %eax,%eax 6096c6: ba fb 0c 00 00 mov $0xcfb,%edx 6096cb: ee out %al,(%dx) 6096cc: bf f8 0c 00 00 mov $0xcf8,%edi 6096d1: 89 fa mov %edi,%edx 6096d3: ee out %al,(%dx) 6096d4: b9 fa 0c 00 00 mov $0xcfa,%ecx 6096d9: 89 ca mov %ecx,%edx Disassembly of section .altinstr_replacement: Disassembly of section .exit.text:

2 1

ANNOUNCE: Qualcomm uses L4!
by Gernot Heiser 23 Nov '05

23 Nov '05

NICTA today announced a collaborative effort with QUALCOMM Incorporated to use NICTA versions of the L4 Microkernel and the Iguana operating system together with select versions of QUALCOMM's Mobile Station)TM) chipsets. See http://www.ertos.nicta.com.au/press/051124_L4_Qualcomm_vfinal.pdf for the full press release. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

ANNOUNCE: NICTA embedded OS framework released
by Gernot Heiser 23 Nov '05

23 Nov '05

The NICTA ERTOS team is pleased to announce the fist official release of its embedded OS framework, consisting of: * NICTA::Pistachio-embedded, the first kernel conforming to the L4-embedded API. NICTA::Pistachio is based on L4Ka::Pistachio; * Iguana, an L4-based OS personality developed specifically for embedded systems; * Kenge, a set of packages for building microkernel-based systems; * Wombat, a de-privileged (para-virtualised) Linux server running on top of L4/Iguana. Presently the full package works on ARM and x86 platforms. MIPS64 is fully supported except for Wombat (which is due for release shortly) and an Alpha version is not far behind. The system is very mature (in commercial deployment); NICTA::Pistachio-embedded is the fastest and most mature L4 kernel on ARM. See also the http://www.ertos.nicta.com.au/Research/news/. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

Re: What happens on timeslice overrun?
by Udo A. Steinberg 23 Nov '05

23 Nov '05

On Sun, 14 Aug 2005 22:16:09 +0200 Rene Wittmann (RW) wrote: RW> I have 2 questions on the RT part in DROPS: RW> RW> 1.) I have 2 RT working threads, each with 3 timeslices: RW> Thread 1: period=10ms RW> ts1=30ms prio1=50 RW> ts2=10ms prio2=30 RW> ts3=20ms prio3=50 RW> RW> Thread 2: period=10ms RW> ts1=20ms prio1=40 RW> ts2=5ms prio2=30 RW> ts3=10ms prio3=40 RW> RW> Assume both threads are ready at the same time. RW> So thread 1 starts and does its work until it RW> releases the voluntarily or it's preempted by RW> its preempter-thread. So say it releases RW> voluntarily after 20ms. When you say "it's preempted by its preempter thread", do you mean the situation when a preempter with a higher priority than the current thread receives a preemption IPC from the kernel and thus preempts the current thread? RW> Who will get the left 10ms? I guess nobody. When a thread is preempted (that means it gets involuntarily descheduled), the remaining time quantum is saved and later restored when the thread is scheduled again. If the thread yields its scheduling context (that means it voluntarily gives it away), the time quantum is no longer available to the thread. A yield can happen in two ways depending on the target thread id specified: 1) if the target ID is the NIL_ID, then the thread yields its active scheduling context to noone - the time is effectively gone. This is what next_reservation does. Note that the kernel checks the user-specified ID, to guard against the case where a thread wants to yield its active scheduling context and the time quantum on that scheduling context expires simultaneously. 2) if the target ID is a valid thread ID in the system, then the action depends on whether the specified thread is ready to run: a) if it is, then the current thread donates the current scheduling context to the specified thread and that thread then becomes the current thread. This is similar to what happens during a donating IPC. b) if the specified thread is not ready, then the current scheduling context is gone, similar to 1) RW> Or can I assign my left time to a specific RW> thread, say ts2 of thread 1, that is has 20ms RW> after recognizing that ts1 was finished 10ms RW> earlier?I could do with l4_rt_change_timeslice(), RW> but this would probably not work for the the RW> current period! (or yes?) A thread can yield the current scheduling context to another thread as described in 2a) above. Note that the thread will yield the current scheduling context (which may not necessarily be the thread's own active scheduling context). As an example consider: A sends a donating IPC to B, now B runs on A's scheduling context. If B yields to C, then C will run on A's time and B will not donate its own scheduling context. If the current scheduling context is in fact the active scheduling context of the donating thread, then realize that the donating thread will likely encounter a timeslice overrun soon after the yield (the donatee will consume the time quantum until it runs out). If you'd rather avoid that, then the donatee will have to yield the scheduling context back to the owner (the original donator) who then has to yield it to noone. Changes to the time quantum of a scheduling context are only visible the next time that scheduling context becomes the current scheduling context. That means if you change the current scheduling context, then the change will not be visible immediately. RW> 2.) Consider we have a deadline miss. And we say RW> l4_rt_next_period(): would it wait for the beginning RW> of the next (which means: RW> period 1: deadline miss RW> period 2: call next period (because we think we're RW> still in period 1)+ wait to end of period RW> period 3: normal work) RW> Or do I have to care that we do not call RW> l4_rt_next_period() in case of a deadline miss? If your thread misses its deadline right before it wanted to call l4_rt_next_period, then l4_rt_next_period blocks the thread until the end of the new period started due to the deadline miss. Since this is likely not what the thread intended to do, it's the preempter's job to handle that situation, e.g. by ex_regs'ing the thread out of it's l4_rt_next_period call. RW> BTW: I compiled the fiasco-kernel with apic+one shot RW> mode. But this should not be relevant for my question. It is indeed not relevant. -Udo.

3 11

how do I...
by Michael Scheibel 22 Nov '05

22 Nov '05

Good evening, I am currently playing around with L4Linux+DOpE and would like to 1. Start and kill L4 processes at runtime (fprov-l4 and run-l4 do not work). 2. Disable the DOpE mouse pointer in the L4Linux console window. 3. Resize the L4Linux console window without just stretching it. 3. Play Quake :) (where do I get it?) Any hints highly appreciated. Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel(a)sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.

4 12

Building Fiasco-UX
by Marko Wolf 21 Nov '05

21 Nov '05

Hi, since several weeks (including now) I can't compile the FIASCO UX target without patching the ../build/auto/std_macros.h file from your CVS. I think it has something to do with the inline definition since the following patch in std_macros.h solves it. #ifndef noinline #define noinline noinline #endif Unfortunately, I have to apply it for every new UX build. Is it a bug or I'm doing something wrong? Best regards Marko PS: The default kernel config (+UX, +UX_CON, +UX_NET) is attached. ----------------------------------------------------------------------------- - ... Making kernel_thread.o /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:104: error: Syntaxfehler before `)' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ISO C++ forbids declaration of `init_switch_time' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: declaration of `int Context::init_switch_time()' outside of class is not definition /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:117: error: ISO C++ forbids declaration of `init_workload' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:119: error: Syntaxfehler before `while' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ISO C++ forbids declaration of `puts' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ` int puts' redeclared as different kind of symbol /usr/include/stdio.h:589: error: previous declaration of `int puts(const char*) ' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: invalid conversion from `const char*' to `int' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:127: error: ISO C++ forbids declaration of `ready_dequeue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: ISO C++ forbids declaration of `sched' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp: In function `int sched()': /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: Syntaxfehler before `->' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:129: error: ISO C++ forbids declaration of `ready_enqueue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:131: error: ISO C++ forbids declaration of `kill_all' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: ISO C++ forbids declaration of `threading_system_active' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: conflicting types for `int Helping_lock::threading_system_active' auto/helping_lock.h:24: error: previous declaration as `bool Helping_lock::threading_system_active' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ISO C++ forbids declaration of `exit' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ` int exit' redeclared as different kind of symbol /usr/include/stdlib.h:640: error: previous declaration of `void exit(int)' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:136: error: Syntaxfehler before `}' token make[2]: *** [kernel_thread.o] Fehler 1 make[2]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make[1]: *** [all] Fehler 2 make[1]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make: *** [all] Fehler 2 -------------------------------------------------------

1 0

[Emscb] Building Fiasco-UX
by Marko Wolf 21 Nov '05

21 Nov '05

Hallo, schon seit längerem (einschließlich der aktuellen Version) von Fiasco bekommen ich und andere beim Kompilieren (w/ gcc 3.3.6) (nur) zum Fiasco-UX Target immer nachfolgende Fehlermeldung, welche vermutlich an einer fehlenden inline Definition liegt. Zumindest müssen wir das ..build/auto/std_macros.h bei jedem UX-Build immer wie folgt patchen: #ifndef noinline #define noinline noinline #endif Gibt es da eine bessere Lösung oder machen wir etwas falsch? Viele Grüße Marko PS: Default Kernel-Config (+UX, +UX_CON, +UX_NET) im Anhang. ------------------------------------------------------------------------------ ... Making kernel_thread.o /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:104: error: Syntaxfehler before `)' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ISO C++ forbids declaration of `init_switch_time' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: prototype for `int Context::init_switch_time()' does not match any in class `Context' auto/context.h:1128: error: candidate is: void Context::init_switch_time() /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: ` int Context::init_switch_time()' and `void Context::init_switch_time()' cannot be overloaded /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:113: error: declaration of `int Context::init_switch_time()' outside of class is not definition /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:117: error: ISO C++ forbids declaration of `init_workload' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:119: error: Syntaxfehler before `while' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ISO C++ forbids declaration of `puts' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: ` int puts' redeclared as different kind of symbol /usr/include/stdio.h:589: error: previous declaration of `int puts(const char*) ' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:122: error: invalid conversion from `const char*' to `int' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:127: error: ISO C++ forbids declaration of `ready_dequeue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: ISO C++ forbids declaration of `sched' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp: In function `int sched()': /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:128: error: Syntaxfehler before `->' token /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:129: error: ISO C++ forbids declaration of `ready_enqueue' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:131: error: ISO C++ forbids declaration of `kill_all' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: ISO C++ forbids declaration of `threading_system_active' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:133: error: conflicting types for `int Helping_lock::threading_system_active' auto/helping_lock.h:24: error: previous declaration as `bool Helping_lock::threading_system_active' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ISO C++ forbids declaration of `exit' with no type /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:135: error: ` int exit' redeclared as different kind of symbol /usr/include/stdlib.h:640: error: previous declaration of `void exit(int)' /home/marko/code/drops/l4/kernel/fiasco/src/kern/kernel_thread.cpp:136: error: Syntaxfehler before `}' token make[2]: *** [kernel_thread.o] Fehler 1 make[2]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make[1]: *** [all] Fehler 2 make[1]: Verlasse Verzeichnis »/home/marko/code/drops/l4/kernel/fiasco/build« make: *** [all] Fehler 2 _______________________________________________ Emscb mailing list Emscb(a)lists.tc.internet-sicherheit.de http://lists.tc.internet-sicherheit.de/mailman/listinfo/emscb

2 1

which libc
by Christoph Mueller 09 Nov '05

09 Nov '05

Hello, I came across dietlibc and uClibc. What is the difference between them? Which one should I use? Thanks, Christoph

2 1

Re: L4Linux without Con or DoPe?
by Marcel Selhorst 06 Nov '05

06 Nov '05

Hi Frank, I tried a lot of things now, but I am not able to get L4Linux working with the VESA-fb and without l4fb through Con/Dope. If I boot Fiasco and L4Linux without l4fb and using vbeset, I see nothing. If I boot Fiasco and L4Linux without l4fb and not using vbeset, I see the log below. (grepped via serial console) If I compile in the VGA-console, l4linux runs smoothly, but I don't get the VESA-fb running... Attaching commandline options to the l4linux-kernel (e.g., vga=791 or video=vesa...) does actually do nothing. Any further ideas? Attached you'll find my .config-file. Thanks in advance and best regards, Marcel Selhorst *loader | vmlinuz26,#d: Starting at l4loader_init (000164d0) *exec | vmlinuz26: Linking *exec | vmlinuz26: Relocating entry 00400000 => 00400000 *exec | vmlinuz26: Packed 721705 bytes of symbols *exec | vmlinuz26: Packed 2050734 bytes of lines *loader | vmlinuz26,#d: Continue at l4env_init (000164e0, libloader.s.so) *l4lx | crt0_construction called. *l4lx | ======> L4Linux 2.6 starting... <======== *l4lx | Binary name: vmlinuz26 *l4lx | Kernel command line (9 args): mem=128M noreplacement root=1:0 load_ra *l4lx : mdisk=1 ramdisk_size=56000 l4env_rd=ramdisk.gz panicblink=0 lang=de v *l4lx : ga=791 *l4lx | My DMphys is at 06.00 *l4lx | My region mapper is at 0d.00 *l4lx | My code starts at 0x00400000 and ends at 0x00740188 [3328 KiB]. *l4lx | Semaphore thread ID: 0d.01 *l4lx | Areas: *l4lx | Text: 00400000 - 00649000 [2340kB] (a bit longer) *l4lx | Data: 00649000 - 006a3388 [360kB] *l4lx | Initdata: 006a6000 - 006d5000 [188kB] *l4lx | BSS: 006d5008 - 00740188 [428kB] *l4lx | l4lx_thread_create: Created thread 0d.03 (server) *l4lx | main thread will be 0d.03 *l4lx | l4env_register_pointer_section: addr = 00400000 size = 3407872 *l4lx | with-init: virt: 0x00400000 to 0x0073ffff [3328 KiB] *l4lx | Noncontinuous region for with-init *l4lx | Probably region overflow for with-init?! *l4lx | with-init: Number of physical regions: 6, 3407872 Bytes *l4lx | with-init: 1: Phys: 0x01415000 to 0x01497000, Size: 532480 *l4lx | with-init: 2: Phys: 0x01150000 to 0x01220000, Size: 851968 *l4lx | with-init: 3: Phys: 0x01355000 to 0x01400000, Size: 700416 *l4lx | with-init: 4: Phys: 0x01259000 to 0x01300000, Size: 684032 *l4lx | with-init: 5: Phys: 0x001ca000 to 0x00240000, Size: 483328 *l4lx | with-init: 6: Phys: 0x010da000 to 0x01100000, Size: 155648 *l4lx | l4env_linux_startup thread 3. *l4lx | main thread: received startup message. *l4lx | setup_l4env_memory: Forcing superpages for main memory *l4lx | Main memory size: 128MB *l4lx | Mainmem DS id: 68 *l4lx | mainmem: virt: 0x00800000 to 0x087fffff [131072 KiB] *l4lx | Main thread running, waiting... *l4lx | mainmem: Number of physical regions: 1, 134217728 Bytes *l4lx | mainmem: 1: Phys: 0x0a800000 to 0x12800000, Size: 134217728 *l4lx | Filling lower ptabs... *l4lx | Done (1047 entries). *l4lx | l4env_rd_path: ramdisk.gz *l4lx | Loading: ramdisk.gz *l4lx | INITRD: Size of RAMdisk is 55000KiB *l4lx | RAMdisk from 08800000 to 0bdb6000 [55000KiB] *l4lx | l4lx_thread_create: Created thread 0d.04 (timer.i0) *l4lx | l4lx_thread_create: Created thread 0d.05 (IRQ12) *l4lx | l4lx_thread_create: Created thread 0d.06 (IRQ15) *l4lx | l4lx_thread_create: Created thread 0d.07 (IRQ1) *l4lx | l4lx_thread_create: Created thread 0d.08 (IRQ11) Frank Mehnert schrieb: > On Friday 28 October 2005 10:45, you wrote: > >>Hi Frank, >> >> >>>Should be possible. Just enable the framebuffer but not l4fb. Where is >>>the problem? >> >>I tried that, but the linux console is just blank and the only output I get >>is from fiasco... > > > Please send me your .config file. > > Frank # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-l4 # Sat Nov 5 15:59:28 2005 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_L4DIR="/Daten/CVS/fiasco/l4" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 # CONFIG_L4_USERPRIV_ONLY is not set CONFIG_L4_EXTERNAL_RTC=y CONFIG_L4_L4ENV_MEMSIZE=32 # CONFIG_L4_TAMED is not set CONFIG_L4_MK_CPU_X86="586" # CONFIG_L4_IRQ_OMEGA0 is not set # # Stub drivers # CONFIG_L4_BLK_DRV=y # CONFIG_L4_FB_DRIVER is not set # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set # CONFIG_L4_SERIAL is not set # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Debuggin options # # CONFIG_L4_DEBUG is not set # # # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_HOTPLUG is not set CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODULE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=y # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_LBD is not set # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_CMD640 is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_SHARE_IRQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # CONFIG_SCSI=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # # CONFIG_BLK_DEV_SD is not set # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set # CONFIG_BLK_DEV_SR is not set # CONFIG_CHR_DEV_SG is not set # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set CONFIG_SCSI_SATA=y # CONFIG_SCSI_SATA_AHCI is not set # CONFIG_SCSI_SATA_SVW is not set CONFIG_SCSI_ATA_PIIX=y # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_PROMISE is not set # CONFIG_SCSI_SATA_QSTOR is not set # CONFIG_SCSI_SATA_SX4 is not set # CONFIG_SCSI_SATA_SIL is not set # CONFIG_SCSI_SATA_SIS is not set # CONFIG_SCSI_SATA_ULI is not set # CONFIG_SCSI_SATA_VIA is not set # CONFIG_SCSI_SATA_VITESSE is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_CPQFCTS is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_NCR53C406A is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS is not set # CONFIG_SCSI_QLOGIC_ISP is not set # CONFIG_SCSI_QLOGIC_FC is not set # CONFIG_SCSI_QLOGIC_1280 is not set CONFIG_SCSI_QLA2XXX=y # CONFIG_SCSI_QLA21XX is not set # CONFIG_SCSI_QLA22XX is not set # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set # CONFIG_SCSI_QLA24XX is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_SEAGATE is not set # CONFIG_SCSI_SYM53C416 is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_ULTRASTOR is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_DM=y CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_SPI is not set # CONFIG_FUSION_FC is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set # CONFIG_EL16 is not set CONFIG_EL3=y # CONFIG_3C515 is not set # CONFIG_VORTEX is not set # CONFIG_TYPHOON is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y # CONFIG_DE2104X is not set CONFIG_TULIP=y # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y CONFIG_PCNET32=y # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set # CONFIG_CS89x0 is not set # CONFIG_DGRS is not set CONFIG_EEPRO100=y # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y CONFIG_8139CP=y CONFIG_8139TOO=y CONFIG_8139TOO_PIO=y # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000_NAPI is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SKGE is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set CONFIG_BNX2=y # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set CONFIG_SERIO_PCIPS2=y CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=y # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # # I2C support # # CONFIG_I2C is not set # CONFIG_I2C_SENSOR is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=y # CONFIG_HWMON_DEBUG_CHIP is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set CONFIG_FB_MODE_HELPERS=y # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # SN Devices # # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set CONFIG_NFS_V4=y # CONFIG_NFS_DIRECTIO is not set # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_RPCSEC_GSS_KRB5=y # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set CONFIG_FRAME_POINTER=y # CONFIG_EARLY_PRINTK is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y

2 1

Unofficial and experimental release of Kaffe on DROPS/L4
by Alexander Boettcher 06 Nov '05

06 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, at [1] you can find a snapshot of a packet, which contains the latest working Kaffe version (without RTSJ experimental extensions) running on top of DROPS. I'm in contact with Dalibor and Jim in order to merge the DROPS/L4 port in the current cvs version of kaffe.org. However, I already got a request for Kaffe on DROPS, therefore I provide it this way for interested people until it is available from kaffe.org. The packet contains a complete snapshot of the sources of kaffe.org (October this year) and not only the port specific files, because the latest cvs version of kaffe.org doesn't build with the DROPS/L4 port :-(. Please note, the state of the port must be considered as experimental. My port specific code are licensed under GPL and I provide it with no warranty. A README is available at [2]. Best regards, Alexander Boettcher. [1] http://wwwos.inf.tu-dresden.de/~ab764283/kaffe.tar.bz2 - 8,4 MB [2] http://wwwos.inf.tu-dresden.de/~ab764283/README.drops [3] http://wwwos.inf.tu-dresden.de/~ab764283/kaffe.tar.bz2.sig -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDbfuEqjRK9KYzJbMRAu8uAJsEaafL9wEM5SWiXzxGShpNt1yjTACgm8nh Bdq8HK/t5MrU8jLsjN19PTM= =y9fd -----END PGP SIGNATURE-----

1 0

l4linux26 @ fiasco-ux w/ dietlibc
by Marko Wolf 02 Nov '05

02 Nov '05

Hi! I tried running l4linux26 on fiasco-ux compiled from the actual CVS with the dietlibc using the following script: fiasco -t 32768 \ -G800x600@16 \ -m 512 \ -R roottask \ -l names \ -l log \ -l dm_phys \ -l simple_ts -t 380 \ -l fuxfprov -n9 \ -l rtc-ux -n10 \ -l l4exec \ -l l4dope-ux \ -l "loader run l4linux26.cfg" Unfortunatly, l4linux causes a null pointer exceptions (see attached log). I tried various kernel compiler options with always the same error. Any idea for the reason or what I can try else? Thanks a lot Marko PS: By the way, Im using gcc 3.3.6

3 12

fiasco for ARM
by Shakthi Kannan 31 Oct '05

31 Oct '05

Greetings! Couple of questions: 1. Will we be getting an announcement in the mailing list when fiasco moves with uclibc and dietlibc without oskit support? 2. What is the current status of fiasco for ARM (cores 9 and above)? The FAQ mentions only about x86 with i486 and above, but, I found some ARM relevant code in l4sys/include-x2/L4API-l4x2/l4/arm. Is there anyone working with fiasco for ARM? Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com

4 4

L4Linux without Con or DoPe?
by Marcel Selhorst 28 Oct '05

28 Oct '05

Hi Hackers, is there a way to use L4Linux without Con or Dope? In detail, I want to boot L4Linux and give a Linux-framebuffer (not the l4fb!) the control of the videocard, so that the console has direct hw-access. Best regards, Marcel Selhorst

2 2

bootstrap + module
by Christoph Mueller 27 Oct '05

27 Oct '05

Hello, I am reusing some code from dde_linux/examples/sound. But I use bootstrap instead of rmgr. Where do I find correct syntax for menu.lst to specify an additional module (sample.pcm) for my server? The syntax from dde_linux/examples/sound/menu.lst uses RMGR. I think, I have to give a parameter to bootstrap that I can access the additional module in my server. syntax from example: >title sounddrv-foo > kernel (nd)/tftpboot/USER/rmgr -sigma0 task modname "sounddrv-foo" module > module (nd)/tftpboot/USER/fiasco -nowait -nokdb >... what i tried: >title l4snd - l4env >kernel $(P)/bootstrap -sigma0 task modname "l4snd" module >modaddr 0x01500000 >module $(P)/fiasco $(FIASCOARGS) >module $(P)/sigma0 >module $(P)/roottask >module $(P)/names -verbose 2 >module $(P)/log >module $(P)/dm_phys >module $(P)/l4io --noirq >module $(P)/l4snd >modaddr 0x01000000 >module $(P)/snd.pcm sample1 l4env_multiboot_info->mods_count is zero. (I assume no module was assigned to my server.) Thanks, Christoph

3 2

Re: Capability Authentication
by Marcus Völp 21 Oct '05

21 Oct '05

Hi, this is a reply to an email I found in the l4-hurd mail archive [http://lists.gnu.org/archive/html/l4-hurd/2005-10/msg00020.html]. I'm not on the list, sorry. On Fri, 2005-10-07 at 23:01 -0400, Jonathan S. Shapiro wrote: >/ > > And, do we need the second one / >/ > > to be provided by idl4? I say, usually the server will not trust its / >/ > > client and this it's useless, as the server will not use the new handle./ >/ / >/ You are making an incorrect assumption. In general, what you say is/ >/ true, but if the server can authenticate the validity of a capability,/ >/ there is no reason not to use it./ ... The more general solution comes from something we call a "constructor". A "foo constructor" is a server that knows how to create new copies of the "foo" program. Every constructor inserts a unique, unforgeable, and undisclosable capability into the process structure of the process that it creates. This capability is called the "brand". Each constructor uses a different brand from all other constructors. In EROS, there is a kernel capability that performs (approximately) the following operation: interface ProcessTool extends key { bool identify(entry_cap_t someProc, cap_t brand); } Given an entry capability to a process and a second capability, the kernel checks whether the second capability is equal to the existing brand in the process. If so, it returns true, else it returns false. By construction, only constructors hold ProcessTool capabilities. However, if you hold a capability to a foo constructor, and you also hold an entry capability, you can turn to the foo constructor and ask "is this an entry capability to some process that you created?" That is: is it an entry capability to an authentic instance of "foo"? This authentication pattern is enormously important for many of the security arrangements that we are able to achieve in EROS. One of my largest concerns about L4sec is that the L4sec team does not (yet) see that this operation is important. Without an operation like this, it is impossible (or at least, we do not see how) to build robust third-party trust contracts. Jonathan, yes so far L4.Sec does not support such an operation. We thought about (I think Bernard Kauer and Marcus Brinkmann already had a discussion on this topic on l4-hackers) adding a compare operation on endpoints which allows you to match identity of two endpoint capability (compare permissions provided). So far we are not sure whether such an operation is really needed or whether you want to construct systems the way you do. The fundamental issue is that a potentially trusted capability is handed to a server by a not completely trusted source (the client C). We thought briefly about two general solutions to this problem: 1) obtain a version of this capability from a trusted source, or, 2) prepare and defend against potential misbehavior of the invoked server. ad 1: This solution assumes a network of trusted "name"-servers and protocols that require the client C in order to share a capability with some other process S that it establishes this sharing with the target of the capability (D). C can do so by giving its name to S to D and asking D to share the rights S can then request a capability to D from its trusted nameservers and ask for the shared capability provided it trusts D. Please keep in mind that we did not build such a system yet and that it is only a preliminary and potentially not working solution. ad 2: Alternatively the server can prepare to defend against misbehavior of D. In L4.Sec the receiver of an IPC controls the location where an incoming message is placed. Thus it can select an area of its address space so that even if D replies with bogus content, S is not harmed. It remains, however, the problem of blocking S. An easy way to defend against blocking attacks is to fork of a thread for this particular client's request and let it invoke the pot. untrusted capability on behalf of the client. Other thread invoking the same server are not affected by this blocking. Again please keep in mind that both are preliminary solutions. We have still to construct a system on top of L4.Sec. Also please note that L4.Sec is not a fixed API but has experimental status and that we welcome both suggestions for improvement and requirements. However, you will find that features will be added only if they cannot be implemented on top of L4.Sec with a reasonable effort. This is one of the fundamental rules which in my opinion contributed to the success of L4. So please apologize my stubbornness in this point. Compare might be such a feature which will get added if we find no way to achieve what Jonathan listed in his mail. Best regards Marcus Völp -- Marcus Völp TU-Dresden Department of Computer Science Institute for System Architecture Tel: +49 (351) 463-38350 Fax: +49 (351) 463-38284

4 7

Module arguments
by Marcel Selhorst 20 Oct '05

20 Oct '05

Hello L4-Hackers, I have a problem regarding the loading of modules: If I want to load a module and put the regarding entry into the menu.lst including parameters for the module, the module cannot be found in the memory. For example, I have the entry: module (nd)/hddencrypter --with-password-dialog or module (nd)/ramdisk --with-password-dialog (the --with-password-dialog is an argument, which forces GRUB to prompt for a password and afterwards replaces the --with-password-dialog with a new parameter --password='xxx'. This is needed for the harddisc encrypter in order to get the password for decrypting the configuration file). But whenever I put a parameter behind a module, the loader isn't able to locate the entry inside the memory (probably because it compares the whole string?). l4lx | l4env_rd_path: ramdisk l4lx | Loading: ramdisk bmodfs | [B.2] generic_fprov/examples/bmodfs/dm.c:135:dm_open(): bmodfs | Error: Object 'ramdisk' not found! l4lx | Couldn't load RAM disk from fprov! Are there any ideas on how to solve this? Best regards, Marcel Selhorst

2 7

L4.Sec Preliminary Microkernel Reference Manual
by Bernhard Kauer 19 Oct '05

19 Oct '05

The operating system's group at Technische Universit?t Dresden is pleased to announce the first draft of the L4.Sec Preliminary Microkernel Reference Manual. The document can be found at http://os.inf.tu-dresden.de/L4/L4.Sec/ L4.Sec is a specification of a next generation microkernel interface targeted to co-host user-level servers implementing security-critical functionality next to untrusted and potentially malicious software. Bernhard Kauer

1 0

RE: Sawmill's dataspaces and the Hurd's physmem
by yuan Darwin-r62832 19 Oct '05

19 Oct '05

Hi Neal, Thanks for your detailed information. > Physical memory management needn't be an all or nothing deal. Certainly, an application might wish to completely > manage the paging policy and its address space layout, however, I tend to think that this is the exception. And as > we will provide a POSIX personality, we need to have some sort of default VM manager. About general VM manager, what I really mean is just the "default VM manager". However, the question is still there: now that those sort of default VM managers provide mmap to those applications who don't want to manage their phsical memory, should they trust these VM managers? If yes, these applications who use the Sawmill's framework should also trust DSMs, now that DSMs provide mapping to them, and DSMs will manage their own physical memory(implement their own replacement policy, they can even just use the library(LRU) provided by Hurd). So, we can divide the applications into 2 categories: some of them wanna manage their physical memory, others won't. For the applications who do intend to do that, they just apply memory directly from Hurd's physmem server which is trustworthy; For others, they can just use the Sawmill's framework. Note that these DSMs also apply memory from Hurd's physmem, instead of Sawmill physmem DSM. So we can just think these DSMs are just the applications who intend to manager their own physical memory. My conclusion is, if Sawmill's framework has security problem on trust model, so has Hurd. So we have to assume that an application must trust its pager ( or pagers in Sawmill's model). Base on this assumption, Hurd & Sawmill's approach can live together. > I see a number of problems with SawMill's dataspaces. The root of this thread is the presentation of a potential security flaw > in the design of dataspaces. (Whether this is important or not depends on the assumed trust model and security goals.) > Another is that as far as I can tell paging decisions are made towards the root of a dataspace hierarchy and not at the applications themselves. As I said above, for those applications who don't want to manage their own physical memory, they don't need to make paging decision. For others, they just apply memory from Hurd's physmem server, and manage the memory by themselves, which means they can make the paging decision by themselves. Correct me if I have any misunderstanding. Thanks. Darwin

2 1

RE: Sawmill's dataspaces and the Hurd's physmem
by yuan Darwin-r62832 19 Oct '05

19 Oct '05

Hi Neal, By reading the document of Hurd(VMM), I guess I had a misunderstanding about Hurd's approach. Sorry for bothering. Best Regards, Darwin -----Original Message----- From: Neal H. Walfield [mailto:neal@walfield.org] Sent: Tuesday, October 18, 2005 9:40 PM To: yuan Darwin-r62832 Cc: l4-hackers(a)os.inf.tu-dresden.de; l4-hurd(a)gnu.org Subject: Re: Sawmill's dataspaces and the Hurd's physmem At Tue, 18 Oct 2005 19:42:27 +0800, yuan Darwin-r62832 wrote: > I think these 2 approachs are not incompatible. Here are the reasons, > > 1. In Hurd's approach, every application could manage its own > physical memory. However, for most of application developers, they > don't want to take care of the VM replacement policy. To solve this > problem, Hurd has to provide a general VM server to be the pager of > this kind of applications. However, as the philosophy of Hurd, should > this applications trust this server? Physical memory management needn't be an all or nothing deal. Certainly, an application might wish to completely manage the paging policy and its address space layout, however, I tend to think that this is the exception. And as we will provide a POSIX personality, we need to have some sort of default VM manager. The solution that I've opted for is a library based one: a default memory management library will, for instance, implement an LRU based eviction scheme and require no application input. For many applications this will be appropriate and sufficient. Those applications wishing to take complete control will also be able to completely replace the library. I think that some applications can provide useful hints in relatively concise ways. A document viewer, for instance xpdf, might want to cache previously rendered pages. It does not make sense to send these to swap if rereading the data and rerendering is cheaper. In this case, the application can attach a function to drain the cache to a library provided hook which is called when there is memory pressure. I think that this small type of change may offer dramatic results. Moreover, if the change is highly isolated (which in this case seems feasible), it will be easily accepted upstream. An even less invasive hint would be to set some environment variables. Clearly we wouldn't expect most users to set these but an application's packager could based on observed behavior. In the case of e.g. grep or cat we might want to set the read ahead parameter to "very aggressive". If a developper so desires, a more aggressive, but more invasive approach, can also be adopted. Instead of using malloc and free, the application can use a slab allocator. I think this can only be effectively done if the slab allocator participates in the eviction scheme. Again, this is possible in our case with a number of library provided hooks but not for user applications running on a traditional Unix-like core. This can be made backwards compatible by having the configure script check for the required mechanisms and if they are not available then to redefine slab_alloc and slab_free to malloc and free. > 2. In Sawmill's DS approach, every task(AS) has a specific thread > named "region mapper" to be the pager of other threads. It captures > the page fault, then decide to forward it to corresponding server, and > get mapped. So from the higher level point of view, these servers are > the pagers of the task. If Hurd application should trust that general > VM pager, the applications using Sawmill's DS framework should trust > these servers as well. I hope it is now clear that there is no general VM server. > 3. Relative to Sawmill's approach, Hurd provides a clear & great > physical memory server, which makes the whole physical memory of > platform could be fairly used by all of the servers & applications. > > Therefore, we can use Hurd's physmem server as the central > controller. Sawmill's DSMs apply physical memory from it. The > applications who wanna use Sawmill's approach could still walk on > their own way. For some applications who wanna manage their own > physical memory, they can apply memory from physmem server directly. I see a number of problems with SawMill's dataspaces. The root of this thread is the presentation of a potential security flaw in the design of dataspaces. (Whether this is important or not depends on the assumed trust model and security goals.) Another is that as far as I can tell paging decisions are made towards the root of a dataspace hierarchy and not at the applications themselves. Hopefully it is clear why I've choosen to reject this scheme. Thanks, Neal

1 0

RE: Sawmill's dataspaces and the Hurd's physmem
by yuan Darwin-r62832 18 Oct '05

18 Oct '05

Hi Neal, I think these 2 approachs are not incompatible. Here are the reasons, 1. In Hurd's approach, every application could manage its own physical memory. However, for most of application developers, they don't want to take care of the VM replacement policy. To solve this problem, Hurd has to provide a general VM server to be the pager of this kind of applications. However, as the philosophy of Hurd, should this applications trust this server? 2. In Sawmill's DS approach, every task(AS) has a specific thread named "region mapper" to be the pager of other threads. It captures the page fault, then decide to forward it to corresponding server, and get mapped. So from the higher level point of view, these servers are the pagers of the task. If Hurd application should trust that general VM pager, the applications using Sawmill's DS framework should trust these servers as well. 3. Relative to Sawmill's approach, Hurd provides a clear & great physical memory server, which makes the whole physical memory of platform could be fairly used by all of the servers & applications. Therefore, we can use Hurd's physmem server as the central controller. Sawmill's DSMs apply physical memory from it. The applications who wanna use Sawmill's approach could still walk on their own way. For some applications who wanna manage their own physical memory, they can apply memory from physmem server directly. [ physmem ] / \ |_ _| [ DSM ] [Hurd app] (manage physmem by itself] / \ |_ _| [Sawmill app] [Sawmill app] Best Regards, Darwin

2 1

Re: Re: Building device drivers with oskit10_support_l4env
by Christian Helmuth 16 Oct '05

16 Oct '05

Hello, On Thu, Oct 13, 2005 at 08:03:38PM +0800, Jianjun Shen wrote: > I think my solution can not help you - I has not > investigated omega0, but just suspected oskit dose not > correctly request service from omega0. In fact, I am > far from a certain answer, and still can not make my > program always play properly. The scis drivers still > do not work, so I just removed scsi support. Too bad. > Some questions: > 1) I know there is a ore stub in l4lx26, then, is > there a one for flips in lx26? Yes, there is a device driver stub for ore in L4Linux-2.6. For flips, there's no such module as Linux does not support more than 1 TCP/IP instance below its socket layer - remember flips is a fully functional network stack implementation providing a BSD socket API. (You're right if think one could implement a virtual device in L4Linux-2.6 and FLIPS that communicate.) If you're looking for an ore device driver stub for flips, I must put you off until a volunteer appears who wants to implement it / port it from L4Linux-2.6 to Linux2.4-based flips. Maybe you're prepared to do the job? ;) > 2) How you have considered a NIC can be shared by > multiple l4lx instance? One IP per instance, or NAT? Please, do not mistake the network interface layers for the "network layer" (that is IP in TCP/IP). If your L4Linux instances are to share one physical device on device layer, ore is what you want. It switches the NIC into promiscuous mode effectively listening to all traffic on the wire. (Yes, there are performance concerns.) Then ore serves network packets on the basis of MAC addresses to clients. If you want network address translation (NAT), you need router software as NAT works on the "network layer". With some effort you may use FLIPS with virtual device(s) or a special L4Linux instance for that purpose. But in this case, you may also need a virtual (wire) switch. > 3) I found a "l4vfs" in your CVS. What is it? Hence the name, l4vfs implements a kind of virtual file system switch, but I'm far from the right person to give voluminous information. Maybe somebody else could step in here? > 4) I am also interested in IPSec, and I noticed there > is a paper: "IPSec-Infrastruktur für Mikro-SINA" (in > German) - is it about an IPSec implementation? Yes, it is, actually about the IKE part of IPSec. You may also have a look at: http://os.inf.tu-dresden.de/papers_ps/dach2005.pdf > Actually, I am trying to develop a secure system based > on l4, in which all "subject"s share some basic > servers, but can only communicate with separate > untrusted servers (e.g. linux) based on their security > classes. Sounds interesting. Is it a term paper or thesis or something else? > Currently, my project is just at initial stage. So I > may often bother all of you in some days. Thanks > first. > > Best regards! > Jianjun Shen Regards -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

3 2

Re: Using l4ide, l4linux and con together (solved)
by Jianjun Shen 15 Oct '05

15 Oct '05

Hi, Sorry for my last mail. I already got the answer - using both --l4io and --omega0. I also found with the latest CVS version, "con" was unable to load "run". Is it just my individual mistake? Best regards! Jianjun Shen --- Jianjun Shen <weishen_cu(a)yahoo.com.cn>: > Hi, > > Thanks for all of your previous help. But I meet > another problem. ;( > > I tried to use l4linux with l4ide which needs > omega0. > Then, I found "con" would fail to load l4linux if > omega0 was running. How can this problem be solved? > > Best regards! > Jianjun Shen > ___________________________________________________________ 雅虎免费G邮箱－中国第一绝无垃圾邮件骚扰超大邮箱 http://cn.mail.yahoo.com

2 1

Using l4ide, l4linux and con together
by Jianjun Shen 14 Oct '05

14 Oct '05

Hi, Thanks for all of your previous help. But I meet another problem. ;( I tried to use l4linux with l4ide which needs omega0. Then, I found "con" would fail to load l4linux if omega0 was running. How can this problem be solved? Best regards! Jianjun Shen ___________________________________________________________ 雅虎邮箱超强增值服务－2G超大空间、pop3收信、无限量邮件提醒 http://cn.mail.yahoo.com

1 0

Dope Crash during large fb output
by Marcel Selhorst 14 Oct '05

14 Oct '05

Hi Hackers, yesterday I was running Dope with L4Linux. Inside the L4Linux-framebuffer I was compiling some applications, which produce lots of output in a very short time. Well, exactly at that point DoPe crashed. Connecting via my serial port to the kdb I got "Dope exited with -1" or something like that. I will try to reproduce that error or is this known already? Best regards, Marcel Selhorst

2 2

L4Linux and ACPI
by Marcel Selhorst 14 Oct '05

14 Oct '05

Hi, is it possible to compile L4Linux with ACPI-support? I get a mass of L4-errors. Attached you'll find the .config-file and the log. Thanks in advance, Marcel Selhorst # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-l4 # Fri Oct 14 09:09:06 2005 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_L4DIR="/Daten/CVS/fiasco/l4" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 # CONFIG_L4_USERPRIV_ONLY is not set CONFIG_L4_EXTERNAL_RTC=y CONFIG_L4_L4ENV_MEMSIZE=32 # CONFIG_L4_TAMED is not set CONFIG_L4_MK_CPU_X86="586" # CONFIG_L4_IRQ_OMEGA0 is not set # # Stub drivers # CONFIG_L4_BLK_DRV=y CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set # CONFIG_L4_SERIAL is not set # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Debuggin options # # CONFIG_L4_DEBUG is not set # # # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_EXTRA_PASS=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_EFI is not set # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y # CONFIG_ACPI_SLEEP_PROC_SLEEP is not set CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m # CONFIG_ACPI_HOTKEY is not set CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m CONFIG_ACPI_IBM=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_X86_PM_TIMER is not set # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # # CONFIG_APM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=y # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # # CONFIG_ISAPNP is not set # CONFIG_PNPBIOS is not set CONFIG_PNPACPI=y # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_LBD is not set # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_SHARE_IRQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_SCSI is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_DM=y CONFIG_DM_CRYPT=y # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_NET_SB1000 is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set # CONFIG_EL16 is not set CONFIG_EL3=y # CONFIG_3C515 is not set # CONFIG_VORTEX is not set # CONFIG_TYPHOON is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y # CONFIG_DE2104X is not set CONFIG_TULIP=y # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y CONFIG_PCNET32=y # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_B44 is not set # CONFIG_FORCEDETH is not set # CONFIG_CS89x0 is not set # CONFIG_DGRS is not set CONFIG_EEPRO100=y # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y # CONFIG_8139CP is not set CONFIG_8139TOO=y CONFIG_8139TOO_PIO=y # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000_NAPI is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SKGE is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=y # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=y # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HPET is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # CONFIG_TCG_TPM=m # CONFIG_TCG_NSC is not set # CONFIG_TCG_ATMEL is not set CONFIG_TCG_INFINEON=m # # I2C support # # CONFIG_I2C is not set # CONFIG_I2C_SENSOR is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=y # CONFIG_HWMON_DEBUG_CHIP is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # SN Devices # # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_REISERFS_FS_XATTR is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set CONFIG_NFS_V4=y # CONFIG_NFS_DIRECTIO is not set # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_RPCSEC_GSS_KRB5=y # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set CONFIG_FRAME_POINTER=y CONFIG_EARLY_PRINTK=y # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_SHA1=y # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set CONFIG_CRYPTO_AES_586=y # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_PC=y GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 arch/l4/kernel/arch-i386/built-in.o(.init.text+0x896): In function `l4x_hybrid_return': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/kernel/arch-i386/dispatch.c:493: undefined reference to `acpi_reserve_bootmem' arch/l4/kernel/arch-i386/built-in.o(.init.text+0x8c1): In function `l4x_hybrid_return': /Daten/CVS/fiasco/l4linux-2.6/include/asm/l4x/syscall.h:12: undefined reference to `acpi_reserve_bootmem' arch/l4/kernel/arch-i386/built-in.o(.init.text+0xda5): In function `l4x_suspend_user': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/kernel/arch-i386/dispatch.c:981: undefined reference to `acpi_boot_table_init' drivers/built-in.o(.text+0x15f7a): In function `acpi_os_install_interrupt_handler': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/osl.c:291: undefined reference to `acpi_gsi_to_irq' drivers/built-in.o(.text+0x2c68d): In function `acpi_sleep_prepare': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/poweroff.c:27: undefined reference to `acpi_wakeup_address' drivers/built-in.o(.text+0x2c9a9): In function `acpi_pm_enter': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:81: undefined reference to `acpi_save_state_mem' drivers/built-in.o(.text+0x2c9dd):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:95: undefined reference to `do_suspend_lowlevel' drivers/built-in.o(.text+0x2c9f8):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:102: undefined reference to `do_suspend_lowlevel_s4bios' drivers/built-in.o(.text+0x2ca1f):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:120: undefined reference to `acpi_restore_state_mem' drivers/built-in.o(.text+0x2ca72): In function `acpi_pm_finish': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/sleep/main.c:145: undefined reference to `init_8259A' drivers/built-in.o(.text+0x305cc): In function `acpi_pci_irq_enable': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/pci_irq.c:470: undefined reference to `acpi_register_gsi' drivers/built-in.o(.text+0x305e9):/Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/pci_irq.c:479: undefined reference to `acpi_register_gsi' drivers/built-in.o(.text+0x3658a): In function `pnpacpi_allocated_resource': /Daten/CVS/fiasco/l4linux-2.6/drivers/pnp/pnpacpi/rsparser.c:170: undefined reference to `acpi_register_gsi' drivers/built-in.o(.text+0x36629):/Daten/CVS/fiasco/l4linux-2.6/drivers/pnp/pnpacpi/rsparser.c:159: undefined reference to `acpi_register_gsi' drivers/built-in.o(.init.text+0x2981): In function `pci_setup': /Daten/CVS/fiasco/l4linux-2.6/drivers/pci/pci.c:793: undefined reference to `acpi_irq_model' drivers/built-in.o(.init.text+0x29d9):/Daten/CVS/fiasco/l4linux-2.6/drivers/pci/pci.c:791: undefined reference to `acpi_irq_model' drivers/built-in.o(.init.text+0x2a96): In function `acpi_early_init': /Daten/CVS/fiasco/l4linux-2.6/drivers/acpi/bus.c: undefined reference to `acpi_ioapic' drivers/built-in.o(.init.text+0x2ac5): In function `quirk_isa_dma_hangs': /Daten/CVS/fiasco/l4linux-2.6/drivers/pci/quirks.c:56: undefined reference to `acpi_pic_sci_set_trigger' drivers/built-in.o(.init.text+0x2ace): In function `quirk_nopcipci': /Daten/CVS/fiasco/l4linux-2.6/drivers/pci/quirks.c:77: undefined reference to `acpi_sci_override_gsi' arch/l4/pci/built-in.o(.text+0x943): In function `get_base_addr': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/../../i386/pci/mmconfig.c:26: undefined reference to `pci_mmcfg_config' arch/l4/pci/built-in.o(.text+0x951):/Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/../../i386/pci/mmconfig.c:26: undefined reference to `pci_mmcfg_config_nu arch/l4/pci/built-in.o(.init.text+0x41f): In function `pci_mmcfg_init': /Daten/CVS/fiasco/l4linux-2.6/include/asm-l4/l4-arch/asm/io.h: undefined reference to `acpi_parse_mcfg' arch/l4/pci/built-in.o(.init.text+0x431): In function `pci_bios_read': /Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/pcbios.c:181: undefined reference to `pci_mmcfg_config_num' arch/l4/pci/built-in.o(.init.text+0x43a):/Daten/CVS/fiasco/l4linux-2.6/arch/l4/pci/pcbios.c:181: undefined reference to `pci_mmcfg_config'

2 3

Building device drivers with oskit10_support_l4env
by Jianjun Shen 13 Oct '05

13 Oct '05

Hi, I do not know why, but I posted this mail the day before yesterday, and has not found it in l4-hackers mail list (and got no reply). So I re-send the same mail. Sorry, if you receive it twice. I am trying to implement an ide server, and I think I can make use of oskit10_support. As a test, I wrote a simple program which calls start_blk_devices() to initialize block drivers. This test program works well when being linked with oskit10_support, but fails when being linked with oskit10_l4env_support_full. In the latter case, it takes quite a long time to probe irqs for each ide device (I think it dose not finally succeed), and fails to use the default irqs and ports at last. Is it that oskit10_support_l4env is not a completed port to l4env (I guess maybe it still try to allocate irqs and ports from rmgr but not l4io)? Is it possible to make the oskit drivers work with l4env? How to? "Using the OSKit as a base for L4 applications" noted that oskit10_support uses lthread_ex_regs to implement interrupt handling, and it may cause some problems. Dose oskit10_support_l4env still have this problem? Thanks! Jianjun Shen ___________________________________________________________ 雅虎免费G邮箱－No.1的防毒防垃圾超大邮箱 http://cn.mail.yahoo.com

4 8

Problem using remote-cvs
by Christoph Mueller 12 Oct '05

12 Oct '05

Hello, I tried to checkout an actual version of drops from the remote-cvs using the commands given on the website. cvs -d :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs login cvs -z3 -d :pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs checkout l4 dde hello l4env It fails with the following error: [..] cvs checkout: Updating l4/tool/dice/src/parser/inc cvs checkout: failed to create lock directory for `/home/remote-cvs/CVSROOT' (/home/remote-cvs/CVSROOT/#cvs.history.lock): The file access permissions do not allow the specified action. cvs checkout: failed to obtain history lock in repository `/home/remote-cvs' What am I doing wrong? Christoph

2 1

no makefile in v4_branch?
by Matthias Lange 11 Oct '05

11 Oct '05

Hi, I've checked out both the modules "fiasco" and "preprocess" from CVS. Because I am going to work on the v4_branch of Fiasco I've only checked out the v4_branch of the fiasco module. Following the build instructions on http://os.inf.tu-dresden.de/fiasco/use.html I wasn't able to locate the Makefile in l4/kernel/fiasco. Checking out the complete module "fiasco" and later updating it with "cvs update -r v4_branch" removes this Makefile. Is this intended behavior or is this Makefile just missing in the v4_branch? Regards, Matthias.

2 1

l4-ux
by Alan Grimes 10 Oct '05

10 Oct '05

Here's wut I get when trying to compile l4-ux: (ofcourse this is a second make run...) I wish I knew how you managed to get a guest kernel to run like this anyway... I wish I knew how you figured out to get a guest kernel to run when the documentation that comes with linux sucks so badly... ################# atg@leenooks ~/source/pot $ make make -r -I"/home/atg/source/l4/kernel/fiasco/src" -f "/home/atg/source/l4/kernel/fiasco/src"/Makefile srcdir="/home/atg/source/l4/kernel/fiasco/src" "all" make[1]: Entering directory `/home/atg/source/pot' make srcdir=/home/atg/source/l4/kernel/fiasco/src -f /home/atg/source/l4/kernel/fiasco/src/Makefile.sub1 make[2]: Entering directory `/home/atg/source/pot' Checking compiler config... unchanged. make[2]: Leaving directory `/home/atg/source/pot' make srcdir=/home/atg/source/l4/kernel/fiasco/src -f /home/atg/source/l4/kernel/fiasco/src/Makefile.sub2 all make[2]: Entering directory `/home/atg/source/pot' ... Making entry-ia32-ux.o ... Making sighandler.o ... Making shortcut-ia32-ux.o ==> Linking kernel.image /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../../i686-pc-linux-gnu/bin/ld: errno: TLS definition in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a(errno.o) section .tbss mismatches non-TLS reference in boot_info-ux.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [kernel.image] Error 1 make[2]: Leaving directory `/home/atg/source/pot' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/atg/source/pot' make: *** [all] Error 2 atg@leenooks ~/source/pot $ ################# -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! http://users.rcn.com/alangrimes/

2 1

ANNOUNCE: NICTA L4-embedded API
by Gernot Heiser 05 Oct '05

05 Oct '05

National ICT Australia and the L4Ka Team are pleased to announce the release of the L4-embedded API. It is based on the X.2 API and aims to provide better support for embedded systems. Specifically, it aims to reduce complexity and memory overhead on architectures with limited resources, while keeping the API small, clean, and mostly compatible to X.2. Reference and user manuals for the new ABI are available from the NICTA L4 site http://www.ertos.nicta.com.au/Research/L4/ and from http://l4hq.org/. A release of a first compliant kernel is planned for later this month. Gernot -- Gernot Heiser Program Leader Professor of Operating Systems Embedded, Real-Time, and Operating Systems University of New South Wales National ICT Australia (NICTA) http://gernot.web.cse.unsw.edu.au http://ertos.nicta.com.au Phone: +61 2 8306 0550 Fax: +61 2 8306 0406

1 0

Re: l4dm_mem_open call from L4Linux user process
by Julian Grizzard 05 Oct '05

05 Oct '05

All, I accidentally responded off list to this topic. Here's Adam's reply that may be helpful to others with similar questions to this thread. Adam's suggestion on where to look for example code and other comments are below. I was able to use the example code to create two linux apps, one which creates a DS and another that attaches to that DS. Julian -------- Original Message -------- Subject: Re: l4dm_mem_open call from L4Linux user process Date: Thu, 29 Sep 2005 22:05:18 +0200 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: Julian Grizzard <grizzard(a)ece.gatech.edu> References: <433ABD93.2020303(a)ece.gatech.edu> <20050929074724.GL31351(a)os.inf.tu-dresden.de> <433C3AE5.4070601(a)ece.gatech.edu> On Thu Sep 29, 2005 at 15:05:09 -0400, Julian Grizzard wrote: > Adam Lackorzynski wrote: > > Hi, > > > > On Wed Sep 28, 2005 at 11:58:11 -0400, Julian Grizzard wrote: > > > >>I've been working with the dataspace calls with the L4Env running x86 > >>Fiasco. I am trying to create a dataspace from a L4Linux user process, > >>but I am having trouble getting the program to compile. Is my Makefile > >>correct for what I am trying to do? Is there any reason I shouldn't be > >>able to link to l4dm_mem_open from a L4Linux user process? Below is my > >>source, Makefile, and compiler error message. Help much appreciated! > >> > > > > > > Umm, basically it's possible to create a new DS in an L4Linux user app, > > as it is created at your DS manager (so most likely dm_phys). This has > > nothing to do with L4Linux or the user app in the first place. > > Attaching to it is a different issue altogether! > > > > Alright, so my eventual goal would be to attach to the DS as well. So, > attaching to a DS is going to be a problem? I figured I would try a > simple case first: just create the DS. The address space of a Linux user app is handled by the Linux server, so if one starts mapping stuff in there without telling Linux it may just overmap this area as it believes it is free, or in other words, no one is mapping stuff in there (which cannot happen in native Linux, so this is ok). So now one could start telling Linux about that region. I think the cleanest way would be to hack something in L4Linux to exclude/reserve a region in an address space of a task. This has not been done yet. Something cheaper could be to mmap something and then overmap it itself, or similar. Depending on what you want to do, there's a good example in l4/pkg/loader/examples/fprov-l4/main.c where a DS is opened but the attaching is done in a way that it works, i.e. some memory in BSS is allocated and unmap, and then, at this location, a page from the DS is mapped in. Just have a look, maybe this is ok for you. > >>---------- SOURCE ---------- > >>#include <l4/dm_mem/dm_mem.h> > >>#include <l4/l4rm/l4rm.h> > >> > >>#include <l4/sys/types.h> > >>#include <l4/dm_generic/types.h> > >> > >>int main(int argc, char**argv){ > >> l4dm_dataspace_t ds; > >> void *addr; > >> > >> l4dm_mem_open(L4DM_DEFAULT_DSM,8192,0,0,"L4RM example",&ds); > >> printf("hi\n"); > >> > >> return 0; > >>} > >> > >>---------- MAKEFILE ---------- > >>PKGDIR ?= ../.. > >>L4DIR ?= $(PKGDIR)/../.. > >> > >>TARGET = $(PKGNAME) > >> > >>MODE = host > > > > > > Mode 'host' has no L4 specific libs, includes etc, try 'l4linux' which > > gives you host + L4 stuff. > > > > This should basically fix your linking problem because the libs you link > > have dependencies to other libs which must be fulfilled. > > Okay, I've tried mode = l4linux. Now I get the error message below. > Looks like some libraries are still not getting pulled in. Do I need to > manually specify some L4LIBS? I tried several combinations but didn't > get anywhere. Any ideas? Whoa, looks like this was the wrong approach. This is pulling much more in which is really too low level for a Linux program. But have a look at the fprov-l4 example, it is hopefully enough for what you want to do. Cheers, Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

drops-demo from hard disk
by Shakthi Kannan 04 Oct '05

04 Oct '05

Greetings! I would like to know if its possible to dump the drops-demo-floppy.img to a primary partition of the hard disk and boot from it? I tried dumping the image to /dev/hdb3 using dd: dd if=drops-demo-floppy.img of=/dev/hdb3 bs=512 count=2880 The above worked fine. I tried to boot it from grub in the MBR using: root (hd0,3) chainloader +1 I get " root (hd0,3) Filesystem type unknown, partition type 0x83 chainloader +1 GRUB" Do we need any filesystem support in drops-demo-floppy.img for it? My GNU/Linux boot entry is: " root (hd0,2) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hdb3 ro single initrd /boot/initrd-2.4.27-2-386 boot " My partitioning scheme is: /dev/hdb1 - fat32 (data) /dev/hdb2 - swap /dev/hdb3 - linux /dev/hdb4 - 1.44 drops image Any suggestions? Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 2

env.ipc_error: unknown
by Shakthi Kannan 30 Sep '05

30 Sep '05

Greetings! I have been working on the BID tutorial in writing the hiworld example. I was able to complete the exercise :) I just found one compilation error, in "4.3 Client helper library", where it said no member ipc_error for env. Declaration is as follows: CORBA_Environment env = dice_default_environment; One usage in the example is: return -env.ipc_error; I checked l4/tool/dice/include/dice/dice-corba-types.h and for l4x2 version, ipc_error is declared inside a _p union. Hence, the usage of: env._p.ipc_error worked fine. Is that correct? I tested hiclient and hiserver replacing demo-drops images with my compiled ones, and it worked fine. My documentation and the source code can be viewed from: http://www.shakthimaan.com -> fiasco Regards, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

About driver stubs for L4Linux
by Jianjun Shen 29 Sep '05

29 Sep '05

Hello, I try to run multiple L4Linux instances. Dose L4Linux-2.4 or L4Linux-2.6 implement the driver stubs for oshkosh, ide driver and bmodfs? Where can I find them? Thanks! Wei ___________________________________________________________ 雅虎邮箱超强增值服务－2G超大空间、pop3收信、无限量邮件提醒 http://cn.mail.yahoo.com

2 1

l4dm_mem_open call from L4Linux user process
by Julian Grizzard 29 Sep '05

29 Sep '05

All, I've been working with the dataspace calls with the L4Env running x86 Fiasco. I am trying to create a dataspace from a L4Linux user process, but I am having trouble getting the program to compile. Is my Makefile correct for what I am trying to do? Is there any reason I shouldn't be able to link to l4dm_mem_open from a L4Linux user process? Below is my source, Makefile, and compiler error message. Help much appreciated! ---------- SOURCE ---------- #include <l4/dm_mem/dm_mem.h> #include <l4/l4rm/l4rm.h> #include <l4/sys/types.h> #include <l4/dm_generic/types.h> int main(int argc, char**argv){ l4dm_dataspace_t ds; void *addr; l4dm_mem_open(L4DM_DEFAULT_DSM,8192,0,0,"L4RM example",&ds); printf("hi\n"); return 0; } ---------- MAKEFILE ---------- PKGDIR ?= ../.. L4DIR ?= $(PKGDIR)/../.. TARGET = $(PKGNAME) MODE = host SYSTEMS = x86-l4v2 x86-l4x0 # list your .c files here SRC_C = main.c LIBCINCDIR = $(addprefix -I,$(L4INCDIR)) # if your server implements the server side of an idl defined in an idl-file # of your package, list the idl file name(s) here (no path needed) SERVERIDL = # list additional library paths and libraries here LIBS = -ldm_generic -ldm_mem include $(L4DIR)/mk/prog.mk ---------- COMPILER ERROR ---------- jgrizza@tomato:~/build_2.6.01/l4/pkg/create_ds/server/src$ make PWD=/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[1]: Entering directory `/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/jgrizza/build_2.6.01/l4/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -c -DRAM_BASE=0x0 -DUSE_OSKIT=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/jgrizza/build_2.6.01/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/jgrizza/build_2.6.01/drops/include/l4v2 -I../../../../../include/x86 -I/home/jgrizza/build_2.6.01/drops/include/x86 -I../../../../../include -I/home/jgrizza/build_2.6.01/drops/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c -o main.o /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c: In function `main': /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c:12: warning: implicit declaration of function `printf' /home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/main.c:9: warning: unused variable `addr' ==> Linking create_ds LD_PRELOAD=/home/jgrizza/build_2.6.01/l4/tool/gendep/libgendep.so GENDEP_TARGET=create_ds GENDEP_BINARY=ld gcc -o create_ds main.o -L../../../../../lib/x86_586/l4v2 -L/home/jgrizza/build_2.6.01/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/jgrizza/build_2.6.01/drops/lib/x86_586 -L../../../../../lib -L/home/jgrizza/build_2.6.01/drops/lib -ldm_generic -ldm_mem ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0xba): In function `l4dm_mem_open': /home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:87: undefined reference to `LOG_logL' ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0xff):/home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:62: undefined reference to `l4env_get_default_dsm' ../../../../../lib/x86_586/l4v2/libdm_mem.a(open.o)(.text+0x12b):/home/jgrizza/build_2.6.01/l4/pkg/dm_mem/lib/clientlib/src/open.c:65: undefined reference to `LOG_logL' collect2: ld returned 1 exit status make[1]: *** [create_ds] Error 1 make[1]: Leaving directory `/home/jgrizza/build_2.6.01/l4/pkg/create_ds/server/src/OBJ-x86_586-l4v2' make: *** [OBJ-x86_586-l4v2] Error 2 Thanks! Julian

2 1

names memory overlap error
by Shakthi Kannan 28 Sep '05

28 Sep '05

Greetings! Just started playing around with fiasco and l4env. I checked out l4env and hello from CVS, which obtained all the required files. I was able to compile it on my x86 Thinkpad (T41) running Debian Sarge 3.1r0a. I've added an entry in boot/grub/menu.lst as follows: title DROPS/Fiasco u-kernel kernel (hd0,0)/boot/fiasco/rmgr -sigma0 module (hd0,0)/boot/fiasco/main -noserial -nowait -nokdb module (hd0,0)/boot/fiasco/sigma0 module (hd0,0)/boot/fiasco/names module (hd0,0)/boot/fiasco/log module (hd0,0)/boot/fiasco/dm_phys module (hd0,0)/boot/fiasco/hello On boot, I get the following output: " RMGR: Starting tasks #OS: loading "(hd0,0)/boot/fiasco/names" from 0022b000 - 002341a4 to [ 02240000 - 00246b52 The module 02: 02240000 - 00246b52 : (hd0,0)/boot/fiasco/names overlaps with module loaded by bootloader at 00100000 - 001ca240: Rmgr 02: 0022b000 - 002341a4: (hd0,0)/boot/fiasco/names 03: 00235000 - 0023d324: (hd0,0)/boot/fiasco/log 04: 0023e000 - 00252584: (hd0,0)/boot/fiasco/dm_phys 05: 00253000 - 0025d7ef: (hd0,0)/boot/fiasco/hello The reason for this error message is that the modules as loaded by grub interface with their final position as defined by the linker. Most often you can solve this problem by inserting the command "modaddr 0x02000000" immediately as next line after the "kernel=" line of your menu.lst. Note that you have to use a special version of GRUB which is available from http://os.inf.tu-dresden.de/drops/download.html. Return reboots, "k" enters L4 kernel debugging. " I already have grub installed in the MBR of the hard disk, and I don't have a floppy drive in the laptop. 1. Is there any other way I can get these modules loaded and tested? Of course, hello module does not require the names, log, dm_phys modules. It runs fine though with rmgr, main and sigma0. 2. I am particularly interested in device drivers. Is there any documentation that covers these in DROPS other than using Linux device drivers? I'd appreciate any help in this regard. Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 6

[ANN] Fiasco 1.2 released
by Adam Lackorzynski 26 Sep '05

26 Sep '05

The operating system's group at Technische Universität Dresden is pleased to announce the release of version 1.2 of the Fiasco L4 microkernel. Since the last release Fiasco has significantly matured and is now thought to be the most stable version available. For a comprehensive list of changes please consult the CHANGES file in the distribution. Highlights are the integration of scheduling extensions targeted at real-time applications, better support for paravirtualised systems as well as numerous bug-fixes. The Fiasco kernel currently runs on the x86 and Linux/x86 platforms (UX) as well as various ARM platforms. All platform implementations are believed to be equally stable. More information is available at the Fiasco website at http://os.inf.tu-dresden.de/fiasco/ Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Did not find VBE info block
by Shakthi Kannan 26 Sep '05

26 Sep '05

Greetings! I am trying to get the console using l4env and fiasco on an old x86 desktop. Is it like the bash shell? Images have been compiled from CVS sources. All images are booted from the grub present in the demo floppy. The grub entry is as follows: kernel (fd0)/l4/v2/rmgr -sigma0 modaddr 0x01500000 kernel (fd0)/l4/v2/main -noserial -nowait -nokdb kernel (fd0)/l4/v2/sigma0 kernel (fd0)/l4/v2/names kernel (fd0)/l4/v2/log kernel (fd0)/l4/v2/dm_phys kernel (fd0)/l4/v2/con The output that I get while booting is as follows: " con | OSKit support: using 128 KB at 0x00002000 as heap con | Characters size is 8x14, font has 256 characters con | vc_init_gr (): con | [8.2] l4con/server/src/vc.c: 315: vc_init_gr(): con | Did not find VBE info block in multiboot info con | Perhaps you have to upgrade GRUB, RMGR or oskit10_support con | GRUB has to set the video mode with the vbeset command con | con | Alternatively, try passing the --vbemode=<mode> switch con | ----PANIC, 'g' for exit " By console, does it correspond to serial port output or the VGA display? The desktop is a Sony Trinitron multiscan 15sx display. Any suggestions/ideas would be useful, Thanks, SK -- Shakthi Kannan, MS Software Engineer, Specsoft (Hexaware Technologies) [E]: shakthimaan(a)yahoo.com [M]: (91) 98407-87007 [W]: http://www.shakthimaan.com [L]: Chennai, India __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 5

Problems porting L4Linux 2.4 module to 2.6
by Derick Swanepoel 22 Sep '05

22 Sep '05

Hi, I'm trying to convert a custom kernel 2.4 module to 2.6. The most serious problem I'm having is that there are now some unresolved symbols with 2.6: *** Warning: "l4rm_detach" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "kmalloc" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4rm_do_attach" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4env_err_ipcstrings" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4lx_thread_shutdown" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4lx_thread_create" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "l4_sleep" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! *** Warning: "names_waitfor_name" [/home/drops/DROPS-20050908/l4/pkg/test/examples/module.ko] undefined! I see that there is no l4_ksyms.c in l4linux 2.6 like there was in 2.4. Secondly, I get more unresolved symbols if the objects that are linked are specified at the end of the command line instead of the beginning (linking succeeds in both cases, however). The kernel build system puts the objects at the end while the DROPS build system puts them at the beginning. Does anyone have an idea why two otherwise equivalent linking commands would cause such different behaviour depending on the position of the object arguments? Here are the two command lines (the paths are slightly different because the kernel build system always outputs to the source directory: DROPS: gcc -o test_module.o test_dev.o main.o test_dm-client.o -r -nostdlib -nostartfiles -L../../../../../lib/x86_686/l4v2 -L/home/drops/DROPS-20050908/drops/lib/x86_686/l4v2 -L../../../../../lib/x86_686 -L/home/drops/DROPS-20050908/drops/lib/x86_686 -L../../../../../lib -L/home/drops/DROPS-20050908/drops/lib -T../../../../../lib/x86_686/main_rel.ld -ltest_lxk -ldm_generic -ldm_phys -ldm_mem kernel: gcc -r -nostdlib -nostartfiles -L/home/drops/DROPS-20050908/drops/lib/x86_686/l4v2 -L/home/drops/DROPS-20050908/drops/lib/x86_686 -L/home/drops/DROPS-20050908/drops/lib -T/home/drops/DROPS-20050908/l4/lib/x86_686/main_rel.ld -ltest_lxk -ldm_generic -ldm_phys -ldm_mem OBJ-x86_686-l4v2/mesg_dm-client.o -o test_module.o test_dev.o main.o Thanks, Derick

2 4

Problem with hybrid L4Linux task
by Mathias Krause 19 Sep '05

19 Sep '05

Hello Hackers, I've got a problem with a hybrid Linux Task. I want to create a little tool to tranfser data between two L4Linuxes easily. A tool similar to the famous netcat but using IPC instead of UDP/TCP. So far so good. Server is listen for client and client is sending data to the server (using long IPC transfering data as dwords). The problem is that the data doesn't arrive at the server task. There only an empty IPC message gets received (no IPC error). After I've played around a while with debug messages I got strange results. Using debug messages (simple printf()) inbetween and the transfer succedes! Digging a little deeper got me to the point that it must be a problem with the compiler. Using 'gcc -O0' generates working code too - 'gcc -O2' doesn't. Trying another compiler (gcc version 4.0.1 (Debian 4.0.1-2)) with -O2 got me also working code. So my question is if really my gcc (version 3.3.5 (Debian 1:3.3.5-13)) is broken or the includes under l4/l4sys/.../ipc.h. Maybe the inline assembly isn't that clean? But just a guess. My GNU assembly knowlegde isn't that good. Greets, Mathias PS: I'm runing Debian sarge over here.

2 4

Compiling DROPS' dietlibc on FreeBSD
by Julian Stecklina 15 Sep '05

15 Sep '05

Hello, after changing minimal parts of dietlibc's build procedure, I get as far as cd pkg/dietlibc ; gmake actually doing something but it fails with the following error: ... Compiling lib/__v_printf.o LD_PRELOAD=/home/blitz/src/l4/tool/gendep/libgendep.so GENDEP_TARGET=lib/__v_printf.o GENDEP_BINARY=cc1 gcc33 -c -nostdinc -DRAM_BASE=0x0 -DUSE_DIETLIBC=y -DSYSTEM_x86_686 -DARCH_x86 -DCPUTYPE_686 -DL4API_ -I../include -I.. -I../../../idl/OBJ-x86- -I/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i686 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c -o lib/__v_printf.o /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:2:20: stdarg.h: No such file or directory In file included from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7: ../dietstdio.h:12:20: stdarg.h: No such file or directory In file included from ../dietstdio.h:52, from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7: ../include/stdio.h:7:20: stdarg.h: No such file or directory In file included from ../dietstdio.h:52, from /home/blitz/src/l4/pkg/dietlibc/lib/dietlibc/lib/__v_printf.c:7: The include directories look bogus, but I am quite puzzled where they come from. Maybe my directory layout is somehow different from what is expected? Any hint is greatly appreciated. Regards, -- Julian Stecklina Lisp nearing the age of 50 is the most modern language out there. GC, dynamic, reflective, the best OO model extant including GFs, procedural macros, and the only thing old-fashioned about it is that it is compiled and fast. -- Kenny Tilton, comp.lang.python

4 9

[Fwd: Re: Inspect L4Linux Memory]
by Julian Grizzard 15 Sep '05

15 Sep '05

Forgot to copy to list...message below -------- Original Message -------- Subject: Re: Inspect L4Linux Memory Date: Tue, 13 Sep 2005 14:12:14 -0400 From: Julian Grizzard <grizzard(a)ece.gatech.edu> To: Marcus Voelp <voelp(a)os.inf.tu-dresden.de> References: <432214B5.8010109(a)ece.gatech.edu> <43225D54.7040009(a)os.inf.tu-dresden.de> Marcus and all, I like option two better: sharing the dataspace that provides L4Linux with memory. After studying docs under l4/pkg/dm_phys/doc/dm_phys/html, seems like first I need to make an l4dm_share call from the L4Linux server. Then, I should be able make an l4dm_map call from the isolated L4 task. Does this sound like the right general approach? Also, I have a question about the examples under l4/pkg/dm_phys/examples. Take list_ds. There is a call to "if_l4dm_generic_list_call". Where is this call defined? It's not clearly locatable in the API? Is this an IDL thing? I'm not too familiar with IDL. Thanks! -Julian Marcus Voelp wrote: > Hi, > there are actually two nice ways how you can access L4Linux kernel > memory. The first is to install a driver to L4Linux which creates an L4 > thread that in turn would read out the memory when requested to do so. > The second is mapping the L4Linux memory to your external observer by > sharing the dataspace that provides L4Linux with memory. > > The first solution obviously is not suited when reading out much data > and you also rely on the thread to live (i.e., if Linux crashes there is > the chance that the driver thread crashes as well). The second solution > provides a faster read access and survives also kernel crashes. > > Regards > Marcus > > Julian Grizzard wrote: > >> Hi all, >> >> I am running L4Linux 2.6 on Fiasco using L4Env. I would like to build >> an isolated L4 task that can inspect the contents of the L4Linux task >> state. Any pointers on the best way to do this? Conceivably, I could >> map the contents of the L4Linux task into my isolated L4 task to read >> the memory, but I'm not sure the best way to do this. >> >> Thanks! >> >> -Julian >> >> _______________________________________________ >> l4-hackers mailing list >> l4-hackers(a)os.inf.tu-dresden.de >> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >> >> >

3 2

Inspect L4Linux Memory
by Julian Grizzard 10 Sep '05

10 Sep '05

Hi all, I am running L4Linux 2.6 on Fiasco using L4Env. I would like to build an isolated L4 task that can inspect the contents of the L4Linux task state. Any pointers on the best way to do this? Conceivably, I could map the contents of the L4Linux task into my isolated L4 task to read the memory, but I'm not sure the best way to do this. Thanks! -Julian

2 1

Re: Reboot does not work anymore!
by Derick Swanepoel 08 Sep '05

08 Sep '05

Very sorry, this should've gone to the list. ---------- Forwarded message ---------- From: Derick Swanepoel <dswanepoel(a)gmail.com> Date: 08-Sep-2005 12:21 Subject: Re: Reboot does not work anymore! To: Frank Mehnert <fm3(a)os.inf.tu-dresden.de> On 8/17/05, Frank Mehnert <fm3(a)os.inf.tu-dresden.de> wrote: > On Wednesday 17 August 2005 15:48, Leon Brits wrote: > > > Should not does any matter. But how do you set the video mode, via GRUB > > > vbeset of via --vbemode parameter of l4con? > > > > grub > > Hmm. Very strange. When you reboot via the l4con console you most probably > mean the pkg/loader/example/run program. Could you please disassemble that > binary > > objdump -ld loader/example/run/OBJ-x86_586-l4v2/run | less > > and search for pc_reset, right? That function should come from oskit10 and > we did not change anything there. Hi, I'm having the same problem (CVS 20050829). Rebooting does not work from "run" or from JDB. It gets as far saying: Return reboots, "k" enters L4 kernel debugger... Rebooting. Shutting down... but then nothing happens. This is on a Pentium 4 machine. Strangely, however, it works on a Xeon. For what it's worth, here is the disassembled pc_reset(): 013082f0 <pc_reset>: pc_reset(): ../kern/x86/pc/reset.c:30 13082f0: 55 push %ebp 13082f1: 89 e5 mov %esp,%ebp 13082f3: 53 push %ebx 13082f4: 50 push %eax 13082f5: bb 63 00 00 00 mov $0x63,%ebx ../kern/x86/pc/reset.c:34 13082fa: a1 ec 05 31 01 mov 0x13105ec,%eax 13082ff: 66 c7 80 72 04 00 00 movw $0x1234,0x472(%eax) 1308306: 34 12 ../kern/x86/pc/reset.c:39 1308308: 83 ec 0c sub $0xc,%esp 130830b: 68 fe 00 00 00 push $0xfe 1308310: e8 1b 00 00 00 call 1308330 <kb_command> ../kern/x86/pc/reset.c:37 1308315: 83 c4 10 add $0x10,%esp 1308318: 4b dec %ebx 1308319: 79 ed jns 1308308 <pc_reset+0x18> ../kern/x86/pc/reset.c:45 130831b: 0f 01 1d 9e 04 31 01 lidtl 0x131049e ../kern/x86/pc/reset.c:46 1308322: cc int3 1308323: 8b 5d fc mov 0xfffffffc(%ebp),%ebx 1308326: c9 leave 1308327: c3 ret Thanks, Derick

2 1

Sawmill's dataspaces and the Hurd's physmem
by Neal H. Walfield 06 Sep '05

06 Sep '05

During my presentation of the design of the Hurd on L4 to the Dresden group, Lars Reuther asked me if I had considered Sawmill's dataspace model and if so why I had rejected it. My answer was that we want to be able to catch any errors at the time of data acquisition and that relying on a file system server to provide a mapping to the data does not guarantee this: a malicious server can unmap mappings and refuse to remap them; or if the server is shorter lived than the client, the the data becomes inaccessible to the client when the server exits. Lars asked for more details. Unfortunately, I failed to provide a coherent and complete argument: my problem was mainly that I came to this conclusion fairly early in the design process and had since forgotten too many details of Sawmill's architecture to reconstruct my argumentation. I've recently revisited some related issues and am now in a position to better answer Lars's question. My primary reference for the Sawmill framework is [1]. I think I may be able to best explain the problem with an illustration: consider a server providing access to a file system backed by a disk. In the Sawmill dataspace model [1], the file system server is a dataspace manager which likely provides a dataspace for each file. When a task wants to use a file, it first identifies the dataspace associated with the file (e.g. gets a capability to the file from the DM) and attaches it to its address space (e.g. tells its pager to associate a portion of the VM with the capability). "After an attach, the region mapping forwards all page fault requests in that region to the dataspace manager. The dataspace manager resolves the faults with map or grant operations." I understand this to mean that a client depends on a DM to: - provide mappings to data - provide resources backing the data When a client requests some data from a dataspace, the DM provides a mapping to the client. The client can proceed to use the data, however, at any point, the server could cause the mapping to be unmapped and possibly render the data inaccessible. The implication is that the client must either trust the server to always provide the mapping or be prepared to recover should the data disappear. The latter approach can be simplified by making a physical copy of data before committing to using it (which can be done by interposing a second DM between the DM and the client). General use of this tactic means a lot of cycles will be spent copying bytes and a reduction in the amount of physical memory sharing in the system. DMs appear to use their own resources to fetch and store data as well as to hold data (neither [1] nor [2] mentions any mechanism for the client to specify to the DM what memory/data space to read data into). I assume that the normal mode of operation is that a file system DM has a certain amount of physical memory available from a "physical memory" DM which it uses to hold data from backing store. Once that memory is exhausted, it must choose some page to evict. There are several problems with this model: because DMs allocate resources on behalf of clients resources are allocated with the priority of the DM and resource accounting is extremely difficult. We know this from our experience with the Hurd on Mach. Moreover, the DM controls the paging policy; not the clients who are actively using the memory. To control the availability of memory, it would seem that a client would again have to copy the data. [ Physmem DM ] | v [ FS DM ] | v [ client ] The framework that I have developed for the Hurd avoids these dependencies on the file system servers. The physical memory manager ("physmem") is part of the TCB. physmem provides capabilities to so-called containers which identify memory reservations (either specific, e.g. a specific set of frames, or general, e.g. a specific number of frames). Given a container capability, the holder can map the contents or logically copy the contains to or from a second container. When a task wants to read data from a file, it passes a container capability to the file system server. The file system server stores the data in the container (if it already read it into memory then it can logically copy it). Then it returns to the client. If the task wants a mapping to the data, it requests one from physmem. Thus, tasks on the Hurd do not depend on file system server to provide mappings. After the read is complete, the task knows that the data is either available or not available. If the file system server exits, this does not affect the data that the client has. [ physmem ] / \ |_ _| [ client ] [ FS ] Because the client passes containers to the server, the server does not allocate memory to store the data on behalf of the client. (The server may need other resources such as CPU time, I/O bandwidth and state, however, we have other provisions for that.) Thus memory allocations are directly attributed to the client which is vital to the correct functioning of accounting. Also, when the client has exhausted its memory quota, it must free some memory before it can allocate a container with the required reserve. Thus, clients fully control their own paging policy. One of the goals of the Hurd framework is to minimize the number of dependencies that a client has on the behavior of servers. This is important to us because clients often interact with other users's servers which may be malicious. Another goal is to more directly link consumers of resources with resource allocators. Our observation is that many applications are hurt due to policies such as the eviction scheme imposed by the OS. Moreover, applications such as garbage collectors and multimedia applications could benefit from knowing how much real resource is actually available to them. (Applications should work in harmony with the mechanisms provided to them and the policies imposed on them; they should not have to work around them.) Thanks. I have tried to be as concise as possible which means I may have missed some details. I am particularly interested in the thoughts of the Sawmill and DROPS developpers. Neal [1] http://l4ka.org/publications/2001/sawmill-framework.pdf [2] http://os.inf.tu-dresden.de/l4env/doc/l4env-concept/l4env.pdf

4 6

DROPS build success on FreeBSD
by Julian Stecklina 04 Sep '05

04 Sep '05

Hello, I managed to compile most (the documentation fails with latex errors) of DROPS using the attached patch on FreeBSD 5.4. Notes on how to build drops on L4 are attached as well. Notable difficulties in porting: * bash assumed to be in /bin/ (solved with sed) * assuming Linux-style /proc in gendep * assuming dynamically-linked gcc It might be worthwile to make kernel/fiasco/src/Makeconf include mk/Makeconf to avoid redundancy. I think the whole build process would be quite portable with some autoconf magic and with gendep removed. Also I did not test the result. Maybe tomorrow. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

1 1

gendep on FreeBSD
by Julian Stecklina 03 Sep '05

03 Sep '05

Hello, in my quest to get the Fiasco tree buildable on FreeBSD I encountered the following problem (this is with gendep compiled with VERBOSE=1) [...] echo BID_LIBGENDEP=/home/blitz/src/l4/tool/gendep/libgendep.so >>./.Makeconf.bid.converted; echo 'BUILD_PIC += $(BUILD_LOADER_PICS)' >>>>./.Makeconf.bid.converted set -e; X="tmp.$$$RANDOM.c" ; echo 'int main(void){}'>$X ; rm -f $X.out ; LD_PRELOAD=/home/blitz/src/l4/tool/gendep/libgendep.so GENDEP_SOURCE=$X GENDEP_OUTPUT=$X.out gcc33 -c $X -o $X.o; test -e $X.out; echo INT_CPP_x86_NAME=`cat $X.out` >>./.Makeconf.bid.converted; rm -f $X $X.{o,out}; fopen(/proc/self/cmdline) real_fopen(/proc/self/cmdline) gendep: Cannot resolve fopen(): Unknown error: 0 It seems that RTLD magic is somehow broken, but I cannot say how... if someone has a hint, I am all ears. My patches to gendep are attached. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

1 1

Fiasco CVS repository
by Julian Stecklina 03 Sep '05

03 Sep '05

Hello, I have some problems with the CVS repository for Fiasco: cvs diff: failed to create lock directory for `/home/remote-cvs/l4/tool/twiddler' (/home/remote-cvs/l4/tool/twiddler/#cvs.lock): A file or directory in the path name does not exist. cvs diff: failed to obtain dir lock in repository `/home/remote-cvs/l4/tool/twiddler' cvs [diff aborted]: read lock failed - giving up Same goes with 'update' always in the twiddler directory. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

2 2

RE: Critics on L4 (NOT Re: shared memory Beispiel?)
by yuan Darwin-r62832 02 Sep '05

02 Sep '05

Hi, >Hi L4Ka::Pistachio developers, > >I have read the source code of L4Ka::Pistachio-0.4. & found that some >features defined in L4 eXperimental Kernel Reference Manual Version X.2 Revision 5 hasn't been implemented yet. For example, appoint redirector by SpaceControl, IO port mapping, etc. > > Please understand that both Pistachio and Fiasco are research prototypes and that the L4 eXperimental Kernel Reference Manual is indeed EXPERIMENTAL which means that it may change unnoticed and which also means that the prototypes may differ from the specification. The missing features that you state are published, e.g., at http://l4ka.org/projects/pistachio/ia32/ under the section Missing Features / Known Bugs for the Pistachio kernel , respectively at http://os.inf.tu-dresden.de/fiasco/status.html for Fiasco. [Darwin Yuan] Thanks for your information, I started to learn L4 just 1 month. A totally junior. Anything I was wrong, pls correct me. >I tried to checkout the newest source code from CVS, & the CVS server >cvs.l4ka.org couldn't be reached. > > I had no problems reaching the server. Though I cannot confirm that it was up all the time. [Darwin Yuan] Thanks, I'll try later. >When those features are going to be implemented? > Fiasco implements IO Flexpages. Neither Redirectors nor Clans and Chiefs are currently implemented in Fiasco and probably never will. I cannot speak for plans regarding Pistachio. [Darwin Yuan] I didn't read the source code of Fiasco. However, from the documents I got from its website, I found that Clans & Chiefs was implemented in its kernel ( It might be removed now). But I don't think it's a good design that this policy was involved in L4 kernel, now that L4 claims it's a real microkernel. However, I think those kind of policies could be implemented outside kernel. Therefore, I think Redirector is a good mechanism to achieve those kind of policies. That's why I think redirector is very important for implementing a flexible system on L4. >Now that those features are very important for implementing a flexible >OS on L4 u-kernel. > > Both redirectors and IO flexpages are not essential to get a system up and running. Their purpose is to control and restrict communication between threads respectively to prevent a thread from reading / writing IO-ports. Feel free to implement those features if you need them. [Darwin Yuan] Yes, That's true. However, a real system should makes peripheral equipment work. IO Fpage is very essential for implementing hardware driver. Can you elaborate on why you thing missing these features prevents someone building a flexible OS on L4? [Darwin Yuan] As mentioned above. >Seems that there are so many differences between L4Ka::Pistachio and >Fiasco. Is there a stardard L4 specification? > There is a standard L4 Specification: L4-V2 by Jochen Liedtke. Also there is the eXperimental specification you already found which is the defacto standard for L4-V4 kernels. The main difference between Pistachio and Fiasco is that the former implements L4-V4, the latter implements L4-V2 whereby some experimental features have been incorporated into Fiasco to better suite our user level software's needs. As you will see Fiasco already implements some parts of the L4-V4 specification. [Darwin Yuan] I see. Thanks. >I think L4Ka::Pistachio is more clean & flexible, why Fiasco put so >many complicated & inflexible policies inside L4 kernel? > > Which policies are you referring to? Can you elaborate on these points? [Darwin Yuan] For example, Clans & Chiefs. Also, I think "Task" is a redundant abstract/concept, "Address Space" is a much better one. By "Thread" & "Address Space", L4Ka::Pistachio makes the abstract very refined, and allows to construct very flexible system. All together, the APIs of X.2 is much better than X.0. >BTW, has any OS or system been built on L4Ka::Pistachio? As I know, >L4-Linux is built on Fiasco, but I don't like its design. I hope I can >get a reference system based on L4Ka::Pistachio. > > > Lets see, there is L4 Linux which runs on both Fiasco and Pistachio, L4 Env, Drops runs on Fiasco, Kenge, Iguana and Wombat on Pistachio. Also there is Mungi, Perseus, L4 Hurd, etc. Have a look at l4hq.org and you may find out much more. [Darwin Yuan] Thanks for your information. Why don't you like the design of L4Linux or do you mean Fiasco? [Darwin Yuan] Actually, I don't like the APIs & mechanism of Fiasco. Now that L4Linux is based on those APIs & mechanism, I don't like this version of L4Linux. Some more final words: It is common practice on mailing lists to start a new topic if you are referring to a totally different topic. [Darwin Yuan] Honestly, I never use any public mailling list before:(. 'cause this original mail is the first mail I got from this mailing list, I replied it. Someone else has told me about that. Thanks anyway. Best regards Marcus -- Marcus Völp TU-Dresden Department of Computer Science Institute for System Architecture Tel: +49 (351) 463-38350 Fax: +49 (351) 463-38284

5 5

RE: Critics on L4 (NOT Re: shared memory Beispiel?)
by yuan Darwin-r62832 02 Sep '05

02 Sep '05

Hi, Please see my comments below. -----Original Message----- From: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] On Behalf Of Adam Lackorzynski Sent: Friday, September 02, 2005 7:14 AM To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Critics on L4 (NOT Re: shared memory Beispiel?) > Hi, > first, please use a proper quoting style. Your style is very unusual and irritating. First of all, I'd like to say that I won't use your "proper" quoting style, because that's just one of the styles which are used widely. In my mail system, the style which I used is set automatically. & more than 20,000 employees of our company around world are using this. If you don't like it, you don't have to read it. However, because this mail is a reply for you. To make you feel comfortable, I made the style as you want by HAND. Again, as I said before, I'm a junior of L4. However, I have been working in OS fields for many years. So, don't tell me any stupid knowledge & ask any stupid quesiton. On Wed Aug 31, 2005 at 21:00:16 +0800, yuan Darwin-r62832 wrote: > > > >When those features are going to be implemented? > > > > > >Fiasco implements IO Flexpages. Neither Redirectors nor Clans and > > >Chiefs > > >are currently implemented in Fiasco and probably never will. I cannot > > >speak for plans regarding Pistachio. > > >[Darwin Yuan] I didn't read the source code of Fiasco. However, from > >the documents I got from its website, I found that Clans & Chiefs was > >implemented in its kernel ( It might be removed now). But I don't > C&C were never implemented, and will never be, in any kernel. As I said, I didn't the source code of Fiasco, & will never be. Now that the documents declare that, I believed that. Thanks anyway for your telling me this. > think it's a good design that this policy was involved in L4 kernel, > now that L4 claims it's a real microkernel. However, I think those > kind of policies could be implemented outside kernel. Therefore, I > think Redirector is a good mechanism to achieve those kind of > policies. That's why I think redirector is very important for > implementing a flexible system on L4. > So what we have now are inflexible systems? If there isn't any inflexible system, why do we need microkernels? > > >Now that those features are very important for implementing a > > >flexible > > >OS on L4 u-kernel. > > > > > > > >Both redirectors and IO flexpages are not essential to get a system up > >and running. Their purpose is to control and restrict communication > >between threads respectively to prevent a thread from reading / writing > >IO-ports. Feel free to implement those features if you need them. > > > > [Darwin Yuan] Yes, That's true. However, a real system should makes > > peripheral equipment work. IO Fpage is very essential for implementing > > hardware driver. >Not having IO protection doesn't mean you cannot use drivers! Not having IO protection means that everyone >can whack your system because everyone runs with IO privileges, that's it. And you need to do this because >you cannot have drivers otherwise. We lived with that for some time but now we have proper IO protection so everything in fine in this regard. Of course I know we can use drivers by opening IO priviledges for all users. However, providing protection is a very essential responsibility for any secure OS. I'd pleased that you have achieved this. > > >I think L4Ka::Pistachio is more clean & flexible, why Fiasco put so > > >many complicated & inflexible policies inside L4 kernel? > > > > > > > > > Which policies are you referring to? Can you elaborate on these > > >points? > > > >[Darwin Yuan] For example, Clans & Chiefs. Also, I think "Task" is a >That's not the fault of Fiasco, C&C is in the V2 spec. These are different things. And as already mentioned C&C where never implemented >as some clever guys noticed before that there are some problems. Everything I know about Fiasco is from V2 spec & other documents from Fiasco website. Frankly speaking, I don't like that spec. If that spec is the first L4 spec I read, I will definitely lost the interests in researching L4. Fortunately, X2 is the one. > >redundant abstract/concept, "Address Space" is a much better one. By >What's the difference between Task and AS? Task & AS are basically identical. However, when we talk about genenel OS concept, we will say that a Task has its own AS. & may owns some of threads. Even it's hard to figure out the difference, but that's the difference. L4 X2 spec use the AS concept instead of Task, will provide more flexible mechanism. For example, L4 X2 spec allows a non-interrupt thread migrated to another AS. If we use the concept "Task", this mechanism will cause confusion. Because from the point of general OS concept view, a thread transfers between Tasks is a little strange. That's why I think using the term "AS" is a better choice than using "Task". > >"Thread" & "Address Space", L4Ka::Pistachio makes the abstract very > >refined, and allows to construct very flexible system. All together, > >the APIs of X.2 is much better than X.0. >X.2 is the successor of V2/X0 so this is no real surprise. But in which way does the API decide how one's building flexible or inflexible systems? API is the interface provided by OS/kernel to outside. It's the reflection of OS/kernel mechanism. If a OS/kernel don't have a good support for build flexible system, can you easily do it? Another example, if hardware didn't provide MMU, can you easily implement VM? > >Why don't you like the design of L4Linux or do you mean Fiasco? > > > >[Darwin Yuan] Actually, I don't like the APIs & mechanism of Fiasco. > >Now that L4Linux is based on those APIs & mechanism, I don't like this > >version of L4Linux. > Cool. So what would I need to do to make it please you? Actually, you don't need anything. Because L4 x.2 & L4Ka::Pistachio are there. Thanks anyway. 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

1 0

Re: shared memory Beispiel?
by Frank Mehnert 02 Sep '05

02 Sep '05

Hi Mathias, please send questions like this to l4-hackers in every case. Simply because I'm not the only one with knowledge about L4/L4-Userland. The other reason is that other L4 developers might be interested in such questions as well. On Wednesday 31 August 2005 10:03, you wrote: > ich versuche eine L4-Anwendung zu schreiben, die mit shared memory > arbeitet. Konkret soll ein Kernel-Thread in L4Linux-2.6 (ein > Netzwerktreiber-Stub) über den gemeinsamen Speicher mit einem L4-Task > (der ausgelagerte Netzwerktreiber) die zu sendenden, bzw. empfangenen > Rahmen austauschen. Ich hab schon im l4/pkg-Verzeichnis nach etwas > passendem gesucht, doch bin nicht wirklich fündig geworden, wie man dass > nun am Besten macht. > Ich will ja nur ein Stück Speicher fester Größe read/write für zwei > L4-Threads mappen. Muss ich dazu den Dataspacemanager benutzen, oder den > Regionmapper, oder gar l4io? Oder geht das vielleicht doch allein mit > den L4.V2-Systemrufen? I would suggest to use the dataspace manager dm_phys to allocate some memory and to map it into both L4Linux 2.6 and the native L4 task. Mapping into the native L4 task should be no problem as long this task has a region manager (the normal case for L4env tasks) -- simply attach the dataspace to the region manager. To map it into L4Linux 2.6, you have to reserve a range of virtual memory inside the Linux server (Adam, which function should someone use for this?) and then map it into that reserved region via l4dm_map_ds() (see dm_phys manual). Since L4Linux 2.6 makes havy use of L4env functionality, this function is available. Make sure that the whole dataspace is mapped into L4Linux since there is no region manager. Finally, make sure that both tasks have the right to map the dataspace. If the Linux server creates the dataspace it has to share the rights explicitly with the native L4 task with l4dm_share(). A more advanced approach would be to use the DSI (DROPS streaming interface) which is also available at the remote CVS. The DSI provides functions for synchronization between clients accessing the same dataspace. There is the dsi_example package. There might be comments from other people reading this list. > Entschuldige, dass ich Dich mit solch banalen Problemen störe, doch ich > weiß eben nicht, wie man das macht und die Dokumentationen (dm_mem, > dm_phys, L4-Referenzmanual, ...) sind dahingehend nicht gerade > aussagekräftig :/ IMHO there still were some threads about this on l4-hackers (please see http://os.inf.tu-dresden.de/mailman/listinfo/) Frank -- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ##

3 3

RE: shared memory Beispiel?
by yuan Darwin-r62832 31 Aug '05

31 Aug '05

Hi L4Ka::Pistachio developers, I have read the source code of L4Ka::Pistachio-0.4. & found that some features defined in L4 eXperimental Kernel Reference Manual Version X.2 Revision 5 hasn't been implemented yet. For example, appoint redirector by SpaceControl, IO port mapping, etc. I tried to checkout the newest source code from CVS, & the CVS server cvs.l4ka.org couldn't be reached. When those features are going to be implemented? Now that those features are very important for implementing a flexible OS on L4 u-kernel. Seems that there are so many differences between L4Ka::Pistachio and Fiasco. Is there a stardard L4 specification? I think L4Ka::Pistachio is more clean & flexible, why Fiasco put so many complicated & inflexible policies inside L4 kernel? BTW, has any OS or system been built on L4Ka::Pistachio? As I know, L4-Linux is built on Fiasco, but I don't like its design. I hope I can get a reference system based on L4Ka::Pistachio. Best Regards, Darwin Yuan -----Original Message----- From: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] On Behalf Of Frank Mehnert Sent: Wednesday, August 31, 2005 4:36 PM To: Mathias Krause Cc: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: shared memory Beispiel? _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

4 3

Re: gcc3.4 problem
by Leon Brits 31 Aug '05

31 Aug '05

Adam, This must be some Ubuntu thing since it compiles fine on a Gentoo box!? Any way now I get "Panic: deceiving ipc"-error after loading the console (l4con) and trying to start "run". Nothing else is loaded (see attachments). Thanks for all your support! Leon

2 1

problem deploying l4env
by Christoph Mueller 25 Aug '05

25 Aug '05

Hello, I tried to build an l4env enabled simple hello world server, but I was not able to deploy it, because the l4env-servers did not start up. (Hello in sigma0-mode did work.) I have attached output from serial console and menu.lst from grub. Thanks, Christoph

2 2

gcc3.4 problem
by Leon Brits 25 Aug '05

25 Aug '05

Hi all, Based on recent posts on this mailing list I decided to also give GCC 3.4 a go and ran into the following error when compiling l4linux-2.4: ljbrits@abc:/home/drops/DROPS/l4linux-2.4 $ make scripts/split-include include/linux/autoconf.h include/config gcc -D__KERNEL__ -I/home/drops/trunk/l4linux-2.4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -gstabs+ -DLINUX_ON_L4 -I/home/drops/DROPS/l4/include/x86/l4v2 -I/home/drops/DROPS/l4/include/x86 -I/home/drops/DROPS/l4/include -DL4API_l4v2 -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-unit-at-a-time -DKBUILD_BASENAME=main -c -o init/main.o init/main.c init/main.c: In function `init': /home/drops/trunk/l4linux-2.4/include/asm-l4/arch-i386/unistd.h:90: sorry, unimplemented: inlining failed in call to '__SC__open': function body not available init/main.c:105: sorry, unimplemented: called from here /home/drops/trunk/l4linux-2.4/include/asm-l4/arch-i386/unistd.h:89: sorry, unimplemented: inlining failed in call to '__SC__dup': function body not available init/main.c:104: sorry, unimplemented: called from here /home/drops/trunk/l4linux-2.4/include/asm-l4/arch-i386/unistd.h:89: sorry, unimplemented: inlining failed in call to '__SC__dup': function body not available init/main.c:104: sorry, unimplemented: called from here make: *** [init/main.o] Error 1 As I said I installed GCC3.4 on my system (Ubuntu 5.04) and changed all the symlinks in /usr/bin to point to the new installation of gcc and g ++. I made sure that everything was compiling just fine before installing the new compiler. Any suggestions? Thanks Leon

2 1

Interrupt latency in L4Linux
by fabs0028＠free.fr 23 Aug '05

23 Aug '05

Hello, well i 'd like to measure the latency of the interrupts in l4linux, between the moment it is triggered in fiasco and the moment it is aknowledged in the top-halves of linux. Some hints would be greatly appreciated. Thanx for your help. Fabien Chaillou

2 1

Re: l4-hackers Digest, Vol 28, Issue 13
by basant mudalgi 22 Aug '05

22 Aug '05

tanks

1 0

Patches for L4linux
by basant mudalgi 22 Aug '05

22 Aug '05

Hi dont know if this is the right place to send this mail to. I am pretty new to the whole l4 concept. I have been trying to download the l4linux-2.6.12 on my pathetic dial-up connection which is obviously taking longer than expected. i would like to know if there are patches which i can apply to the standard linux (monolithic) kernel to make it an l4linux kernel and save a lot of download time and effort. ie. something like: linux-2.6.xx ----patch----> l4linux-2.6.xx If so where do i find them? If not ...could anyone do the favour? Regards ------------ Basant Mudalgi

2 1

l4linux based distro
by PhilT 19 Aug '05

19 Aug '05

Is L4Linux good enough to be included in a standard Linux distro? I was wondering if anyone was planning to do so? I am trying to compile L4Linux under Ubuntu but am getting lots of error messages during the compile. My lack of knowledge of Linux/L4 etc means it will probably be difficult to ever get this working. Does anyone have pre-compile binaries? Many thanks Rabbit

3 2

RT-Drops : Admission Server
by Arthur Mielimonka 18 Aug '05

18 Aug '05

Hi, when we (Erlangen INF 6) were in Dresden you told us about an Admission Server which assures that periodic realtime-threads can reserve cpu-time with a validation that no over-reservation is made. I didn't find it in the remote-cvs, would you please add it or send it to me? Thanks, Arthur PS: See http://os.inf.tu-dresden.de/papers_ps/steinberg-diplom.pdf , chapter 3.1.3 for the Programming model for Admission Servers

2 1

Via C3 Assertion Failed
by Christoph Mueller 18 Aug '05

18 Aug '05

Hello, I tried to run the demo-CD on my laptop that has a Via C3 CPU. The following error occured: >Assertion failed: '!(*pte & INTEL_PTE_VALID)' > in .../boot/ia32/boot_cpu.cc:450 in function (null) at 00300539 Some more info about the processor: $ cat /proc/cpuinfo: processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 7 model name : VIA Ezra stepping : 8 cpu MHz : 798.007 cache size : 64 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de tsc msr cx8 mtrr pge mmx 3dnow bogomips : 1592.52 Is there a way to run DROPS on Via C3 or should i reinstall the energy-intensive Intel Pentium 3? Thanks, Christoph

2 1

Re: Reboot does not work anymore!
by Frank Mehnert 17 Aug '05

17 Aug '05

On Wednesday 17 August 2005 15:48, Leon Brits wrote: > > Should not does any matter. But how do you set the video mode, via GRUB > > vbeset of via --vbemode parameter of l4con? > > grub Hmm. Very strange. When you reboot via the l4con console you most probably mean the pkg/loader/example/run program. Could you please disassemble that binary objdump -ld loader/example/run/OBJ-x86_586-l4v2/run | less and search for pc_reset, right? That function should come from oskit10 and we did not change anything there. Frank -- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ##

1 0

Reboot does not work anymore!
by Leon Brits 17 Aug '05

17 Aug '05

Hi all, I've moved to the latest CVS checkout of L4 and L4Env and now the "Reboot Sequence" in the console (Shift-6-6) does not work anymore. It prints the second "rebooting" message and then just hangs. Any suggestions? Thanks Leon NB. It is the first time I am using l4con instead of con.

2 1

c++ stl in l4/pkg/libstdc++
by Bert van Leeuwen 17 Aug '05

17 Aug '05

Hi, Can somebody (Frank?) please give me some pointers on how to replace the STL in l4/pkg/libstdc++ for gcc 3.3.x (i.e. /l4/pkg/libstdc++/lib/src-v3 and l4/pkg/libstdc++/contrib/libstdc++-v3)? It seems to be rather an old version, and I would like to try a newer version to eliminate possible sources of error in my program. I tried just replacing drops/include/c++/3.3 with the STL on my box, but that gave hundreds of compile errors. (My program is hanging sporadically, and everytime I get a backtrace into the hung thread, it is somewhere inside STL list. I cannot reproduce this behaviour in linux, only in L4, so I want to see if replacing the STL with a newer version will help) Thanks, Bert

2 1

prebuilt environment
by Julian Stecklina 16 Aug '05

16 Aug '05

Hello, is there somewhere a prebuilt build environment for Fiasco/L4-Env/ DROPS? My primary development box (and in fact all PCs I own) run FreeBSD and I do not plan to switch to some GNU/Linux which most parts of the build process seem to assume. Even a Linux build would be useful to me, as I could run it using the Linuxulator. Regards, -- Julian Stecklina (Of course SML does have its weaknesses, but by comparison, a discussion of C++'s strengths and flaws always sounds like an argument about whether one should face north or east when one is sacrificing one's goat to the rain god.) -- Thant Tessman

2 4

Re: What happens on timeslice overrun?
by Udo A. Steinberg 15 Aug '05

15 Aug '05

On Mon, 15 Aug 2005 15:17:20 +0200 Rene Wittmann (RW) wrote: RW> > When a thread is preempted (that means it gets involuntarily RW> > descheduled), the remaining time quantum is saved and later RW> > restored when the thread is scheduled again. If the thread RW> > yields its scheduling context (that means it voluntarily RW> > gives it away), the time quantum is no longer available to RW> > the thread. A yield can happen in two ways depending on the RW> > target thread id specified: RW> > RW> > 1) if the target ID is the NIL_ID, then the thread yields its active RW> > scheduling context to noone - the time is effectively gone. This is RW> > what next_reservation does. Note that the kernel checks RW> > the user-specified RW> > ID, to guard against the case where a thread wants to RW> > yield its active RW> > scheduling context and the time quantum on that scheduling RW> > context expires RW> > simultaneously. RW> > RW> > 2) if the target ID is a valid thread ID in the system, then RW> > the action RW> > depends on whether the specified thread is ready to run: RW> > a) if it is, then the current thread donates the current scheduling RW> > context to the specified thread and that thread then becomes the RW> > current thread. This is similar to what happens during RW> > a donating IPC. RW> > RW> > b) if the specified thread is not ready, then the current RW> > scheduling RW> > context is gone, similar to 1) RW> > RW> How can I specify the target ID? When creating the thread? But how? The target thread ID for l4_thread_switch, i.e. the thread to yield to, is a parameter to that system call. The L4 interface (see L4.V2 manual) describes the ABI for x86: The following registers are defined for Fiasco: EAX scheduling context ID ESI low part of the target thread ID After the system call returns, the following registers are defined: EAX return value (0 = success, -1 = failure) ECX low part of remaining time on yielded sched. context (if EAX is 0) EDX high part of remaining time on yielded sched. context (if EAX is 0) You probably need not concern yourself with these low-level details of the L4 ABI - there should be bindings in l4/pkg/l4sys that provide high-level interfaces to l4_thread_switch. -Udo.

1 0

AW: What happens on timeslice overrun?
by Rene Wittmann 15 Aug '05

15 Aug '05

> RW> I have 2 questions on the RT part in DROPS: > RW> > RW> 1.) I have 2 RT working threads, each with 3 timeslices: > RW> Thread 1: period=10ms > RW> ts1=30ms prio1=50 > RW> ts2=10ms prio2=30 > RW> ts3=20ms prio3=50 > RW> > RW> Thread 2: period=10ms > RW> ts1=20ms prio1=40 > RW> ts2=5ms prio2=30 > RW> ts3=10ms prio3=40 > RW> > RW> Assume both threads are ready at the same time. > RW> So thread 1 starts and does its work until it releases the > RW> voluntarily or it's preempted by its preempter-thread. So say it > RW> releases voluntarily after 20ms. > > When you say "it's preempted by its preempter thread", do you > mean the situation when a preempter with a higher priority > than the current thread receives a preemption IPC from the > kernel and thus preempts the current thread? > That's what I meant. The preempter has a higher priority and receives the IPC and thus "tells" (via IPC or via common variable if in same address space) the thread to stop the work. > RW> Who will get the left 10ms? I guess nobody. > > When a thread is preempted (that means it gets involuntarily > descheduled), the remaining time quantum is saved and later > restored when the thread is scheduled again. If the thread > yields its scheduling context (that means it voluntarily > gives it away), the time quantum is no longer available to > the thread. A yield can happen in two ways depending on the > target thread id specified: > > 1) if the target ID is the NIL_ID, then the thread yields its active > scheduling context to noone - the time is effectively gone. This is > what next_reservation does. Note that the kernel checks > the user-specified > ID, to guard against the case where a thread wants to > yield its active > scheduling context and the time quantum on that scheduling > context expires > simultaneously. > > 2) if the target ID is a valid thread ID in the system, then > the action > depends on whether the specified thread is ready to run: > a) if it is, then the current thread donates the current scheduling > context to the specified thread and that thread then becomes the > current thread. This is similar to what happens during > a donating IPC. > > b) if the specified thread is not ready, then the current > scheduling > context is gone, similar to 1) > How can I specify the target ID? When creating the thread? But how? > RW> Or can I assign my left time to a specific thread, say > ts2 of thread > RW> 1, that is has 20ms after recognizing that ts1 was finished 10ms > RW> earlier?I could do with l4_rt_change_timeslice(), but this would > RW> probably not work for the the current period! (or yes?) > > A thread can yield the current scheduling context to another > thread as described in 2a) above. Note that the thread will > yield the current scheduling context (which may not > necessarily be the thread's own active scheduling context). > As an example consider: > A sends a donating IPC to B, now B runs on A's scheduling > context. If B yields to C, then C will run on A's time and B > will not donate its own scheduling context. If the current > scheduling context is in fact the active scheduling context > of the donating thread, then realize that the donating thread > will likely encounter a timeslice overrun soon after the > yield (the donatee will consume the time quantum until it runs out). > If you'd rather avoid that, then the donatee will have to > yield the scheduling context back to the owner (the original > donator) who then has to yield it to noone. > > Changes to the time quantum of a scheduling context are only > visible the next time that scheduling context becomes the > current scheduling context. That means if you change the > current scheduling context, then the change will not be > visible immediately. > OK, that's clear now. > RW> 2.) Consider we have a deadline miss. And we say > RW> l4_rt_next_period(): would it wait for the beginning of the next > RW> (which means: > RW> period 1: deadline miss > RW> period 2: call next period (because we think we're > RW> still in period 1)+ wait to end of period > RW> period 3: normal work) > RW> Or do I have to care that we do not call > RW> l4_rt_next_period() in case of a deadline miss? > > If your thread misses its deadline right before it wanted to > call l4_rt_next_period, then l4_rt_next_period blocks the > thread until the end of the new period started due to the > deadline miss. Since this is likely not what the thread > intended to do, it's the preempter's job to handle that > situation, e.g. by ex_regs'ing the thread out of it's > l4_rt_next_period call. > OK, clear. Thanks, Rene

1 0

freebsd style task heap memory
by Bert van Leeuwen 15 Aug '05

15 Aug '05

I've been trying to find info on this in the fiasco docs, but no luck so far. Perhaps someone on this list can give me a brief rundown. How is the heap memory for a freebsd_env style task allocated? I'm not sure whether it comes from dm_phys, rmgr, sigma0 etc. Actually, it would be nice if you could point me to a doc or info about how exactly sigma0,rmgr,dm_phys etc. interact wrt memory management. Thanks in advance!

2 2

What happens on timeslice overrun?
by Rene Wittmann 14 Aug '05

14 Aug '05

Hi, I have 2 questions on the RT part in DROPS: 1.) I have 2 RT working threads, each with 3 timeslices: Thread 1: period=10ms ts1=30ms prio1=50 ts2=10ms prio2=30 ts3=20ms prio3=50 Thread 2: period=10ms ts1=20ms prio1=40 ts2=5ms prio2=30 ts3=10ms prio3=40 Assume both threads are ready at the same time. So thread 1 starts and does its work until it releases the voluntarily or it's preempted by its preempter-thread. So say it releases voluntarily after 20ms. Who will get the left 10ms? I guess nobody. Or can I assign my left time to a specific thread, say ts2 of thread 1, that is has 20ms after recognizing that ts1 was finished 10ms earlier?I could do with l4_rt_change_timeslice(), but this would probably not work for the the current period! (or yes?) I could even imagine that it would work in my case described above, as thread 2 would be next after ts1 of thread 1, but consider thread 2 didn't exist... 2.) Consider we have a deadline miss. And we say l4_rt_next_period(): would it wait for the beginning of the next (which means: period 1: deadline miss period 2: call next period (because we think we're still in period 1)+ wait to end of period period 3: normal work) Or do I have to care that we do not call l4_rt_next_period() in case of a deadline miss? BTW: I compiled the fiasco-kernel with apic+one shot mode. But this should not be relevant for my question. Regards, Rene

1 0

Re: Logging/printf's in RT env
by Rene Wittmann 10 Aug '05

10 Aug '05

Hi, first of all: sorry for my late answer, I've been away... On Thu, Aug 04, 2005 at 03:09:12PM +0200, Adam Lackorzynski wrote: > On Thu Aug 04, 2005 at 13:45:12 +0200, Rene Wittmann wrote: > > I have also the problem that I want to output some of my symbols+values > > during the execution of my application. > > Furthermore I'm working in the RT scheduling mode (with APIC one shot > > mode). > > > > I have three timeslices: > > 1. mandatory > > 2. optional > > 3. "mandatory" (if part of optional was executed) > > > > The preempter recognizes timeslice overruns and sets a > > global variable, the working thread checks this variable and therefore > > knows about those "events". > > > > This works fine if my priorites are set to 50,30,50, > > but fails after a few periods with a pagefault if setting the priorities to > > 200,190,200. > > > > In each part I use some calls to LOG() to output a few things I'm > > interested in. If I leave out those LOG()-calls, it works also with the > > high priorites (200,190,200). > > So I assume, there's a LOG-buffer overflow (as the LOG priority is not > > that high)? > > > > Could I prevent this by using printf instead of LOG or is LOG just a > > kind of macro for printf? > > printf is usually also a log function. > > The priorities of the logserver are at 32, so in the first example > they're inbetween and in the latter one completely below. > > Does the PF go away when you add --prio 210 (or similar) as an argument > to log? > Yes, it goes away. But I thought that, if you have a real-time application running it will not be influenced by some "time-sharing" application as the logserver should be. > Can you send me a backtrace with unstripped binaries when the PF > happens? Thanks. > Sure, I can if you tell me how to do it... The exact error message is: app| L4RM: [PF] write at 0x01306f58, eip 0380e48b, src 9.02 app| [9.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): app| unhandled page fault And then it enters the kernel debugger. I've compiled my program with "CFLAGS = -g" so it should be unstripped, right? But when typing "bt<CR>" in the kernel debugger, there are no symbols and the output just looks like this #4 f000763b #5 f0027332 #6 f000e718 #7 f000627a #8 f000e1fd #9 f000627a #10 f000e1fd #11 f000acb0 #12 f0005f6d #13 f000627a #14 f0006280 #15 f0005c3f #16 f000627a #17 f0006280 #18 f0005aec #19 f999c5f5 #20 f00176ed #21 f0006d54 #22 f0027300 #23 f000cfa5 #24 f0006a5a #25 f000784b #26 f00272dc So I don't expect any helpful information in there or is it? BTW: my grub config looks like this: title llv1_decode (all layers, log locally) root (hd0,2) kernel /drops/bin/x86_586/l4v2/rmgr -sigma0 modaddr 0x08000000 module /l4/kernel/fiasco/build/fiasco_apic -nokdb -nowait -serial -serial_esc module /drops/bin/x86_586/l4v2/sigma0 module /drops/bin/x86_586/l4v2/log_net -net -local -ip 131.188.36.211 -buffer 4096 module /drops/bin/x86_586/l4v2/names module /drops/bin/x86_586/l4v2/dm_phys module /drops/bin/x86_586/l4v2/simple_ts module /drops/bin/x86_586/l4v2/app OK, this modaddr seems huge, but my data is just linked to the binary and I need this huge value... So how would one produce a useful backtrace inside fiasco? Or is there a way to use another debugger (gdb?)? Greetings, Rene

4 4

Fiasco + L4Linux auf echter Hardware
by Marcel Selhorst 09 Aug '05

09 Aug '05

Hallo L4-Hackers, ich kämpfe nunmehr seit drei Tagen mit dem Versuch, Fiasco+L4Linux auf echter Hardware (Pentium 4, 512MB RAM) ans Laufen zu bekommen. Was sich ursprünglich als leichtes Unterfangen anbahnte, entpuppte sich hinlänglich als 'Fiasco' und ich bin mit meinem Latein am Ende :-) Folgende (hoffentlich einfache) Frage: Welche Einstellungen muss man im Fiasco-Kern treffen (mit welchen Experimental- Optionen), und welche im L4Linux, um es gemeinsam ans Laufen zu bekommen? Gibt es zu den einzelnen Optionen irgendwo detailliertere Dokumentationen außer der ein- bis zweizeiligen Onlinehilfe im "make menuconfig"? Ursprüngliche Kompilierungsschwierigkeiten ließen sich durch zwei CVS-Updates an zwei aufeinanderfolgenden Tagen beheben, aber der fiasco bleibt jedesmal beim booten von L4Linux stehen und friert ein, _bevor_ das eigentliche Linux-Fenster in Dope geöffnet wird. Im dmon steht als letzte Zeile: =====> L4Linux 2.6 starting <======= Hoffnungsvolle Grüße, Marcel Selhorst

3 6

Some broken packages in remote-cvs
by Arthur Mielimonka 04 Aug '05

04 Aug '05

Hi, I checked out L4 and tried to compile it. There are some broken packages, which don't compile: /l4/pkg/cpu_reserve/examples/utcb-watch /l4/pkg/loader/examples/fprov-l4 /l4/pkg/dmon/server /l4/pkg/dsi_staticfs /l4/pkg/rt_mon/examples/dope_mon /l4/pkg/rt_mon/examples/l4vfs_dope_mon/ Just to inform you. Bye, Arthur

3 4

Logging/printf's in RT env
by Rene Wittmann 04 Aug '05

04 Aug '05

Hi, I have also the problem that I want to output some of my symbols+values during the execution of my application. Furthermore I'm working in the RT scheduling mode (with APIC one shot mode). I have three timeslices: 1. mandatory 2. optional 3. "mandatory" (if part of optional was executed) The preempter recognizes timeslice overruns and sets a global variable, the working thread checks this variable and therefore knows about those "events". This works fine if my priorites are set to 50,30,50, but fails after a few periods with a pagefault if setting the priorities to 200,190,200. In each part I use some calls to LOG() to output a few things I'm interested in. If I leave out those LOG()-calls, it works also with the high priorites (200,190,200). So I assume, there's a LOG-buffer overflow (as the LOG priority is not that high)? Could I prevent this by using printf instead of LOG or is LOG just a kind of macro for printf? Regards, Rene

2 1

remote gdb stub
by Bert van Leeuwen 04 Aug '05

04 Aug '05

Is there a tutorial or guide somewhere about how to use remote gdb (from a linux machine) to debug an L4 task? I haven't been able to find much more info about this other than casual mention that it is supported...

3 5

i can't find filesystem server pkg and SCSI driver pkg in your CVS
by 강후영 03 Aug '05

03 Aug '05

3 2

kill-l4 fails to kill a task started with run-l4
by Derick Swanepoel 03 Aug '05

03 Aug '05

Hi all, I am using kill-l4 to try and kill a task started with run-l4, but it fails as follows: simplets| l4_ts_kill_recursive_component(): Kill 21.00 sent by 20.00 owner 20.00 simplets| task_kill(): Kill 21.00 from 20.00 but owner is 20.00 | l4ts_kill_task_recursive(): failed (server=8.00, ret=-11, exc 0) Any ideas? Thanks, Derick

2 1

I retry to send mail.. sorry encoding problem..
by ??? 02 Aug '05

02 Aug '05

hello~! I am master course student of pohang university of science and technology in korea I try to l4 testing on fiasco and i have a question.. my machine is only one (now, not used flips NIC) I like to tests that write to SCSI hard disk. I think that this work needs to filesystem server and SCSI driver but i can't find filesystem server pkg and SCSI driver pkg in your CVS how do i get this packages please help me i am looking forward to your answer thank

1 0

i can't find filesystem server pkg and SCSI driver pkg in your CVS
by 강후영 02 Aug '05

02 Aug '05

hello~! I am master course student of pohang university of science and technology in korea   I try to l4 testing on fiasco and i have a question..   my machine is only one (now, not used flips NIC) I like to tests that write to SCSI hard disk.   I think that this work needs to filesystem server and SCSI driver but i can't find filesystem server pkg and SCSI driver pkg in your CVS   how do i get this packages   please help me   thank

1 0

how do i get fliesystem server and SCSI dirver pkg...
by 강후영 02 Aug '05

02 Aug '05

hello~! I am master course student of pohang university of science and technology in korea   I have a question.. my machine is only one (now, not used flips NIC) I like to tests that write to SCSI hard disk.   I think that this work needs to filesystem server and SCSI driver but i can't find filesystem server pkg and SCSI driver pkg in your CVS   how do i get this packages   please help me   thank        

1 0

heap memory usage in L4 drops/oskit task
by Bert van Leeuwen 29 Jul '05

29 Jul '05

How can I check how much heap space is left (or used) in my drops/oskit program? Normally (in linux/gnu) I would use getrusage, which also returns a number of other useful statistics, but this function doesn't seem to exist in drops/oskit...

2 10

Problem compiling docs
by Leon Brits 25 Jul '05

25 Jul '05

Hi all, I've been using Ubuntu (Debian) ever since I started with L4 but always found this problem when compiling the documents. Doxygen 1.4.0.1 is installed as well as TeTex 2.0.2-25. Any suggestions? Thankx Leon <snip> Babel <v3.7h> and hyphenation patterns for american, french, german, ngerman, b ahasa, basque, catalan, croatian, czech, danish, dutch, finnish, greek, iceland ic, irish, italian, latin, magyar, norsk, norsk, portuges, romanian, russian, s lovak, slovene, spanish, swedish, turkish, ukrainian, nohyphenation, loaded. (/usr/share/texmf/tex/latex/base/article.cls Document Class: article 2001/04/21 v1.4e Standard LaTeX document class (/usr/share/texmf/tex/latex/base/size10.clo)) (/usr/share/texmf/tex/latex/base/inputenc.sty (/usr/share/texmf/tex/latex/base/latin1.def)) ! LaTeX Error: File `html.sty' not found. Type X to quit or <RETURN> to proceed, or enter new name. (Default extension: sty) Enter file name: (/usr/share/texmf/tex/latex/tools/longtable.sty) (/usr/share/texmf/tex/latex/base/makeidx.sty) (/usr/share/texmf/tex/latex/misc/geometry.sty (/usr/share/texmf/tex/latex/graphics/keyval.sty) (/usr/share/texmf/tex/latex/config/geometry.cfg)) (/usr/share/texmf/tex/latex/caption/caption.sty) (/usr/share/texmf/tex/latex/fancyvrb/fancyvrb.sty Style option: `fancyvrb' v2.7, with DG/SPQR fixes <2000/03/21> (tvz)) (/usr/share/texmf/tex/latex/fancyhdr/fancyhdr.sty) (/usr/share/texmf/tex/latex/mdwtools/syntax.sty) (/usr/share/texmf/tex/latex/tools/array.sty) (./todo.sty) (/usr/share/texmf/tex/latex/psnfss/times.sty) ! LaTeX Error: Environment htmlonly undefined. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.17 \begin{htmlonly} ? X No pages of output. Transcript written on spec.log. make[2]: *** [spec.dvi] Error 1 make[2]: Leaving directory `/home/ljbrits/DROPS/l4/doc/bid-spec' make[1]: *** [bid-spec] Error 2 make[1]: Leaving directory `/home/ljbrits/DROPS/l4/doc' make: *** [doc] Error 2

2 1

L4Linux hybrid programs
by Adam Lackorzynski 25 Jul '05

25 Jul '05

Hi, I just wanted to announce that hybrid programs for L4Linux-2.6 do _not_ need to be patched anymore. We now added an interface to make it possible to trap system calls making the patching workaround void. As a bonus, Fiasco-UX now runs on L4Linux, if you ever happen to do such things. ;) Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Memory usage in l4linux
by fabs0028＠free.fr 25 Jul '05

25 Jul '05

Hello, well i 'd like to know how much memory uses each l4 application launched in my l4linux system. I'm pretty sure that there's no program for this purpose. I'm gonna write this but i don't really how to do it so if someone could give me so hints about how to start (mainly what library to use to obtain the informations i need) Thanx for your help Fabien Chaillou

3 3

L4Linux boot message
by Leon Brits 22 Jul '05

22 Jul '05

Hi, Anybody knows what this message means when L4Linux boots... hm, page 00000000 reserved twice. Thanks Leon

2 1

problem compiling pkg/crtx
by Jayesh Salvi 21 Jul '05

21 Jul '05

Hi, I am trying to compile the L4 packages in l4/pkg directory. When I compile pkg/crtx I get: [jayesh@orion crtx]$ make test -f include/broken -o -f include/obsolete || \ if [ -f include/Makefile ] ; then PWD=/home/jayesh/src/l4/pkg/crtx/include make -C include ; fi make[1]: Entering directory `/home/jayesh/src/l4/pkg/crtx/include' make[1]: Leaving directory `/home/jayesh/src/l4/pkg/crtx/include' test -f lib/broken -o -f lib/obsolete || \ if [ -f lib/Makefile ] ; then PWD=/home/jayesh/src/l4/pkg/crtx/lib make -C lib ; fi make[1]: Entering directory `/home/jayesh/src/l4/pkg/crtx/lib' test -f src/broken -o -f src/obsolete || \ if [ -f src/Makefile ] ; then PWD=/home/jayesh/src/l4/pkg/crtx/lib/src make -C src ; fi make[2]: Entering directory `/home/jayesh/src/l4/pkg/crtx/lib/src' PWD=/home/jayesh/src/l4/pkg/crtx/lib/src/OBJ-x86_586 make -C OBJ-x86_586 -f Makefile make[3]: Entering directory `/home/jayesh/src/l4/pkg/crtx/lib/src/OBJ-x86_586' make[3]: *** No rule to make target `crt0_x.o', needed by `crt0.o'. Stop. make[3]: Leaving directory `/home/jayesh/src/l4/pkg/crtx/lib/src/OBJ-x86_586' make[2]: *** [OBJ-x86_586] Error 2 make[2]: Leaving directory `/home/jayesh/src/l4/pkg/crtx/lib/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/jayesh/src/l4/pkg/crtx/lib' make: *** [lib] Error 2 I checked the Makefile. It really does not have any rule for crt0_x. There is crt0_x.S, but no rule to create object file from it. If my guess is correct, some other packages are also dependent on successful compilation of crt0_x. Any idea, what might be wrong? Thanks. -- Jayesh

2 5

(no subject)
by Wang, Chip 20 Jul '05

20 Jul '05

Hi, I am getting kernel panic when booting my vmlinuz26. I am using the RAM Disk 'drops-rd' I downloaded from DROPS. Linux would boot. After I log in and typed 'ls', l4RM complained that no data manager was found. The system was hung. I suspect it was my L4Linux configuration problem. I attached my config at the end of the message. Could someone point out what was missing or wrong? Thanks, Chip RMGR: Stage1 Using extended multiboot info loading (cd)/l4/v2/sigma0 loading kernel (cd)/l4/v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 - comport 1 kernel at 00001000-003496a4 detected new-style DD-L4(v2)/Fiasco configuring sigma0: 00090000-00095000, start: 00090000 reserve modules memory range: 0205a000-03e30419 starting kernel (cd)/l4/v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 proto=0x101fc0 @ 0x003009a0 Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Sat Jul 9 15:47:15 2005 compiled with gcc 3.4.3 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Enabling special fully nested mode for PIC Enabling KIP-LIPC Using the PIT (i8254) on IRQ 0 for scheduling CPU: GenuineIntel (6:7:3:0) Model: Pentium III (Katmai) at 551 MHz 32 Entry I TLB (4K pages) 2 Entry I TLB (4M pages) 64 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 16 KB L1 I Cache (4-way associative, 32 bytes per line) 16 KB L1 D Cache (4-way associative, 32 bytes per line) 512 KB L2 U Cache (4-way associative, 32 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 164kB for maintenance structures. RMGR: Stage2 running on Fiasco bootloader loaded 17 modules at 0205f000-03e30419 setting kip location 00001000 total RAM size = 392767 KB (reported by bootloader) received 359956 KB RAM from sigma0 808 KB reserved for RMGR received no I/O ports attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f ] RMGR: Parsing the config options of command line. configured task 0x0b: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:10 small:ff ] configured task 0x12: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:a8 small:ff ] log_mask: 00000000, log_types: 00000000 RMGR: Starting tasks. #05: loading "(cd)/l4/v2/names" from 0205f000-02067360 to [ 00240000-00246811 00247000-00250000 ] starting at entry 00240000 via trampoline page code 0005c458 #06: loading "(cd)/l4/v2/log --prio 0xA1 --buffer 0" from 02068000-020702bc to [ 00400000-00406a79 00407000-004394f0 ] starting at entry 00400000 via trampoline page code 0005d46c #07: loading "(cd)/l4/v2/dm_phys" from 02071000-020844dc to [ 01500000-01511d0a 01512000-015193b0 ] starting at entry 01500000 via trampoline page code 0005e458 #08: loading "(cd)/l4/v2/simple_ts -t 380" from 02085000-0208f2bc to [ 01400000-014080aa 01409000-014147f0 ] starting at entry 01400000 via trampoline page code 0005f460 #09: loading "(cd)/l4/v2/rtc" from 02090000-0209629c to [ 01080000-01084708 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 00060454 #0a: loading "(cd)/l4/v2/l4io --noirq" from 02097000-020e38f0 to [ 00b70000-00b9097a 00b91000-00bc25ac ] starting at entry 00b70000 via trampoline page code 0006145c #0b: loading "(cd)/l4/v2/bmodfs" from 020e4000-020fb570 to [ 01220000-01235728 01236000-0123b64c ] passing module (cd)/l4/v2/libloader.s.so [ 020fc000-0218209d ] passing module (cd)/l4/lx/vmlinuz26 [ 02183000-02cf664c ] passing module (cd)/l4/v2/vscrtest [ 02cf7000-02d5d670 ] passing module (cd)/l4/cfg/lx/l4linux26.cd.k_us.cfg [ 02d5e000-02d5e0a9 ] passing module (cd)/l4/rd/drops-rd.gz [ 02d5f000-03d5f000 ] starting at entry 01220000 via trampoline page code 00062458 #11: loading "(cd)/l4/v2/l4exec" from 03d5f000-03d88634 to [ 01100000-0112743e 01128000-0112f4ec ] starting at entry 01100000 via trampoline page code 00063458 #12: loading "(cd)/l4/v2/l4dope --l4io" from 03d89000-03dd0c54 to [ 01b00000-01b42cfe 01b43000-01b74000 ] starting at entry 01b00000 via trampoline page code 00064460 #13: loading "(cd)/l4/v2/dopelog" from 03dd1000-03dea174 to [ 01ba0000-01bb6e96 01bb7000-01bca338 ] starting at entry 01ba0000 via trampoline page code 00065458 #14: loading "(cd)/l4/v2/doperun --fprov=BMODFS" from 03deb000-03e08174 to [ 00a80000-00a9ae4e 00a9b000-00ab02b8 ] starting at entry 00a80000 via trampoline page code 00066468 #15: loading "(cd)/l4/v2/loader --fprov=BMODFS l4linux26.cd.k_us.cfg" from 03e09000-03e30418 to [ 01300000-01324e7a 01325000-01336000 ] starting at entry 01300000 via trampoline page code 0006747c simplets| Configured for 380 tasks. rtc | Date:19.07.2005 Time:13:36:07 exec | OSKit support: using 4096KB at 0x00400000 as heap (growing) io | OSKit support: using 1024KB at 0x00180000 as heap io | do_args(): Disabling internal IRQ handling. l4dope | OSKit support: using 6144KB at 0x00180000 as heap l4dope | DOpE(init): using L4 IO server io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | Limiting direct PCI/PCI transfers. io | 00000000-ffffffff : PCI mem io | eea00000-f6afffff : PCI Bus #01 io | f0000000-f3ffffff : ATI Technologies Inc Rage 128 RF/SG AGP io | f8000000-fbffffff : Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host br io : idge io | ff700000-ff7fffff : PCI Bus #01 io | ff7fc000-ff7fffff : ATI Technologies Inc Rage 128 RF/SG AGP io | ff900000-ff9fffff : Cirrus Logic CS 4614/22/24 [CrystalClear SoundF io : usion Audio Accelerator] io | ffafe000-ffafefff : Cirrus Logic CS 4614/22/24 [CrystalClear SoundF io : usion Audio Accelerator] io | ffaffe00-ffaffeff : Macronix, Inc. [MXIC] MX987x5 io | ffafff00-ffafffff : Lucent Microelectronics 56k WinModem io | 0000-ffff : PCI IO io | 0400-043f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI io | 0440-045f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI io | 0cf8-0cff : PCI conf1 io | d000-dfff : PCI Bus #01 io | dc00-dcff : ATI Technologies Inc Rage 128 RF/SG AGP io | e800-e8ff : Macronix, Inc. [MXIC] MX987x5 io | ec00-ecff : Lucent Microelectronics 56k WinModem io | ef80-ef9f : Intel Corp. 82371AB/EB/MB PIIX4 USB io | eff0-eff7 : Lucent Microelectronics 56k WinModem io | ffa0-ffaf : Intel Corp. 82371AB/EB/MB PIIX4 IDE l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 loader | OSKit support: using 128KB at 0x00002000 as heap bmodfs | Passed the following modules: bmodfs | module "(cd)/l4/v2/libloader.s.so" (537kB) bmodfs | module "(cd)/l4/lx/vmlinuz26" (11726kB) bmodfs | module "(cd)/l4/v2/vscrtest" (410kB) bmodfs | module "(cd)/l4/cfg/lx/l4linux26.cd.k_us.cfg" (1kB) bmodfs | module "(cd)/l4/rd/drops-rd.gz" (16384kB) loader | sleeping for 2000 ms l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 l4dope | input: AT Raw Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 l4dope | connect "AT Raw Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | dope: addr=f0000000 size=16384KiB l4dope | Mapped video memory at f0000000 to 04000000+000000 [16384kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=16777216(0x1000000) offset=0(0x0) l4dope | Frame buffer base: 0x04000000 l4dope | Resolution: 640x480x16 l4dope | Bytes per scanline: 1280 l4dope | Current video mode is 640x480 red=11:5 green=5:6 blue=0:5 res=0:0 exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 572768 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 21449 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 00004de0 => 00014de0 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#c: Starting at l4loader_init (00015490) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 003ff000 => 003ff000 exec | vmlinuz26: Packed 507546 bytes of symbols exec | vmlinuz26: Packed 1619023 bytes of lines loader | vmlinuz26,#c: Continue at l4env_init (000154a0, libloader.s.so) l4lx | crt0_construction called. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (8 args): mem=64M noreplacement root=/dev/ram loa l4lx : d_ramdisk=1 ramdisk_size=16384 l4env_rd=drops-rd.gz panicblink=0 lang l4lx : =us l4lx | My DMphys is at 07.00 l4lx | My region mapper is at 0c.00 l4lx | My code starts at 0x003ff000 and ends at 0x006a21a8 [2700 KiB]. l4lx | Semaphore thread ID: 0c.01 l4lx | Areas: l4lx | Text: 003ff000 - 005c1000 [1800kB] (a bit longer) l4lx | Data: 005c1000 - 00602a80 [262kB] l4lx | Initdata: 00606000 - 00632000 [176kB] l4lx | BSS: 00632008 - 006a21a8 [448kB] l4lx | l4lx_thread_create: Created thread 0c.03 (server) l4lx | main thread will be 0c.03 l4lx | l4env_register_pointer_section: addr = 604000 size = 192512 l4lx | with-init: virt: 0x00604000 to 0x00632fff [188 KiB] l4lx | with-init: Number of physical regions: 1, 192512 Bytes l4lx | with-init: 1: Phys: 0x00bff000 to 0x00c2e000, Size: 5858613 l4lx | l4env_linux_startup thread 3. l4lx | main thread: received startup message. l4lx | Main memory size: 64MB l4lx | Main thread running, waiting... l4lx | Mainmem DS id: 54 l4lx | mainmem: virt: 0x006a3000 to 0x046a2fff [65536 KiB] l4lx | mainmem: Number of physical regions: 1, 67108864 Bytes l4lx | mainmem: 1: Phys: 0x03d5f000 to 0x07d5f000, Size: 5858363 l4lx | Filling lower ptabs... l4lx | Done (889 entries). l4lx | l4env_rd_path: drops-rd.gz l4lx | Loading: drops-rd.gz l4lx | INITRD: Size of RAMdisk is 16384KiB l4lx | RAMdisk from 46a3000 to 56a3000 [16384KiB] l4lx | l4lx_thread_create: Created thread 0c.04 (timer.i0) l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=e0000, lh.high=80000, id=3e, size=96000 l4dope | SharedMem(get_adr): address = 800000 l4lx | l4lx_thread_create: Created thread 0c.06 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 0c.07 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 0c.08 (IRQ10) *run | [14.0] l4rm/lib/src/config.c:92:l4rm_get_dsm(): *run | L4RM: no dataspace man*dope_log| [13.0] l4rm/lib/src/config.c:92:l4r m_get_dsm(): *dope_log| L4RM: no datager found! --PANIC-------------------------------------------------EIP: 00a8a89c (14.00) jdb: My L4Linux config: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12-l4 # Tue Jul 19 12:52:50 2005 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_L4DIR="/home/drops/l4" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set # CONFIG_L4_USERPRIV_ONLY is not set CONFIG_L4_EXTERNAL_RTC=y # # Advanced options # CONFIG_L4_L4ENV_MEMSIZE=64 # CONFIG_L4_TAMED is not set CONFIG_L4_BLK_DRV=y CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_SERIAL is not set CONFIG_L4_MK_CPU_X86="586" # CONFIG_L4_IRQ_OMEGA0 is not set # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DEBUG is not set # # # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # # CONFIG_EXPERIMENTAL is not set CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_HOTPLUG is not set CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODULE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set CONFIG_SECCOMP=y # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # CONFIG_ACPI is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_COW_COMMON is not set # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_LBD is not set # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y # CONFIG_BLK_DEV_IDE is not set # CONFIG_BLK_DEV_HD_ONLY is not set # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_SCSI is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Fusion MPT device support # # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Networking support # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set CONFIG_EL3=y # CONFIG_3C515 is not set # CONFIG_VORTEX is not set # CONFIG_TYPHOON is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y CONFIG_TULIP=y # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y CONFIG_PCNET32=y # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_APRICOT is not set # CONFIG_CS89x0 is not set # CONFIG_DGRS is not set CONFIG_EEPRO100=y # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000_NAPI is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_R8169 is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=y # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=800 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=600 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ATKBD is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # # CONFIG_SERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # # I2C support # # CONFIG_I2C is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Misc devices # # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # # CONFIG_VGA_CONSOLE is not set # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y # CONFIG_EXT2_FS_POSIX_ACL is not set # CONFIG_EXT2_FS_SECURITY is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_ZISOFS_FS=y # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_HFSPLUS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_SUNRPC=y # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_BUGVERBOSE is not set CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set CONFIG_FRAME_POINTER=y # CONFIG_EARLY_PRINTK is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

3 2

Missing data manager
by Wang, Chip 19 Jul '05

19 Jul '05

Hi, I am getting kernel panic when booting my vmlinuz26. I am using the RAM Disk 'drops-rd' I downloaded from DROPS. Linux would boot. After I log in and typed 'ls', l4RM complained that no data manager was found. The system was hung. I suspect it was my L4Linux configuration problem. I attached my config at the end of the message. Could someone point out what was missing or wrong? Thanks, Chip RMGR: Stage1 Using extended multiboot info loading (cd)/l4/v2/sigma0 loading kernel (cd)/l4/v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 - comport 1 kernel at 00001000-003496a4 detected new-style DD-L4(v2)/Fiasco configuring sigma0: 00090000-00095000, start: 00090000 reserve modules memory range: 0205a000-03e30419 starting kernel (cd)/l4/v2/fiasco -nokdb -nowait -serial_esc -comspeed 115200 -comport 1 proto=0x101fc0 @ 0x003009a0 Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Sat Jul 9 15:47:15 2005 compiled with gcc 3.4.3 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Enabling special fully nested mode for PIC Enabling KIP-LIPC Using the PIT (i8254) on IRQ 0 for scheduling CPU: GenuineIntel (6:7:3:0) Model: Pentium III (Katmai) at 551 MHz 32 Entry I TLB (4K pages) 2 Entry I TLB (4M pages) 64 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 16 KB L1 I Cache (4-way associative, 32 bytes per line) 16 KB L1 D Cache (4-way associative, 32 bytes per line) 512 KB L2 U Cache (4-way associative, 32 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: no. Allocated 164kB for maintenance structures. RMGR: Stage2 running on Fiasco bootloader loaded 17 modules at 0205f000-03e30419 setting kip location 00001000 total RAM size = 392767 KB (reported by bootloader) received 359956 KB RAM from sigma0 808 KB reserved for RMGR received no I/O ports attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f ] RMGR: Parsing the config options of command line. configured task 0x0b: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:10 small:ff ] configured task 0x12: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:a8 small:ff ] log_mask: 00000000, log_types: 00000000 RMGR: Starting tasks. #05: loading "(cd)/l4/v2/names" from 0205f000-02067360 to [ 00240000-00246811 00247000-00250000 ] starting at entry 00240000 via trampoline page code 0005c458 #06: loading "(cd)/l4/v2/log --prio 0xA1 --buffer 0" from 02068000-020702bc to [ 00400000-00406a79 00407000-004394f0 ] starting at entry 00400000 via trampoline page code 0005d46c #07: loading "(cd)/l4/v2/dm_phys" from 02071000-020844dc to [ 01500000-01511d0a 01512000-015193b0 ] starting at entry 01500000 via trampoline page code 0005e458 #08: loading "(cd)/l4/v2/simple_ts -t 380" from 02085000-0208f2bc to [ 01400000-014080aa 01409000-014147f0 ] starting at entry 01400000 via trampoline page code 0005f460 #09: loading "(cd)/l4/v2/rtc" from 02090000-0209629c to [ 01080000-01084708 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 00060454 #0a: loading "(cd)/l4/v2/l4io --noirq" from 02097000-020e38f0 to [ 00b70000-00b9097a 00b91000-00bc25ac ] starting at entry 00b70000 via trampoline page code 0006145c #0b: loading "(cd)/l4/v2/bmodfs" from 020e4000-020fb570 to [ 01220000-01235728 01236000-0123b64c ] passing module (cd)/l4/v2/libloader.s.so [ 020fc000-0218209d ] passing module (cd)/l4/lx/vmlinuz26 [ 02183000-02cf664c ] passing module (cd)/l4/v2/vscrtest [ 02cf7000-02d5d670 ] passing module (cd)/l4/cfg/lx/l4linux26.cd.k_us.cfg [ 02d5e000-02d5e0a9 ] passing module (cd)/l4/rd/drops-rd.gz [ 02d5f000-03d5f000 ] starting at entry 01220000 via trampoline page code 00062458 #11: loading "(cd)/l4/v2/l4exec" from 03d5f000-03d88634 to [ 01100000-0112743e 01128000-0112f4ec ] starting at entry 01100000 via trampoline page code 00063458 #12: loading "(cd)/l4/v2/l4dope --l4io" from 03d89000-03dd0c54 to [ 01b00000-01b42cfe 01b43000-01b74000 ] starting at entry 01b00000 via trampoline page code 00064460 #13: loading "(cd)/l4/v2/dopelog" from 03dd1000-03dea174 to [ 01ba0000-01bb6e96 01bb7000-01bca338 ] starting at entry 01ba0000 via trampoline page code 00065458 #14: loading "(cd)/l4/v2/doperun --fprov=BMODFS" from 03deb000-03e08174 to [ 00a80000-00a9ae4e 00a9b000-00ab02b8 ] starting at entry 00a80000 via trampoline page code 00066468 #15: loading "(cd)/l4/v2/loader --fprov=BMODFS l4linux26.cd.k_us.cfg" from 03e09000-03e30418 to [ 01300000-01324e7a 01325000-01336000 ] starting at entry 01300000 via trampoline page code 0006747c simplets| Configured for 380 tasks. rtc | Date:19.07.2005 Time:13:36:07 exec | OSKit support: using 4096KB at 0x00400000 as heap (growing) io | OSKit support: using 1024KB at 0x00180000 as heap io | do_args(): Disabling internal IRQ handling. l4dope | OSKit support: using 6144KB at 0x00180000 as heap l4dope | DOpE(init): using L4 IO server io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | Limiting direct PCI/PCI transfers. io | 00000000-ffffffff : PCI mem io | eea00000-f6afffff : PCI Bus #01 io | f0000000-f3ffffff : ATI Technologies Inc Rage 128 RF/SG AGP io | f8000000-fbffffff : Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host br io : idge io | ff700000-ff7fffff : PCI Bus #01 io | ff7fc000-ff7fffff : ATI Technologies Inc Rage 128 RF/SG AGP io | ff900000-ff9fffff : Cirrus Logic CS 4614/22/24 [CrystalClear SoundF io : usion Audio Accelerator] io | ffafe000-ffafefff : Cirrus Logic CS 4614/22/24 [CrystalClear SoundF io : usion Audio Accelerator] io | ffaffe00-ffaffeff : Macronix, Inc. [MXIC] MX987x5 io | ffafff00-ffafffff : Lucent Microelectronics 56k WinModem io | 0000-ffff : PCI IO io | 0400-043f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI io | 0440-045f : Intel Corp. 82371AB/EB/MB PIIX4 ACPI io | 0cf8-0cff : PCI conf1 io | d000-dfff : PCI Bus #01 io | dc00-dcff : ATI Technologies Inc Rage 128 RF/SG AGP io | e800-e8ff : Macronix, Inc. [MXIC] MX987x5 io | ec00-ecff : Lucent Microelectronics 56k WinModem io | ef80-ef9f : Intel Corp. 82371AB/EB/MB PIIX4 USB io | eff0-eff7 : Lucent Microelectronics 56k WinModem io | ffa0-ffaf : Intel Corp. 82371AB/EB/MB PIIX4 IDE l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. l4dope | L4INPUT: !!! W A R N I N G !!! l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 loader | OSKit support: using 128KB at 0x00002000 as heap bmodfs | Passed the following modules: bmodfs | module "(cd)/l4/v2/libloader.s.so" (537kB) bmodfs | module "(cd)/l4/lx/vmlinuz26" (11726kB) bmodfs | module "(cd)/l4/v2/vscrtest" (410kB) bmodfs | module "(cd)/l4/cfg/lx/l4linux26.cd.k_us.cfg" (1kB) bmodfs | module "(cd)/l4/rd/drops-rd.gz" (16384kB) loader | sleeping for 2000 ms l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 l4dope | input: AT Raw Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 l4dope | connect "AT Raw Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | dope: addr=f0000000 size=16384KiB l4dope | Mapped video memory at f0000000 to 04000000+000000 [16384kB] via L4IO l4dope | mapping: vaddr=0x4000000 size=16777216(0x1000000) offset=0(0x0) l4dope | Frame buffer base: 0x04000000 l4dope | Resolution: 640x480x16 l4dope | Bytes per scanline: 1280 l4dope | Current video mode is 640x480 red=11:5 green=5:6 blue=0:5 res=0:0 exec | vmlinuz26: Loading exec | vmlinuz26: Interpreter section found, contains "/usr/lib/libc.so.1" exec | vmlinuz26: Saved 572768 bytes of symbols exec | libloader.s.so: Loading exec | libloader.s.so: Saved 21449 bytes of symbols exec | libloader.s.so: Relocating to 00010000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 00004de0 => 00014de0 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26: Setting section flag 0800 loader | vmlinuz26: Starting l4env-style application loader | vmlinuz26,#c: Starting at l4loader_init (00015490) exec | vmlinuz26: Linking exec | vmlinuz26: Relocating entry 003ff000 => 003ff000 exec | vmlinuz26: Packed 507546 bytes of symbols exec | vmlinuz26: Packed 1619023 bytes of lines loader | vmlinuz26,#c: Continue at l4env_init (000154a0, libloader.s.so) l4lx | crt0_construction called. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (8 args): mem=64M noreplacement root=/dev/ram loa l4lx : d_ramdisk=1 ramdisk_size=16384 l4env_rd=drops-rd.gz panicblink=0 lang l4lx : =us l4lx | My DMphys is at 07.00 l4lx | My region mapper is at 0c.00 l4lx | My code starts at 0x003ff000 and ends at 0x006a21a8 [2700 KiB]. l4lx | Semaphore thread ID: 0c.01 l4lx | Areas: l4lx | Text: 003ff000 - 005c1000 [1800kB] (a bit longer) l4lx | Data: 005c1000 - 00602a80 [262kB] l4lx | Initdata: 00606000 - 00632000 [176kB] l4lx | BSS: 00632008 - 006a21a8 [448kB] l4lx | l4lx_thread_create: Created thread 0c.03 (server) l4lx | main thread will be 0c.03 l4lx | l4env_register_pointer_section: addr = 604000 size = 192512 l4lx | with-init: virt: 0x00604000 to 0x00632fff [188 KiB] l4lx | with-init: Number of physical regions: 1, 192512 Bytes l4lx | with-init: 1: Phys: 0x00bff000 to 0x00c2e000, Size: 5858613 l4lx | l4env_linux_startup thread 3. l4lx | main thread: received startup message. l4lx | Main memory size: 64MB l4lx | Main thread running, waiting... l4lx | Mainmem DS id: 54 l4lx | mainmem: virt: 0x006a3000 to 0x046a2fff [65536 KiB] l4lx | mainmem: Number of physical regions: 1, 67108864 Bytes l4lx | mainmem: 1: Phys: 0x03d5f000 to 0x07d5f000, Size: 5858363 l4lx | Filling lower ptabs... l4lx | Done (889 entries). l4lx | l4env_rd_path: drops-rd.gz l4lx | Loading: drops-rd.gz l4lx | INITRD: Size of RAMdisk is 16384KiB l4lx | RAMdisk from 46a3000 to 56a3000 [16384KiB] l4lx | l4lx_thread_create: Created thread 0c.04 (timer.i0) l4lx | Starting L4FB via DOpE l4dope | SharedMem(alloc): hl.low=e0000, lh.high=80000, id=3e, size=96000 l4dope | SharedMem(get_adr): address = 800000 l4lx | l4lx_thread_create: Created thread 0c.06 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 0c.07 (L4DOpEinput) l4lx | l4lx_thread_create: Created thread 0c.08 (IRQ10) *run | [14.0] l4rm/lib/src/config.c:92:l4rm_get_dsm(): *run | L4RM: no dataspace man*dope_log| [13.0] l4rm/lib/src/config.c:92:l4r m_get_dsm(): *dope_log| L4RM: no datager found! --PANIC-------------------------------------------------EIP: 00a8a89c (14.00) jdb: My L4Linux config: # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12-l4 # Tue Jul 19 12:52:50 2005 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_L4DIR="/home/drops/l4" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set # CONFIG_L4_USERPRIV_ONLY is not set CONFIG_L4_EXTERNAL_RTC=y # # Advanced options # CONFIG_L4_L4ENV_MEMSIZE=64 # CONFIG_L4_TAMED is not set CONFIG_L4_BLK_DRV=y CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_SERIAL is not set CONFIG_L4_MK_CPU_X86="586" # CONFIG_L4_IRQ_OMEGA0 is not set # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DEBUG is not set # # # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # # CONFIG_EXPERIMENTAL is not set CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set # CONFIG_HOTPLUG is not set CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set CONFIG_EMBEDDED=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y # CONFIG_MODULE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_HPET_TIMER is not set # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set CONFIG_SECCOMP=y # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # ACPI (Advanced Configuration and Power Interface) Support # # CONFIG_ACPI is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_FW_LOADER is not set # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_COW_COMMON is not set # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" # CONFIG_LBD is not set # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y # CONFIG_BLK_DEV_IDE is not set # CONFIG_BLK_DEV_HD_ONLY is not set # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_SCSI is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Fusion MPT device support # # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Networking support # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y # CONFIG_IP_PNP_BOOTP is not set # CONFIG_IP_PNP_RARP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set CONFIG_NET_VENDOR_3COM=y # CONFIG_EL1 is not set # CONFIG_EL2 is not set # CONFIG_ELPLUS is not set CONFIG_EL3=y # CONFIG_3C515 is not set # CONFIG_VORTEX is not set # CONFIG_TYPHOON is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # # Tulip family network device support # CONFIG_NET_TULIP=y CONFIG_TULIP=y # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set # CONFIG_DE4X5 is not set # CONFIG_WINBOND_840 is not set # CONFIG_DM9102 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y CONFIG_PCNET32=y # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_APRICOT is not set # CONFIG_CS89x0 is not set # CONFIG_DGRS is not set CONFIG_EEPRO100=y # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set CONFIG_NE2K_PCI=y # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set CONFIG_E1000=y # CONFIG_E1000_NAPI is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_R8169 is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=y # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=800 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=600 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_KEYBOARD_ATKBD is not set # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y # CONFIG_MOUSE_PS2 is not set # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_INPORT is not set # CONFIG_MOUSE_LOGIBM is not set # CONFIG_MOUSE_PC110PAD is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # # CONFIG_SERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # # I2C support # # CONFIG_I2C is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Misc devices # # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # # CONFIG_VGA_CONSOLE is not set # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y # CONFIG_EXT2_FS_POSIX_ACL is not set # CONFIG_EXT2_FS_SECURITY is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # # XFS support # # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_ZISOFS_FS=y # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_HFSPLUS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_SUNRPC=y # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_BUGVERBOSE is not set CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_FS is not set CONFIG_FRAME_POINTER=y # CONFIG_EARLY_PRINTK is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_4KSTACKS is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # # CONFIG_CRC_CCITT is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

1 0

Shared dataspace problem
by Leon Brits 19 Jul '05

19 Jul '05

Hi all, I have a dataspace, reserved as pool 1 by dm_phys, which two tasks shares. They synchronise access to the data by setting a lock at the start of the dataspace with a cmpxchg-loop. All tasks map the dataspace to their own VM area. The problem is that if one of the tasks exists then the other would stop with a page fault error the next time it accesses the shared dataspace. Both of them where happily reading and writing to the dataspace at exactly the place where the page fault occur. Any suggestions? Thanks Leon

2 2

Unable to compile DROPS grub package
by Wang, Chip 19 Jul '05

19 Jul '05

Hi, I can't compile the DROPS version of GRUB. I checked out the grub package from the DROPS anonymous CVS. When compiling it with gcc 3.4.3 I got numerous errors. Each time I edited the source file to get it go a little farther, I got more errors. I know I could just use the copy of stage2_elterito from the demo CD, but I really like to have the capability to build my own GRUB. By the way, GRUB from GNU compiles successfully. But it lacks the features found in DROPS enhanced version. What was the problem? Excerpts of make logs from my five attempts are attached. It's a bit long. I apologize. Thanks, Chip (1) make all-recursive make[1]: Entering directory `/home/drops/modules/drops/grub' Making all in netboot make[2]: Entering directory `/home/drops/modules/drops/grub/netboot' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/drops/modules/drops/grub/netboot' Making all in stage2 make[2]: Entering directory `/home/drops/modules/drops/grub/stage2' gcc -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -g -c -o pre_stage2_exec-asm.o `test -f asm.S || echo './'`asm.S asm.S:0: warning: -malign-loops is obsolete, use -falign-loops asm.S:0: warning: -malign-jumps is obsolete, use -falign-jumps asm.S:0: warning: -malign-functions is obsolete, use -falign-functions source='bios.c' object='pre_stage2_exec-bios.o' libtool=no \ depfile='.deps/pre_stage2_exec-bios.Po' tmpdepfile='.deps/pre_stage2_exec-bios.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-bios.o `test -f bios.c || echo './'`bios.c bios.c:1: warning: -malign-loops is obsolete, use -falign-loops bios.c:1: warning: -malign-jumps is obsolete, use -falign-jumps bios.c:1: warning: -malign-functions is obsolete, use -falign-functions source='boot.c' object='pre_stage2_exec-boot.o' libtool=no \ depfile='.deps/pre_stage2_exec-boot.Po' tmpdepfile='.deps/pre_stage2_exec-boot.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-boot.o `test -f boot.c || echo './'`boot.c boot.c:1: warning: -malign-loops is obsolete, use -falign-loops boot.c:1: warning: -malign-jumps is obsolete, use -falign-jumps boot.c:1: warning: -malign-functions is obsolete, use -falign-functions source='builtins.c' object='pre_stage2_exec-builtins.o' libtool=no \ depfile='.deps/pre_stage2_exec-builtins.Po' tmpdepfile='.deps/pre_stage2_exec-builtins.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-builtins.o `test -f builtins.c || echo './'`builtins.c builtins.c:1: warning: -malign-loops is obsolete, use -falign-loops builtins.c:1: warning: -malign-jumps is obsolete, use -falign-jumps builtins.c:1: warning: -malign-functions is obsolete, use -falign-functions builtins.c: In function `displayapm_func': builtins.c:886: error: missing terminating " character builtins.c:887: error: `Version' undeclared (first use in this function) builtins.c:887: error: (Each undeclared identifier is reported only once builtins.c:887: error: for each function it appears in.) builtins.c:887: error: syntax error before ':' token builtins.c:887:20: invalid suffix "x" on integer constant builtins.c:888:20: invalid suffix "x" on integer constant builtins.c:889:20: invalid suffix "x" on integer constant builtins.c:890:20: invalid suffix "x" on integer constant builtins.c:891:20: invalid suffix "x" on integer constant builtins.c:892:20: invalid suffix "x" on integer constant builtins.c:893:20: invalid suffix "x" on integer constant builtins.c:894:20: invalid suffix "x" on integer constant builtins.c:894: error: stray '\' in program builtins.c:894: error: missing terminating " character make[2]: *** [pre_stage2_exec-builtins.o] Error 1 make[2]: Leaving directory `/home/drops/modules/drops/grub/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/drops/modules/drops/grub' make: *** [all] Error 2 (2) make all-recursive make[1]: Entering directory `/home/drops/modules/drops/grub' Making all in netboot make[2]: Entering directory `/home/drops/modules/drops/grub/netboot' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/drops/modules/drops/grub/netboot' Making all in stage2 make[2]: Entering directory `/home/drops/modules/drops/grub/stage2' source='builtins.c' object='pre_stage2_exec-builtins.o' libtool=no \ depfile='.deps/pre_stage2_exec-builtins.Po' tmpdepfile='.deps/pre_stage2_exec-builtins.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-builtins.o `test -f builtins.c || echo './'`builtins.c builtins.c:1: warning: -malign-loops is obsolete, use -falign-loops builtins.c:1: warning: -malign-jumps is obsolete, use -falign-jumps builtins.c:1: warning: -malign-functions is obsolete, use -falign-functions source='common.c' object='pre_stage2_exec-common.o' libtool=no \ depfile='.deps/pre_stage2_exec-common.Po' tmpdepfile='.deps/pre_stage2_exec-common.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-common.o `test -f common.c || echo './'`common.c common.c:1: warning: -malign-loops is obsolete, use -falign-loops common.c:1: warning: -malign-jumps is obsolete, use -falign-jumps common.c:1: warning: -malign-functions is obsolete, use -falign-functions source='char_io.c' object='pre_stage2_exec-char_io.o' libtool=no \ depfile='.deps/pre_stage2_exec-char_io.Po' tmpdepfile='.deps/pre_stage2_exec-char_io.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-char_io.o `test -f char_io.c || echo './'`char_io.c char_io.c:1: warning: -malign-loops is obsolete, use -falign-loops char_io.c:1: warning: -malign-jumps is obsolete, use -falign-jumps char_io.c:1: warning: -malign-functions is obsolete, use -falign-functions char_io.c: In function `grub_printf': char_io.c:93: warning: dereferencing type-punned pointer will break strict-aliasing rules char_io.c: In function `grub_sprintf': char_io.c:149: warning: dereferencing type-punned pointer will break strict-aliasing rules source='cmdline.c' object='pre_stage2_exec-cmdline.o' libtool=no \ depfile='.deps/pre_stage2_exec-cmdline.Po' tmpdepfile='.deps/pre_stage2_exec-cmdline.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-cmdline.o `test -f cmdline.c || echo './'`cmdline.c cmdline.c:1: warning: -malign-loops is obsolete, use -falign-loops cmdline.c:1: warning: -malign-jumps is obsolete, use -falign-jumps cmdline.c:1: warning: -malign-functions is obsolete, use -falign-functions cmdline.c: In function `print_cmdline_message': cmdline.c:53: error: missing terminating " character cmdline.c:55: error: `lists' undeclared (first use in this function) cmdline.c:55: error: (Each undeclared identifier is reported only once cmdline.c:55: error: for each function it appears in.) cmdline.c:55: error: syntax error before "possible" cmdline.c:56: error: stray '\' in program cmdline.c:56: error: missing terminating " character make[2]: *** [pre_stage2_exec-cmdline.o] Error 1 make[2]: Leaving directory `/home/drops/modules/drops/grub/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/drops/modules/drops/grub' make: *** [all] Error 2 (3) make all-recursive make[1]: Entering directory `/home/drops/modules/drops/grub' Making all in netboot make[2]: Entering directory `/home/drops/modules/drops/grub/netboot' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/drops/modules/drops/grub/netboot' Making all in stage2 make[2]: Entering directory `/home/drops/modules/drops/grub/stage2' source='cmdline.c' object='pre_stage2_exec-cmdline.o' libtool=no \ depfile='.deps/pre_stage2_exec-cmdline.Po' tmpdepfile='.deps/pre_stage2_exec-cmdline.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-cmdline.o `test -f cmdline.c || echo './'`cmdline.c cmdline.c:1: warning: -malign-loops is obsolete, use -falign-loops cmdline.c:1: warning: -malign-jumps is obsolete, use -falign-jumps cmdline.c:1: warning: -malign-functions is obsolete, use -falign-functions source='disk_io.c' object='pre_stage2_exec-disk_io.o' libtool=no \ depfile='.deps/pre_stage2_exec-disk_io.Po' tmpdepfile='.deps/pre_stage2_exec-disk_io.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-disk_io.o `test -f disk_io.c || echo './'`disk_io.c disk_io.c:1: warning: -malign-loops is obsolete, use -falign-loops disk_io.c:1: warning: -malign-jumps is obsolete, use -falign-jumps disk_io.c:1: warning: -malign-functions is obsolete, use -falign-functions disk_io.c: In function `set_device': disk_io.c:940: warning: dereferencing type-punned pointer will break strict-aliasing rules disk_io.c:969: warning: dereferencing type-punned pointer will break strict-aliasing rules source='gunzip.c' object='pre_stage2_exec-gunzip.o' libtool=no \ depfile='.deps/pre_stage2_exec-gunzip.Po' tmpdepfile='.deps/pre_stage2_exec-gunzip.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-gunzip.o `test -f gunzip.c || echo './'`gunzip.c gunzip.c:1: warning: -malign-loops is obsolete, use -falign-loops gunzip.c:1: warning: -malign-jumps is obsolete, use -falign-jumps gunzip.c:1: warning: -malign-functions is obsolete, use -falign-functions source='fsys_ext2fs.c' object='pre_stage2_exec-fsys_ext2fs.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_ext2fs.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_ext2fs.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_ext2fs.o `test -f fsys_ext2fs.c || echo './'`fsys_ext2fs.c fsys_ext2fs.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_ext2fs.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_ext2fs.c:1: warning: -malign-functions is obsolete, use -falign-functions fsys_ext2fs.c: In function `ext2fs_dir': fsys_ext2fs.c:495: warning: 'str_chk' might be used uninitialized in this function source='fsys_fat.c' object='pre_stage2_exec-fsys_fat.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_fat.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_fat.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_fat.o `test -f fsys_fat.c || echo './'`fsys_fat.c fsys_fat.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_fat.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_fat.c:1: warning: -malign-functions is obsolete, use -falign-functions source='fsys_ffs.c' object='pre_stage2_exec-fsys_ffs.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_ffs.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_ffs.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_ffs.o `test -f fsys_ffs.c || echo './'`fsys_ffs.c fsys_ffs.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_ffs.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_ffs.c:1: warning: -malign-functions is obsolete, use -falign-functions source='fsys_minix.c' object='pre_stage2_exec-fsys_minix.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_minix.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_minix.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_minix.o `test -f fsys_minix.c || echo './'`fsys_minix.c fsys_minix.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_minix.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_minix.c:1: warning: -malign-functions is obsolete, use -falign-functions fsys_minix.c: In function `minix_dir': fsys_minix.c:303: warning: 'str_chk' might be used uninitialized in this function source='fsys_reiserfs.c' object='pre_stage2_exec-fsys_reiserfs.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_reiserfs.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_reiserfs.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_reiserfs.o `test -f fsys_reiserfs.c || echo './'`fsys_reiserfs.c fsys_reiserfs.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_reiserfs.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_reiserfs.c:1: warning: -malign-functions is obsolete, use -falign-functions fsys_reiserfs.c:115: error: long, short, signed or unsigned used invalidly for `j_mount_id' fsys_reiserfs.c: In function `next_key': fsys_reiserfs.c:759: warning: operation on `depth' may be undefined make[2]: *** [pre_stage2_exec-fsys_reiserfs.o] Error 1 make[2]: Leaving directory `/home/drops/modules/drops/grub/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/drops/modules/drops/grub' make: *** [all] Error 2 (4) make all-recursive make[1]: Entering directory `/home/drops/modules/drops/grub' Making all in netboot make[2]: Entering directory `/home/drops/modules/drops/grub/netboot' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/drops/modules/drops/grub/netboot' Making all in stage2 make[2]: Entering directory `/home/drops/modules/drops/grub/stage2' source='fsys_reiserfs.c' object='pre_stage2_exec-fsys_reiserfs.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_reiserfs.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_reiserfs.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_reiserfs.o `test -f fsys_reiserfs.c || echo './'`fsys_reiserfs.c fsys_reiserfs.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_reiserfs.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_reiserfs.c:1: warning: -malign-functions is obsolete, use -falign-functions fsys_reiserfs.c: In function `next_key': fsys_reiserfs.c:759: warning: operation on `depth' may be undefined source='fsys_vstafs.c' object='pre_stage2_exec-fsys_vstafs.o' libtool=no \ depfile='.deps/pre_stage2_exec-fsys_vstafs.Po' tmpdepfile='.deps/pre_stage2_exec-fsys_vstafs.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-fsys_vstafs.o `test -f fsys_vstafs.c || echo './'`fsys_vstafs.c fsys_vstafs.c:1: warning: -malign-loops is obsolete, use -falign-loops fsys_vstafs.c:1: warning: -malign-jumps is obsolete, use -falign-jumps fsys_vstafs.c:1: warning: -malign-functions is obsolete, use -falign-functions fsys_vstafs.c: In function `vstafs_read': fsys_vstafs.c:189: warning: declaration of 'a' shadows a global declaration fsys_vstafs.c:66: warning: shadowed declaration is here fsys_vstafs.c:191: warning: declaration of 'curr_ext' shadows a global declaration fsys_vstafs.c:65: warning: shadowed declaration is here source='hercules.c' object='pre_stage2_exec-hercules.o' libtool=no \ depfile='.deps/pre_stage2_exec-hercules.Po' tmpdepfile='.deps/pre_stage2_exec-hercules.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-hercules.o `test -f hercules.c || echo './'`hercules.c hercules.c:1: warning: -malign-loops is obsolete, use -falign-loops hercules.c:1: warning: -malign-jumps is obsolete, use -falign-jumps hercules.c:1: warning: -malign-functions is obsolete, use -falign-functions source='serial.c' object='pre_stage2_exec-serial.o' libtool=no \ depfile='.deps/pre_stage2_exec-serial.Po' tmpdepfile='.deps/pre_stage2_exec-serial.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-serial.o `test -f serial.c || echo './'`serial.c serial.c:1: warning: -malign-loops is obsolete, use -falign-loops serial.c:1: warning: -malign-jumps is obsolete, use -falign-jumps serial.c:1: warning: -malign-functions is obsolete, use -falign-functions source='smp-imps.c' object='pre_stage2_exec-smp-imps.o' libtool=no \ depfile='.deps/pre_stage2_exec-smp-imps.Po' tmpdepfile='.deps/pre_stage2_exec-smp-imps.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-smp-imps.o `test -f smp-imps.c || echo './'`smp-imps.c smp-imps.c:1: warning: -malign-loops is obsolete, use -falign-loops smp-imps.c:1: warning: -malign-jumps is obsolete, use -falign-jumps smp-imps.c:1: warning: -malign-functions is obsolete, use -falign-functions smp-imps.c: In function `imps_read_config_table': smp-imps.c:437: error: label at end of compound statement make[2]: *** [pre_stage2_exec-smp-imps.o] Error 1 make[2]: Leaving directory `/home/drops/modules/drops/grub/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/drops/modules/drops/grub' make: *** [all] Error 2 (5) make all-recursive make[1]: Entering directory `/home/drops/modules/drops/grub' Making all in netboot make[2]: Entering directory `/home/drops/modules/drops/grub/netboot' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/drops/modules/drops/grub/netboot' Making all in stage2 make[2]: Entering directory `/home/drops/modules/drops/grub/stage2' source='smp-imps.c' object='pre_stage2_exec-smp-imps.o' libtool=no \ depfile='.deps/pre_stage2_exec-smp-imps.Po' tmpdepfile='.deps/pre_stage2_exec-smp-imps.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-smp-imps.o `test -f smp-imps.c || echo './'`smp-imps.c smp-imps.c:1: warning: -malign-loops is obsolete, use -falign-loops smp-imps.c:1: warning: -malign-jumps is obsolete, use -falign-jumps smp-imps.c:1: warning: -malign-functions is obsolete, use -falign-functions source='stage2.c' object='pre_stage2_exec-stage2.o' libtool=no \ depfile='.deps/pre_stage2_exec-stage2.Po' tmpdepfile='.deps/pre_stage2_exec-stage2.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-stage2.o `test -f stage2.c || echo './'`stage2.c stage2.c:1: warning: -malign-loops is obsolete, use -falign-loops stage2.c:1: warning: -malign-jumps is obsolete, use -falign-jumps stage2.c:1: warning: -malign-functions is obsolete, use -falign-functions source='md5.c' object='pre_stage2_exec-md5.o' libtool=no \ depfile='.deps/pre_stage2_exec-md5.Po' tmpdepfile='.deps/pre_stage2_exec-md5.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-md5.o `test -f md5.c || echo './'`md5.c md5.c:1: warning: -malign-loops is obsolete, use -falign-loops md5.c:1: warning: -malign-jumps is obsolete, use -falign-jumps md5.c:1: warning: -malign-functions is obsolete, use -falign-functions gcc -g -o pre_stage2.exec -nostdlib -Wl,-N -Wl,-Ttext -Wl,8200 pre_stage2_exec-asm.o pre_stage2_exec-bios.o pre_stage2_exec-boot.o pre_stage2_exec-builtins.o pre_stage2_exec-common.o pre_stage2_exec-char_io.o pre_stage2_exec-cmdline.o pre_stage2_exec-disk_io.o pre_stage2_exec-gunzip.o pre_stage2_exec-fsys_ext2fs.o pre_stage2_exec-fsys_fat.o pre_stage2_exec-fsys_ffs.o pre_stage2_exec-fsys_minix.o pre_stage2_exec-fsys_reiserfs.o pre_stage2_exec-fsys_vstafs.o pre_stage2_exec-hercules.o pre_stage2_exec-serial.o pre_stage2_exec-smp-imps.o pre_stage2_exec-stage2.o pre_stage2_exec-md5.o pre_stage2_exec-builtins.o(.text+0x13bb): In function `install_func': /home/drops/modules/drops/grub/stage2/builtins.c:1809: undefined reference to `memcpy' pre_stage2_exec-builtins.o(.text+0x1476):/home/drops/modules/drops/grub/stage2/builtins.c:1854: undefined reference to `memcpy' pre_stage2_exec-builtins.o(.text+0x2b54): In function `setup_func': /home/drops/modules/drops/grub/stage2/builtins.c:3680: undefined reference to `memcpy' collect2: ld returned 1 exit status make[2]: *** [pre_stage2.exec] Error 1 make[2]: Leaving directory `/home/drops/modules/drops/grub/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/drops/modules/drops/grub' make: *** [all] Error 2 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

How to load and run multiple instances of L4Linux, etc.
by Wang, Chip 18 Jul '05

18 Jul '05

Hi, My primary interest is to use Fiasco/L4Linux as a network emulator. To do so I'd like to run multiple copies of L4Linux on my PC, with each copy emulating a node in my network. I have just managed to get my compiled L4Linux-2.6 up and running using a copy of the GRUB menu.lst from the demo CD. But I am a new L4 user and have no idea on how to configure my boot to achieve this. Could someone suggest a sample menu.lst for booting multiple instances of L4Linux? Another novice question is how to run a Linux application on L4Linux. Can I simply add my application binary (e.g. XORP) that was pre-compiled for my desktop Linux to my L4Linux RAM disk? Or do I have to re-compile and link my app for L4 environment? Any help is greatly appreciated. Thanks, Chip The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

Support for Intel Xeon
by Wang, Chip 18 Jul '05

18 Jul '05

Hi, Do anybody know if Fiasco and L4Linux support Intel Xeon processors? Chip The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

Archive into libloader.s.so Fails
by Kenji Miyamoto 17 Jul '05

17 Jul '05

When using the same configuration as last time ( http://os.inf.tu-dresden.de/pipermail/l4-hackers/2005/002346.html ), I recieve this error well into the build of L4Env: ==> Archiving into libloader.s.so LD_PRELOAD=/mnt/l4/usr/src/l4/tool/gendep/libgendep.so GENDEP_TARGET=libloader.s.so GENDEP_BINARY=ld ld -o libloader.s.so -shared \ -T../../../../../lib/x86_586/main_rel.ld main.s.o helper_dyn.s.o errstr-l4ipc.s.o -L../../../../../lib/x86_586/l4v2 -L/mnt/lfs/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/mnt/lfs/lib/x86_586 -L../../../../../lib -L/mnt/lfs/lib -L../../../../../../oskit10/lib -L/mnt/lfs/lib/oskit10 --whole-archive -lsemaphore.p -lthread.p -ldm_generic.p -ldm_mem.p -lslab.p -ll4env_err.p -ll4rm.p -ll4env_loaderruntime.p -llogserver.p -lnames.p -lroot.o.p -lgeneric_ts.p -lloaderif.p --no-whole-archive -ll4util.p -ul4util_reboot -ugetopt_long /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/libgcc.a --nostdlib ld: cannot find -lroot.o.p make[5]: *** [libloader.s.so] Error 1 make[5]: Leaving directory `/mnt/l4/usr/src/l4/pkg/loader/lib/runtime/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/mnt/l4/usr/src/l4/pkg/loader/lib/runtime' make[3]: *** [runtime] Error 2 make[3]: Leaving directory `/mnt/l4/usr/src/l4/pkg/loader/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/mnt/l4/usr/src/l4/pkg/loader' make[1]: *** [loader.lib] Error 2 make[1]: Leaving directory `/mnt/l4/usr/src/l4/pkg' make: *** [pkg] Error 2 What doen the "ld: cannot find -lroot.o.p" mean? - Kenji

2 1

L4Evn-2.6 Fails to Configure
by Kenji Miyamoto 16 Jul '05

16 Jul '05

According to the build instructions, a "make config" in the l4 directory will create a configuration menu. It doesn't seem to work in today's (07-16-2005) CVS version: l4 # make config make: *** No rule to make target `config'. Stop. l4 # make xconfig make: *** No rule to make target `xconfig'. Stop. There isn't a Makefile in the l4 directory, either. Why is this so? - Neil

2 1

L4Env Compilation Error at "Multiboot-SMP" on Gentoo
by Kenji Miyamoto 13 Jul '05

13 Jul '05

Hello all, I am getting an error when compiling L4Env on my computer: Gentoo 2005.0 i386 (Pentium 4) kernel-2.6.12-gentoo-r4 gcc-3.3.5.20050130 I have download the newest CVS sources as of today (July 12th, 2005). I have had my drive in both the CVS directory (/usr/src/cvs/l4linux-2.6/l4) and a secondary mounted hard drive (/l4-linux/usr/src/l4linux-2.6/l4) with no different in results. How would I get it to build? My configuration options are as follows, from DROPS: Target Architectures ---> [*] x86 CPU types: "686" [*] L4 V2 [*] Build shared libloaders.s.so Paths and Directories ---> DROPS_STDDIR: "/l4-linux" DROPS_INSTDIR: "$(DROPS_STDDIR)" L4LINUX22_DIR: "$(L4DIR)/../linux22" [*] Linux 2.6 kernel sources available Path to Linux 2.6 sources: "$(L4DIR)/../l4linux-2.6" DDE include path (DDE_INCDIR): "$(L4DIR)/include/$(ARCH)/l4/dde_linux $(DROPS_STDDIR)/include/$(ARCH)/l4/dde_linux" DDE-2.6 include path (DDE26_INCDIR): "$(L4DIR)/include/$(ARCH)/l4/dde_linux26 $(DROPS_STDDIR)/include/$(ARCH)/l4/dde_linux26 $(L4DIR)/include/l4/dde_linux26 $(DROPS_STDDIR) SDL include path (SDL_INCDIR): "$(L4DIR)/include/l4/sdl $(DROPS_STDDIR)/include/l4/sdl" Verboseness and Messages ---> [*] Verbose dependency building [*] Verbose compilation and building [*] Short messages for compilation [*] Colored build-steps Compilers and Tools ---> [*] System has ld.so (highly recommended if so) [*] Automatically determine internal gcc preprocessor names [*] Automatically determine internal ld names [*] Strip binaries on install [*] Generate stabs-compatible debug Infos with gcc-3+ [*] GCC: Omit Frame-pointers [*] Generate Map-files for binaries This is where the error starts: make[3]: Entering directory `/l4-linux/usr/src/l4linux-2.6/oskit/examples' ld -Ttext 100000 -L../lib \ -o multiboot-smp ../lib/multiboot.o multiboot-smp.o \ -lsmp -lkern -lmc -llmm ../lib/crtn.o /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/libgcc.a ../lib/libsmp.a(boot.o)(.text+0x29): In function `_SMP_TRAMP_START_': : relocation truncated to fit: R_386_16 _SMP_TRAMP_32_ENTRY_ make[3]: *** [multiboot-smp] Error 1 make[3]: Leaving directory `/l4-linux/usr/src/l4linux-2.6/oskit/examples' make[2]: *** [examples/all.MAKE] Error 2 make[2]: Leaving directory `/l4-linux/usr/src/l4linux-2.6/oskit' make[1]: *** [all] Error 2 make[1]: Leaving directory `/l4-linux/usr/src/l4linux-2.6/oskit' make: *** [../oskit] Error 2 Any help would be greatly appreciated. - Neil

2 1

L4Env Compilation Error at "Multiboot-SMP" on Gentoo
by fabs0028＠free.fr 13 Jul '05

13 Jul '05

Hello i had the same problem some weeks ago. It is just an example that seems broken. For my part i changed the makefile : in the subfolder x86 , edit the GNUMakerules and in the targets comment multiboot-smp and it should be fine. Fabien Chaillou

1 0

RE: Error in building l4linux-2.6-env
by Wang, Chip 12 Jul '05

12 Jul '05

Hi Adam, I did not intentionally checkout dde. It just came with l4linux-2.6-env. I think it was part of the module. If it is not required to build l4linux-2.6 maybe you would want to separate it from the module? By the way, how can I receive CVS commit notifications via email, or is it even possible? I am looking forward to you publishing the fix soon. Thanks, Chip -----Original Message----- From: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de]On Behalf Of Adam Lackorzynski Sent: Tuesday, July 12, 2005 10:43 AM To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Error in building l4linux-2.6-env On Tue Jul 12, 2005 at 10:09:26 -0600, Wang, Chip wrote: > After skipped building fprov-l4 and kill-l4 in l4/pkg/loader/examples, > I managed to get a little further. > This time my make failed at l4/pkg/dde for conflicting function > prototypes. It appears the make was using Linux 2.4 header files while > building for 2.6 This is actually correct as dde_linux is for Linux2.4. The compiler error appears with more recent compiler versions, and I have now finally fixed it internally. Should be in our public CVS by tomorrow. On the other side, how did it come that you checked out dde? You don't need it to get L4Linux going. 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 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

L4Linux 2.4 server priority
by Leon Brits 12 Jul '05

12 Jul '05

Hi all, I have some questions with regard to the priority of a L4Linux server: Q1: In my loader script I set the "priority" parameter to what some help file somewhere (I think on the website) showed namely 0xA0. When I do a l4lx_thread_prio_get inside a kernel module I get the value "100". Is the loader "priority" parameter hex or decimal? [0xA0 -> 100 ????] Q2: If I set the "priority" parameter of a second L4Linux server to 0x30 I also get 100. Does this parameter actually work? - if not where is "100" defined? Q3: The API call l4lx_thread_prio_get() actually fails when the module loads complaining about exported symbols, while l4lx_thread_create() which is defined in the same header file (thread.h) and in the same source file (thread.c) works fine. Can somebody please help me understand this!? Q4: In the L4Linux server the kernel's priority is set based on a define named PRIO_KERNEL which is defined as 127. How does this PRIO_KERNEL defined value (and other PRIO_* values) relate to the "priority" parameter. Thanks Leon

2 1

Error in building l4linux-2.6-env
by Wang, Chip 12 Jul '05

12 Jul '05

Hi, After skipped building fprov-l4 and kill-l4 in l4/pkg/loader/examples, I managed to get a little further. This time my make failed at l4/pkg/dde for conflicting function prototypes. It appears the make was using Linux 2.4 header files while building for 2.6 Does anybody have an idea of what went wrong? Chip make[5]: Entering directory `/home/drops/l4/pkg/dde_linux/lib/src/OBJ-x86_586-l4v2' ... Compiling mm.o LD_PRELOAD=/home/drops/l4/tool/gendep/libgendep.so GENDEP_TARGET=mm.o GENDEP_BINARY=cc1 gcc -c -D__KERNEL__ -DDDE_LINUX -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../lib/include -I../../../../../include/x86/l4/dde_linux -I/home/drops/include/x86/l4/dde_linux -I../../../../../include/linux-24 -I/home/drops/include/linux-24 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/drops/include/l4v2 -I../../../../../include/x86 -I/home/drops/include/x86 -I../../../../../include -I/home/drops/include -nostdinc -DOSKIT -I../../../../../../oskit10 -I../../../../../../oskit10/oskit/c -I/home/drops/include/oskit10 -I/home/drops/include/oskit10/oskit/c -I/usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -fno-strict-aliasing /home/drops/l4/pkg/dde_linux/lib/src/mm.c -o mm.o In file included from ../../../../../include/linux-24/linux/bitops.h:69, from ../../../../../include/x86/l4/dde_linux/asm/system.h:10, from ../../../../../include/x86/l4/dde_linux/linux/spinlock.h:8, from ../../../../../include/linux-24/linux/wait.h:16, from ../../../../../include/linux-24/linux/fs.h:12, from ../../../../../include/linux-24/linux/capability.h:17, from ../../../../../include/linux-24/linux/binfmts.h:5, from ../../../../../include/x86/l4/dde_linux/linux/sched.h:11, from ../../../../../include/linux-24/linux/mm.h:4, from ../../../../../include/linux-24/linux/slab.h:14, from /home/drops/l4/pkg/dde_linux/lib/src/mm.c:50: ../../../../../include/linux-24/asm/bitops.h:343: warning: static declaration of 'ffs' follows non-static declaration In file included from ../../../../../include/x86/l4/dde_linux/linux/sched.h:25, from ../../../../../include/linux-24/linux/mm.h:4, from ../../../../../include/linux-24/linux/slab.h:14, from /home/drops/l4/pkg/dde_linux/lib/src/mm.c:50: ../../../../../include/linux-24/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule' ../../../../../include/x86/l4/dde_linux/asm/smp.h:44: error: previous declaration of 'smp_send_reschedule' was here ../../../../../include/linux-24/linux/smp.h:29: error: conflicting types for 'smp_send_reschedule' ../../../../../include/x86/l4/dde_linux/asm/smp.h:44: error: previous declaration of 'smp_send_reschedule' was here make[5]: *** [mm.o] Error 1 make[5]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib/src/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/drops/l4/pkg/dde_linux/lib' make[2]: *** [lib] Error 2 make[2]: Leaving directory `/home/drops/l4/pkg/dde_linux' make[1]: *** [dde_linux.lib] Error 2 make[1]: Leaving directory `/home/drops/l4/pkg' make: *** [pkg] Error 2 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

L4Env Isolating Hard Drives
by Julian Grizzard 12 Jul '05

12 Jul '05

All, Consider a x86 computer that has two physical IDE hard drives. Is it possible for an L4Env I/O manager to allocate exactly one hard drive to an L4Linux2.6 server and allocate the second hard drive to another L4 task in a way that the L4Linux2.6 server has no way of knowing that the second hard drive exists? Thanks! -Julian

3 3

Help! Unable to build L4Env-0.2
by Wang, Chip 12 Jul '05

12 Jul '05

Hi fellow hackers, I am a newbie here. I am trying to build my first L4Linux-2.6 setup, but failed at building L4Env. I downloaded and unpacked the following S/W from the L4Env download page: - l4env-0.2 tarball - dde-0.2 tarball - libstdc++.0.2 - oskit-06302003 - oskit10-06302003 I also checked out L4Linux-2.6-env from CVS. I then followed the instructions and did 'make config' and 'make' from inside the 'l4' directory. The compilation eventually failed at building l4/pkg/loader. The linker complained that the library -lcon was missing. My Linux is 2.6.11 from Mandrake with KDE. My platform is an Acer TravelMate c300 notebook. I searched the mailing list archive but didn't see similar report of the problem I figure I must be missing some other pieces or having the wrong versions. By the way, I also got errors when building 'multiboot-smp'. I followed the suggestion to skip the example by creating a null executable. Should I do the same for this example? Could someone please show me what I did wrong? Thanks in advance for your help Chip The last portion of the build log is attached below. === Building servers, examples of "loader" === PWD=/home/drops/l4/pkg/loader make -C loader all -o lib -o include -o idl make[2]: Entering directory `/home/drops/l4/pkg/loader' test -f server/broken -o -f server/obsolete || \ if [ -f server/Makefile ] ; then PWD=/home/drops/l4/pkg/loader/server make -C server ; fi make[3]: Entering directory `/home/drops/l4/pkg/loader/server' test -f src/broken -o -f src/obsolete || \ if [ -f src/Makefile ] ; then PWD=/home/drops/l4/pkg/loader/server/src make -C src ; fi make[4]: Entering directory `/home/drops/l4/pkg/loader/server/src' PWD=/home/drops/l4/pkg/loader/server/src/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/home/drops/l4/pkg/loader/server/src/OBJ-x86_586-l4v2' ==> Linking loader LD_PRELOAD=/home/drops/l4/tool/gendep/libgendep.so GENDEP_TARGET=loader GENDEP_BINARY=ld gcc -o loader ../../../../../lib/x86_586/crt0.o trampoline.s.o main.o cfg-parse.o cfg.o pager.o app.o fprov-if.o dm-if.o exec-if.o idl.o events.o lib.o loader-server.o -Ttext=0x01300000 -L../../../../../lib/x86_586/l4v2 -L/home/drops/lib/x86_586/l4v2 -L../../../../../lib/x86_586 -L/home/drops/lib/x86_586 -L../../../../../lib -L/home/drops/lib -L../../../../../../oskit10/lib -L/home/drops/lib/oskit10 -T../../../../../lib/x86_586/main_stat.ld -ll4exec -lgeneric_ts -lgeneric_fprov -lloaderif -lcon -ldm_phys -levents -lparsecmdline -static -loskit10_support_l4env.o -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver -lnames -ll4util -lrmgr -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -loskit_c -loskit_kern -loskit_clientos -loskit_lmm -loskit_kern -loskit_c /usr/lib/gcc/i586-mandrake-linux-gnu/3.4.3/libgcc.a -loskit_c -Ttext=0x01300000 -Wl,-gc-sections /usr/bin/ld: cannot find -lcon collect2: ld returned 1 exit status make[5]: *** [loader] Error 1 make[5]: Leaving directory `/home/drops/l4/pkg/loader/server/src/OBJ-x86_586-l4v2' make[4]: *** [OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/drops/l4/pkg/loader/server/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/drops/l4/pkg/loader/server' make[2]: *** [server] Error 2 make[2]: Leaving directory `/home/drops/l4/pkg/loader' make[1]: *** [loader.bin] Error 2 make[1]: Leaving directory `/home/drops/l4/pkg' make: *** [pkg] Error 2 The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. Thank you.

2 1

build failure and fix for typo
by Julian Stecklina 12 Jul '05

12 Jul '05

Hello, I tried to build fiasco on FreeBSD today using the following commands: > cd kernel/fiasco > gmake config > env AWKP=awk gmake I got as far as: gmake srcdir=/usr/home/blitz/src/os/l4/kernel/fiasco/src -f /usr/home/ blitz/src/os/l4/kernel/fiasco/src/Makefile.sub2 all gmake[3]: Entering directory `/usr/home/blitz/src/os/l4/kernel/fiasco/build' ... Making kip.o g++ -c -MD -nostdinc -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/types/ia32 -I/usr/home/blitz/src/os/l4/kernel/fiasco/src/types -I/ usr/home/blitz/src/os/l4/kernel/fiasco/src/drivers/ia32 -I/usr/home/ blitz/src/os/l4/kernel/fiasco/src/drivers -I/usr/home/blitz/src/os/l4/ kernel/fiasco/src/kern/ia32 -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/kern/shared -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/kern -I/ usr/home/blitz/src/os/l4/kernel/fiasco/src/boot -I/usr/home/blitz/src/ os/l4/kernel/fiasco/src/lib/libk/ia32 -I/usr/home/b litz/src/os/l4/ kernel/fiasco/src/lib/libk -I/usr/home/blitz/src/os/l4/kernel/fiasco/ src/lib/kern/include -I/usr/home/blitz/src/os/l4/ kernel/fiasco/src/lib/ amm -I/usr/home/blitz/src/os/l4/kernel/fiasco/src/lib/gzip -I/usr/home/ blitz/src/os/l4/kernel/fiasco/src/lib/di sasm -I/usr/home/blitz/src/os/ l4/kernel/fiasco/src/lib/perfctr -I/usr/home/blitz/src/os/l4/kernel/ fiasco/src/lib/regex -I/usr/home/bl itz/src/os/l4/kernel/fiasco/src/lib/ minilibc/ia32/include -I/usr/home/blitz/src/os/l4/kernel/fiasco/src/lib/ minilibc/include -I. -Iauto -I/usr/lib//include -fno-implement-inlines -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium2 -fno-defer-pop -freg-struct-re turn -g -Wall -W -Wformat=2 -ffunction-sections -fomit- frame-pointer -gstabs+ -fno-rtti -fno-exceptions -Wno-non-virtual- dtor -O2 - finline-limit=10000 --param large-function-insns=10000 - fweb -frename-registers auto/kip.cc -o kip.o In file included from auto/ kip.h:6, from auto/kip.cc:3: /usr/home/blitz/src/os/l4/kernel/fiasco/ src/types/types.h:4:20: stddef.h: No such file or directory (some spaces have crept in due to copy&paste from xterm) minilibc does not seem to provide stddef.h, so the one of the host compiler is probably meant (is this correct?), but -I/usr/include//bin seems kind of bogus. Has anyone an idea where to tweak this? As a general remark: Hardcoded paths in the build process should be avoided. Best example #!/bin/bash in scripts which should be replaced by #!/usr/bin/env bash or even better #!/bin/sh for better portability. I think the whole build process needs some kind of autoconf magic, too, to make it less GNU/Linux dependent. Regards, -- Julian Stecklina LISP has survived for 21 years because it is an approximate local optimum in the space of programming languages. - John McCarthy (1980)

2 7

using l4linux structures in l4
by Andrew Davenport 11 Jul '05

11 Jul '05

Hello, What is the simplest way to use (eg) the task_struct from linux inside the l4 microkernel. I want to use exactly the same declaration in the kernel, but I am having difficulty using it. Thanks, Andrew

2 1

exception -> l4_ipc ?
by Andrew Davenport 11 Jul '05

11 Jul '05

hi, i see thread::raise_exception(ts), and i know this is where l4 notices a linux sys call (int 0x80), however, i do *not* see where the ipc is sent to the linux server to tell it that a syscall has occured (and to get the parameters and handle it)... thanks in advance, -andrew

2 7

documentation booting fiasco
by Emanuel Thomas 11 Jul '05

11 Jul '05

Hello, is there any detailed documentation about the Fiasco boot process available? Emanuel

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers