- l4-hackers - example.com Site

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 22 Nov '98

22 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