l4-hackers

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

2827 discussions

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers