l4-hackers November 1998

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

17 participants
29 discussions

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

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 November 1998