- 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

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