- l4-hackers - example.com Site

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 15 Oct '98

15 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