- l4-hackers - example.com Site

segment fault for fiasco-ux
by halo.duan 11 Dec '06

11 Dec '06

Hi all I am newbie for L4 and just downloaded the fiasco last week. as i compiled as ux and run fiasco hello stuff. loading of sigma0 and roottask and irq0 is ok. but nothing displayed. as i use strace attach the fiasco process, it shown full screen segment fault. only think i can do is "kill -9 PID". any sugestion? best regards

2 1

Re: l4-hackers Digest, Vol 44, Issue 4
by cb huang 09 Dec '06

09 Dec '06

> > Hi, > > On Mon Dec 04, 2006 at 22:33:48 +0800, cb huang wrote: > > These days I'm studying the fiasco especially the IPC mechanism, so I > > want to get the paper The Fiasco Kernel: System Architecture, but it > seems > > that the paper is not yet published.Who can tell me where I can get it. > > I think this will never be published. It's also quite old and the IPC > path has changed significantly since then so it's probably not very > useful either. Yes, I know it's quite old, whereas I don't know whether there is another more useful one. Thanks for your reply!

2 1

Where can I get the paper The Fiasco Kernel: System Architecture
by cb huang 06 Dec '06

06 Dec '06

Hi These days I'm studying the fiasco especially the IPC mechanism, so I want to get the paper The Fiasco Kernel: System Architecture, but it seems that the paper is not yet published.Who can tell me where I can get it. Thanks a lot! -- cbhuang

2 1

Re: L4Linux and USB Keyboard/Mouse
by FERANDELLE Pascal 06 Dec '06

06 Dec '06

I added the UHCI HCD support to my config (thanks to lspci -v command ...), and now my keyboard is ok. Under DOpE, my mouse doesn't move from (0,0), but that's an old problem ... Pascal

1 0

L4Linux and USB Keyboard/Mouse
by FERANDELLE Pascal 05 Dec '06

05 Dec '06

On a PC with keyboard/mouse on USB, I booted L4Linux 2.6.17, but I only had keyboard running. That was not a problem when using only l4con. Now, with L4Linux 2.6.18, neither keyboard and mouse are running ... Everything is ok on a PC with keyboard/mouse on PS/2.

2 1

vbemode option in l4dope?
by "Gábor Bérczi (Gabucino)" 05 Dec '06

05 Dec '06

Greetings. I'd like to ask if it's planned to implement l4con's --vbemode command line option in l4dope too? I couldn't get grub's vbeset option to work in QEMU (always ends up in black screen), but l4con-s vbemode option does work. -- Gábor Bérczi

3 9

Can't start L4Linux-2.6.18
by FERANDELLE Pascal 04 Dec '06

04 Dec '06

In august, I tested L4Linux on PC, and everything was working fine with L4Linux-2.6.17. Now, I get the snapshots of 20061116, and rebuild everything. The L4Linux kernel is now 2.6.18. The build is ok, but I can't start it under Fiasco. Here is the log : Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Sat Nov 11 18:26:23 2006 compiled with gcc 3.4.6 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling SERIAL ESC: allocated IRQ 4 for serial uart SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:4:9:0) Model: Pentium 4E (Prescott/Nocona) at 2793 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 16 KB L1 D Cache (8-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) SIGMA0: Hello! ... ... l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.18-l4 (root@PClinux) (gcc version 3.4.6) #1 Fri Dec l4lx : 1 18:41:42 CET 2006 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (7 args): earlyprintk=yes mem=64M video=l4fb load l4lx : _ramdisk=1 ramdisk_size=16384 root=/dev/ram l4env_rd=test-rd.rd l4lx | The running kernel does not have the l4lx | exception_ipc l4lx | feature enabled! Of course, I have the exception_ipc feature enabled in Fiasco !!! If I rebuild L4Linux-2.6.17, with the L4Env from 20061116, and try to start it under Fiasco, there is no problem ...

2 3

L4Env for X.2 (L4Ka::Pistachio)?
by Christian, Martin, OPEE45 01 Dec '06

01 Dec '06

Hi! On "http://l4hq.org/projects/env/l4env/" I read about L4Env: "Support for X.2 (L4Ka::Pistachio) will follow shortly." Is someone working on it? How is the status? When could I expect a release? Will it be architecture/platform independent? Thanks, Martin.

2 1

Re:Timing problem on mem_fpage_unmap() in the fiasco kernel
by WanKeun Jo 24 Nov '06

24 Nov '06

Hi, I prevented the timing problem to occur by simply unset the l4linux-2.6 option "Show timing information on printks" before. When the option is set, then in the function 'vprintk()' of "l4linux-2.6/kernel/printk.c", the system get current jiffies and then converted it to the string and add it to log buffer. The system works well right before the following codes in the function. When I remove the following code, the system works well without adding timing information on log buffer. ------------------------------------------------ tlen = sprintf(tbuf, 590 "<%c>[%5lu.%06lu] ", 591 loglev_char, 592 (unsigned long)t, 593 nanosec_rem/1000); 594 595 for (tp = tbuf; tp < tbuf + tlen; tp++) 596 emit_log_char(*tp); 597 printed_len += tlen; ------------------------------------------------ However, when I add one of the above three statements - (1) tlen = sprintf(), (2) for(), (3) printed_len += tlen - then the timing error occur during the "Freeing INITRD". even one statement of them.. This is so strange to me and also to you. I'm just beginner in this kind of works, so there might something that I overlooked. Is there somebody who can give me an advice for this kind of ERRORs..?? Thank you.

2 1

fiasco compilation problems
by Hendrik Tews 24 Nov '06

24 Nov '06

I just failed in trying to build fiasco-ux: First I followed the fiasco building and using page (the hello module variant) using the public cvs: - The following dependencies are not mentioned: libncurses5-dev, autoconf, automake1.9, doxygen I don't understand autoconf: the configure scripts should be generated at the distributors site? When autoconf was missing, I got a message saying I need autoconf 2.50, it didn't say I need automake1.9. Here autoconf comes by default with 1.8. Further I don't understand doxygen: Wouldn't it be better to have a separate doc goal and the main make goal independent from doxygen? I appreciate the different config tools in l4 and fiasco as sign of big freedom in this world (and in Dresden in particular). ;-) However, it would make live easier for the casual l4 configurator (like me) if keybindings would agree and fiasco config had an exit button. - the fiasco-ux site says Enable at least the following configuration options: * Target platform (choose UX) * Assembler IPC shortcut * Generate inline code I could neither find IPC shortcut nor inline code. - Then I got the following message: Flex and Byacc. (If you don't have Byacc, but Bison, try setting "bison -y" in the L4 configuration menu under "Compilers and Tools". Other Yacc implementations might do it as well.) but neither the message nor the website says where to find the L4 config menu. Wouldn't it be possible to let the config automatically choose bison if byacc is not found? - the "-C l4" in in 2.a seems to prohibit relativ path for the builddir. Why not cd l4 before? - Point 3.a says "cd l4", but there is no l4 inside l4 - Somebody told me that the preferred way to download fiasco nowadays is to use one of the opentc snapshots. If thats true if would be nice to have a link to these snapshots. - Finally fiasco-ux and all the modules were compiled: tandem l4v2 38> ./fiasco Fiasco-UX on Linux 2.6.17-2-k7 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096d44 [sigma0-ux] Loading Module 0x00120000-0x002bd9f4 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Nov 23 10:27:00 2006 compiled with gcc 4.1.2 for Intel Pentium CPU: AuthenticAMD (F:23:2:0) Model: Athlon 64 X2 (Toledo) at 2418 MHz 32/512 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/512 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /home/tews/Fiasco/current/l4/kernel/fiasco/src/kern/ux/hostproc.cpp:120 Now I tried the latest opentc snapshot. I ingored the opentc build instructions and applied the fiasco build instructions to this tree. At some stage it was complaining about gcc-4.1.2 being the wrong compiler version. I changed the compilers to gcc-3.4/g++-3.4 in the l4 config. After that make skipped a lot of dirs, because the goals were done before already. Shouldn't it recompile everything after changing the compiler? So I did make clean then and rebuild. But still I saw a lot of messages with ``g++'' (which would be 4.1.2). That's unproblematic? The compilation stoped eventually with make[3]: Entering directory `/home/tews/Fiasco/opentc-snap/l4/build/doc/building-howto' cp building.tex drops-building.tex cp: cannot stat `building.tex': No such file or directory make[3]: *** [drops-building.tex] Error 1 make[3]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/build/doc/building-howto' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/doc/building-howto' make[1]: *** [building-howto] Error 2 make[1]: Leaving directory `/home/tews/Fiasco/opentc-snap/l4/doc' make: *** [doc] Error 2 There seems a problem with the builddir, because tandem l4 29> find . -name building.tex ./doc/building-howto/building.tex However, the build/bin/x86_586/l4v2 dir looked already very full, so I decided to ignore the build instructions and tried: tandem l4v2 7> ./fiasco Fiasco-UX on Linux 2.6.17-2-k7 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Loading Module 0x00090000-0x00096ce4 [sigma0-ux] Loading Module 0x00120000-0x002bda14 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Unknown compiled with gcc 4.1.2 for Intel Pentium CPU: AuthenticAMD (F:23:2:0) Model: Athlon 64 X2 (Toledo) at 2418 MHz 32/512 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/512 Entry D TLB (4K pages) 8 Entry D TLB (4M pages) 64 KB L1 I Cache (2-way associative, 64 bytes per line) 64 KB L1 D Cache (2-way associative, 64 bytes per line) 1024 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) ASSERTION_FAILED (((((*(int *) &(status))) & 0xff) == 0x7f) && ((((*(int *) &(status))) & 0xff00) >> 8) == 10) in function static unsigned int Hostproc::create(unsigned int) in file /home/tews/Fiasco/opentc-snap/l4/kernel/fiasco/src/kern/ux/hostproc.cpp:120 which is the same problem as before. Bye, Hendrik

2 1