January 2006 - l4-hackers - example.com Site

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

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