- l4-hackers - example.com Site

How many tasks can be started?
by Daniel Vandersee 15 Mar '07

15 Mar '07

Hi there, can you tell me how many Tasks can be started from L4? As the task id has 11 bit, the theoretical maximum seems to be 2048, but if I configure simple_ts to use 246 tasks, I can't create a new task without using simple_ts (I use rmgr_get_task and rmgr_task_new). In this case the first free task number is 256. The task creation via rmgr_task_new seems to work (a valid task id is returned), but it seems that I can't serve the first page fault. If I serve it with an fpage, I immediately get the same page fault again and again. With simple_ts configured to 245 tasks everything works fine. Regards, Daniel

2 2

Build problems (with automake version)
by Igor Shmukler 08 Mar '07

08 Mar '07

Hello, I am having problems with CVS version of L4 not building due automake version error. Please advise. Error pasted below: ./bootstrap: ERROR: `automake' is too old. automake (GNU automake) 1.10 Written by Tom Tromey <tromey(a)redhat.com> and Alexandre Duret-Lutz <adl(a)gnu.org>. Copyright 2006 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. (version 1.9 or newer is required) ./bootstrap: ERROR: `aclocal' is too old. aclocal (GNU automake) 1.10 Written by Tom Tromey <tromey(a)redhat.com> and Alexandre Duret-Lutz <adl(a)gnu.org>. Copyright (C) 2006 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. (version 1.9 or newer is required) make[2]: *** [GNUmakefile] Error 1 make[2]: Leaving directory `/home/ubuntu/l4-devel/l4/tool/dice' make[1]: *** [dice] Error 2 make[1]: Leaving directory `/home/ubuntu/l4-devel/l4/tool' make: *** [tool] Error 2 ubuntu@ubuntu:~/l4-devel/l4$

3 10

minor makefile error in examples
by Igor Shmukler 08 Mar '07

08 Mar '07

This one is minor, but i think it's nor imaginary - makefile does not make a symlink or something. I'll just copy the file. make[5]: Entering directory `/home/ubuntu/l4-devel/build/pkg/loader/examples/fprov-l4/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/ubuntu/l4-devel/l4/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cc1 gcc -c -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/home/ubuntu/l4-devel/build/pkg/loader/idl/OBJ-x86-l4v2 -I/home/ubuntu/l4-devel/build/include/x86/l4v2 -I/home/drops/include/x86/l4v2 -I/home/ubuntu/l4-devel/build/include/l4v2 -I/home/drops/include/l4v2 -I/home/ubuntu/l4-devel/build/include/x86 -I/home/drops/include/x86 -I/home/ubuntu/l4-devel/l4/tool/dice/include -I/home/ubuntu/l4-devel/build/include -I/home/drops/include -I/usr/lib/gcc-lib/i486-linux-gnu/3.3.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common /home/ubuntu/l4-devel/l4/pkg/loader/examples/fprov-l4/main.c -o main.o /home/ubuntu/l4-devel/l4/pkg/loader/examples/fprov-l4/main.c:22:18: zlib.h: No such file or directory

2 1

and now linking problems
by Igor Shmukler 08 Mar '07

08 Mar '07

Hello, First, I would like to thank Ronald, Michael, Adam and everyone else for helping me to get started. I have another problem. This time it's linking issue. I was compiling with gcc 3.3. Please advise: --- -e ... Making gdb_copy.o -e ... Making gdb_pc_com_intr.o -e ==> Archiving into libkern.a -e ==> Linking kernel.image thread-log.o: In function `sys_ipc_log_wrapper': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:65: undefined reference to `__stack_chk_fail' /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/thread-log.cpp:179: undefined reference to `__stack_chk_fail' main-ia32-amd64.o: In function `main_arch()': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/main-ia32-amd64.cpp:112: undefined reference to `__stack_chk_fail' cpu-common.o: In function `Cpu::show_cache_tlb_info(char const*)': /home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:(.initcall.text+0x381): undefined reference to `__stack_chk_fail' cpu-common.o:/home/ubuntu/l4-devel/l4/kernel/fiasco/src/kern/shared/cpu-common.cpp:892: more undefined references to `__stack_chk_fail' follow make[4]: *** [kernel.image] Error 1 make[4]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco/build' make[2]: *** [build] Error 2 make[2]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel/fiasco' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/ubuntu/l4-devel/l4/kernel' make: *** [kernel] Error 2 ubuntu@ubuntu:~/l4-devel/l4$ ---

3 4

Can I use L4/Fiasco in Dual Core CPU ?
by chenggh 08 Mar '07

08 Mar '07

Hi: Now I have a machine with dual core cpu of Athlon. I want to know if I could boot L4/Fiasco in dual core cpu and if there is some optimization of L4/Fiasco for dual core cpu. Thanks. cheng

2 1

[BUG] Deadlock in Fiasco kernel
by Daniel Vandersee 06 Mar '07

06 Mar '07

Hi there, I noticed that the Fiasco kernel hangs under some circumstances so the whole system stops working. Unfortunately I wasn't even able to enter the kernel debugger via a serial cable in this case. The error is reproducible on different plattforms (e.g. Thinkpad T43, 1GB RAM, Pentium M 1.8 GHz or Thinkpad T41) even though it only appears from time to time (probability ~50% or even better). Within VMWare or Qemu this deadlock does *not* appear. Furthermore this error does not occur if the kernel was started using the "-esc" option. I wasn't able to reproduce this bug on a HP nx7400 (Dual Core T2300, 1GB RAM). We use an own dynamic loader to load some L4 tasks whereas other L4 tasks, as the mGUI, are loaded by GRUB. The bug can be reproduced on real hardware using the iso-image which I will upload to the SLOX server (deadlock.iso). You have to choose GRUB entry two or three. If the error occurs the system hangs in text mode otherwise a graphical mode is entered. Sometimes you have to reboot up to 20 times but it usually occurs immediately. Kind regards Daniel

3 2

DROPS and vbeset 0x117
by Igor Shmukler 05 Mar '07

05 Mar '07

I tried running DROPS demo CD on VMWare Server 1.0. I am getting an error on vbeset 0x117. I guess there is no VESA support in server or something like that. Should I just try using the Free Player to run the demo? Thank you in advance.

3 3

Problem booting l4linux
by Eduard Benes 28 Feb '07

28 Feb '07

Hi all, I'm newbie in this area, and I would like to ask for help with some problems I run into (hope this is the right place). I've finally build l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". (please let me know if there is better document to start with) dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. I had some problem finding out the right configuration of the l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). Right now I'm trying to run it on real hw (How to make it run under qemu?) but when I try to boot DOpE using patched grub, it hangs when (at least I assume) trying to enter graphic mode. The screen shows this: [VESA 2.0 info @ 0x75b5000, 0x2ff bytes] boot <blank> I've tried the L4Linux demo CD, but with the same result. Tried to boot into DOpE or console. I suspect that video card might not be supported. But during many attempts, once the DOpE environment flashed for a second (before doing the restart routine accidentally) and that really surprise for me. The graphical user interface is not necessary, but I don't know yet how to run L4Linux in console. I'm able to get into kernel debugger, when I boot the L4Linux by remote serial console variant of grub menu.lst entries (based on the kickstart document mentioned above). In the kernel debugger mode was logged one error: [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): Error: Missing 'deceit_bit_disables_switch' kernel feature! Startup: semaphore lib initialization failed (-1)! It is probably not related to the problem with video card, but might show some mistakes in my l4linux-2.6 kernel configuration. Here is my PCI device list: $ lspci 00:00.0 Host bridge: ATI Technologies Inc Radeon 9100 IGP Host Bridge (rev 02) 00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge 00:13.0 USB Controller: ATI Technologies Inc OHCI USB Controller #1 (rev 01) 00:13.1 USB Controller: ATI Technologies Inc OHCI USB Controller #2 (rev 01) 00:14.0 SMBus: ATI Technologies Inc ATI SMBus (rev 16) 00:14.1 IDE interface: ATI Technologies Inc ATI Dual Channel Bus Master PCI IDE Controller 00:14.3 ISA bridge: ATI Technologies Inc Unknown device 434c 00:14.4 PCI bridge: ATI Technologies Inc Unknown device 4342 00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller 00:14.6 Modem: ATI Technologies Inc IXP AC'97 Modem (rev 01) 01:05.0 VGA compatible controller: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP] 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) 02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01) 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01) 02:07.0 USB Controller: NEC Corporation USB (rev 43) 02:07.1 USB Controller: NEC Corporation USB (rev 43) 02:07.2 USB Controller: NEC Corporation USB 2.0 (rev 04) My final goal is to compare performance of L4Linux and native Linux on real hw. I will appreciate any suggestions or study literature on this topic. Other questions I would like to ask: What is the right way to boot from serial console? How can be achieved networking under L4Linux? Regards, Eduard Benes

2 1

RE: Learning and Hacking L4 - My Bookshelf
by Stitt, Michael (AGRE) 28 Feb '07

28 Feb '07

Hi Jeff, Being in a similar boat, I don't have a good answer for you. But here's a copy (in semi-alphabetical order) of my L4 bookshelf and links to the other bookshelves I know about. Maybe you've found these already. -Hope this helps -Mike ++++L4 - My Bookshelves L4 eXperimental Kernel Reference Manual - (Karlsruhe) - Version X.2, Revision 5 - June 4 2004 http://l4ka.org/projects/pistachio/l4-x2-r5.pdf L4 User Manual - NICTA L4-embedded API - Ihor Kuz - Document Version 1.11 of October 5, 2005 http://www.ertos.nicta.com.au/software/kenge/pistachio/latest/userman.pdf L4Ka::Pistachio PowerPC Implementation Revision: 1.9 - Joshua LeVasseur - Karlsruhe http://l4ka.org/projects/pistachio/powerpc/ppc.pdf NICTA L4-embedded Kernel Reference Manual Version NICTA N1, Revision 5 http://www.ertos.nicta.com.au/software/kenge/pistachio/latest/refman.pdf On Micro-Kernel Contruction - Jochen Liedke - Karlsruhe - 15th ACM Symposium on Operating System Principles (SOSP) December 3-6, Copper Mountain Resort, Colorado http://www.l4ka.org/publications/1995/ukernel-construction.pdf Real-Time Programming and L4 Microkernels - Sergio Ruocco - NICTA - UNSW - 2007 http://www.ertos.nicta.com.au/publications/papers/Ruocco_06.abstract.pml Towards Real Microkernels - Jochen Liedke - Karlsruhe - September 1996/Vol. 39, No. 9 Communications of the ACM http://i30www.ira.uka.de/research/documents/l4ka/towards-ukernels.pdf ++++L4 - Other Bookshelves Dresden L4 Developer's Bibliography http://os.inf.tu-dresden.de/L4/bib.html Karlsruhe L4Ka Publications - OR - Karlsruhe System Architecture Group L4ka Publications http://www.l4ka.org/publications/ - OR - http://i30www.ira.uka.de/research/publications/l4ka/index.php?lid=en NICTA ERTOS Publications http://www.ertos.nicta.com.au/publications/ Teaching material from University of Karlsruhe http://i30www.ira.uka.de/teaching/courses/lecture.php?courseid=130 Teaching material from University of New South Wales http://www.cse.unsw.edu.au/~cs9242/06/lectures/ -----Original Message----- From: l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] On Behalf Of Jeff Douglas Sent: Tuesday, February 27, 2007 11:29 AM To: l4-hackers(a)os.inf.tu-dresden.de Subject: Learning and Hacking L4 Hi Coly, I've read through the X.2 spec and some of the other papers that looked like they might be useful. Unfortunately, they are not really helpful to me. Or, perhaps it is better to say that they don't seem to paint a full picture. What I think would really be helpful is the L4 System Programmer's Manual. I've waited for it to materialize for years now, but it still hasn't appeared. Do you have any particular papers to suggest? Does you know if/when the System Programmer's Manual will be released? Regards, JD >Jeff: >hi, do you read some papers for L4 ? Maybe you can start from reading >these papers. > >Coly > >在 2007-02-27二的 22:36 +0900，Jeff Douglas写道： > Greetings, > > I have had some interest in os development and theory for quite some > time now, and a particular interest in L4. I'm a newbie, but I've read > through a lot, and have done some os programming for fun in the past. > > My question is: what is your advice on learning and hacking L4? > > I've read through quite a bit of the documentation, but reading > through specs does not seem like a good way to really understand; it > seems like too much to digest at once. And of course, the purpose of a > specification is to specify, not explain. I've browsed through source > code, but that is even worse. > > I'm sorry if my question is overly broad, but I'd appreciate any > advice that anyone can spare. > > Regards, > JD > > _______________________________________________ > l4-hackers mailing list > l4-hackers at os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ______________________________________________________________________ CAUTION: This message was sent via the Public Internet and its authenticity cannot be guaranteed. ______________________________________________________ ************************************************ The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ************************************************

3 2

Re: Problem booting l4linux
by chenggh 28 Feb '07

28 Feb '07

On Wednesday 28 February 2007 11:12, Eduard Benes wrote: > Hi all, > > I'm newbie in this area, and I would like to ask for help with some > problems I run into (hope this is the right place). I've finally build > l4linux following instructions in the "L4/Fiasco/L4Linux Kickstart". > (please let me know if there is better document to start with) > dslab.lzu.edu.cn/docs/publications/l4_kickstart.pdf. We have tested this document many times and some Linux newbie used this document to build the L4Linux very successfully. And please pay attention that this document is made in the case of kernel 2.6.17. Maybe in the kernel 2.6.19 there are some problems, too. > I had some problem finding out the right configuration of the > l4linux-2.6.19-l4 kernel (could someone provide example of the .conf file). > Right now I'm trying to run it on real hw (How to make it run under qemu?) > but when I try to boot DOpE using patched grub, it hangs when (at least I > assume) trying to enter graphic mode. The screen shows this: If you use L4Linux or Fiasco the first thing is to study how to use serial console to debug the Fiasco especially in the graphical mode you don't see anything important in the screen. Some booting error messages could only be output by the serial console. > I've tried the L4Linux demo CD, but with the same result. Tried to boot > into DOpE or console. I suspect that video card might not be supported. But > during many attempts, once the DOpE environment flashed for a second > (before doing the restart routine accidentally) and that really surprise > for me. The graphical user interface is not necessary, but I don't know yet > how to run L4Linux in console. I'm able to get into kernel debugger, when I > boot the L4Linux by remote serial console variant of grub menu.lst entries > (based on the kickstart document mentioned above). In the kernel debugger > mode was logged one error: > [B.0] semaphore/lib/src/semaphore.c:500:l4semaphore_init(): > Error: Missing 'deceit_bit_disables_switch' kernel feature! > Startup: semaphore lib initialization failed (-1)! > It is probably not related to the problem with video card, but might show > some mistakes in my l4linux-2.6 kernel configuration. > If you still have some problems about compiling or booting, please download this tar ball (http://dslab.lzu.edu.cn/~chenggh/doc/L4.tar) I have tested this tar ball many times successfully and if you use this directory and do as the kickstart says. I promise you could be successful. In this letter there are 2 attachments: one is 2.4.17 configuration file for booting from serial console and another is 2.4.17 configuration file for booting from Dope. > My final goal is to compare performance of L4Linux and native Linux on real > hw. I will appreciate any suggestions or study literature on this topic. I have done some similar work as you want to do and if you want know something about my paper and data please access my home page (dslab.lzu.edu.cn/~chenggh). > Other questions I would like to ask: > What is the right way to boot from serial console? Please review my kickstart and some configuration file. > How can be achieved networking under L4Linux? In my benchmark about performance comparasion between L4Linux and Linux I use L4Linux network (It is same as you do in Linux). But if you want to use Fiasco network there is a module ORe (the Oshkosh Resurrection) you could try. But I think this module only show us the Fiasco supports network, too and you don't do anything meaningful. Thank you. I hope you could modify my kickstart and give the new version of this kickstart. Thank you. cheng

1 0