l4-hackers

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

2827 discussions

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

I have made dmon work. What should I report here? It gives no error but finally it logs : l4lx_thread_create: Created thread 0f.0a (IRQ14) l4lx_thread_create: Created thread 0f.0b (IRQ15) and it starts giving lost interrupt for hard disk and cdrom. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Burak OGUZ <burakoguzs(a)yahoo.com> To: Ronald Aigner <ra3(a)os.inf.tu-dresden.de>; l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, April 2, 2007 3:33:31 PM Subject: Re: hda : lost interrupt Also I have changed the l4 linux configuration file. I think I should adjust linux configuration too. After changing my linux configuration to this : verbose 0 task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb" all_sects_writable allow_cli After changing the configuration l4linux started to give this error: l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.19-l4 (root@think) (gcc version 3.4.6) #1 Wed Mar 2 l4lx : 8 15:42:40 EEST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (3 args): earlyprintk=yes mem=256M video=l4fb l4lx | Image: 00400000 - 00790000 [3648 KiB]. l4lx | Areas: Text: 00400000 - 00696000 [2648kB] (a bit longer) l4lx | Data: 00696000 - 006e408c [312kB] l4lx | Initdata: 006e8000 - 00722000 [232kB] l4lx | BSS: 00724000 - 0078e300 [424kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 006e6000 size = 249856 l4lx | sec-w-init: virt: 0x006e6000 to 0x00722fff [244 KiB] l4lx | sec-w-init: Number of physical regions: 1, 249856 Bytes l4lx | sec-w-init: 1: Phys: 0x01191000 to 0x011ce000, Size: 249856 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0d400000 to 0x1d400000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1517 entries). l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) DMphys | ds 32, client F.00, rights 0x0003, has 0x0001 DMphys | [8.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): DMphys | DMphys: bad permissions l4lx | L4RM: dataspace at 0x00400000-0x00695fff, id 32 at 8.00 l4lx | L4RM: dataspace manager call failed ("permission denied") l4lx | L4RM: [PF] write at 0x00400038, ip 004101d0, src F.02 l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault --PANIC, 'g' for exit------------------------------------IP: a00b43dd (f.00) jdb: Best regards, -- burak() (ps: bf) METU CENG '06 ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html

1 0

Re: hda : lost interrupt
by chenggh 02 Apr '07

02 Apr '07

On Monday 02 April 2007 12:33, Burak OGUZ wrote: > permission What is your choice of option in Fiasco configuration? [ ] Enable I/O port protection If you enable this option only kernel has full access to all I/O ports. As a result when l4lx could access some resources it has no enough rights. So there is "bad permission" or "permission denied" message. So If you run l4linux disenble this option. It is my opinin. You can try. Thanks cheng

1 0

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

Sorry for the last e-mail I accidently pushed sent button.. The content of the bin folder doesn't contain 'isocreator' executable. And I am stuck in creating iso . I have tried to create iso with mkisofs but I could not succeed. Also I couldn't find dmon in the svn repos. Could you give the exact repo address for dmon so I can check it out. Best regards.. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Ronald Aigner <ra3(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Cc: Burak OGUZ <burakoguzs(a)yahoo.com> Sent: Friday, March 30, 2007 11:34:47 AM Subject: Re: hda : lost interrupt -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Burak, Burak OGUZ wrote on 29.03.2007 13:58 this: > My grub configuration does not contain -esc. ok. > How can I run my installed l4 over qemu? you could for instance create a bootable cd-rom image: 1. create a directory which will contain all the files of the iso-image. Lets call it iso 2. in the iso directory create a boot/grub directory 3. put the files you want to boot somewhere into the iso directory (preferably into boot/) 4. create the respective Grub entries in boot/grub/menu.lst (have a look at the demo-cd boot/grub/menu.lst for examples) 5. in the iso directory, call '$(L4DIR)/tool/bin/isocreator . image' 6. boot the image with 'qemu -serial stdio -cdrom image' You might want to check which VBE modes qemu supports. The option -serial stdio gives you the serial console in the terminal window where you started 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? As an alternative you can obtain the package dmon from our SVN repository (if you do not have it already). In the dmon directory is a README how to use it. Dmon basically opens a dope window and collects all debug logging information. This way you can see the log output even if you do not have a serial null modem cable and a second computer to debug. On the downside you will have to copy the debug information by hand (write it down, type it into your email program...). HTH, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGDMun2sAx3Dtx9+YRAgXhAJ9uXDdr0TFG6z9BuNqXA3CzxzK7cwCfTBZc ngqJj+W6aLgjGQ7q6xJorkw= =IBss -----END PGP SIGNATURE----- ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html

2 5

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

Jump to page:

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