l4-hackers January 1999

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

14 participants
30 discussions

gcc VS g++
by Paul Phillips 26 Jan '99

26 Jan '99

When I compile Fiasco with CC=gcc I get a message : KERNEL: no page fault handler for region: 0xffff0000, error 0x0. However, when I compile with CC=g++ I get no such message. Any ideas why this is happening?

1 0

Alrighty then...
by steven_weiss＠hotmail.com 21 Jan '99

21 Jan '99

--Looking to Go into business?-- Enjoy the Benefits of Working from Home! Build a Financial Future For You and Your Family! Learn How to Make Money with The Internet! --- The Money is NOT in the Technical End, it is IN the Marketing! Complete Training and Support! No Selling! Not an M.L.M or Network Marketing ! ------------------------------------------------------------------ --- Income Potential = $4,500 -$10,000 a month.* *(Based on Appox. 15-20 hrs every wk) ------------------------------------------------------------------ --- Requirements: 10-20 hrs a wk. 18 yrs or Older. Have or Apply for an In Home Business License. Be Ready to Learn--(this is NOT rocket science). (Click Reply) with Name, Address, Phone # and the Best Time to Reach You! Please give brief description of why you are looking for a business, How long you have been looking, What type of Business that you have run before (if any). How much computer experience do you have?

1 0

multiple servers
by Paul Phillips 21 Jan '99

21 Jan '99

I have successfully booted L4-Linux under Fiasco. There are problems, but I will work them out eventually. Thanks for a neat platform to work on. I plan to do lots of work on Fiasco and L4. Right now I'm trying to run two servers concurrently. This is just a "proof of concept" for now. I am trying to run the "hello" server (relocated to 0x2400000) along with the L4-Linux server. I load the "hello"server first and then L4-Linux. L4-linux gets to the "Calibrating delay loop.." and hangs. I am obviously forgetting something here. Is the printf used by the hello server causing a problem? BTW - I ran across the problem of the "relocation truncated ...." The problem is in the oskit/libsmp/x86/boot.S which contains the trampoline code. When the jump is made to the 32 bit code some linkers have a problem resolving the long jump. ljmp $KERNEL_CS,......... The fix is to put the ".code32" before the jump. This problem has been fixed in the latest release of the OSkit. Thanks in advance. Paul Phillips

1 0

Re: TCB size in ix86 L4
by Michael Hohmuth 17 Jan '99

17 Jan '99

"Adam 'WeirdArms' Wiggins" <awiggins(a)cse.unsw.edu.au> writes: > Is L4/Alpha suitable for real time (ie DROPS) or similar to > L4/ix86? I think it's more like L4/x86, but Sebastian would be the definitive source for this information. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: Fiasco Bug Tracking System
by Michael Hohmuth 17 Jan '99

17 Jan '99

Tom Linden <tom(a)kednos.com> writes: > Just curious why you chose jitterbug rather than, say, gnats. I am in > the process of setting up gnats and would be intyerested in your thoughts. > Certainly the interface is more modern. Which package's interface is more modern? I don't know any Gnats interface which is very ``modern.'' I chose Jitterbug because it's easy to set up and operate. It's interface is simplistic, but I like that. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Tyson vs Botha Wannna Bet!
by 5hbi＠yahoo.com 16 Jan '99

16 Jan '99

Feeling Lucky?? CASH IN ON thE FIGHT!!!! - http://209.67.19.99/want_to_bet/ TYSON V.s. BOTHA SATURDAY NIGHT JAN 16 9pm! REAL LIVE LAS VEGAS GAMBLING Place your bet online with up to the minute odds! Mike Tyson -750 Frans Botha +500 http://209.67.19.99/want_to_bet/ <a href="http://209.67.19.99/want_to_bet/index.html">CLICK HERE</a> to enter

1 0

Re: L4-Linux fails to boot - hangs setting up IDT
by Paul Phillips 16 Jan '99

16 Jan '99

Hi Jean, You were right, this was a problem encountered befor. The "magic" in the Makefile wasn't implemented because I did not have cpp in my path. I found a reference to the fix in an email to Sun-Mi Yu. I'm not home free yet, but I' closer. Thanks again! Paul Phillips -----Original Message----- From: Jean Wolter <jw5(a)os.inf.tu-dresden.de> To: Paul Phillips <pphillips(a)ivue.com> Cc: l4-hackers(a)os.inf.tu-dresden.de <l4-hackers(a)os.inf.tu-dresden.de> Date: Friday, January 15, 1999 4:53 AM Subject: Re: L4-Linux fails to boot - hangs setting up IDT >"Paul Phillips" <pphillips(a)ivue.com> writes: > >> 1.) Why are you calculating the address of the table by subtracting >> out EMULIB_CODE_ADDRESS (Which is 0xA0008000?) ? > >The emulation library is relocated to address 0xa0008000 and idt_table >is a symbol of the emulation library. If you have a look at the symbol >table you will find > >a00084a8 A idt_table > >So ((unsigned long)&idt_table - EMULIB_CODE_ADDRESS) is the offset of >the idt within our emulation library. > > >> 2.) How & why is the emulator code moved to "special page". Where is >> the "special page" set up since paging isn't set up until after this >> code is executed? > > >We have to copy the code to ensure that it is page aligned. The >special page is mapped into the address space of every unix process >when it raises its first page fault. Every unix process (L4Linux >process) starts at a fixed address, so we know, that the very first >page fault will request the emulation library page. > >> 3.) Any clue why this is hanging here? I should have a remote >> debugger set up soon, but I have -nokdb set and I don't get any >> kernel panics or reg dumps. The system just hangs. > >If my memory serves right, someone else had the same problem. For some >strange reason L4Linux raised a page fault at this point and the page >fault could not be resolved by the underlying pager. The L4Linux >server now hangs in an endless loop trying to resolve the page >fault. But I'm not sure about that. Michael? > >There is a possibility to monitor all page faults in the system, but I >don't know, how you activate that. > >Jean >-- >I get up each morning, gather my wits. >Pick up the paper, read the obits. >if I'm not there I know I'm not dead. >So I eat a good breakfast and go back to bed. Peete Seeger

1 0

Re: L4-Linux fails to boot - hangs setting up IDT
by Paul Phillips 15 Jan '99

15 Jan '99

Thanks for the input Jean. My symbol table shows: 00000000 A emulib_start 00000328 A user_level_pager 000003a0 A _user_task_init 00000478 A emulib_idt_descr 00000480 A idt_table 00000520 A emulib_debug_idt_descr 00000741 A emulib_end I am using gcc version 2.7.2.3 under Red Hat Linux 5.2. I am compiling the l4-981207 release of the L4-Linux code. Does this shed any light on the problem? Thanks again. Paul Phillips -----Original Message----- From: Jean Wolter <jw5(a)os.inf.tu-dresden.de> To: Paul Phillips <pphillips(a)ivue.com> Cc: l4-hackers(a)os.inf.tu-dresden.de <l4-hackers(a)os.inf.tu-dresden.de> Date: Friday, January 15, 1999 4:53 AM Subject: Re: L4-Linux fails to boot - hangs setting up IDT >"Paul Phillips" <pphillips(a)ivue.com> writes: > >> 1.) Why are you calculating the address of the table by subtracting >> out EMULIB_CODE_ADDRESS (Which is 0xA0008000?) ? > >The emulation library is relocated to address 0xa0008000 and idt_table >is a symbol of the emulation library. If you have a look at the symbol >table you will find > >a00084a8 A idt_table > >So ((unsigned long)&idt_table - EMULIB_CODE_ADDRESS) is the offset of >the idt within our emulation library. > > >> 2.) How & why is the emulator code moved to "special page". Where is >> the "special page" set up since paging isn't set up until after this >> code is executed? > > >We have to copy the code to ensure that it is page aligned. The >special page is mapped into the address space of every unix process >when it raises its first page fault. Every unix process (L4Linux >process) starts at a fixed address, so we know, that the very first >page fault will request the emulation library page. > >> 3.) Any clue why this is hanging here? I should have a remote >> debugger set up soon, but I have -nokdb set and I don't get any >> kernel panics or reg dumps. The system just hangs. > >If my memory serves right, someone else had the same problem. For some >strange reason L4Linux raised a page fault at this point and the page >fault could not be resolved by the underlying pager. The L4Linux >server now hangs in an endless loop trying to resolve the page >fault. But I'm not sure about that. Michael? > >There is a possibility to monitor all page faults in the system, but I >don't know, how you activate that. > >Jean >-- >I get up each morning, gather my wits. >Pick up the paper, read the obits. >if I'm not there I know I'm not dead. >So I eat a good breakfast and go back to bed. Peete Seeger

1 0

Re: L4-Linux fails to boot - hangs setting up IDT
by Jean Wolter 15 Jan '99

15 Jan '99

"Paul Phillips" <pphillips(a)ivue.com> writes: > 1.) Why are you calculating the address of the table by subtracting > out EMULIB_CODE_ADDRESS (Which is 0xA0008000?) ? The emulation library is relocated to address 0xa0008000 and idt_table is a symbol of the emulation library. If you have a look at the symbol table you will find a00084a8 A idt_table So ((unsigned long)&idt_table - EMULIB_CODE_ADDRESS) is the offset of the idt within our emulation library. > 2.) How & why is the emulator code moved to "special page". Where is > the "special page" set up since paging isn't set up until after this > code is executed? We have to copy the code to ensure that it is page aligned. The special page is mapped into the address space of every unix process when it raises its first page fault. Every unix process (L4Linux process) starts at a fixed address, so we know, that the very first page fault will request the emulation library page. > 3.) Any clue why this is hanging here? I should have a remote > debugger set up soon, but I have -nokdb set and I don't get any > kernel panics or reg dumps. The system just hangs. If my memory serves right, someone else had the same problem. For some strange reason L4Linux raised a page fault at this point and the page fault could not be resolved by the underlying pager. The L4Linux server now hangs in an endless loop trying to resolve the page fault. But I'm not sure about that. Michael? There is a possibility to monitor all page faults in the system, but I don't know, how you activate that. Jean -- I get up each morning, gather my wits. Pick up the paper, read the obits. if I'm not there I know I'm not dead. So I eat a good breakfast and go back to bed. Peete Seeger

1 0

Fiasco Bug Tracking System
by Michael Hohmuth 14 Jan '99

14 Jan '99

Hackers, I have set up a new bug tracking system for Fiasco; I hope you'll like it. I've already imported a few of your bug reports, but it's well possible that I've forgotten some. Please visit <URL:http://os.inf.tu-dresden.de/fiasco/bugs/> and tell me what you think. Use this page to report new (or old) bugs, or email your reports to <fiasco-bugs(a)os.inf.tu-dresden.de>, to make sure they won't get lost. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

2 1

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 January 1999