l4-hackers

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

2 participants
2880 discussions

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

Jump to page:

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