l4-hackers March 2007

l4-hackers@os.inf.tu-dresden.de

17 participants
22 discussions

Fiasco runtime error
by eschierb＠sci.kun.nl 30 Mar '07

30 Mar '07

Hi, For my verification of Fiasco I would like to test some of the assumptions I am making in the proof. One way to test these assumptions is to add these assumptions as assert() calls in the kernel and check if they fire when the kernel is running a stress-test. The idea is to create an L4Linux instance and run an IPC-intensive application on it. For the compilation of l4-env and Fiasco I followed the instructions on this webpage: http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml. However, when I tried to execute step 3 (Go to the l4 directory and call make config) the system complained: make config does not work: need to give builddir with O=.../buildir. Stop. Of course this was easy to correct but I thought Id notify you anyway. After compiling Fiasco and l4-env, I thought Id try out the hello module. I moved the fiasco, irq0 and ux-con files from the Fiasco build directory to the DROPS build directory after which I started Fiasco as follows: ./fiasco l hello This resulted in the following: Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: AuthenticAMD (6:6:2:0) Model: Athlon (Palomino) at 1160 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 39f5000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures --Interception--------------------------------------ESP:00096748 EIP:000907cf (2.00) jdb: As you can see we automatically entered the debugger, any attempt to continue (using the g command) failed. I compiled Fiasco with the following options: Target platform: UX Exception IPC: Y Handle and preserve segments: Y Graphical console: Y Generate inline code: Y I also tried to run a test of Fiasco using: ./fiasco T which indicates that something is wrong: Fiasco-UX on Linux 2.6.18-1.2798.fc6 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: AuthenticAMD (6:6:2:0) Model: Athlon (Palomino) at 1160 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. KERNEL: 2.0 (tcb=20080000) killed: Unhandled trap EAX 00000000 EBX 0000c000 ECX 039f5000 EDX 00000000 ESI 00000000 EDI 00000000 EBP 00000000 ESP bf9ee09c EIP 00002000 EFLAGS 00200246 CS 0002 SS 007b DS 007b ES 007b FS 0000 GS 0007 trap 13 (General Protection), error 00000402, from user mode (internal event regarding IDT gate descriptor no. 0x80) --Interception--------------------------------------ESP:20000790 EIP:0004ee8b (0.00) jdb: Do you have any idea what might be wrong? With regards, Erik Schierboom ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

3 3

Re: hda : lost interrupt
by Burak OGUZ 30 Mar '07

30 Mar '07

My grub configuration does not contain -esc. How can I run my installed l4 over qemu? Do you mean RS232 cable serial null modem cable? I am working L4 on laptop therefore I don't have a direct RS232 access. I can not maintain that logs now. Are there any other ways that can I collect that this log info? Best regards -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Christian Helmuth <ch12(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Thursday, March 29, 2007 2:04:23 PM Subject: Re: hda : lost interrupt Hi, On Thu, Mar 29, 2007 at 01:01:08AM -0700, Burak OGUZ wrote: > Also a warning complains about I should not use -esc in L4Input. As libinput has no chance to check Fiasco's command line, it always logs this message. Just make sure your Fiasco grub module line does not contain "-esc". Anyway, did you attach a serial null modem cable to your test box/virtual machine? Greets -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12 _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php

2 2

DROPS/TUD:OS repository moved to subversion
by Adam Lackorzynski 29 Mar '07

29 Mar '07

Hi all, the public DROPS/TUD:OS repository has been moved to subversion and is now available at the following URL: http://svn.tudos.org/repos/tudos/trunk L4Linux is available at: http://svn.tudos.org/repos/l4linux/trunk The repositories contain the common svn structure with trunk, tags and branches. To make it easier for you to check out selected parts of the archive we have written a script that knows different modules. Do the following to get the Fiasco kernel and the packages for the 'hello' program. $ svn checkout -N http://svn.tudos.org/repos/tudos/trunk tudos $ cd tudos $ ./repomgr co hello To show all the available modules, issue: $ ./repomgr modules The repositories are updated after a successful build that is run once a day. Note that the internal directory structure changed a bit, the 'kernel' and 'dice' directories have been moved out of the l4 directory. The old public CVS repository will still be available for some time. It is not updated anymore. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 2

Re: hda : lost interrupt
by Burak OGUZ 29 Mar '07

29 Mar '07

There was an error, which was caused by removal of the vbeset command from grub. Also a warning complains about I should not use -esc in L4Input. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Wednesday, March 28, 2007 8:49:09 PM Subject: Re: hda : lost interrupt On Wed Mar 28, 2007 at 08:01:09 -0700, Burak OGUZ wrote: > I have successfully booted the L4 and saw the dope. However, while > L4Linux is booting up it gives "hda : lost interrupt" for my hard disk > and "hdc : lost interrupt" for my cd-rom. I have applied whatever says > in the l4-kickstart manual except l4exec because I have read that it > is deprecated. > > Also same problem has occured when I have booted up with live CD. 'lost interrupt' indicates that there's some problem with the interrupt handling on your system. Can you maybe show us the log output that comes on the serial console and your menu.lst? You may also use e.g. qemu and compare the serial output of both systems to see if there's some significant difference which might indicate a problem. For testing purposes you may also comment out the vbeset command in the menu.lst as well as the line that loads dope. With this change you'll see the debug output directly on the screen. Look for messages that might indicate an error. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html

2 1

Re: hda : lost interrupt
by Burak OGUZ 29 Mar '07

29 Mar '07

How can I reach to the logs of serial output and grub? Does it writes them anywhere on the disk? -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Wednesday, March 28, 2007 8:49:09 PM Subject: Re: hda : lost interrupt On Wed Mar 28, 2007 at 08:01:09 -0700, Burak OGUZ wrote: > I have successfully booted the L4 and saw the dope. However, while > L4Linux is booting up it gives "hda : lost interrupt" for my hard disk > and "hdc : lost interrupt" for my cd-rom. I have applied whatever says > in the l4-kickstart manual except l4exec because I have read that it > is deprecated. > > Also same problem has occured when I have booted up with live CD. 'lost interrupt' indicates that there's some problem with the interrupt handling on your system. Can you maybe show us the log output that comes on the serial console and your menu.lst? You may also use e.g. qemu and compare the serial output of both systems to see if there's some significant difference which might indicate a problem. For testing purposes you may also comment out the vbeset command in the menu.lst as well as the line that loads dope. With this change you'll see the debug output directly on the screen. Look for messages that might indicate an error. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front

2 1

Re: hda : lost interrupt
by Burak OGUZ 28 Mar '07

28 Mar '07

Hi all, I have successfully booted the L4 and saw the dope. However, while L4Linux is booting up it gives "hda : lost interrupt" for my hard disk and "hdc : lost interrupt" for my cd-rom. I have applied whatever says in the l4-kickstart manual except l4exec because I have read that it is deprecated. Also same problem has occured when I have booted up with live CD. Thanks in advance. -- burak() (ps: bf) METU CENG '06 ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/

2 1

hda : lost interrupt
by Burak OGUZ 28 Mar '07

28 Mar '07

1 0

getting started with L4Linux and DDE
by Igor Shmukler 27 Mar '07

27 Mar '07

Hello, First, I would like to thank everyone for their assistance me with getting up and running. I built a cross sandbox under Ubuntu 6.10 - not a major achievement :) If anyone wants the VMWare image, please let me know. It's 4GB in size, so please prepare enough space for upload. Now, I have been looking through sources. So far these seem quite clear. I even started hacking together something of my own. I do however have questions about using the system. The make installs everything (besides bootstrap and perhaps another tool or two) into the /home/drops/bin/... There is no GRUB menu.lst in that specific directory, but there are a few samples along with various modules. So far everything is very clear and logical. What puzzles me. The DDE (sound) sample needs a missing file - fiasco. However, I only have fiasco_top in my bin. Am I missing it because I need to build (or install) it manually? There is a file in l4/kernel/fiasco/build/fiasco (symlink to the main). That file is an ELF binary. Seems like a logical candidate. :) Are these files not copied by make install because kernels are interchangeable and I could swap one for another? Is there a quick way to test that everything works? Is the TUD GRUB's only difference support for JDB, or are there are features? Do I have to use TUD GRUB to boot, or only when I need debugging? I am assuming the answer to the next question has to be "YES," however I would like to know for sure. Is TUD GRUB 100% compatible with a regular GRUB? If not, am I likely to need the old GRUB for booting regular Linux? Sorry for spamming the list. I could not find good documentation covering this topic. Thank you in advance, igor

2 1

X Windowing System Under Dope
by SwiftBoo 26 Mar '07

26 Mar '07

Is there a "how-to" on configuring the X Windowing System for running under dope? If not, I'd be happy to write one up afterwards, if someone could help me through the process... I am interested in running the X Windowing System from within L4Linux on my existing DROPS workstation (currently using my existing distribution -- Debian Sarge) on native hardware. With Adam's previous help, I have managed to get everything else (fiasco, dope, l4linux with networking) up and running perfectly fine. Thanks! I see from the Nitpicker demo on the Demo CD, that xorg.conf is configured to run the OvlScreen device driver, and xinitrc runs an ovltrack process, however i didn't see these binaries get built as part of the usual drops build process. I did find an ovlscreen.c in the examples directory... is there a separate build process for generating the binaries to use under l4linux? How can I build ovlscreen and ovltrack for my system? Is Nitpicker required or is it optional? I noticed there is now an l4ovlwm, in addition to the nitovlwm binary referenced by the demo cd -- however, i don't see a nitdope binary that the demo cd references. Has this been integrated directly into l4dope, or perhaps no longer supported? Am I missing other pieces as well? Thanks in advance for any help you might offer! -Mike

3 2

Re: How can i know the meaning of options when I configure the Fiasco kernel
by Adam Lackorzynski 24 Mar '07

24 Mar '07

On Sat Mar 24, 2007 at 07:39:07 +0000, chenggh wrote: > > Most configuration options in the kernel configurator have a help text > > which is displayed when pressing '?'. How does it not work for you? > If I press '?' it displays this sentence "Search symbols for regular > expression: " not a help text. This dialog is displayed when pressing '/'. You might also want to press shift to get '?'. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers March 2007