- l4-hackers - OS Site

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

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

14 Jan '99

I am trying to boot L4-Linux using the Fiasco microkernel. The microkernel boots fine, but when L4Linux is booting, in module chead.c you have the code: /* create idt */ { extern long idt_table; struct entry_t {unsigned short w0, w1,w2,w3;} ; struct entry_t *entries = (struct entry_t *)((unsigned long)emu_lib_text + ((unsigned long)&idt_table - EMULIB_CODE_ADDRESS)); unsigned short int tmp; int i; for (i=0; i<20; i++, entries++) { tmp = entries->w1; entries->w1 = entries->w3; entries->w3 = tmp; } } My system hangs when it attempts to execute this code. I understand why you are swapping the shorts in the table (swapping the offset bytes with the selector bytes) but there are a couple of things I don't understand Several questions: 1.) Why are you calculating the address of the table by subtracting out EMULIB_CODE_ADDRESS (Which is 0xA0008000?) ? 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? 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. Thanks in advance!! Paul Phillips

1 0

Re: TCB size in ix86 L4
by Torsten Paul 08 Jan '99

08 Jan '99

Michael Hohmuth <hohmuth(a)innocent.com> writes: > can't meet real-time requirements; the task_delete operation seems to > be especially bad, sometimes disabling interrupts for more than one > second. > Yes, the measurements showed interrupt a latency of sometimes 1.5 seconds (even if the interrupt thread had the highest priority) when in the L4-Linux System had to serve a lot of calls to fork/exec. This was tested with the lat_proc benchmark from the lmbench-suite that tries to measure the latency for creating simple processes (that only call exit) Still there is only one explanation for this: disabled interrupts while flushing the complete address space of a task when doing task_delete. ciao, Torsten. -- Torsten Paul Es ist leichter, einen Atomkern zu paul(a)os.inf.tu-dresden.de // spalten als ein Vorurteil. __________________________ooO_(+ +)_Ooo________Albert Einstein_(1879-1955) U

2 1

Re: next-gen mapping
by Michael Hohmuth 08 Jan '99

08 Jan '99

"Adam 'WeirdArms' Wiggins" <awiggins(a)cse.unsw.edu.au> writes: > Would an assembler based L4 benifit from this new mapping tree > data base too? It certainly sounds easier to handle memory for. I think that the binary-tree representation is easier to implement than the trees-in-fixed-size-arrays one. One factor which complicates the latter is that the fixed-size arrays have to be efficiently allocated, deallocated, and moved around in memory. Lukas' implementation includes a generic slab allocator for tree allocation. > I'm trying to work out my dynamic data structures now. So far i have > TCB's (512 bytes), 1st level page table entries 16K, 2nd level page > table entries 1K, mapping tree nodes ??? no idea yet. I got Lukas's > paper but i failed german in my high school years :( I'm trying to > get it translated. It there any code somewhere i can look at which > would illistraight it? Or does lukas have the time to give me an > english run down? I think Gernot is trying to translate the paper using Babelfish; Lukas has sent him his paper's sources. Other than that, I'm positive that we can help you understanding it. (If you're patient enough, you might even just wait until I've finished my technical report about Fiasco's design -- but don't hold your breath, please. :) Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

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

07 Jan '99

Adam, thanks for your replies! "Adam 'WeirdArms' Wiggins" <awiggins(a)cse.unsw.edu.au> writes: > Question here. Is Jochen's L4 got higher interupt latencies then > fiasco due to masking out interupts or is time in the kernel small enough > for real time applications. Our measurements with L4/x86 version 2 indicate that this kernel is not suitable for real-time work. The ``Taming Linux'' pager details some of these concerns <URL:http://os.inf.tu-dresden.de/papers_ps/part98.ps>. Recently, Torsten Paul did a series of measurements which show that L4/x86 often can't meet real-time requirements; the task_delete operation seems to be especially bad, sometimes disabling interrupts for more than one second. (Torsten, if you're reading this: Is this data correct?) Real-time requirements in our DROPS system are one reason why Fiasco tries to be interruptible at almost any time. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

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

06 Jan '99

[ As a courtesy to new readers: TCB = "thread control block", the kernel data structure holding thread-specific data including the thread's stack. ] "Adam 'WeirdArms' Wiggins" <awiggins(a)cse.unsw.edu.au> writes: > I was woundering why the TCB size in ix86 L4 is 1K, how much of > the stack at the end of the TCB is actually used? Very little: Most of the time, less than 150 bytes. > Could the TCB be reduced to 512K? If not why not? ^^^^ 512 bytes? I think it could. L4/x86 has disabled hardware interrupts most of the time, so the theoretical maximal stack usage probably isn't much higher than the one we see, maybe 100 bytes more. I guess Jochen didn't know it was so little when he designed L4, and never changed it later. In the Fiasco kernel, things are different: This kernel had been written in C++, and it may be interrupted at almost any time; handlers may interrupt each other and stack up on one thread's stack. That's why the theoretical maximal stack usage is much higher. Although I haven't computed it yet, I have estimated that a < 1K stack is too small for the current implementation. That's why Fiasco by default is configured to use 2-KByte TCBs. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

2 1

Re: ARM/L4
by Michael Hohmuth 06 Jan '99

06 Jan '99

"Adam 'WeirdArms' Wiggins" <awiggins(a)cse.unsw.edu.au> writes: > I've started work on writting an assembler (perhaps with some C) > version of L4 for ARM version 4 starting with the StrongARM SA-1100 (on > the Brutus evaluation platform and some custom hardware). > If anyone is interested in the port or has started their own and > has any advice or suggestion please contact me. > At release time it will be covered by the GPL. That's great! Are you doing this out of sheer fun, or do you have in mind a specific application? Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: next-gen mapping
by Michael Hohmuth 06 Jan '99

06 Jan '99

"Adam 'WeirdArms' Wiggins" <awiggins(a)cse.unsw.edu.au> writes: > Can anyone explain whats different/new about the planned > next-generation mapping tree for fiasco? I'd appreciate a detailed > explination if anyones got the time. The new thing about the new mapping database is that its data structures are much smaller. It uses compact linear arrays of fixed sizes, instead of elements linked in binary trees, to store the mapping trees for a given physical page frame. The size of the current mapping database implementations (in L4/x86 and Fiasco) can become a severe problem: To support a heavily-loaded L4Linux, one eighth of the main memory has to reserved for mappings. This also has performance implications, as our AIM multiuser benchmark measurements show: If we steal original (monolithic) Linux one eighth of its main memory, the application-level performance penalty between Linux and L4Linux decreases from 3.8 percent to 2 percent (on our hardware). Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: Some questions about Fiasco
by Michael Hohmuth 06 Jan '99

06 Jan '99

Benjamin Gerfelder <benjamin(a)dante.saar.de> writes: > I just succeeded in booting Linux on Fiasco. Just in case anyone > is interested, here are the warnings I got while booting: [ warning messages appended below for reference ] Congratulations for getting it up! All of the bootup warning messages are normal (and probably should be removed from the code base). > [...] I just get *a lot of* > > wake_idle_if_needed: ipc failed > > messages, but this seems to be no problem. We decided to not remove this L4Linux warning message in this release because we think it hints at a potential problem; at least we don't get this message under Jochen's L4/x86. I have to discuss this some more with my colleagues... > The only thing I`ve found that doesn`t work is XFree86, when I try > to start it, the machine freezes with blank screen. A remote debugger or a second (Hercules) video card would be of help here. One idea I have is that maybe we don't see these hangs because we let Fiasco send the "ipc failed" warning messages to the Hercules screen instead of the VGA console. Perhaps XFree86 crashes when someone else fiddles with the video memory? I'll try this out. > 1) Are there any documents you suggest reading, besides the L4 Reference > Manual? Any document would be of use, since I don`t have a clue on > L4, but I want to play around with it. Is there anything like > "L4 for dummies" ? :) UNSW has an L4 User's Guide which covers MIPS L4, but some people have said it's interesting from an x86 perspective, too; see <URL:http://www.cse.unsw.EDU.AU/~disy/L4/l4uman.ps.gz>. Other than that, I suggest you read some (depending on your interest) papers about L4 and L4Linux at <URL:http://os.inf.tu-dresden.de/pubs/#l4linux>. Unfortunately, something like an ``L4 for dummies'' doesn't exist. > 2) Is Fiasco capable of running multiple servers at once? Yes, this is possible. > I tried to start two instances of this helloworld-server, but it > crashed immediately. This doesn't work because Rmgr, the boot-up server and resource manager, is not a sophisticated memory manager. It can only run servers which want a one-to-one physical-to-virtual virtual-memory- space mapping. You example would work if the two instances of "hello" were linked to different virtual memory locations. As an example which works out of the box, try running "hello" and the L4Linux server parallelly. > 3) Is there a simple way to reboot the system after Fiasco startet? > My Laptop has no reset button :) No, there isn't, unless your program does it for you. For instance, L4Linux uses the keyboard controller method to reset the machine when it shutdowns; this arguably is not the ``correct'' solution to this problem. Does anyone have a good idea for an interface to reset the machine in the normal and exceptional cases? Greetings, Michael > ----------------------------------- > Welcome to Fiasco! > DD-L4/x86 microkernel (c) 1998 TU Dresden - Dec 24 1998 > linux_startup > checking OFFS_TSS: ok, OFFS_TSS still 536 > detect processorsetup_paging > end linux_startup, calling start_kernel > setup_arch > sigma0 denies mapping of address 00001000 > No kernel code/data > sigma0 denies mapping of address 00002000 > No kernel code/data > [...] > sigma0 denies mapping of address 00149000 > No kernel code/data > > mb4 already requested > > 4m page received > sigma0 denies mapping of address 00ccc000 > No kernel code/data > > Memory end: 00ccc000 > > kernel info page mappt to: 00001000 > root: rcvd 2, 424a25 > Hmm, strange, that shouldn't happen anymore > Root: null pointer deref in 5.3 at addr: 2 and eip: 424a25 (pte: 27) > ------------------------------------- -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

next-gen mapping
by Adam 'WeirdArms' Wiggins 05 Jan '99

05 Jan '99

Can anyone explain whats different/new about the planned next-generation mapping tree for fiasco? I'd appreciate a detailed explination if anyones got the time. Cheers Adam

1 0

Re: About external preempters
by Harald Fritzsche 03 Jan '99

03 Jan '99

Hello, it seems to me that external preempters are usefull for future use? So i have grabbed some information from the list and other sources. > [SH: S. Houidek]Hello, > > I have finished reading the L4/x86 reference manual, > and I have some questions about preempters : > > (1) What are the exact purposes of external and > internal preempters ? (See the L4 User manual from http://www.cse.unsw.edu.au/~disy/.) There exist (exclusivly?) only one internal preempter, wich is invoked after each timer interupt if the timesclice of running thread is expired or if it is called directly by kernel or user (l4_thread_switch or similar). This internal preempter is essential for the system itself. The scheduling is done by the thread_t::schedule() funtion in fiasco. External preempter: That is not a really preempter, its a user level scheduler. The preemption is done by the kernel described above. The External preempter is scheduled by the kernel if no task/thread with higher priority is ready. The intended purpose of an external preempter is to refine the kernels scheduling method with any user level method. There are 2 syscalls intended for use in external preempters, (i) l4_thread_switch and (ii) l4_thread_schedule. There are 5 variables, 1(3) syscall(s) and 1 ipc related to preemption/scheduling: (1) time_slice (2) priority (3) maximum controlled priority (4) external preempter (set by l4_thread_schedule, but not yet used?) (5) internal preempter (set by l4_ex_regs, but never used?) (6) l4_thread_switch (7) Preemption RPC (mentioned in the L4 Reference manual, but not implemented, see below) > (2) What differenciate them from scheduling tasks ? > > (3) What is the flow of control, from kernel to elected thread, > at time quantum exhaustion ? Needs to be defined? > (4) What is the role of the L4 internal scheduler, in the presence > of scheduling tasks ? [from another thread:] >> L4 or L4Linux does not use external preempters? >[JW]No, since there is currently no implementation of this concept. There >are some problems with clans&chiefs if you handle 'time slice faults' >(preemption) via ipc. I don't know whether fiasco will provide the >first implementation for external preempters, at least we are thinking >about it. An external preempter has to do at least 3 things: (1) user level scheduling, (2) waits on a kernel side IPC indicating time slice expiration, (3) communication with connected threads (i) inserting/deleting of threads in the user level queues (ii) additional support, time slice and priority changes, etc.. Is there a way to emulate the time slice expiration IPC? The following way may work: As noted in L4 User Manual the External Preempter runs with a higher priority than all other tasks which are scheduled by this external preempter. That means that the external preempter is always scheduled before any other task under control of this external preempter. So the external preempter is able to calculate the time consumed by a thread before the preempter calls l4_thread_switch to switch to the next task. This calculation can emulate the information given by a time slice expiration fault. Further questions are: Who is invoking an external preempter? (rmgr?) Where gets the preempter memory, needed by dynamical sized queues? Does the function ::new() work inside a L4 task, or what is to do to bring ::new() in operation? So far my questions. Regards and a happy new year Harald Fritzsche

2 1

For the Rest of Your Life, WE Will Remind You!
by Hal 31 Dec '98

31 Dec '98

Never Forget Again because THE LIFETIME REMINDER SERVICE will send you a postcard 1 week prior to every date you that want to be reminded of year after year for the rest of your life! ++++++++++++++++++++++++++++++++++++ Do you forget? Friends Birthdays? Anniversaries? When to change your oil? Your annual outdoor activities such as hunting, fishing, or camping trips? Any Important dates that you want to be reminded of? Or even reminders to do things like call your friend in Alaska once a year! ***************************************************** Purcahse your lifetime membership for a one time fee of $9.95 and we will snail mail your membership ID# and reminder form which is everything that you need to start receiving unlimited reminders in your mailbox. Yes, the number of occasions that we will remind you of each year is unlimited AND you can change your reminders at ANYTIME!! Order 24 hours a day, 7 days a week (800) 860 - 6821 ////////////////////////////////////////////////////// To be removed reply to mailto:prfct@eudoramail.com?subject=remove //////////////////////////////////////////////////////

1 0

TCB size in ix86 L4
by Adam 'WeirdArms' Wiggins 30 Dec '98

30 Dec '98

I was woundering why the TCB size in ix86 L4 is 1K, how much of the stack at the end of the TCB is actually used? Could the TCB be reduced to 512K? If not why not? Cheers Adam

1 1

Some questions about Fiasco
by Benjamin Gerfelder 27 Dec '98

27 Dec '98

Hi, I just succeeded in booting Linux on Fiasco. Just in case anyone is interested, here are the warnings I got while booting: (both packages are of 12/07/98, compiled under Linux) ----------------------------------- Welcome to Fiasco! DD-L4/x86 microkernel (c) 1998 TU Dresden - Dec 24 1998 linux_startup checking OFFS_TSS: ok, OFFS_TSS still 536 detect processorsetup_paging end linux_startup, calling start_kernel setup_arch sigma0 denies mapping of address 00001000 No kernel code/data sigma0 denies mapping of address 00002000 No kernel code/data [...] sigma0 denies mapping of address 00149000 No kernel code/data mb4 already requested 4m page received sigma0 denies mapping of address 00ccc000 No kernel code/data Memory end: 00ccc000 kernel info page mappt to: 00001000 root: rcvd 2, 424a25 Hmm, strange, that shouldn't happen anymore Root: null pointer deref in 5.3 at addr: 2 and eip: 424a25 (pte: 27) ------------------------------------- Then Linux tries to initialize the serial driver and stops because I logged this messages over serial cable. When I boot it without cable, everything works fine and stable, I just get *a lot of* wake_idle_if_needed: ipc failed messages, but this seems to be no problem. The only thing I`ve found that doesn`t work is XFree86, when I try to start it, the machine freezes with blank screen. Today I`ll try to get pcmcia running. Ok, now my questions :) 1) Are there any documents you suggest reading, besides the L4 Reference Manual? Any document would be of use, since I don`t have a clue on L4, but I want to play around with it. Is there anything like "L4 for dummies" ? :) 2) Is Fiasco capable of running multiple servers at once? I tried to start two instances of this helloworld-server, but it crashed immediately. 3) Is there a simple way to reboot the system after Fiasco startet? My Laptop has no reset button :) Ok, I`ve already stolen enough of your time, many thanks for being patient with me :) MfG Benjamin

2 1

re: Your Account info.
by zbwa＠mailcity.com 20 Dec '98

20 Dec '98

ADULTS ONLY! Looking for the hottest ADULT ACTION? Looking for the net's youngest women? <a href="http://209.67.19.98/girlsgirlsgirls1/index.html">CLICK HERE</a> to enter http://209.67.19.98/girlsgirlsgirls1/index.html Only $3.95 to Join ! Live Voyeur Feeds 1000's of Hot Young Teen Pix Updated every 2 weeks Live Sex Feeds with Chat 6 Live Teen Girl Strip Tease Feeds Live Nude Chat with Sound using Real Player Full Length Porno Movies with Sound in Vivo and Real Player Format Masturbation Video's of our hottest young models and there favorite vibrators. Bio's on all the girls Email all the models and tell them you fantasies and get a personal reply ! <a href="http://209.67.19.98/girlsgirlsgirls1/index.html">CLICK HERE</a> to enter http://209.67.19.98/girlsgirlsgirls1/index.html

1 0

Between our..
by Pete 12 Dec '98

12 Dec '98

NO TRICKS - IT'S FREE! Process all major credit cards on your web site. NO MONTHLY COSTS, NO TRANSACTION FEES. CHECK IT OUT. You get: - Virtual Terminal for phone/fax/mail orders - Email receipt - Recurring billing feature - Password generation for membership sites - Automatic batch closing - Address Verification Service (AVS) - Backoffice to access account history - Remote mode - Interface for all major shopping carts - Installation included For our free information package just reply to: mailto:ccard1@eastmail.com?subject=more_info If you are interested in becoming an authorized agent please reply to: mailto:ccard1@eastmail.com?subject=agent If you wish to be removed from our mailing list please reply to: mailto:gran6@edmail.com?subject=remove

1 0

Re: L4-Linux 0.5.1 failed to boot...
by Michael Hohmuth 12 Dec '98

12 Dec '98

OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> writes: > I tried new snapshot, 0.5.1, but I couldn't boot it. After L4-Linux > bootstrap, it couldn't detect my NE2000-compatible card and it > couldn't accept input from keyboard. The "login: " prompt appeared, > but I could do nothing, because console and network didn't work. My > CPU is AMD K6, but I don't think it is the source. My system is based > on Slackware-3.5.0, and is it possible that it may influece L4-Linux? Did this work before? One thing which won't work is loading original Linux kernel modules into L4Linux. From Linux' perspective, L4Linux is a different architecture, and modules have to be recompiled for L4Linux. Did you try loading the NE2000 driver as an original Linux kernel module? In this case, I recommend you compile the driver into your L4Linux kernel (or as an L4Linux module). Michael PS: Next week I'll be on vacation, and I won't answer my email. I'll try to catch up afterwards, so please keep sending in bug reports. They're appreciated a lot! -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: some bugs
by Michael Hohmuth 11 Dec '98

11 Dec '98

Sed, thanks for your report! I'll to reproduce the problem when I return from my vacation in ten days. roux(a)ecoledoc.lip6.fr (Cedric ROUX) writes: [...] > When i run it under fiasco, it runs a little, then it blocks, so i press > ctrl+c, that nornmally should end up the program and give me back the > shell, but not, it just continues a little more, and stops again, and so on > until the end of the program. > Then i see a lot of "Aiee: scheduling in interrupt 00422ba (activ 10000)" > with sometimes a 0 in place of the 10000. This looks like a scheduling problem in Fiasco: An interrupt thread is still active while the Linux scheduling code is run. This should not happen because interrupt threads have a higher priority and never block. Interesting. [...] > Third, but it was before patch3, > i ran through my hd, making ls, cat, rm and so on, and at one time, > after a ls, and before the result being displayed, i receive this message > "page fault in signal handler". Maybe patch3 fixes that, huh ? Maybe yes, but I'm not sure. > And last, i normally have shift+page-up to see last lines, but it does > not works under fiasco (maybe kernel 2.0.21 doesn't handle it anyway). > Little problem, but problem. This doesn't work because hardware scrolling is disabled in L4Linux. We did this because L4Linux shares the console's video memory with Fiasco/L4 and potentially other L4 tasks. > I soon gonna be able to debug with a second machine, so my next reports > will be better. That's cool! Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

some bugs
by roux＠ecoledoc.lip6.fr 11 Dec '98

11 Dec '98

Hello FIASCO people, here are some more bugs (yes, it is possible :)). First of all, when you press shift+print-screen (or control+print-screen, don't remember what bugs), everything blocks with a message that i forgot to write or that i've lost (i am in exams, my brain becomes a little strange, i forget things). If one could tried it to see if it happens on others machines. Note: it was before i applied path3 and patch4, so maybe it solves the problem. It might be a sigfault in a cli section, but nothing is sure. Second, i could run koules with svgalib !! but, a program of mine don't work. If someone could try it to see if it's my machine or what ? available at : http://www.ecoledoc.lip6.fr/~roux/demo/lost.tar.gz and a binary is provided at : http://www.ecoledoc.lip6.fr/~roux/demo/lost If you could try it with a clean linux to see what should be the correct behavior, then try it with fiasco. It's just a poor animation with some sound (maybe sound is necessary for it to behave bad, don't know). When i run it under fiasco, it runs a little, then it blocks, so i press ctrl+c, that nornmally should end up the program and give me back the shell, but not, it just continues a little more, and stops again, and so on until the end of the program. Then i see a lot of "Aiee: scheduling in interrupt 00422ba (activ 10000)" with sometimes a 0 in place of the 10000. This works too with patch3, i don't have put patch4, but don't think it is relevent. And when i press Esc, it simply reboots. Third, but it was before patch3, i ran through my hd, making ls, cat, rm and so on, and at one time, after a ls, and before the result being displayed, i receive this message "page fault in signal handler". Maybe patch3 fixes that, huh ? And last, i normally have shift+page-up to see last lines, but it does not works under fiasco (maybe kernel 2.0.21 doesn't handle it anyway). Little problem, but problem. I soon gonna be able to debug with a second machine, so my next reports will be better. See you, Sed.

1 0

L4-Linux 0.5.1 failed to boot...
by OKUJI Yoshinori 11 Dec '98

11 Dec '98

Hello. I tried new snapshot, 0.5.1, but I couldn't boot it. After L4-Linux bootstrap, it couldn't detect my NE2000-compatible card and it couldn't accept input from keyboard. The "login: " prompt appeared, but I could do nothing, because console and network didn't work. My CPU is AMD K6, but I don't think it is the source. My system is based on Slackware-3.5.0, and is it possible that it may influece L4-Linux? Thanks, OKUJI ---------------------------------------------------------------------- ~o o~ OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> s ) http://duff.kuicr.kyoto-u.ac.jp/~okuji (check "okuji.asc" !)

1 0

Re: l4-linux booted ! [patch3]
by Michael Hohmuth 10 Dec '98

10 Dec '98

Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > i have tried the patch also. Thanks for trying it! > It seems, that l4linux-2.0.21 is more stable than before. > Also the module package seems to work (dummy.o ne.o and related). That means > in my case that these modules are autoloaded (ping works). But i haven´t a > real network. > > Occasianally the system does not reached the login, unfortunatly i have no > copy of the given message (probably rcv fault, during /sbin/init). If you get a message, it would be interesting to know what it says exactly. > Other times the reboot command causes a seg fault (null pointer > derefenrence) after the message "Send all processes kill sig" (This is > reported earlier). I haven't ever seen this. Do you get a register/stack dump from L4Linux? In this case it should be possible to find the location of the page fault (with System.map and disassembly output ("objdump -ld vmlinux")). Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: page size assertion
by Eiji Ota 09 Dec '98

09 Dec '98

Michael-san, > Please try the patch appended below. > > I still would like to know which program triggers this problem as I > have not been able to reproduce it. Even after applying it, the same trouble happened. As my trial, I commented out that assertion in space.cc and the system seemed to work at that time.... However, I missed the important point, which I didn't know until that time. I used i486 PC-note(old, old note PC) and I set -nopentium to rmgr, it worked... i486 doesn't support a large page, does it ? oh, I'm sorry that you worry about a funny thing and I appreciate your advice because I thought you forgot this. Regards, Eiji Ota PS. Another funny thing. After removing the assertion, it worked even on i486. It might happen to work at that time...

1 0

New Fiasco snapshot
by Michael Hohmuth 07 Dec '98

07 Dec '98

I have released a new Fiasco snapshot (0.5.1, dated 981207) which has integrated all patches which have been posted to this mailing list. New snapshots of the support stuff also have been uploaded, including a new grub-ext2fs-floppy.gz (which doesn't any longer contain a confusing menu.lst file, and which is capable of loading gzip'd files and uncompressing them on the fly). I have changed the directory naming scheme in the tar files: They now all unpack into a directory called "l4", and not any longer "l4-<date>". This should make it easier to update only a part of the whole distribution in the future. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: l4-linux booted !
by Michael Hohmuth 06 Dec '98

06 Dec '98

roux(a)ecoledoc.lip6.fr (Cedric ROUX) writes: > Then, another time, the boot process blocks with this time the message : > ipc.cc:169 : failed assertion `! in_sender_list()' Attached below are some Fiasco patches which should help. This problem was a symptom of a familiar problem: Code which disables interrupts to protect a critical region trapped into a page fault which subsequently enabled interrupts again. We now protect against this problem by pre-installing all pages required for the operation in a safe way before the actual critical region starts. Ugly synchronization problems like this have been one of the main reasons to try to get rid of disabling interrupts altogether. However, the occasional "cli" instruction is still lurking in the code, waiting to be replaced with better mechanisms (like non-blocking synchronization). The patch also includes a fix which enhances compatibility with Jochen's L4 so that L4Linux can handle segmentation faults better. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: page size assertion
by Michael Hohmuth 04 Dec '98

04 Dec '98

> Eiji Ota <age(a)yk.fujitsu.co.jp> writes: > > > > > > I'm interested in this fantastic work(of course, L4). When I tried to > > > > > feel it, I faced an assertion failed by assert(size == PAGE_SIZE) in > > > > > space.cc(178 line). > > > > > > > > > > The wrong page size seemed to be passed by fpage_map in ipc_map.cc as > > > > > a SUPERPAGE_SIZE, but I don't find the root cause for this trouble. I wrote: > I think I have a theory on what the problem in Fiasco is (more on that > below). However, it would still be useful to know what the system is > trying to do when the error occurs; this would help me to reproduce > and track down the problem. > > My theory is that we fail to test rigorously enough that a receiver > really has enough space in its virtual address space to take a > superpage mapping. I think we currently test that just 4K are > unmapped in the receiver (that is, no mapping exists for the target > virtual address); that's not enough. Please try the patch appended below. I still would like to know which program triggers this problem as I have not been able to reproduce it. Regards, Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

l4-linux booted !
by roux＠ecoledoc.lip6.fr 03 Dec '98

03 Dec '98

Hello FIASCO people, well, strange things happened. I used the same grub floppy than the one used for my first experiments (that both crashed), and it booted ! really strange... I tried to run X, it didn't work (my screen power off, surely because of bad values for the horizontal and vertical frequencies, but i am not sure. I'll keep on trying (especially basic modes, like standard vga, and so on). Then, in a next boot, i tried 'reboot' command and i receive a KDB: unexpected system call and all is blocked (i am still in single machine mode, the cables i need to be able to debug with my second machine are not here yet, and for Michael: no, my machines are not connected anywhere, so remote debug won't be possible). In another test, i tried 'shutdown -h 0', which worked. Didn't try 'reboot' again, will do it this afternoon. Then, another time, the boot process blocks with this time the message : ipc.cc:169 : failed assertion `! in_sender_list()' Another strange thing is that it too often check the hd, with a message i never had before : /dev/hda2 has gone too long without being checked, check forced. Really really strange. Now, little questions : with the rmgr configfile (that i finnaly understood, at first the "glinux" task was not used because rmgr matched it against the configfile, so i had to add a line "task", for it to match the good module), there is a field 'irq'. Isn't it possible to allow only l4-linux to use the mouse-irq, so we can have mouse ? For my future work, i absoulty need X to work and the mouse would be appreciated (but i can deal without it). Once again, by configuring things correctly in the rmgr configfile, wouldn't it be possible to run X ? seems that people (especially Michael) succeded in running X, how did you do !? sanx, Sed. PS : this is a repost, the first message doesn't seem to have arrived, does it ? (i'm sure all those lost mails are preparing something ugly...). Is your mail server running under fiasco ? :) Hope this one will come to destination... sanx to Michael for his kernel config.

1 0

Re: This is an absolute FIASCO !
by Michael Hohmuth 01 Dec '98

01 Dec '98

I wrote: > roux(a)ecoledoc.lip6.fr (Cedric ROUX) writes: > > > I have a second machine, so i could have tried the debugger, but > > some pieces are missing and i don't have a null-modem, but i'll > > try to solve that. > > It would be great if you could generate a backtrace or even a state > analysis for the thread whose stack space runs out. PS: I can also debug this via the Internet if your debug host is connected to it (and you would give me an account on it). Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: This is an absolute FIASCO !
by Michael Hohmuth 01 Dec '98

01 Dec '98

Hi Sed! roux(a)ecoledoc.lip6.fr (Cedric ROUX) writes: > linux boots, everything seems alright, then it loads the deamons, then > the keymap, then the login should be there, but it reboots. > That was the first try. > I tried it just after this boot. And i now have this : > It boots, then at a time (don't remember exactly when), it shows that : > thread.cc:304: failed assertion 't->kernel_sp==0 || reinterpret_cast<vm_offset_t>(t->kernel_op) > reinterpret_cast<vm_offset_t>(t)+sizeof(thread_t)+0x20' > then it's over, asking me to reboot or run the debugger. > > So my questions are : > - what does it mean ? This is a panic because a kernel invariant wasn't met. In this case, the kernel's thread switching code detected a stack overrun in the target thread. This may also have been the reason for the crash/reboot you've seen. Are you trying to run the X Window System at this point? If so, this is a know problem. You should boot into a runlevel which doesn't run X11 to try out Fiasco. > - is it a problem in my compiling of l4-linux ? (i disabled serial support) I don't think that your L4Linux server is at fault. > I have a second machine, so i could have tried the debugger, but some pieces > are missing and i don't have a null-modem, but i'll try to solve that. It would be great if you could generate a backtrace or even a state analysis for the thread whose stack space runs out. > Hope this is not an already known bug. No, it's not (unless you're running X11). > (if someone could send me his kernel configuration, you run make xconfig and > you save it and you send it to me, of course if it works !) My .config file is appended below. > (don't know if it had to be done, but it checked my hd, and during > this process i had a lot of 'wake_idle_if_needed : ipc failed') This message should be removed: It's just informational. (The reason it doesn't bug me as much as you is that I have redirected it to a second monitor (Hercules, using the "-hercules") option.) > PS : i have the idea to do a distributed memory managment for my > studies, do you think it's possible with fiasco ? Yes, I think it's possible, and I think this would be an interesting application for Fiasco. > and when you run under l4-linux, can you make process that directly > talk to fiasco ? Yes, that's both possible and easy to do. However, we would need to come up with some documentation, and it would help if long IPC messages were available (I'm in the process of implementing them right now) so that our local name server could be utilized. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

This is an absolute FIASCO !
by roux＠ecoledoc.lip6.fr 01 Dec '98

01 Dec '98

Hi FIASCO people, i was lost in the net, then i saw a little light up on my head... it was FIASCO ! so i decided to take a look at it (well, in fact, a friend of mine told me about it, but a little romance sounds nice, eh ?). So, first, the hello server works. Then, i tried the linux one. And nothing to do. I applied the two patches available. Here is what's going on : linux boots, everything seems alright, then it loads the deamons, then the keymap, then the login should be there, but it reboots. (don't know if it had to be done, but it checked my hd, and during this process i had a lot of 'wake_idle_if_needed : ipc failed') That was the first try. I tried it just after this boot. And i now have this : It boots, then at a time (don't remember exactly when), it shows that : thread.cc:304: failed assertion 't->kernel_sp==0 || reinterpret_cast<vm_offset_t>(t->kernel_op) > reinterpret_cast<vm_offset_t>(t)+sizeof(thread_t)+0x20' then it's over, asking me to reboot or run the debugger. So my questions are : - what does it mean ? - is it a problem in my compiling of l4-linux ? (i disabled serial support) (if someone could send me his kernel configuration, you run make xconfig and you save it and you send it to me, of course if it works !) I have a pentium 200 mmx 64MHz, a hd ide of 4Go with hda2 for linux and hda3 for swap (70Mo), there is a cd-rom (hdb). I have no scsi, if it can help. I have a second machine, so i could have tried the debugger, but some pieces are missing and i don't have a null-modem, but i'll try to solve that. Hope this is not an already known bug. I'll keep on trying, it was late yesterday, had no time to make more than two tests. PS : i have the idea to do a distributed memory managment for my studies, do you think it's possible with fiasco ? and when you run under l4-linux, can you make process that directly talk to fiasco ? Thank you, Sed.

1 0

Re: L4/Linux problem
by Michael Hohmuth 30 Nov '98

30 Nov '98

"Sun-Mi You" <smyou(a)postech.ac.kr> writes: > I've change Makefile and Linux was compiled sucessfully. > But, the problem still occurs at same point. > > Is there other suggestion? Hmm... Are you sure you re-built the emulib? If in doubt, please "make clean" and rebuild the whole kernel. Changing the Makefile and just doing a "make" in the top-level directory is not enough because the Makefiles are probably not included in the object dependencies. Sorry for being so overly accurate with this; I just want to make sure it's not that known problem. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: page size assertion
by Michael Hohmuth 30 Nov '98

30 Nov '98

Eiji Ota <age(a)yk.fujitsu.co.jp> writes: > > > > I'm interested in this fantastic work(of course, L4). When I tried to > > > > feel it, I faced an assertion failed by assert(size == PAGE_SIZE) in > > > > space.cc(178 line). > > > > > > > > The wrong page size seemed to be passed by fpage_map in ipc_map.cc as > > > > a SUPERPAGE_SIZE, but I don't find the root cause for this trouble. > > Hi, after I changed the 113-line in ipc_map.cc to the following, it > worked, though I don't know whether it was correct or not. > > if (size > snd_size // want to send less that a superpage? > | > V > if (size >= snd_size // want to send less that a superpage? This is not the correct fix, I'm afraid. What you do here is to effectively prohibiting the passing of superpage (4-MByte) mappings. I think I have a theory on what the problem in Fiasco is (more on that below). However, it would still be useful to know what the system is trying to do when the error occurs; this would help me to reproduce and track down the problem. My theory is that we fail to test rigorously enough that a receiver really has enough space in its virtual address space to take a superpage mapping. I think we currently test that just 4K are unmapped in the receiver (that is, no mapping exists for the target virtual address); that's not enough. I will try to verify this theory when I'm in the office later today. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: page size assertion
by Eiji Ota 30 Nov '98

30 Nov '98

> > > I'm interested in this fantastic work(of course, L4). When I tried to > > > feel it, I faced an assertion failed by assert(size == PAGE_SIZE) in > > > space.cc(178 line). > > > > > > The wrong page size seemed to be passed by fpage_map in ipc_map.cc as > > > a SUPERPAGE_SIZE, but I don't find the root cause for this trouble. Hi, after I changed the 113-line in ipc_map.cc to the following, it worked, though I don't know whether it was correct or not. if (size > snd_size // want to send less that a superpage? | V if (size >= snd_size // want to send less that a superpage? - Eiji

1 0

Re: L4/Linux problem
by Sun-Mi You 30 Nov '98

30 Nov '98

: :I think this is a problem one other user also experienced: The system :call IPC library (called ``emulation library'' for hysterical reasons) :in linux/arch/l4-i386/emulib/ has been linked to a wrong virtual :address because the magic in this directory's Makefile failed. One :possible reason is that you don't have a `cpp' in your $PATH. : :Does it help to replace "cpp" with "gcc -E" in this Makefile? : :Michael :-- I've change Makefile and Linux was compiled sucessfully. But, the problem still occurs at same point. Is there other suggestion?

1 0

ADV: LIVE Adult Paradise -- FREE !!
by Steve 29 Nov '98

29 Nov '98

------------------------------------------------------------- This message is sent in compliance of the new email bill section 301. Per Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you by the sender of this email may be stopped at no cost to you by emailing mailto:sgarner@tophosting.com Please type "Remove" in the subject line. Your request to be remove will be processed within 24 hours. Please DO NOT reply to this email if you wish to be removed. ------------------------------------------------------------- FREE Adult Offer -- Five FREE Minutes -- All LIVE NEED A LITTLE SPICE IN YOUR LIFE? All Your Desires Are Satisfied -- The Best LIVE CyberNet Models Do As You Please! ALL LIVE -- ALL DAY -- ALL NIGHT Seductive Women: http://204.248.170.151/196/index.html HardBody Hunks: http://204.248.170.151/215/index.html ** LIVE 1-on-1 Shows! ** MALE or FEMALE! ** 5 FREE MINUTES of HOT ADULT LIVE ACTION! ** SATISFACTION GUARANTEED! All our shows are 100% LIVE and INTERACTIVE for your enjoyment! Ask And You Shall Receive SEDUTIVE WOMEN That Do It ALL! http://204.248.170.151/196/index.html -- OR -- HARDBODY HUNKS Give You What You Ask! http://204.248.170.151/215/index.html <a href="http://204.248.170.151/196/index.html">AOL Users Click Here!</a> See for yourself - We'll give you 5 FREE Steamy Minutes -- Satisfaction Guaranteed!

1 0

Re: page size assertion
by Eiji Ota 28 Nov '98

28 Nov '98

> > I'm interested in this fantastic work(of course, L4). When I tried to > > feel it, I faced an assertion failed by assert(size == PAGE_SIZE) in > > space.cc(178 line). > > > > The wrong page size seemed to be passed by fpage_map in ipc_map.cc as > > a SUPERPAGE_SIZE, but I don't find the root cause for this trouble. > > > > Any ideas ? > > If you can attach a remote GDB via a serial line, you can generate a > backtrace. I'm not familiar with this analysis, anyway, I'll try this, however, I'm happy if you tell me how-to at this point if possible. > This might be a bug either in Fiasco or in an application (in which > case the code in v_insert() must be made more robust; that is, it must > return an error instead of panicking the kernel). > > What are you doing when the assertion fails? Booting? Starting X11? It was booting. I'll dig this out later as far as I can. - Eiji

1 0

Re: page size assertion
by Michael Hohmuth 28 Nov '98

28 Nov '98

Eiji Ota <age(a)yk.fujitsu.co.jp> writes: > I'm interested in this fantastic work(of course, L4). When I tried to > feel it, I faced an assertion failed by assert(size == PAGE_SIZE) in > space.cc(178 line). > > The wrong page size seemed to be passed by fpage_map in ipc_map.cc as > a SUPERPAGE_SIZE, but I don't find the root cause for this trouble. > > Any ideas ? If you can attach a remote GDB via a serial line, you can generate a backtrace. This might be a bug either in Fiasco or in an application (in which case the code in v_insert() must be made more robust; that is, it must return an error instead of panicking the kernel). What are you doing when the assertion fails? Booting? Starting X11? Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

page size assertion
by Eiji Ota 27 Nov '98

27 Nov '98

Hi all, I'm interested in this fantastic work(of course, L4). When I tried to feel it, I faced an assertion failed by assert(size == PAGE_SIZE) in space.cc(178 line). The wrong page size seemed to be passed by fpage_map in ipc_map.cc as a SUPERPAGE_SIZE, but I don't find the root cause for this trouble. Any ideas ? - Eiji Ota

1 0

Re: L4-Linux
by Michael Hohmuth 27 Nov '98

27 Nov '98

Harald Fritzsche <harald.fritzsche(a)mpd.de> writes: > i have applied Michaels patch and fortunatly the message > <KERNEL: no page fault handler ...> > does never occur. > > L4Linux boots now. > > Thanks so far and congratulation for such a system (Linux on Fiasco). Congratulations for getting it running, and thanks for going through all the hassles! > startx or something else (xdm,kdm,X,...) scrambles the screen and blocks the > keyboard. I assume that this is causes by the disabled serial interface and > related IRQ's (i have configured out serial interface)? It might as well be a bug in Fiasco. So far, we also haven't been very successful in getting up X11 (I think I've seen it running once or twice, but it must have been a lucky day). Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: L4/Linux problem
by Michael Hohmuth 27 Nov '98

27 Nov '98

"Sun-Mi You" <smyou(a)postech.ac.kr> writes: > Our L4/Linux was hanged at follow code. > > in 'linux/arch/l4-i386/chead.c ' > > /* create idt */ > { > extern long idt_table; > struct entry_t {unsigned short w0, w1,w2,w3;} ; > struct entry_t *entries = > (struct entry_t *)((unsigned long)emu_lib_text + > ((unsigned long)&idt_table - EMULIB_CODE_ADDRESS)); > unsigned short int tmp; > int i; > > => this point! > > for (i=0; i<20; i++, entries++) > { > tmp = entries->w1; > entries->w1 = entries->w3; > entries->w3 = tmp; > } > > What problem is this? > > ( I think it may be some memory problem. ) I think this is a problem one other user also experienced: The system call IPC library (called ``emulation library'' for hysterical reasons) in linux/arch/l4-i386/emulib/ has been linked to a wrong virtual address because the magic in this directory's Makefile failed. One possible reason is that you don't have a `cpp' in your $PATH. Does it help to replace "cpp" with "gcc -E" in this Makefile? Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

L4/Linux problem
by Sun-Mi You 25 Nov '98

25 Nov '98

Our L4/Linux was hanged at follow code. in 'linux/arch/l4-i386/chead.c ' /* create idt */ { extern long idt_table; struct entry_t {unsigned short w0, w1,w2,w3;} ; struct entry_t *entries = (struct entry_t *)((unsigned long)emu_lib_text + ((unsigned long)&idt_table - EMULIB_CODE_ADDRESS)); unsigned short int tmp; int i; => this point! for (i=0; i<20; i++, entries++) { tmp = entries->w1; entries->w1 = entries->w3; entries->w3 = tmp; } What problem is this? ( I think it may be some memory problem. ) Additionaly, our test platform is pentium/64Mb memory. Thanks in advance. :) ---------------------------------------------------------- Sun-Mi You (smyou(a)postech.ac.kr) System Software Laboratory Dept. of Computer Science and Engineering POSTECH, Pohang, KOREA Phone: +82-562-279-5668 http://sslab.postech.ac.kr/~woodstok ----------------------------------------------------------

1 0

Re: L4-Linux
by Michael Hohmuth 25 Nov '98

25 Nov '98

Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > I found (i hope so) the reason for the kbd: sig_sched: invalid > ext_preempter in > L4-Linux, reported earlier. > > In file : > linux/arch/l4-i386/lib/task.c > in function: > start_linux_server_thread() > is used the variable > l4_threadid_t foo_id > uninitialized. > I set foo_id to L4_INVALID_ID and the sig_sched disappears. But i don't > if this is intended from the authors. Your fix is correct. The problem occurred because I forgot to commit some patches before taking the snapshot. I've appended the patches (which include your fix) below. [ from a different message: ] > The function rs_init() hangs during boot (the boot stops for ever). Or a > function after this part of initialization. The last what i see is: > tty0* ... is a 16550A. > > If i disable the serial interface the boot goes on up to VFS mount and stops > than. This might be because the kernel debugger stub grabs irq 3 (the interrupt for COM2). Maybe Linux' serial driver waits for an interrupt that never arrives because L4Linux cannot attach to irq3. Configuring out the serial driver is the correct solution when using a remote Gdb attached via a serial line. If you don't have a remote Gdb, try booting with the "-nokdb" kernel option and see if the problem goes away. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: Error while booting fiasco
by Michael Hohmuth 23 Nov '98

23 Nov '98

Ludger Martin <lumartin(a)vlsi.informatik.tu-darmstadt.de> writes: > I tryed to build a fiasco boot disk. I followed the instruction on the > WWW-page > http://os.inf.tu-dresden.de/fiasco/use.html > and every thing was fine. So I tryed to boot fiasco but i got the > folowing error: > KERNEL: no page fault handler for region: 0xfffffffc, error 0x2 You forgot to load a sigma0 server (or forgot to specify the "-sigma0" command line option). Please use a menu.lst containing the example configuration from the web page you cite. (The configuration on the web page had a bug for a few days which resulted in the problem you observed -- maybe you've picked up an old cached copy of it?) Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

Re: L4-Linux
by Michael Hohmuth 23 Nov '98

23 Nov '98

Robert Kaiser <rob(a)sysgo.de> writes: > On Fri, 6 Nov 1998, OKUJI Yoshinori wrote: > > kernel info page mappt to: 00001000KDB: sig_sched: invalid ext_preempter > Same here. I'm not sure if I got the menu.lst and rmgr.cfg right. > > Would someone who has a working setup (there's got to be someone > who has, right ?) please kindly post his menu.lst and rmgr.cfg to > this forum ? You don't need a rmgr.cfg, and your menu.lst should contain something like: title= Fiasco + Linux kernel= (fd0)/hohmuth/rmgr -sigma0 module= (fd0)/hohmuth/main -nowait module= (fd0)/hohmuth/sigma0 module= (fd0)/hohmuth/glinux.gz That is equivalent to the configuration used to boot the "hello world" server, just that we load "glinux.gz" instead of "hello". Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Re: modname glinux doesn't match...
by Michael Hohmuth 23 Nov '98

23 Nov '98

Erik Oliver Bla� <erik(a)ifib.uni-karlsruhe.de> writes: > Booting Fiasco+Linux I get the following error message: > > Error: modname glinux doesn't match cmdline (hd0,0)/boot/grub/rmgr.cfg > > although rmgr.cfg is Dresdens original version. You don't really need to use the rmgr.cfg you find on the boot floppy (the example on <URL:http://os.inf.tu-dresden.de/fiasco/use.html#boot> doesn't use it). If you want to use a custom Rmgr configuration (rmgr.cfg): - Add the "-configfile" option to the "rmgr" command line <URL:http://os.inf.tu-dresden.de/L4/l4libman/rmgr.html>. - Don't forget that you also need to load the Sigma0 server (the old menu.lst file on the floppy image doesn't load it). If forget this, you get a page fault at 0xfffffffc (because the stack pointer for the [non-loaded] Sigma0 server is initialized to 0). Also don't forget the "-sigma0" command line option for "rmgr". - There might be a buglet in Rmgr which results in the error message you quote. You can work around this by removing (or commenting out) the "modname <something>" directives from rmgr.cfg. I haven't yet had time to try to reproduce and fix this, but this is still in the queue. > After that the Linux kernel seems to load anyway, but stops at the error > reported from Harald. > > Why ? Please try the patches I posted a few minutes ago. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Re: Fiasco compile problems on 486
by Michael Hohmuth 23 Nov '98

23 Nov '98

I'm crossposting this to the OSKit mailing list because this is an OSKit question. "James Gibson" <jgibson62(a)hotmail.com> writes: > I've been trying to build Fiasco on a 486 (running Linux 2.0.35 and egcs > 1.1). The OS kit build fails with this message: > make[2]: Entering directory `/usr/src/l4-981012/oskit/examples' > ld -Ttext 100000 -L../lib \ > -o multiboot ../lib/multiboot.o multiboot.o \ > -lkern -lmc -llmm ../lib/crtn.o > ld -Ttext 100000 -L../lib \ > -o multiboot-gdb ../lib/multiboot.o multiboot-gdb.o \ > -lkern -lmc -llmm ../lib/crtn.o > ld -Ttext 100000 -L../lib \ > -o multiboot-smp ../lib/multiboot.o multiboot-smp.o \ > -lsmp -lkern -lmc -llmm ../lib/crtn.o > ../lib/libsmp.a(boot.o): In function `_SMP_TRAMP_START_': > boot.o(.text+0x29): relocation truncated to fit: R_386_16 > _SMP_TRAMP_32_ENTRY_ > make[2]: *** [multiboot-smp] Error 1 > > Question: Since I don't need SMP, would it be possible (and if so, would > it be worthwhile) to disable SMP support? (This is an FAQ -- check out <URL:http://os.inf.tu-dresden.de/fiasco/faq.html>.) I cannot reproduce this problem. However, as this binary isn't needed, you can work around this problem by "touch oskit/examples/multiboot-smp". My guess is that this problem is caused by some combination of compiler and linker versions. Can anyone shed some light on this? Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: L4Linux booting (KERNEL:no page fault handler)
by Michael Hohmuth 23 Nov '98

23 Nov '98

Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > Hello Hackers, > > as stated earlier my L4Linux boots up to VFS - mount. > > Than the execution of /sbin/init (linux/init/main.c) leads to > > wake_up_process: ipc_failed (7 or 8 times) That's sort of normal -- we probably should remove this message from L4Linux. > and finally to > KERNEL: no page fault handler for region: 0xeab2f800, error 0x0 This probably is a kernel bug. Fiasco does a read at an invalid virtual address. If you boot with the "-nokdb" kernel option, you should be able to get a register dump even even if you don't have connected a remote Gdb. This, together with the output of "nm main | sort", could give you a hint about the reason of the crash. > This error seems to be caused by /sbin/init > > I am using Linux SuSe 5.3 with init v 2.65 f (i hope it is correct). > Which init do TUD prefer? I don't think the version of `init' makes a difference here. However, I will send you the version details soon. Right now I can't check because my test machine is busy this week doing benchmarks... :-( Is anyone willing to donate another test machine? Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

1 0

mirror in Japan
by OKUJI Yoshinori 23 Nov '98

23 Nov '98

Hello. I manage a mirror site at duff.kuicr.kyoto-u.ac.jp, and for some reasons, the directory has been changed to /mirrors/L4 from /pub/L4. Please update the Fiasco page. Thanks, OKUJI ---------------------------------------------------------------------- ~o o~ OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> s ) http://duff.kuicr.kyoto-u.ac.jp/~okuji (check "okuji.asc" !)

1 0

L4Linux booting (KERNEL:no page fault handler)
by Harald Fritzsche 22 Nov '98

22 Nov '98

Hello Hackers, as stated earlier my L4Linux boots up to VFS - mount. Than the execution of /sbin/init (linux/init/main.c) leads to wake_up_process: ipc_failed (7 or 8 times) and finally to KERNEL: no page fault handler for region: 0xeab2f800, error 0x0 This error seems to be caused by /sbin/init I am using Linux SuSe 5.3 with init v 2.65 f (i hope it is correct). Which init do TUD prefer? Remark: I have skipped the rs_init function because this function hangs up the bootstrap also. Regards Harald Fritzsche

1 0

Fiasco compile problems on 486
by James Gibson 20 Nov '98

20 Nov '98

I've been trying to build Fiasco on a 486 (running Linux 2.0.35 and egcs 1.1). The OS kit build fails with this message: make[2]: Entering directory `/usr/src/l4-981012/oskit/examples' ld -Ttext 100000 -L../lib \ -o multiboot ../lib/multiboot.o multiboot.o \ -lkern -lmc -llmm ../lib/crtn.o ld -Ttext 100000 -L../lib \ -o multiboot-gdb ../lib/multiboot.o multiboot-gdb.o \ -lkern -lmc -llmm ../lib/crtn.o ld -Ttext 100000 -L../lib \ -o multiboot-smp ../lib/multiboot.o multiboot-smp.o \ -lsmp -lkern -lmc -llmm ../lib/crtn.o ../lib/libsmp.a(boot.o): In function `_SMP_TRAMP_START_': boot.o(.text+0x29): relocation truncated to fit: R_386_16 _SMP_TRAMP_32_ENTRY_ make[2]: *** [multiboot-smp] Error 1 Question: Since I don't need SMP, would it be possible (and if so, would it be worthwhile) to disable SMP support? James ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

1 0

modname glinux doesn't match...
by Erik Oliver Blaß 17 Nov '98

17 Nov '98

Hi ! Booting Fiasco+Linux I get the following error message: Error: modname glinux doesn't match cmdline (hd0,0)/boot/grub/rmgr.cfg although rmgr.cfg is Dresdens original version. After that the Linux kernel seems to load anyway, but stops at the error reported from Harald. Why ? Erik

1 0

Re: L4-Linux
by Jean Wolter 16 Nov '98

16 Nov '98

Harald Fritzsche <harald.fritzsche(a)mpd.de> writes: > > Hello, > > Jean Wolter schrieb: > > > Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > > > > Thanks for reporting this. Since L4/Intel never used the value of > > 'external preempter' we (at least I) have not seen this 'error'. > > > > L4 or L4Linux does not use external preempters? No, since there is currently no implementation of this concept. There are some problems with clans&chiefs if you handle 'time slice faults' (preemption) via ipc. I don't know whether fiasco will provide the first implementation for external preempters, at least we are thinking about it. > That is that what i see: Hmm, strange, ...It seems that i was > misunderstanding this. Actually there some more misleading debug messages (for instance 'sigma0 denies mapping of ...') which have to be cleaned up some day :) 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
by Jean Wolter 16 Nov '98

16 Nov '98

Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > > Hallo Hackers, > > I found (i hope so) the reason for the kbd: sig_sched: invalid > ext_preempter in > L4-Linux, reported earlier. > > In file : > linux/arch/l4-i386/lib/task.c > in function: > start_linux_server_thread() > is used the variable > l4_threadid_t foo_id > uninitialized. > I set foo_id to L4_INVALID_ID and the sig_sched disappears. But i don't > if this is intended from the authors. Thanks for reporting this. Since L4/Intel never used the value of 'external preempter' we (at least I) have not seen this 'error'. > Also the null-pointer test gives an error message. Could you provide some more details? If everything works correctly you should see a complained from the root pager (something like 'Hmm, strange, that shouldn't happen anymore' on a hercules monitor) and a message from the linux server 'mem_init: null pointer dereference detection seems to work'. If you see 'mem_init: null pointer check failed' then something is wrong and the zero page was not flushed correctly. That's something Michael should be interested in. 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

2 1

RE: L4-Linux
by Harald Fritzsche 15 Nov '98

15 Nov '98

Hallo Hackers, I found (i hope so) the reason for the kbd: sig_sched: invalid ext_preempter in L4-Linux, reported earlier. In file : linux/arch/l4-i386/lib/task.c in function: start_linux_server_thread() is used the variable l4_threadid_t foo_id uninitialized. I set foo_id to L4_INVALID_ID and the sig_sched disappears. But i don't if this is intended from the authors. L4Linux boots now up to tty-init and hangs than. Also the null-pointer test gives an error message. Regards Harald Fritzsche

1 0

L4 Alpha available now in PRE-BETA version
by Sebastian Schoenberg 12 Nov '98

12 Nov '98

See http://os.inf.tu-dresden.de/~schoenbg/alpha. Unfortunately, we cannot distribute all required tools, since they need to be purchased from Digtial Equipment (Compaq). Please contact me, if you've problems. Everyone is welcome to contribute and add the missing parts !!!!!!! Sebastian

3 2

Cost Effective Advertising Stategies
by Sam 11 Nov '98

11 Nov '98

GET INSTANT RESULTS TODAY! Through extensive online marketing research, we have found that e-mail marketing is the key to a successful website or small business. Our company has over 3 years experience marketing online. We develope our own bulk email software and use the most highly targeted lists. Call today and find out how you can advertise your small business and get immediate results without paying a fortune. Prices start at: $150 for 100,000 emails $300 for 500,000 emails $450 for 1,000,000 emails ASK ABOUT OUR START-UP PACKAGE WHICH INCLUDES A 50,000 MASS MAILINGS ALONG WITH A LIST MANAGER. YOU CAN SORT, FILTER, AN REMOVE DUPLICATES WITH THIS NEAT LITTLE PROGRAM. THIS WHOLE PACKAGE IS ONLY $79.95!! CALL TODAY AT 401-433-5811

1 0

L4-Linux
by OKUJI Yoshinori 10 Nov '98

10 Nov '98

Hello. I've tried to boot L4-Linux for a while, but I cannot boot it with too many error printings. For example, sigma0 denies mapping of address 02666000 No kernel code/data or, kernel info page mappt to: 00001000KDB: sig_sched: invalid ext_preempter My menu.lst is: ---------------------------------------------------------------------- title= Resource Manager + Linux root= (hd0,0) kernel= /l4/rmgr -sigma0 -configfile module= /l4/main -nowait module= /l4/sigma0 module= /l4/rmgr.cfg module= /l4/glinux.gz root=/dev/hda1 ---------------------------------------------------------------------- and my rmgr.cfg is: ---------------------------------------------------------------------- #!rmgr ### this is an example RMGR config file ### first, some global settings # small address spaces have a size of 64 MB small_space_size 0x04000000 # wait for key press after initialization bootwait ### configuration for Sigma0 and RMGR follows # NOTE: it's generally useless to specify any resource allocation # constraints for Sigma0 and RMGR here: most will be ignored because # these tasks statically allocate all of their resources. That's why # we only specify bootstrap parameters here. task sigma0 boot_priority 100 task rmgr boot_priority 100 # enable next line if you want RMGR to run in small address space # 3 #boot_small 3 # XXX: configuration file itself is needed. task modname "cfg" ### configuration for boot modules follows task modname "glinux" # make sure this entry # corresponds to a Linux server boot_small 2 # small address space # 2 boot_priority 100 boot_mcp 0x90 # maximum controlled priority log_mcp 0x90 # logical maximum controlled priority # -- useful if "boot_mcp 0" child max 512 in [10, 1023] # at most 512 child tasks in that range memory in [0, 0x02000000] # use only lower 32 MB RAM high_memory in [0xc0000000, 0xffffffff] # use only hi memory in that range small in [1,3] # allow these small address # spaces to be allocated # enable next line if you want to disallow allocation if IRQs 3 and 4 # (IRQs for serial lines COM2 and COM1) #irq mask 0xffffffe7 end ---------------------------------------------------------------------- Any suggestions? Thanks, OKUJI ---------------------------------------------------------------------- ~o o~ OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> s ) http://duff.kuicr.kyoto-u.ac.jp/~okuji (check "okuji.asc" !)

3 2

Magazines for low prices!
by magazines 10 Nov '98

10 Nov '98

MAGAZINE SUBSCRIPTIONS AT $4.95 for one full year, PC COMPUTING, FAMILY CIRCLE, ELLE, POPULAR SCIENCE, WIRED, FITNESS, PENTHOUSE and hundreds of others to choose from at a DEEP DEEP DISCOUNT. COMPARE OUR PRICES, great holiday gifts. There are no shipping or other fees to USA zip codes. FOR INFORMATION mailto:zines701@planetall.com?subject=info To be removed from future mailings, please send an email to mailto:jolsy9432@usa.netXKEdKELD

1 0

Error while booting fiasco
by Ludger Martin 02 Nov '98

02 Nov '98

Hi, I tryed to build a fiasco boot disk. I followed the instruction on the WWW-page http://os.inf.tu-dresden.de/fiasco/use.html and every thing was fine. So I tryed to boot fiasco but i got the folowing error: KERNEL: no page fault handler for region: 0xfffffffc, error 0x2 Doas anyone havs an idee? Thanks Ludger Martin PS: I working on a P133, 64MB Ram, Adaptec 2940U, Matrox Milenium, 3c905 -- Ludger Martin e-mail: lumartin(a)vlsi.informatik.tu-darmstadt.de

1 0

Hey! look what I found
by battman76＠writeme.com 31 Oct '98

31 Oct '98

Hi, Great stuff @ http://195.64.77.20/gator/ ******************************************************************************* Please reply with subject "remove to be removed" *******************************************************************************

1 0

Re: Fehler beim Booten von Fiasco
by Michael Hohmuth 27 Oct '98

27 Oct '98

Konrad Neitzel <neitzel(a)neitzel.de> writes: > >l4-hackers is an international mailing list; the discussion language > >is English. If you need to discuss something in German, please > >contact <fiasco-core(a)os.inf.tu-dresden.de>. > What is the difference between the two mailling-lists? l4-hackers is a public mailing list while fiasco-core is a private mailing list for the members of the current Fiasco core group. > >Also, I guess I now have to set up a mailing list archive -- the > >issues you raised have popped up several times now. > Maybe add it to the FAQ on the web! I think, that i didn't found it there. Thanks for this suggestion -- I've updated the FAQ. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

None
by bohemia＠compuserve.com 26 Oct '98

26 Oct '98

10/25/98 Y2K Solution! 8 Pine Circle Dr., Silicon Valley, Calif. OTC Company "TCFG" 21 st. Century Frontier Group has through several members of their administrative research department leaked vital information about their companies efforts... Everyone was tight lipped and interviews were refused, and through un-named sources we have learned that the technology and software solution are in the process of being patented! In over 1640 trials, using various data systems the use of the new technology and software solved the Y2K problem 100% of the time. This small publicly traded company "TCFG" which is just 3 years old is through various sources now negotiating with the "Big Boys"! "TCFG" the letters to look for..... ________________________________________________________________

1 0

New mailing list archive; new FAQ entries
by Michael Hohmuth 24 Oct '98

24 Oct '98

An archive for this mailing list is now available at <URL:http://www.mail-archive.com/l4-hackers@os.inf.tu-dresden.de/>. Also, the Fiasco FAQ has been updated with some entries addressing common problems people have had building and using Fiasco: <URL:http://os.inf.tu-dresden.de/fiasco/faq.html#problems>. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Re: Compilations- und Bootproblem mit Fiasco/L4
by Michael Hohmuth 23 Oct '98

23 Oct '98

Harald Fritzsche <harald.fritzsche(a)mpd.de> writes: > now it works. Cool! > Is Fiasco the very first C++ Kernel? I remember me, that Siemens > Nixdorf has canceld a plan to develop BS2000 (V13) with C++. No, Fiasco is not the first kernel written in C++. I can think offhand of at least two other kernel projects using C++: Chorus and Off++. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: Fehler beim Booten von Fiasco
by Michael Hohmuth 23 Oct '98

23 Oct '98

Hi Konrad, l4-hackers is an international mailing list; the discussion language is English. If you need to discuss something in German, please contact <fiasco-core(a)os.inf.tu-dresden.de>. Also, I guess I now have to set up a mailing list archive -- the issues you raised have popped up several times now. Konrad Neitzel <neitzel(a)neitzel.de> writes: > main.cc:174: failed check > 'space_index_t(i).set_chief(space_index(),space_index_t(config::boot_taskno))' Please apply the patch at <URL:ftp://ftp.inf.tu-dresden.de/pub/os/L4/fiasco/fiasco-l4-981012.patch-01.gz> -- it should fix this bug. The problem was caused by an incomplete constructor which assumed statically-allocated storage would be zero-initialized. > [ other minor build problems many people have stumbled across ] I'll address these in a small patch to be released next week. Thanks for trying Fiasco! Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

2 1

Fehler beim Booten von Fiasco
by Konrad Neitzel 23 Oct '98

23 Oct '98

Hallo, entschuldigt, dass ich euch damit nerve, aber bisher weiss ich noch nicht genug ueber Fiasco, als dass ich den Fehler selber finden koennte (aber das wird dann ja in der Zukunft vielleicht noch was :) ) Ich erhalte beim Boot folgenden Fehler: main.cc:174: failed check 'space_index_t(i).set_chief(space_index(),space_index_t(config::boot_taskno))' (Hoffentlich habe ich mir das jetzt so richtig notiert :) ) Ich habe mir die aktuellen Sourcen vom Server geholt, und Sie auf meinem SuSE 5.2 System compiliert. (gcc 2.7.2.1) Bei meinem Rechner handelt es sich um einen K5-166 mit 128 MB Hauptspeicher. Boot-configuration ist wie in der Webseite angegeben (einfaches staren vom "hello world" Programm. Beim compilieren ist mir aufgefallen: - nach dem start von make im verzeichnis l4 meckert er, dass er "configure" nicht findet, wenn "." nicht im Pfad ist. - Er meckert in zwei Verzeichnissen, dass er verschiedene .d Files nicht findet. Da keine solchen Files irgendwo zu finden sind, mache ich mir da auch keine weiteren Gedanken drueber. (Auf Wunsch kann ich dies noch genauer schildern!) -Im Makefile unter l4/server/rmgr/src/ hat er als Yacc "byacc" eingetragen - ein solcher existiert in meinem System aber nicht. Ich habe diesen Eintrag einfach in "yacc" geaendert (Falls dies mein Fehler sein sollte, so tut mir das leid - dann wuerde mich interessieren, wie ich den Fehler umgehen kann!). Ich wuerde mich freuen, wenn Ihr mir helfen koenntet. Greetings, Konrad Neitzel -- Konrad Neitzel neitzel(a)neitzel.de

1 0

Re: Compilations- und Bootproblem mit Fiasco/L4
by Michael Hohmuth 22 Oct '98

22 Oct '98

Harald, l4-hackers is an international mailing list; the discussion language is English. If you need to discuss something in German, please contact <fiasco-core(a)os.inf.tu-dresden.de>. Harald Fritzsche <Harald.Fritzsche(a)mpd.de> writes: > make[2]: Entering directory > `/volumes/v3/HOME3/FRITZSCHE/L4/l4-981012/oskit/examples' > ld -Ttext 100000 -L../lib \ > -o multiboot-smp ../lib/multiboot.o multiboot-smp.o > \ > -lsmp -lkern -lmc -llmm ../lib/crtn.o > ../lib/libsmp.a(boot.o): In function `_SMP_TRAMP_START_': > boot.o(.text+0x29): relocation truncated to fit: R_386_16 > _SMP_TRAMP_32_ENTRY_ This has been reported before; however, I cannot reproduce this. A simple workaround is to "touch oskit/examples/multiboot-smp" -- this program isn't really needed. > main.cc 174 check failed Please apply the patch at <URL:ftp://ftp.inf.tu-dresden.de/pub/os/L4/fiasco/fiasco-l4-981012.patch-01.gz> -- it should fix this bug. The problem was caused by an incomplete constructor which assumed statically-allocated storage would be zero-initialized. Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Compilations- und Bootproblem mit Fiasco/L4
by Harald Fritzsche 21 Oct '98

21 Oct '98

Hallo an alle Fiasco-Entwickler und Beteiligte! Ich habe euer FIASCO-Packet -981012- zum Ausprobieren beschafft. Das kompilieren des OS-Kits führt im Directory examples zu nachfolgend aufgeführten Problemen: Ich benutzte den g++ (siehe unten) und SuSe-Linux5.3. gcc -v Reading specs from /usr/lib/gcc-lib/i486-linux/2.7.2.1/specs gcc version 2.7.2.1 Hier beginnt das Problem: make[2]: Entering directory `/volumes/v3/HOME3/FRITZSCHE/L4/l4-981012/oskit/examples' ld -Ttext 100000 -L../lib \ -o multiboot-smp ../lib/multiboot.o multiboot-smp.o \ -lsmp -lkern -lmc -llmm ../lib/crtn.o ../lib/libsmp.a(boot.o): In function `_SMP_TRAMP_START_': boot.o(.text+0x29): relocation truncated to fit: R_386_16 _SMP_TRAMP_32_ENTRY_ Alle zum Booten notwendigen Datein gemäß use.html waren erzeugbar. (byacc durch yacc ersetzt) Das Booten (Start von hello) schien erfolgreich zu laufen, aber der Kernel bringt eine Fehlermeldung ohne das eine "hello" erfolgt.: main.cc 174 check failed (sinngem"as) Das passiert sowohl auf einem AMD Proc. (~ Pentium 75, zu Hause) als auch einem Pentium II/233 (auf Arbeit.) Debuggen kann ich mangels zweitem PC nicht. Bin gern bereit mehr Info zu liefern, oder meine Fragen in englisch zu formulieren. mfg. Harald Fritzsche

1 0

Portability and bug fixes for Fiasco
by Michael Hohmuth 16 Oct '98

16 Oct '98

Fiasco now also compiles with egcs-1.0 and egcs-1.1. (Egcs-1.1 will whine a bit that it ignores many "volatile"s for asm() statements, but this is not a serious problem; this will be fixed with the next OSKit update.) I've created a patch that contains Kevin Moule's numerous ANSI C++ fixes (many thanks!), some compatibility code for the various compiler versions, a workaround for a compiler bug (egcs doesn't like template functions containing inline assembler statements), and a bug fix for the space_registry_t constructor. This patch will be uploaded to ftp.inf.tu-dresden.de (once the admins have created some free space on the ftp partition :-), and because it's short, I've also attached it to this message. Please note that the installation instructions on the web site contained an error: The "-sigma0" option was missing in Fiasco's command line in the GRUB config file. Thanks to Andrew Thomas for stepping into this trap! Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

Re: Fiasco: A new L4-compatible microkernel
by Michael Hohmuth 14 Oct '98

14 Oct '98

OKUJI Yoshinori <okuji(a)kuicr.kyoto-u.ac.jp> writes: > Congratulations! May I "mirror" Fiasco and its development toolkits? Yes, of course! However, I request that people who mirror Fiasco tell me about it so that I can list the mirrors on the Fiasco website. Michael -- hohmuth(a)innocent.com, hohmuth(a)sax.de http://www.sax.de/~hohmuth/

2 1

Fiasco: What's happening
by Michael Hohmuth 14 Oct '98

14 Oct '98

Dear readers of the L4-Hackers mailing list, first, a big ``Thank you!'' to all who have sent congratulations, best wishes, and even bug reports and code contributions! We really appreciate your interest! This message is intended to plug this mailing list a bit. Currently, people prefer to send their questions and problem reports to me privately instead of publicly on this mailing list. This is OK, but I do invite you to discuss Fiasco on this list so that other people can see what's going on, learn, and maybe even contribute. (Otherwise, I ask you to at least Cc your messages to <fiasco-core(a)os.inf.tu-dresden.de> so that the other members of Team Fiasco can follow the discussion.) To initialize you with some current information, I'm now going to post a summary of what is happening so far: It seams that the Fiasco build process is quite dependent on our current build environment: Gcc-2.7.2.3, Binutils-2.9.1. I am planning to switch this to Egcs-1.1 soon (and to make Fiasco more portable to other compiler versions in the process). One contributor has sent patches that make Fiasco compile with Egcs (thanks again!), and I'm going to release an update as soon as some problems with them are sorted out: Egcs doesn't seem to like inline assembly very much, especially in template functions (this even leads to an internal compiler error) and when using lots of register constraints. Some people have experienced crashes in the early kernel boot process. That's why, here are some hints at debugging: Fiasco can be source-level-debugged using a remote debugger running on a second machine via a serial connection: Just connect one of your test machine's serial ports (default: COM2) to your development host using a null-modem cable. Edit fiasco/src/.gdbinit to match your host's serial port, remove the "-nowait" boot option from your GRUB config file, reboot Fiasco, and start your GDB (or your favorite GDB-based debugger) when the "KDB: init" message appears. You can then set breakpoints, continue the execution, and even interrupt Fiasco by typing Control-C in the debugger. Here are some useful boot options for Fiasco (`main'): - "-nowait" removes the initial "KDB: init" breakpoint. The installation instructions on the Fiasco web site recommend this option; if you plan to do some serious debugging, you shouldn't use it. - "-nokdb" disables the kernel debugger. Should Fiasco raise an exception, it will just dump its register contents and die. - "-comspeed n" will set the rate of the serial interface to n bytes/second. 115200 bytes/second is the default. - "-comport n" will use COMn for serial communication. COM2 is the default. - "-hercules" will output kernel messages to a Hercules (or MGA) screen instead of the default VGA console. - "-serial" will additionally output kernel messages to the serial interface; this can save you copying kernel messages by hand. If "-nokdb" is also enabled, you can use a terminal program on the host to control Fiasco. If you are connected to a remote GDB, messages are copied to GDB's console. - "-profile" will profile the kernel; you need to compile it with "-DPROFILE" for this to work. When you terminate Fiasco (e.g., using the remote debugger), the profiling information is printed in uuencoded 4.4BSD gmon.out format to the serial interface; you can capture it using a terminal program. Unfortunately, current versions of GNU `gprof' don't understand the 4.4BSD gmon.out format; the next version hopefully does. I've sent a patch to the `gprof' maintainer (the patch is also available on request from me). There are some more options dealing with interrupt allocation for user threads, but they are hardly relevant for anyone. That's it for today! Happy hacking, Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

1 0

Fiasco: A new L4-compatible microkernel
by Michael Hohmuth 13 Oct '98

13 Oct '98

Dear readers of the L4-Hackers mailing list, the Operating Systems Group at TU Dresden is proud to announce the first development version of a new L4-compatible microkernel, called ``Fiasco.'' This release is distributed under GNU General Public License. Fiasco is a microkernel with real-time capabilities and runs on x86 PCs. Fiasco can run L4Linux, a port of the Linux kernel to the L4 interface which executes completely in user mode. Please find more information about the new kernel on the Fiasco website at <URL:http://os.inf.tu-dresden.de/fiasco/>. Regards, Michael -- hohmuth(a)innocent.com, hohmuth(a)inf.tu-dresden.de http://home.pages.de/~hohmuth/

2 1

2025

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