- l4-hackers - OS Site

Re: Compiling L4Linux-2.6 without L4Env on L4::Fiasco
by kazilus kazilus 13 Dec '07

13 Dec '07

Ok thanks for the info. How about the L4Linux-2.4. So far, i found info that it can be build on top Fiasco without L4Env, but the problem i wasn't able to get source codes of L4Linux 2.4 until now. May i know where can i get them? ----- Original Message ---- From: Bjoern Doebel <doebel(a)os.inf.tu-dresden.de> To: kazilus kazilus <amadkamal(a)yahoo.com> Cc: l4-hackers(a)os.inf.tu-dresden.de Sent: Thursday, December 13, 2007 3:24:08 PM Subject: Re: Compiling L4Linux-2.6 without L4Env on L4::Fiasco Hi, > I've got problem to compiling L4Linux-2.6 on Fiasco. > > For information, i didn't install L4Env package. > > Does it possible to install L4Linux-2.6 without L4Env, if so, may i know > a basic start to do that? No. You need to build L4Env, too, because L4Linux is using L4Env as the underlying paravirtualization layer. Just keep to the instructions on the website, then this should be fine. Regards, Bjoern ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Compiling L4Linux-2.6 without L4Env on L4::Fiasco
by kazilus kazilus 13 Dec '07

13 Dec '07

Hi All, I've got problem to compiling L4Linux-2.6 on Fiasco. For information, i didn't install L4Env package. Does it possible to install L4Linux-2.6 without L4Env, if so, may i know a basic start to do that? Regards, Ahmad Kamal ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

2 1

Little fix about ORe
by Marc CHALAND 10 Dec '07

10 Dec '07

Hi, I've found that when an ORe client finishes, ORe doesn't stop associated worker thread. Context is correctly freed but not thread. This may lead a lack of thread when several clients finishes and restart several times. Here is a little patch to fix this. Regards Marc

2 1

UX question
by Nicholas Mc Guire 06 Dec '07

06 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi ! latest svn (as of yesterday) booting ux with the default hello module ends up in jdb and it seems like nither "g" nor "^" nor control-C will kill the beast :) any way out, aside from switching consoles and trampling on fiasco ? some details: root 11705 25.2 3.3 66704 7512 pts/0 S+ 13:48 1:41 ./fiasco - -I hello root 11706 0.0 0.0 0 0 pts/0 Z+ 13:48 0:00 [hello] <defunct> so the hello that happily prints on the real-hw seems to be dead under UX (seems well reproducible) After CNTRL-C I end at: debian:/home/l4/tudos/ux_test# ./fiasco -I hello <snip> Loading Module 0x00100000-0x00109380 [sigma0] Loading Module 0x00110000-0x002ae000 [roottask] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/ia32 microkernel (C) 1998-2007 TU Dresden Rev: r247 compiled with gcc 4.1.2 for Intel Pentium [] CPU: AuthenticAMD (F:4F:2:0) Model: Unknown CPU at 1803 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... - --Interception--------------------------------------ESP:200007a8 EIP:000ceaf6 (0.00) jdb: t thread: 0.00 <00000000> prio: 00 mcp: ff mode: Con state: 001 ready wait for: polling: rcv descr: lcked by: ---.-- timeout : cpu time: 0 timeslice: 100000/100000 s pager : ---.-- cap: ---.-- utcb: 00000000 preemptr: ---.-- not monitored ready lnk: ???.?? ???.?? prsnt lnk: 0.00 0.00 EAX=00000000 ESI=00000000 DS=007b EBX=00000000 EDI=00000000 ES=007b je 0xceae0 ECX=00000000 EBP=63efc000 GS=0000 mov 0xa0(%ebp),%esi EDX=00000000 ESP=200007a8 SS=0000 trap 1 (Debug), error 00000000, from kernel mode CS=0000 EIP=000ceaf6 EFlags=00000246 200007a8 00000000 00000246 00096b24 20000000 00000000 00000000 000cd5f6 00000000 7c0 200007cc 20000000 000cd7ba 00015540 00000000 00000000 00000000 00000000 7e0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 t/bt/l etc. shows only one task and that task is marked ready. any hint ? thx! hofrat -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFHV8wJnU7rXZKfY2oRArptAJ49z8//ypf7IupiBqaIKO89+Y9PBgCbBH4j GSvlkztmVMcICMLsjo7X0dw= =cpwv -----END PGP SIGNATURE-----

2 2

The problems of compiling grub-0.97-os.6
by cheng.guanghui.ml 01 Dec '07

01 Dec '07

Hi: I compile the grub-0.97 patched the os.6 provided by Adam home page. But there are some error messages like following: pre_stage2_exec-bios.o: In function `get_cdinfo': /home/cheng/tudos/grub-0.97/stage2/bios.c:179: undefined reference to `__stack_chk_fail' pre_stage2_exec-bios.o: In function `get_diskinfo': /home/cheng/tudos/grub-0.97/stage2/bios.c:317: undefined reference to `__stack_chk_fail' pre_stage2_exec-boot.o: In function `load_image': /home/cheng/tudos/grub-0.97/stage2/boot.c:759: undefined reference to `__stack_chk_fail' pre_stage2_exec-builtins.o: In function `blocklist_func': /home/cheng/tudos/grub-0.97/stage2/builtins.c:224: undefined reference to `__stack_chk_fail' pre_stage2_exec-builtins.o: In function `embed_func': /home/cheng/tudos/grub-0.97/stage2/builtins.c:1191: undefined reference to `__stack_chk_fail' pre_stage2_exec-builtins.o:/home/cheng/tudos/grub-0.97/stage2/builtins.c:1350: more undefined references to `__stack_chk_fail' follow collect2: ld returned 1 exit status gcc version: 4.1.3 OS: ubuntu 7.10 gutsy

3 2

Re: l4x_hybrid_return for ovlscreen driver
by Adam Lackorzynski 23 Nov '07

23 Nov '07

Hi Marc, On Wed Nov 21, 2007 at 14:38:54 +0100, Marc CHALAND wrote: > 2007/11/21, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > > > > Are you using 2k or 4k stack in Fiasco? If 2k, try 4k. > > I've tried 4k without success. Should I compile all l4env ? No, this is just a kernel matter. > > Also, there's a > > stack depth debugging feature, i.e. when you look at the thread list > > there's figure how much stack is used. You could look at those figure > > too. > > When it crashes, X has got a figure of 1016. It's not necessarily the X process. What are the highest numbers and to which task do they belong? > I join fiasco binary. pf occurs at 0xf0020d8d. Is there something to exploit ? Please send me (in private mail) the fiasco.image file. The one you attached is the stripped version which gives me difficulties finding the correspondig source location. > I also tried to not use assembler IPC shortcut, but fiasco crashes at boot time. Uh? That should not happen and it works for me. Could you send me the config you used for this setup? > > I'd suspect inlining is using a bit more stack than without > > inlining. > > I would have think the opposite as parameters, ebp and eip should be > stacked as with inline code, it shouldn't ? Inlining will duplicate code and thus use more stack, at least that's our experience. I guess gcc could be smarter about stack usage but well... Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 1

l4x_hybrid_return for ovlscreen driver
by Marc CHALAND 21 Nov '07

21 Nov '07

Hi, With Nitpicker, I try to start X server with ovlscreen driver. After a little while, I get the following message : l4lx | l4x_hybrid_return: Invalid hybrid return for 23.00 (0x0688d570, e, 0, l4lx : -1, f0020d5d)! l4lx | l4x_hybrid_return: Currently running: 00.00 After some debugging and tracing, I've found that this message happens when X server does a rmgr_get_task_id on names. I don't understand why this IPC fails as ping_call perfectly works (I enabled traces on roottask and saw ping_component call). I tried to enable IPC monitoring with I* into jdb, but I get an assertion in Fiasco : Assertion failed: 'this == current()' in /home/chaland/l4/tudos/kernel/fiasco/src/kern/context.cpp:512 at f0023378 I don't understand what happens. Could you help me please ? Regards Marc

3 8

Error when compiling l4linux
by fang zhengshu 12 Nov '07

12 Nov '07

Hello, after some days trying to compile l4linux , I reach the following problem while compiling l4linux : . . . AR lib/lib.a CC arch/l4/lib/arch-i386/../proc.o LD arch/l4/lib/arch-i386/proc.o LD arch/l4/lib/arch-i386/built-in.o CC arch/l4/lib/arch-i386/../../../i386/lib/bitops.o CC arch/l4/lib/arch-i386/../../../i386/lib/delay.o CC arch/l4/lib/arch-i386/../../../i386/lib/mmx.o CC arch/l4/lib/arch-i386/../../../i386/lib/string.o CC arch/l4/lib/arch-i386/../../../i386/lib/strstr.o CC arch/l4/lib/arch-i386/../memcpy_user.o CC arch/l4/lib/arch-i386/../pte.o CC arch/l4/lib/arch-i386/../uaccess.o CC arch/l4/lib/arch-i386/checksum.o CC arch/l4/lib/arch-i386/memcpy.o make[1]: *** No rule to make target "arch/l4/lib/arch-i386/mmx.o",need by "arch/l4/lib/arch-i386/lib.a". stop。 make: *** [arch/l4/lib/arch-i386] Error 2 ------- I use the /l4linux-2.6/arch/l4/configs/x86-native_defconfig as the defconfig; cp /l4linux-2.6/arch/l4/configs/x86-native_defconfig config cp config .config make oldconfig ;make menuconfig and also I modified the cpu type and device driver. but when I compiled it on AMD Athlon the error apear; when I compiled it on p4 it worked well. -------- I really don't know how to resolve this. Help would be very welcome. Thanks, Dennis

2 1

Mad Mouse
by Marc CHALAND 08 Nov '07

08 Nov '07

Hi I use Nitpicker with dope applications. Sometimes, mouse cursor becomes mad: it goes from right to the left or up to the down. On serial console, I get the following message : nitpicke| serio: i8042 AUX port at 0x60,0x64 irq 12 nitpicke| serio: i8042 KBD port at 0x60,0x64 irq 1 ... nitpicke| connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 nitpicke| connect "AT Raw Set 2 keyboard", isa0060/serio0/input0 nitpicke| connect "PC Speaker", isa0061/input0 nitpicke| connect "L4 input event injector", l4/sys ... nitpicke| psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronizati nitpicke: on, throwing 3 bytes away. fiasco is started with -serial_esc option. I tried to modify ACPI parameters into bios, but nothing changed. On google, I've found that noacpi should be used but this option is not available into l4input. I also tried to change mouse. With a linux live cd configuration works perfectly. Have you got any idea about this problem ? Driver should be updated (I use current svn version) ? Something else wrong into my configuration ? Regards Marc

3 12

Hide linux console into DOpE
by Marc CHALAND 08 Nov '07

08 Nov '07

Hi, I added into l4linux a feature that seems to me interesting. With the following patch, it is possible to hide linux console window with the following linux command: echo N > /sys/module/l4fb/parameters/console_visible The console can be shown with the following command : echo Y > /sys/module/l4fb/parameters/console_visible Regards Marc

2 1

problem compiling l4linux - arm
by Dennis Gessner 06 Nov '07

06 Nov '07

Hi, I have some difficulties, compiling l4linux for arm. (I use the toolchain from http://www.ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.bz2.) Using the version from SVN (# svn co -N http://svn.tudos.org/repos/tudos/trunk tudos), I don't have any problems compiling fiasco or the l4env, but if I try to compile l4linux (... "repomgr co fiasco dice l4linux-2.6-env" ... and after disabling the VGA-Console) - I get the following error-message: --- l4linux-2.6 # make L4ARCH=arm CROSS_COMPILE=arm-linux- CHK include/linux/version.h CHK include/linux/utsrelease.h CALL scripts/checksyscalls.sh <stdin>:91:1: warning: "__IGNORE_sync_file_range" redefined In file included from <stdin>:2: include/asm-l4/arm-arch/asm/unistd.h:444:1: warning: this is the location of the previous definition <stdin>:1097:2: warning: #warning syscall fadvise64 not implemented <stdin>:1265:2: warning: #warning syscall migrate_pages not implemented <stdin>:1321:2: warning: #warning syscall pselect6 not implemented <stdin>:1325:2: warning: #warning syscall ppoll not implemented <stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented CHK include/linux/compile.h GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 arch/l4/kernel/arch-arm/built-in.o(.init.text+0x824): In function `start_thread': /root/tudos/l4linux-2.6/include/asm-l4/arm-arch/asm/current.h:9: undefined reference to `l4env_load_initrd' make: *** [.tmp_vmlinux1] Error 1 --- How can I solve this error-message? By the way, using a l4linux Version from 2007-06-30 works very well, but there I have the problem, that the openmoko-kernel-patchset is made for linux 2.6.22.x and my 2007-06-30-Version is 2.6.21.x. Any help would be very welcome! Thanks, Dennis

4 5

Can't using keyboard when start from serial port.
by 丁莹 05 Nov '07

05 Nov '07

Hi,all These day we test the l4linux-2.6.23 on debian and ubuntu ,both on them the dope is runing well,but we have problem with starting from serial port,that is the keyboard can't input.It's seems the keyboard is actived,but can't input anything.And the output message as follow. ----------------------------------------------------------------------------------- Welcome to minicom 2.2 OPTIONS: I18n Compiled on Mar 7 2007, 15:10:03. Port /dev/ttyS0 Press ESC,Z for help on special keys Welcome to Fiasco(ia32)! DD-L4(v2)/ia32 microkernel (C) 1998-2007 TU Dresden Rev: r231 compiled with gcc 4.1.2 for Intel Pentium [] Performance-critical config option(s) detected: CONFIG_NDEBUG is off Enabling special fully nested mode for PIC Using the PIT (i8254) on IRQ 0 for scheduling Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:2:9:9) Model: Pentium 4 (Northwood/Prestonia) at 2790 MHz 128 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K �-ops T Cache (8-way associative) 8 KB L1 D Cache (4-way associative, 64 bytes per line) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 20480 bytes (5 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 1000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Command line found: "/boot/L4Linux/roottask task modname "bmodfs" attached 4 modules" 252478kB ( 246MB) total RAM (reported by bootloader) 226200kB ( 221MB) received RAM from Sigma0 26112kB ( 26MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 4 5 6 7 8 9 A B C D E F 10 11 ] Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:3ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:4 Roottask: Loading 14 modules. #05: loading "/boot/L4Linux/events" from [06129000-06166bb9] to [01540000-01548b90][01549000-0155e5b0] entry at 0005b070 via trampoline page code symbols at [0e32c000-0e32e000] (8kB), lines at [0e326000-0e32c000] (24kB) #06: loading "/boot/L4Linux/names --events" from [06167000-061a602c] to [002d0000-002d6317][002d7000-002e2000] entry at 0005c078 via trampoline page code symbols at [0e324000-0e326000] (8kB), lines at [0e31e000-0e324000] (24kB) #07: loading "/boot/L4Linux/log --events" from [061a7000-061e25fa] to [00400000-00406b4a][00407000-00439848] entry at 0005d074 via trampoline page code symbols at [0e31c000-0e31e000] (8kB), lines at [0e316000-0e31c000] (24kB) #08: loading "/boot/L4Linux/dm_phys --isa=0x00800000 -v --events" from [061e3000-0627a0c3] to [01500000-01512ad7][01513000-0151d000] entry at 0005e08c via trampoline page code symbols at [0e311000-0e316000] (20kB), lines at [0e304000-0e311000] (52kB) #09: loading "/boot/L4Linux/simple_ts -t 300 --events" from [0627b000-062c65a1] to [01400000-0140842a][01409000-01418608] entry at 0005f080 via trampoline page code symbols at [0e302000-0e304000] (8kB), lines at [0e2fb000-0e302000] (28kB) #0a: loading "/boot/L4Linux/rtc --events" from [062c7000-062f503e] to [01080000-010843c0][01085000-0108a000] entry at 00061074 via trampoline page code symbols at [0e2f9000-0e2fb000] (8kB), lines at [0e2f5000-0e2f9000] (16kB) #0b: loading "/boot/L4Linux/l4io --noirq --events module" from [062f6000-06560cc0] to [00c20000-00c42a75][00c43000-00cb1000] entry at 00062084 via trampoline page code symbols at [0e29f000-0e2f5000] (344kB), lines at [0e286000-0e29f000] (100kB) #0c: loading "/boot/L4Linux/omega0 --l4io" from [06561000-065a4980] to [00360000-0036779c][00368000-0036d000] entry at 00063074 via trampoline page code symbols at [0e284000-0e286000] (8kB), lines at [0e27d000-0e284000] (28kB) #0d: loading "/boot/L4Linux/loader --fprov=BMODFS linux26.cfg" from [065a5000-0667c018] to [01300000-01325d21][01326000-01345000] entry at 00064088 via trampoline page code symbols at [0e276000-0e27d000] (28kB), lines at [0e25e000-0e276000] (96kB) #0e: loading "/boot/L4Linux/bmodfs" from [0667d000-0671ee67] to [01220000-012362e1][01237000-0124e000] passing module /boot/L4Linux/vmlinuz [ 0671f000-077f95d2 ] passing module /boot/L4Linux/linux26.cfg [ 077fa000-077fa0a6 ] passing module /boot/L4Linux/libloader.s.so [ 077fb000-0789473f ] passing module /boot/L4Linux/libld-l4.s.so [ 07895000-0790bbad ] entry at 00065120 via trampoline page code symbols at [0e259000-0e25e000] (20kB), lines at [0e248000-0e259000] (68kB) log | /boot/L4Linux/log: unrecognized option `--events' log | Unrecognized option: - ? log | Usage: /boot/L4Linux/log <options>. Option list: log | [ -h | --help ] - this help log | [ -v | --verbose ] - verbose mode log | [ -l | --local ] - flush to local console log | [ -L | --nolocal ] - do not flush to local console log | [ -s | --comport num ] - flush to specified serial interface (0) log | [ -e | --serial-esc ] - enter kdebug on esc on serial log | [ -b | --buffer num ] - buffered mode (0) log | [ --flushprio num ] - priority of flusher thread (0x20) log | [ -p | --prio num ] - priority of main thread (0x20) names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:30.10.2007 Time:21:32:43 omega0 | /boot/L4Linux/omega0: unrecognized option `--l4io' omega0 | Unrecognized option: - ? omega0 | Usage: /boot/L4Linux/omega0 <options>. Option list: omega0 | [ -h | --help ] - this help omega0 | [ -e | --events ] - enable exit handling via events omega0 | omega0 | Exiting with 1 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x0f6f0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0f6f0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x0009f000 -- -- RESERVED DMphys | 0x00100000-0x00161000 -- -- RESERVED DMphys | 0x00161000-0x001ad000 -- -- DENIED DMphys | 0x001ad000-0x002ad000 7 12 MAPPED DMphys | 0x002ad000-0x002ae000 -- -- DENIED DMphys | 0x002ae000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e2000 -- -- DENIED DMphys | 0x002e2000-0x00360000 7 12 MAPPED DMphys | 0x00360000-0x0036d000 -- -- DENIED DMphys | 0x0036d000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x00a07000 7 12 MAPPED DMphys | 0x00a07000-0x00c20000 0 12 MAPPED DMphys | 0x00c20000-0x00cb1000 -- -- DENIED DMphys | 0x00cb1000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x0124e000 -- -- DENIED DMphys | 0x0124e000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01345000 -- -- DENIED DMphys | 0x01345000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01419000 -- -- DENIED DMphys | 0x01419000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151d000 -- -- RESERVED DMphys | 0x0151d000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0155f000 -- -- DENIED DMphys | 0x0155f000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x0671f000 0 12 MAPPED DMphys | 0x0671f000-0x0790c000 -- -- DENIED DMphys | 0x0790c000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0e000000 0 22 MAPPED DMphys | 0x0e000000-0x0e248000 0 12 MAPPED DMphys | 0x0e248000-0x0f6f0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 201668KB total, 201668KB free, 32KB reserved DMphys | 0x00a07000-0x00c20000 ( 2148KB, 2MB) free DS: DMphys | 0x00cb1000-0x01080000 ( 3900KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x0124e000-0x01300000 ( 712KB, 1MB) free DS: DMphys | 0x01345000-0x01400000 ( 748KB, 1MB) free DS: DMphys | 0x01419000-0x01500000 ( 924KB, 1MB) free DS: DMphys | 0x0151d000-0x01540000 ( 140KB, 0MB) free DS: DMphys | 0x0155f000-0x0671f000 ( 83712KB, 82MB) free DS: DMphys | 0x0790c000-0x0e248000 (107760KB, 105MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x001ad000-0x002ad000 ( 1024KB, 1MB) free DS: DMphys | 0x002ae000-0x002d0000 ( 136KB, 0MB) free DS: DMphys | 0x002e2000-0x00360000 ( 504KB, 0MB) free DS: DMphys | 0x0036d000-0x00400000 ( 588KB, 1MB) free DS: DMphys | 0x0043a000-0x00a07000 ( 5940KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz" (17258kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (614kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so " (475kB) io | /boot/L4Linux/l4io: unrecognized option `--noirq' io | Enabling events support. io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 io | Transparent bridge - Intel Corporation 82801 PCI Bridge io | PCI: Enabling device 00:1f.1 (0005 -> 0007) io | 00000000-ffffffff : PCI mem io | 80000000-8007ffff : Intel Corporation 82845G/GL[Brookdale-G]/GE Chi io : pset Integrated Graphics Device io | 80080000-800803ff : Intel Corporation 82801DB (ICH4) IDE Controller io | 88000000-8fffffff : Intel Corporation 82845G/GL[Brookdale-G]/GE Chi io : pset Integrated Graphics Device io | c0080000-c00803ff : Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB io : 2 EHCI Controller io | c0080800-c00808ff : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ io : ICH4-M) AC'97 Audio Controller io | c0080c00-c0080dff : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ io : ICH4-M) AC'97 Audio Controller io | c0100000-c0100fff : Intel Corporation 82801DB PRO/100 VE (LOM) Ethe io : rnet Controller io | d0000000-dfffffff : Intel Corporation 82845G/GL[Brookdale-G]/GE/PE io : DRAM Controller/Host-Hub Interfa io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | 1800-181f : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) io : USB UHCI Controller #1 io | 1820-183f : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) io : USB UHCI Controller #2 io | 1840-185f : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) io : USB UHCI Controller #3 io | 1860-186f : Intel Corporation 82801DB (ICH4) IDE Controller io | 1880-189f : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) io : SMBus Controller io | 18c0-18ff : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) io : AC'97 Audio Controller io | 1c00-1cff : Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) io : AC'97 Audio Controller io | 2000-203f : Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Con io : troller loader | vmlinuz: Starting application using libld-l4.s.so loader | vmlinuz,#f: Loading binary loader | vmlinuz,#f: Loading ldso loader | vmlinuz,#f: Starting libld-l4.s.so at 00013870 via 0000cf40 io | Available IRQs=[ <!0> 1 <!2> 3 4 5 6 7 8 9 a b c d e f 10 11 ] l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.23-l4 (root@l4) (gcc version 4.1.2 20061115 (prerel l4lx : ease) (Debian 4.1.1-21)) #3 Tue Oct 30 15:08:10 CST 2007 l4lx | Binary name: vmlinuz l4lx | Kernel command line (7 args): earlyprintk=yes console=ttyLv0 init=2 m l4lx : em=64M video=l4fb root=/dev/hda8 ro l4lx | Image: 00400000 - 007d4000 [3920 KiB]. l4lx | Areas: Text: 00400000 - 006e1000 [2948kB] (a bit longer) l4lx | Data: 006e1000 - 0070009c [124kB] l4lx | Initdata: 00704000 - 0073f000 [236kB] l4lx | BSS: 00740000 - 007d1650 [581kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer0) l4lx | Tamer0 is 0f.03 l4lx | Using tamed mode. l4lx | Connecting to l4io server. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (cpu0) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 00702000 size = 860160 l4lx | sec-w-init: virt: 0x00702000 to 0x007d3fff [840 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 2, 860160 Bytes l4lx | sec-w-init: 1: Phys: 0x01345000 to 0x01392000, Size: 315392 l4lx | sec-w-init: 2: Phys: 0x0127b000 to 0x01300000, Size: 544768 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x0a000000 to 0x0e000000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1545 entries). Linux version 2.6.23-l4 (root@l4) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #3 Tue Oct 30 157 dm_phys: 0000000000c00000 - 0000000004c00000 (usable) dm_phys: 0000000000800000 - 0000000000a00000 (usable) 68MB memory available. Zone PFN ranges: DMA 0 -> 2560 Normal 2560 -> 19456 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0 -> 19456 Allocating PCI resources starting at 10000000 (gap: 00a00000:ff600000) Built 1 zonelists in Zone order. Total pages: 19304 Kernel command line: earlyprintk=yes console=ttyLv0 init=/bin/sh mem=64M video=l4fb root=/dev/hda8 ro Initializing CPU#0 PID hash table entries: 512 (order: 9, 2048 bytes) Detected 2790.722 MHz processor. Console: colour VGA+ 80x25 l4ser_init_ports l4ser: input not enabled! console [ttyLv0] enabled Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 65776k/77824k available (2350k kernel code, 1752k reserved, 721k data, 236k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffb000 - 0xfffff000 ( 16 kB) vmalloc : 0x08000000 - 0x10000000 ( 128 MB) lowmem : 0x00000000 - 0x04c00000 ( 76 MB) .init : 0x00704000 - 0x0073f000 ( 236 kB) .data : 0x0064bb9c - 0x0070009c ( 721 kB) .text : 0x00400000 - 0x0064bb9c (2350 kB) l4lx_irq_timer_startup(0) l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) timer_irq_thread: Starting timer IRQ thread. Calibrating delay using timer specific routine.. 5583.02 BogoMIPS (lpj=27915100) Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Compat vDSO mapped to bfc08000. CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Checking 'hlt' instruction... l4lx | Jumping over 4x 'hlt' at 0x70d47e OK. stop_nmi called restart_nmi called NET: Registered protocol family 16 PCI: Using configuration type 1 Setting up standard PCI resources SCSI subsystem initialized PCI: Probing PCI hardware PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 1180-11bf claimed by ICH4 GPIO PCI: Transparent bridge - 0000:00:1e.0 l4lx | idler0: utcb=0xbff00400 0f.04 l4lx | l4lx_thread_create: Created thread 0f.06 (idler) PCI: Bridge: 0000:00:1e.0 IO window: 2000-2fff MEM window: c0100000-c01fffff PREFETCH window: disabled. NET: Registered protocol family 2 Time: tsc clocksource has been installed. IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered __l4x_ioremap: Requested region at c0080000 [0x400 Bytes] __l4x_ioremap: Mapping physaddr c0080000 [0x400 Bytes, c0080000+000400] to 04c00000+000000 __l4x_ioremap: Requested region at c0100000 [0x8 Bytes] __l4x_ioremap: Mapping physaddr c0100000 [0x8 Bytes, c0100000+001000] to 04c01000+000000 PCI: Firmware left 0000:02:08.0 e100 interrupts enabled, disabling L4 serial driver l4ser_init_ports l4ser: input not enabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Intel(R) PRO/1000 Network Driver - version 7.3.20-k2 Copyright (c) 1999-2006 Intel Corporation. pcnet32.c:v1.33 27.Jun.2006 tsbogend(a)alpha.franken.de eepro100.c:v1.09j-t 9/29/99 Donald Becker eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin < saw(a)saw.sw.com.sg> and others __l4x_ioremap: Requested region at c0100000 [0x1000 Bytes] __l4x_ioremap: Mapping physaddr c0100000 [0x1000 Bytes, c0100000+001000] to 04c02000+000000 eth0: OEM i82557/i82558 10/100 Ethernet, 00:0D:60:35:8F:53, IRQ 3. Board assembly 000000-000, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH4: IDE controller at PCI slot 0000:00:1f.1 ICH4: chipset revision 1 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x1868-0x186f, BIOS settings: hdc:DMA, hdd:pio hda: ST340014A, ATA DISK drive l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. l4lx | l4lx_thread_create: Created thread 0f.07 (IRQ14) ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: LTN486S, ATAPI CD/DVD-ROM drive l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. l4lx | l4lx_thread_create: Created thread 0f.08 (IRQ15) ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 512KiB hda: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100) hda: cache flushes supported hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 > hdc: ATAPI 48X CD-ROM drive, 120kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12. l4lx | l4lx_thread_create: Created thread 0f.09 (IRQ12) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ1) serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode input: AT Translated Set 2 keyboard as /class/input/input0 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Failed to execute 2. Attempting defaults... INIT: version 2.86 booting Clocksource tsc unstable (delta = 95826122 ns) Time: jiffies clocksource has been installed. * udev requires hotplug support, not started. failed! Activating swap...Adding 1052216k swap on /dev/hda7. Priority:-1 extents:1 across:1052216k done. Checking root file system...fsck 1.40-WIP (14-Nov-2006) /dev/hda8: clean, 90992/635232 files, 656505/1269127 blocks done. EXT3 FS on hda8, internal journal Setting the system clock.. modprobe: FATAL: Could not load /lib/modules/2.6.23-l4/modules.dep: No such file or directory Cleaning up ifupdown.... Loading kernel modules...FATAL: Could not load /lib/modules/2.6.23-l4/modules.dep: No such file or directory Loading device-mapper support. Checking file systems...fsck 1.40-WIP (14-Nov-2006) /dev/hda9: clean, 117549/478080 files, 483560/955859 blocks done. Setting kernel variables...done. Mounting local filesystems...kjournald starting. Commit interval 5 seconds EXT3 FS on hda9, internal journal EXT3-fs: mounted filesystem with ordered data mode. done. Activating swapfile swap...done. Setting up networking.... Configuring network interfaces...done. Setting console screen modes and fonts. INIT: Entering runlevel: 2 Starting system log daemon: syslogd. Starting kernel log daemon: klogd. * Not starting internet superserver: no services enabled. Starting OpenBSD Secure Shell server: sshd. Starting periodic command scheduler: crond. ------------------------------------------------------------------------------------ We have found there is a error hint in this message:l4ser: input not enabled!,but we can't find out what caused this,does it the key to our problem? And the linux26.cfg we used as follow: ----------------------------------------------------------------------------------- modpath "(hda0,7)/boot/L4Linux/" task "vmlinux" " earlyprintk=yes console=ttyLv0 init=/bin/sh mem=64M video=l4fb root=/dev/hda8 ro" all_sects_writable allow_cli ----------------------------------------------------------------------------------- And our Grub config is: ----------------------------------------------------------------------------------- title L4Linux26/Fiasco-test-23 root (hd0,7) kernel /boot/test-23/bootstrap modaddr 0x06000000 module /boot/test-23/main -nowait -nokdb -serial -serial_esc -comspeed 115200 -comport 1 module /boot/test-23/sigma0 module /boot/test-23/roottask task modname "bmodfs" attached 4 modules module /boot/test-23/events module /boot/test-23/names --events module /boot/test-23/log --events module /boot/test-23/dm_phys --isa=0x00800000 -v --events module /boot/test-23/simple_ts -t 300 --events module /boot/test-23/rtc --events module /boot/test-23/l4io --noirq --events module /boot/test-23/omega0 --l4io module /boot/test-23/loader --fprov=BMODFS linux26.cfg module /boot/test-23/bmodfs module /boot/test-23/vmlinuz module /boot/test-23/linux26.cfg module /boot/test-23/libloader.s.so module /boot/test-23/libld-l4.s.so ---------------------------------------------------------------------------------- Any help is musch appreciated! Ding Ying Best Regards!

2 1

Trouble with semaphore library
by Marc CHALAND 24 Oct '07

24 Oct '07

Hello, I encounter strange problems with semaphore library from l4env. I use a vanillia revision 230 on an intel PIII architecture. After some debugging and tracing, I get the following scenarion : 1. thread 03 of my process calls a semaphore down timed which then calls BLOCKTIMED IPC to semaphore thread 02. So semaphore structure is: counter = -1 pending = 0 queue = 03 2. thread 08 calls semaphore_up inline assembler code. Before IPC call, the semaphore structure is as follow : counter = 0 pending = 0 queue = 03 3. Thread 03 gains the CPU after timeout and calls IPC RELEASETIMED : counter = 1 pending = 0 queue = empty 4. Thread 02 doesn't find thread into queue, so that pending is set to 1. counter = 1 pending = 1 queue = empty 5. Thread 03 calls semaphore_down. No IPC is called. counter = 0 pending = 1 queue = empty 6. Thread 03 calls semaphore_down again and IPC BLOCK is called. IPC awakes imediately 03 with a counter value of -1 and nobody into queue. counter = -1 pending = 0 queue = empty It seems to me that this state is not normal. Do you agree ? Is this scenario possible as I observe clearly state 4 5 and 6 ? What pending is for ? Thanks in advance for your answers. Marc

3 8

Re: l4-hackers Digest, Vol 54, Issue 9
by 丁莹 17 Oct '07

17 Oct '07

2007/10/16, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de>: > > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: The keyboard problems (Adam Lackorzynski) > 2. Re: L4Linux and weird newlines (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Oct 2007 00:30:30 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: The keyboard problems > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20071015223030.GR19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Mon Oct 15, 2007 at 12:18:37 +0800, ???? wrote: > > My keyboard is the normal ps/2 AT keyboard and I have enabled the all > kind > > of keyboard drivers in l4linux,but the things again,the state is that I > have > > logged in the l4linux and the prompt have appeared,but the cursor is > > flashing in the head of the prompt,not in the back of the #.And I have > try > > the init=/bin/sh option in my command line ,but the keyboard isn't > working > > as before.The attachment is my l4linux's configuration file.Thanks a lot > for > > you help! > > So, looking at the config file, you neither have VGA_CONSOLE switched on > nor L4_FB_DRIVER. So how does your setup look like? I guess that's why > you're actually not seeing anything really useful on the screen. So how > about enabling VGA_CONSOLE? > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ I hava enabled the VGA_CONSOLE,and could saw some chang when starting,just like some words's color turned normal,but the keyboard didn't working sitll.Then I enable the L4_FB_DRIVER,but it can't compile right,the error message like this: arch/l4/kernel/main.c:80:5: warning: #warning WARNING: L4FB enabled and also CONFIG_SERIO_I8042 or CONFIG_SERIO_LIBPS2 or CONFIG_VGA_CONSOLE arch/l4/kernel/main.c:81:5: error: #error WARNING: This is usually not wanted. make[1]: *** [arch/l4/kernel/main.o] error 1 make: *** [arch/l4/kernel] error 2 and I used ubuntu-6.06 with gcc version gcc-4.0.3. There seems some problem in my configuration,but I can't solve it. Could you show me with your l4linux config file? Best Regards! ding ------------------------------ > > Message: 2 > Date: Tue, 16 Oct 2007 00:32:50 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: L4Linux and weird newlines > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20071015223250.GS19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Mon Oct 15, 2007 at 09:38:35 +0200, Stefan Scheler wrote: > > I'm getting lots of weird newlines in L4Linux. Where do they come from > > and how do I turn them of? Here's a simple example which shows the > problem: > > > > localhost ~ # dd if=/dev/urandom of=/dev/null count=100 > > 100+0 records in > > 100+0 records out > > 51200 bytes (51 kB) copied, 0.0262116 s, 2.0 MB/s > > localhost ~ # dd if=/dev/urandom of=/dev/null count=1000 > > > > > > 1000+0 records in > > 1000+0 records out > > 512000 bytes (512 kB) copied, 0.274718 s, 1.9 MB/s > > localhost ~ # dd if=/dev/urandom of=/dev/null count=2000 > > > > > > > > 2000+0 records in > > 2000+0 records out > > > > 1024000 bytes (1.0 MB) copied, 0.580115 s, 1.8 MB/s > > localhost ~ # > > > > The higher the count value is, the more new lines I get. It's often > > impossible to see any actual output messages. > > I'm occasionally seeing this with slow hosts on Fiasco-UX. What's your > setup? > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 54, Issue 9 > ***************************************** >

2 1

L4Linux and weird newlines
by Stefan Scheler 17 Oct '07

17 Oct '07

Hello, I'm getting lots of weird newlines in L4Linux. Where do they come from and how do I turn them of? Here's a simple example which shows the problem: localhost ~ # dd if=/dev/urandom of=/dev/null count=100 100+0 records in 100+0 records out 51200 bytes (51 kB) copied, 0.0262116 s, 2.0 MB/s localhost ~ # dd if=/dev/urandom of=/dev/null count=1000 1000+0 records in 1000+0 records out 512000 bytes (512 kB) copied, 0.274718 s, 1.9 MB/s localhost ~ # dd if=/dev/urandom of=/dev/null count=2000 2000+0 records in 2000+0 records out 1024000 bytes (1.0 MB) copied, 0.580115 s, 1.8 MB/s localhost ~ # The higher the count value is, the more new lines I get. It's often impossible to see any actual output messages. Any help greatly appreciated. -- Stefan Scheler

2 3

about the L4Linux scheduler
by Lin 17 Oct '07

17 Oct '07

Hello. I have some questions about the scheduler system on DROPS L4Linux. I would like your help or some hints. The version of my source is ... DROPS SVN revision : 205 L4Linux SVN revision : 61 Fiasco version : 1.2 L4Linux version : 2.6.22 In L4Linux system (on L4Env), there are two schedulers (in Fiasco and in Linux server), you know. Some papers say any Linux user process consists of L4 task and the L4 shceduler schedules all L4 thread. It is ok, but I can't understand the work of the Linux scheduler. In fact, a new thread is created in L4 when a process (has one thread) is created in Linux, and the active thread is changed when the context switch occurs in Linux server (made sure by using Fiasco JDB). I want to make this relation clear. In other words, what does the Linux scheduler do at these time. 1. Task creating ~~~~~~~~~~~~~~~~ When "fork()" (or such functions) is called, the function: l4x_setup_next_exec (in "arch/l4/kernel/arch-i386/dispatch.c") may be called. This function seems push the argument function "ret_from_fork" to the stack of the new "task_struct" instance to execute it first when the task is scheduled. Then, when "fork()" ends (when "do_fork()" returns), the new "task_struct" instance is created in Linux system. At this time, is the L4 thread (task ?) corresponds to that "task_struct" is not created yet ? (I assume it is created after the "task_struct" is scheduled.) 2. Linux server's scheduling ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In L4Linux task, there are 7 threads and IRQ threads: (1)l4lx.rm (2)l4lx.sem (3)l4lx.main (4)l4lx.tamer (5)l4lx.cpu0 (6)l4lx.timer.i0 (7)l4lx.idler ... "l4lx.main" creates "l4lx.cpu0" (Linux server) and waits this end. "l4lx.cpu0" does many initialization in the function "start_kernel()", and then it reaches at the function: l4x_idle (in "arch/l4/kernel/dispatch.c"). In this function, the Linux server creates the thread "l4lx.idler" and then enters the scheduling and IPC waiting loop. What does this function do ?? (My expectation about it is written in 4.) And more, What is the thread "l4lx.idler" used for ?? 3. Scheduled new Linux task ~~~~~~~~~~~~~~~~~~~~~~~~~~~ The function "switch_to()" (depends on L4 arch) in Linux kernel only saves and restores the registers ESI, ..., ESP, and EIP. So, when all new created "task_struct"s are scheduled by the Linux server, they runs from "ret_from_fork" as the Linux server thread. (Is it right ?) ^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ "ret_from_fork" reaches at the function: l4x_user_dispatcher (in "arch/l4/kernel/dispatch.c"). It calls "l4x_spawn_cpu_thread()" before its loop. I assume it creates the new L4 thread corresponds to the now scheduled "task_struct" in Linux server. And, the loop in "l4x_user_dispatcher" seems to reply or wait page fault, exception and system call IPCs from any L4 thread runs as a Linux user task. What does this loop do in fact ?? When the context switch occurs in Linux server for some reasons, the active L4 thread is also switched almost at the same time. (I see it by using "ps" on Linux and the thread list of JDB on L4.) I want to know the mechanism of this synchronization. 4. Summary ~~~~~~~~~~ My main quiestions is ... (1) What is "l4lx.idler" created for ? (in 2) (2) What does the function "l4x_idle" do ? (in 2) (3) Do all Linux user tasks ("task_struct" instance) only execute "l4x_user_dispatcher" (from "ret_from_fork") as the Linux server ? (in 1 and 3) (4) What does the function "l4x_user_dispatcher" do ? How to switch contexts in Linux and in L4 almost at the same time ? (in 3) My expectation about Linux scheduling system is the following: - When there is no need to reschedule Linux user processes, Linux server is in IPC sleep and waiting the wakeup IPC in "l4x_idle". - If Linux server gets IPC for some reasons, it wakes up and check the IPC sender. Then, if the sender is a thread corresponds to certain Linux task, Linux server wakes up this Linux task and reschedules by calling "schedule()". - The waked up task will be active as Linux server. This context may execute only "l4x_user_dispatcher" which replies and wait IPCs and handles page faults and exceptions based on information of the received IPC. - When the L4 thread of the Linux task exits, that Linux task in Linux (task_struct instance) also is freed. If there is no schedulable task in Linux at that time, the original context (executes "l4x_idle") is re-scheduled. If you find my incorrect understanding, please tell me. Sorry for my poor English and lengthy question. I'm glad if you give me some hints or corrections. Regards, Lin (a college student in Japan)

2 5

The keyboard problems
by 丁莹 16 Oct '07

16 Oct '07

Hi,adam! My keyboard is the normal ps/2 AT keyboard and I have enabled the all kind of keyboard drivers in l4linux,but the things again,the state is that I have logged in the l4linux and the prompt have appeared,but the cursor is flashing in the head of the prompt,not in the back of the #.And I have try the init=/bin/sh option in my command line ,but the keyboard isn't working as before.The attachment is my l4linux's configuration file.Thanks a lot for you help! Best Regards! ding

2 1

why the keyboard can't use?
by 丁莹 14 Oct '07

14 Oct '07

Hi!all I recompiled l4linux-2.6.22 and disabled any dope options,then started l4linux in console ttyLv0,38400,and the prompt appeared,but the keybodard can't using.I have choosed the keyboard options,but the problem is still,what problem causing that?Everyone know this,please help me!Thanks a lot! Best Regards!

2 1

what console options should using in the linux26.cfg
by 丁莹 14 Oct '07

14 Oct '07

Hi!all When I want to start the l4linux in serial port and used console options as this:console=ttyS0,115200,There is some strange message appeared both in serial port and native screen as follow: io | Available IRQs=[ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f 10 11 ] l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.22-l4 (cheng@dingy-desktop) (gcc version 4.0.3(Ubu l4lx : ntu 4.0.3-1ubuntu5)) #3 Wed Oct 10 11:43:39 CST 2007 l4lx | Binary name: vmlinuz l4lx | Kernel command line (6 args): earlyprintk=yes console=ttyS0,115200 in l4lx : it=2 mem=64M root=/dev/hda2 ro l4lx | Console output set to ttySx. Not recommended. And then I changed console options in linux26.cfg to:console=ttyLv0,38400,It showed the right l4 start message just like: ............................................................................................. l4lx | l4lx_irq_dev_startup_hw:Starting IRQ thread for IRQ 12. l4lx | l4lx_thread_create:Created thread 0f.0a(IRQ12) l4lx | l4lx_irq_dev_startup_hw:Starting IRQ thread for IRQ 1. l4lx | l4lx_thread_create:Created thread 0f.0a(IRQ1) l4lx | l4lx_irq_dev_startup_hw:Starting IRQ thread for IRQ 11. l4lx | l4lx_thread_create:Created thread 0f.0a(IRQ11) in last,but It can't turn to the l4linux starting,What the problem? Eeveryone know this please help me,Thanks a lot! Best Regards!

2 1

Fwd: The problem of grub-0.97 install
by li fei 14 Oct '07

14 Oct '07

---------- Forwarded message ---------- From: li fei <tezuka158(a)gmail.com> Date: 2007-10-12 下午12:00 Subject: The problem of grub-0.97 install To: l4 <l4-hackers(a)os.inf.tu-dresden.de> Hi!all, When I compiled the grub, I met some problems. I patched the patches which I down from the http://os.inf.tu-dresden.de/~adam/grub/0.97/<http://os.inf.tu-dresden.de/%7Eadam/grub/0.97/> . I patched the patches from the grub-0.97-os.1.diff to the grub-0.97-grub-0.97-os.5.diff, and I found they all have mistakes, the error from the grub-0.97-os.2.diff to the grub-0.97-os.5 were the same.Below are the errors: pre_stage2_exec-bios.o : In function `get_cdinfo': /home/l4/Desktop/grub-0.97/stage2/bios.c:179: undefined reference to `__stack_chk_fail' pre_stage2_exec-bios.o: In function `get_diskinfo': /home/l4/Desktop/grub- 0.97/stage2/bios.c:317: undefined reference to `__stack_chk_fail' pre_stage2_exec-boot.o: In function `load_image': /home/l4/Desktop/grub-0.97/stage2/boot.c:759: undefined reference to `__stack_chk_fail' pre_stage2_exec-builtins.o: In function `blocklist_func': /home/l4/Desktop/grub-0.97/stage2/builtins.c:224: undefined reference to `__stack_chk_fail' pre_stage2_exec-builtins.o: In function `embed_func': /home/l4/Desktop/grub-0.97/stage2/builtins.c:1191: undefined reference to `__stack_chk_fail' pre_stage2_exec-builtins.o:/home/l4/Desktop/grub-0.97/stage2/builtins.c:1350: more undefined references to `__stack_chk_fail' follow collect2: ld returned 1 exit status make[2]: *** [pre_stage2.exec] Error 1 make[2]: Leaving directory `/home/l4/Desktop/grub-0.97/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/l4/Desktop/grub- 0.97' make: *** [all] Error 2 And the error when I patched the grub-0.97-os.1.diff is different. The error is below: builtins.c: In function 'vbeset_func': builtins.c :4891: warning: pointer targets in passing argument 1 of 'get_vbe_pmif' differ in signedness builtins.c:4891: warning: pointer targets in passing argument 2 of 'get_vbe_pmif' differ in signedness builtins.c: In function 'toggle_func': builtins.c:5463: error: invalid storage class for function 'process_var' builtins.c:5463: warning: no previous prototype for 'process_var' builtins.c:5523: error: invalid storage class for function 'process_block' builtins.c:5523: warning: no previous prototype for 'process_block' builtins.c: In function 'toggle_trigger_init': builtins.c:5744: error: invalid storage class for function 'detect_vmware' builtins.c:5744: warning: no previous prototype for 'detect_vmware' make[2]: *** [pre_stage2_exec- builtins.o] Error 1 make[2]: Leaving directory `/home/l4/grub-0.97/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/l4/grub-0.97' make: *** [all] Error 2 I compiled the grub under the ubuntu 7.04 environment, using the gcc-4.1.2and g++- 4.1.2.

2 1

Capability based L4
by Luke A. Guest 08 Oct '07

08 Oct '07

Hi, I'm interested in seeing how capabilities work in a real OS kernel and was wondering if there is any source or documents available that I could read? Preferably not the Haskell stuff as I just don't get it :( Is there an implementation of L4.sec? The spec seems like it's missing stuff, is there an update anywhere? Thanks, Luke.

2 1

Re: the problems of l4linux
by Adam Lackorzynski 08 Oct '07

08 Oct '07

On Wed Sep 19, 2007 at 09:01:38 +0000, chenggh wrote: > > Looks the same as the other mail. Enter helps? Actually, what do you > > expect to see? :) > Thanks. > I also read another mail with the same situation. I use Slackware 12.0 not > Ubuntu because in Ubuntu there is a glibc bug which has been existed at least > for more than half year - "undefined reference to __stack_chk_fail". This bug > has been reported many times and has committed to the Ubuntu Bug List. But > bug is as before. That's no bug, it's a stack protection feature they use. I didn't really care because I do not use Ubuntu myself but I think we have to work around this. > The first question: > the l4 boot log is like this: > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > l4lx | acquire_irq: Error attaching to IRQ 2 > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > l4lx | acquire_irq: Error attaching to IRQ 1 > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some errors > like "acquire_irq: Error attaching to IRQ x". But later attaching IRQ is ok. > What is the matter? IRQ1 and IRQ12 are related with keyboard and monse, IRQ2 > is related with cascade, IRQ9 is about acpi. I have removed these drivers > from linux. why is it also like this? Think about who is supposed to have these IRQs. Keyboard and Mouse are already taken by the windowing/console system, so Linux can obviously not get them. So it is really ok that attaching those IRQs fail, it's supposed to be like this. > The second problem is: > The Linux booting stops at /ect/random-seed to initialize /dev/urandom and > there is no login interface. I have checked the normal linux booting and > after the using /ect/random-seed to initialize /dev/urandom the linux will > finish booting kernel, enter the linux user space "INIT: Entering init X". > So I think it is still the problem of l4linux kernel not the special linux > distribution. Is it right? Same question: Is your Slackware starting a login on tty1? What happens with normal Linux? You may want to disable your X for the test and check your /etc/inittab. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 1

cvs down?
by Bérczi Gábor 07 Oct '07

07 Oct '07

Greets, cvs [update aborted]: connect to os.inf.tu-dresden.de(141.76.48.99): 2401 failed: Connection refused -- Bérczi Gábor (Gabucino / ex-MPlayer Core Team) http://www.gabucino.be/

2 2

l4linux-2.6.22 starting
by 丁莹 07 Oct '07

07 Oct '07

Hi,everyone: Is there anybody have started the latest l4linux-2.6.22 on slackware 12.0? I do the job these days,but I couldn't start it,and the problem is strange.When I start the l4linux ,the dope is OK and the l4linux has started ,but finally the l4linux will stop with following error message: l4dope | SharedMem(get_adr): address = 0x21000 l4dope | dope: paddr=88000000 size=8000KiB l4dope | Mapped video memory at 88000000 to 00800000+000000 [8000kB] via L4IO l4dope | mapping: vaddr=0x800000 size=8192000(0x7d0000) offset=0(0x0) l4dope | Frame buffer base: 0x800000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4dope | SharedMem(alloc): hl.raw=100000, id=82, size=96000 l4dope | SharedMem(get_adr): address = 0x400000 l4lx | l4lx_thread_create: Created thread 0f.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 0f.09 (L4DOpEinput) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ14) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ15) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12. l4lx | acquire_irq: Error attaching to IRQ 12 l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ12) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. l4lx | acquire_irq: Error attaching to IRQ 1 l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ1) l4dope | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, l4dope : might be trying access hardware directly. l4dope | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, l4dope : might be trying access hardware directly. l4dope | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, l4dope : might be trying access hardware directly. l4dope | atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, l4dope : might be trying access hardware directly. And I have disable the keyboard and mouse when compiling the l4linux.Butwhen I put this binary which compilered on slackware 12.0 to ubuntu 6.06,the l4linux-2.6.22 started ,and some other people have tested it on Qmenu,its also started ,my binary have put to the ftp://mirror.lzu.edu.cn/temp.Everyone who intresting in it could test it. So may be it is the problem with slackware 12.0 inittab? But I can't fix it,i am just a new both in l4linux and linux.The slackware 12.0 inittab is as follow: # # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Version: @(#)inittab 2.04 17/05/93 MvS # 2.10 02/10/95 PV # 3.00 02/06/1999 PV # 4.00 04/10/2002 PV # # Author: Miquel van Smoorenburg, <miquels(a)drinkel.nl.mugnet.org> # Modified by: Patrick J. Volkerding, <volkerdi(a)slackware.com> # # These are the default runlevels in Slackware: # 0 = halt # 1 = single user mode # 2 = unused (but configured the same as runlevel 3) # 3 = multiuser mode (default Slackware runlevel) # 4 = X11 with KDM/GDM/XDM (session managers) # 5 = unused (but configured the same as runlevel 3) # 6 = reboot # Default runlevel. (Do not set to 0 or 6) id:5:initdefault: # System initialization (runs when system boots). si:S:sysinit:/etc/rc.d/rc.S # Script to run when going single user (runlevel 1). su:1S:wait:/etc/rc.d/rc.K # Script to run when going multi user. rc:2345:wait:/etc/rc.d/rc.M # What to do at the "Three Finger Salute". ca::ctrlaltdel:/sbin/shutdown -t5 -r now # Runlevel 0 halts the system. l0:0:wait:/etc/rc.d/rc.0 # Runlevel 6 reboots the system. l6:6:wait:/etc/rc.d/rc.6 # What to do when power fails. pf::powerfail:/sbin/genpowerfail start # If power is back, cancel the running shutdown. pg::powerokwait:/sbin/genpowerfail stop # These are the standard console login getties in multiuser mode: c1:1235:respawn:/sbin/agetty 38400 tty1 linux c2:1235:respawn:/sbin/agetty 38400 tty2 linux c3:1235:respawn:/sbin/agetty 38400 tty3 linux c4:1235:respawn:/sbin/agetty 38400 tty4 linux c5:1235:respawn:/sbin/agetty 38400 tty5 linux c6:12345:respawn:/sbin/agetty 38400 tty6 linux # Local serial lines: #s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100 #s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100 # Dialup lines: #d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100 #d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100 # Runlevel 4 used to be for an X window only system, until we discovered # that it throws init into a loop that keeps your load avg at least 1 all # the time. Thus, there is now one getty opened on tty6. Hopefully no one # will notice. ;^) # It might not be bad to have one text console anyway, in case something # happens to X. x1:4:respawn:/etc/rc.d/rc.4 export XMODIFIERS="@im=fcitx" export XIM=fcitx # End of /etc/inittab Everybody know this please give me a help,Thanks a lot! Best Regards!

2 1

Re: the problems of l4linux
by chenggh 01 Oct '07

01 Oct '07

> When using ttyLv0 as a console you also need to start a getty there, > similar to an ttyS0 entry. Otherwise no login prompt will appear there. > My inittab looks a bit different but I don't see some obvious reasons > why yours isn't popping up a login-prompt on tty1, at least on the first > glance. > Just booting to single user mode works? Not yet. This time without dope in ttyLv0 the booting log is: proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) Starting udevd: /sbin/udevd --daemon error initializing netlink socket Triggering udev events: /sbin/udevtrigger Adding 491864k swap on /dev/hda1. Priority:-1 extents:1 across:491864k Setting system time from the hardware clock (localtime). Testing root filesystem status: read-write filesystem *** ERROR: Root partition has already been mounted read-write. Cannot check! For filesystem checking to work properly, your system must initially mount the root partition as read only. Please modify your kernel with 'rdev' so that it does this. If you're booting with LILO, add a line: read-only to the Linux type 'lilo' to reinstall it. If you boot from a kernel on a floppy disk, put it in the drive and type: rdev -R /dev/fd0 1 If you boot from a bootdisk, or with Loadlin, you can add the 'ro' flag. This will fix the problem *AND* eliminate this annoying message Press ENTER to continue. But now I can't use keyboard. I have tried to make l4linux with keyboard module and without keyboard module twice. I can't still use keyboard, too. What is the matter? Cheng Guanghui

2 1

The ultimate HOW-TO
by ComputerScienceStudent 01 Oct '07

01 Oct '07

<?xml version="1.0" encoding="UTF-8"?> @page { size: 20.999cm 29.699cm; margin-top: 2cm; margin-bottom: 2cm; margin-left: 2cm; margin-right: 2cm } table { border-collapse:collapse; border-spacing:0; empty-cells:show } td, th { vertical-align:top; } h1, h2, h3, h4, h5, h6 { clear:both } ol, ul { padding:0; } * { margin:0; } *.Caption { font-family:'Thorndale AMT'; font-size:12pt; margin-top:0.212cm; margin-bottom:0.212cm; font-style:italic; } *.Heading { font-family:'Albany AMT'; font-size:14pt; margin-top:0.423cm; margin-bottom:0.212cm; } *.Index { font-family:'Thorndale AMT'; font-size:12pt; } *.List { font-family:'Thorndale AMT'; font-size:12pt; margin-top:0cm; margin-bottom:0.212cm; } *.P1 { font-family:'Thorndale AMT'; font-size:12pt; } *.P2 { font-family:'Thorndale AMT'; font-size:12pt; } *.P3 { font-family:'Thorndale AMT'; font-size:12pt; margin-left:1.251cm; margin-right:0cm; text-indent:0cm; } *.P4 { font-family:'Thorndale AMT'; font-size:12pt; margin-left:0cm; margin-right:0cm; text-indent:0cm; } *.Standard { font-family:'Thorndale AMT'; font-size:12pt; } *.Textbody { font-family:'Thorndale AMT'; font-size:12pt; margin-top:0cm; margin-bottom:0.212cm; } *.BulletSymbols { font-family:StarSymbol; font-size:9pt; } *.NumberingSymbols { } *.T1 { vertical-align:sup; } *.T2 { } Hi all!! These are the sources that I've downloaded (and where I've placed them): /root/l4-linux-2.6 /root/l4-linux-2.6-env /root/fiasco /root/l4env /root/hello I want to install L4Linux creating an entry on GRUB, because I've to work also with Suse 10.2 and Windows XP (the OSs installed on my notebook), but I haven't do anything similar in my own life! My question is: how to install L4Linux? Meaning: How to compiling, building and in what order? How to modifying the GRUB bootloader to preserve my old configuration of OSs? What I would like to have is that at the boot, the bootloader ask me if I want to go in Suse, Windows or L4Linux.. Thank a lot for every suggestion you'll give me!! PS. Once that I've do all my jobs -is a research for an universitary course- can I return to have only Suse 10.2 and Windows XP? -- View this message in context: http://www.nabble.com/The-ultimate-HOW-TO-tf4192072.html#a11921435 Sent from the L4 mailing list archive at Nabble.com.

3 46

error report
by chenggh 26 Sep '07

26 Sep '07

Hi: When compiling dde_linux26 there are some errors like this: In file included from /home/L4/tudos/l4/build/include/x86/l4/linux-26-headers/asm/thread_info.h:16, from /home/L4/tudos/l4/build/include/l4/linux-26-headers/linux/thread_info.h:21, from /home/L4/tudos/l4/build/include/l4/dde_linux26/linux/spinlock.h:12, from /home/L4/tudos/l4/build/include/l4/linux-26-headers/linux/mmzone.h:8, from /home/L4/tudos/l4/build/include/l4/linux-26-headers/linux/gfp.h:4, from /home/L4/tudos/l4/build/include/l4/dde_linux26/linux/slab.h:15, from /home/L4/tudos/l4/pkg/dde_linux26/lib/src/mm.c:46: /home/L4/tudos/l4/build/include/x86/l4/linux-26-headers/asm/processor.h:86: error: array type has incomplete element type make[3]: *** [mm.o] Error 1 make[3]: Leaving directory `/home/L4/tudos/l4/build/pkg/dde_linux26/lib/src/OBJ-x86_586-l4v2' make[2]: *** [/home/L4/tudos/l4/build/pkg/dde_linux26/lib/src/OBJ-x86_586-l4v2] Error 2 make[2]: Leaving directory `/home/L4/tudos/l4/pkg/dde_linux26/lib/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/L4/tudos/l4/pkg/dde_linux26/lib' make: *** [lib] Error 2 Cheng Guanghui

4 3

Re: the problems of l4linux
by Adam Lackorzynski 22 Sep '07

22 Sep '07

On Thu Sep 20, 2007 at 17:59:41 +0000, chenggh wrote: > > > __stack_chk_fail". This bug has been reported many times and has > > > committed to the Ubuntu Bug List. But bug is as before. > > > > That's no bug, it's a stack protection feature they use. I didn't really > > care because I do not use Ubuntu myself but I think we have to work > > around this. > Yes, basically it is not a bug but I should have used fno-stack-protector to > fix the problem. But later I found although I use fno-stack-protector the > problem is still. I google the key word __stack_chk_fail and there are lots > of people with same problem as me. So I think it is a bug of glic problem. If google finds many pages with something this doesn't mean all those pages show the truth just because they are so many. Using -fno-stack-protector is fine as long as _all_ code is compiled with this option. When linking against code that is built _with_ the stack-protection feature enabled that compile time option won't help you. This happens e.g. when linking against libraries supplied by gcc. On Ubuntu those libraries are built with the stack protection feature enabled. To fix this you either rebuild gcc-libs with stack protection or provide those symbols. The latter seems far more convenient. > > > The first question: > > > the l4 boot log is like this: > > > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > > > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > > > l4lx | acquire_irq: Error attaching to IRQ 2 > > > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > > l4lx | acquire_irq: Error attaching to IRQ 1 > > > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some > > > errors like "acquire_irq: Error attaching to IRQ x". But later attaching > > > IRQ is ok. What is the matter? IRQ1 and IRQ12 are related with keyboard > > > and monse, IRQ2 is related with cascade, IRQ9 is about acpi. I have > > > removed these drivers from linux. why is it also like this? > > Think about who is supposed to have these IRQs. Keyboard and Mouse are > > already taken by the windowing/console system, so Linux can obviously > > not get them. So it is really ok that attaching those IRQs fail, it's > > supposed to be like this. > Thanks. I think I should read the l4linux code and later if I encouter the > similar question I could understand. :) > > > The second problem is: > > > The Linux booting stops at /ect/random-seed to initialize /dev/urandom > > > and there is no login interface. I have checked the normal linux booting > > > and after the using /ect/random-seed to initialize /dev/urandom the linux > > > will finish booting kernel, enter the linux user space "INIT: Entering > > > init X". So I think it is still the problem of l4linux kernel not the > > > special linux distribution. Is it right? > > > > Same question: Is your Slackware starting a login on tty1? What happens > > with normal Linux? You may want to disable your X for the test and check > > your /etc/inittab. > Not ,the problem is also. I disable X and try to boot l4linux on ttyLv0. The > Linux also stops here "/ect/random-seed to initialize /dev/urandom". There is > an attachment which is my inittab. When using ttyLv0 as a console you also need to start a getty there, similar to an ttyS0 entry. Otherwise no login prompt will appear there. My inittab looks a bit different but I don't see some obvious reasons why yours isn't popping up a login-prompt on tty1, at least on the first glance. Just booting to single user mode works? > # > # inittab This file describes how the INIT process should set up > # the system in a certain run-level. > # > # Version: @(#)inittab 2.04 17/05/93 MvS > # 2.10 02/10/95 PV > # 3.00 02/06/1999 PV > # 4.00 04/10/2002 PV > # > # Author: Miquel van Smoorenburg, <miquels(a)drinkel.nl.mugnet.org> > # Modified by: Patrick J. Volkerding, <volkerdi(a)slackware.com> > # > > # These are the default runlevels in Slackware: > # 0 = halt > # 1 = single user mode > # 2 = unused (but configured the same as runlevel 3) > # 3 = multiuser mode (default Slackware runlevel) > # 4 = X11 with KDM/GDM/XDM (session managers) > # 5 = unused (but configured the same as runlevel 3) > # 6 = reboot > > # Default runlevel. (Do not set to 0 or 6) > id:3:initdefault: > > # System initialization (runs when system boots). > si:S:sysinit:/etc/rc.d/rc.S > > # Script to run when going single user (runlevel 1). > su:1S:wait:/etc/rc.d/rc.K > > # Script to run when going multi user. > rc:2345:wait:/etc/rc.d/rc.M > > # What to do at the "Three Finger Salute". > ca::ctrlaltdel:/sbin/shutdown -t5 -r now > > # Runlevel 0 halts the system. > l0:0:wait:/etc/rc.d/rc.0 > > # Runlevel 6 reboots the system. > l6:6:wait:/etc/rc.d/rc.6 > > # What to do when power fails. > pf::powerfail:/sbin/genpowerfail start > > # If power is back, cancel the running shutdown. > pg::powerokwait:/sbin/genpowerfail stop > > # These are the standard console login getties in multiuser mode: > c1:1235:respawn:/sbin/agetty 38400 tty1 linux > c2:1235:respawn:/sbin/agetty 38400 tty2 linux > c3:1235:respawn:/sbin/agetty 38400 tty3 linux > c4:1235:respawn:/sbin/agetty 38400 tty4 linux > c5:1235:respawn:/sbin/agetty 38400 tty5 linux > c6:12345:respawn:/sbin/agetty 38400 tty6 linux > > # Local serial lines: > #s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100 > #s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100 > > # Dialup lines: > #d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100 > #d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100 > > # Runlevel 4 used to be for an X window only system, until we discovered > # that it throws init into a loop that keeps your load avg at least 1 all > # the time. Thus, there is now one getty opened on tty6. Hopefully no one > # will notice. ;^) > # It might not be bad to have one text console anyway, in case something > # happens to X. > x1:4:respawn:/etc/rc.d/rc.4 > > # End of /etc/inittab > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

O.S. question
by huang 22 Sep '07

22 Sep '07

dear Adam: Could you tell me the debain version that you are using now! And are there any other things about compilation environment I should pay attentation to? I want to use the same compilation environment as yours! :) thanks a lot! Best wishes! huang

2 1

Re: the problems of l4linux
by chenggh 20 Sep '07

20 Sep '07

> > __stack_chk_fail". This bug has been reported many times and has > > committed to the Ubuntu Bug List. But bug is as before. > > That's no bug, it's a stack protection feature they use. I didn't really > care because I do not use Ubuntu myself but I think we have to work > around this. Yes, basically it is not a bug but I should have used fno-stack-protector to fix the problem. But later I found although I use fno-stack-protector the problem is still. I google the key word __stack_chk_fail and there are lots of people with same problem as me. So I think it is a bug of glic problem. > > The first question: > > the l4 boot log is like this: > > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > > l4lx | acquire_irq: Error attaching to IRQ 2 > > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > l4lx | acquire_irq: Error attaching to IRQ 1 > > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some > > errors like "acquire_irq: Error attaching to IRQ x". But later attaching > > IRQ is ok. What is the matter? IRQ1 and IRQ12 are related with keyboard > > and monse, IRQ2 is related with cascade, IRQ9 is about acpi. I have > > removed these drivers from linux. why is it also like this? > Think about who is supposed to have these IRQs. Keyboard and Mouse are > already taken by the windowing/console system, so Linux can obviously > not get them. So it is really ok that attaching those IRQs fail, it's > supposed to be like this. Thanks. I think I should read the l4linux code and later if I encouter the similar question I could understand. :) > > The second problem is: > > The Linux booting stops at /ect/random-seed to initialize /dev/urandom > > and there is no login interface. I have checked the normal linux booting > > and after the using /ect/random-seed to initialize /dev/urandom the linux > > will finish booting kernel, enter the linux user space "INIT: Entering > > init X". So I think it is still the problem of l4linux kernel not the > > special linux distribution. Is it right? > > Same question: Is your Slackware starting a login on tty1? What happens > with normal Linux? You may want to disable your X for the test and check > your /etc/inittab. Not ,the problem is also. I disable X and try to boot l4linux on ttyLv0. The Linux also stops here "/ect/random-seed to initialize /dev/urandom". There is an attachment which is my inittab. Thanks. Cheng Guanghui

1 0

Re: l4-hackers Digest, Vol 53, Issue 22
by 丁莹 20 Sep '07

20 Sep '07

2007/9/19, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de>: > > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: The ultimate HOW-TO (Adam Lackorzynski) > 2. Re: l4linux starting problem (Adam Lackorzynski) > 3. Re: the problems of l4linux (Adam Lackorzynski) > 4. Re: the problems of l4linux (chenggh) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 19 Sep 2007 00:11:06 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: The ultimate HOW-TO > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070918221106.GD19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Tue Sep 18, 2007 at 08:05:18 -0700, ComputerScienceStudent wrote: > > > > Maybe this is the longest email you'll receive, but I would give you all > the > > possible informations. > > There are three sections: > > - THE MAKE ERRORS > > - L4LINUX CONFIGURATION > > - HARDWARE INFO. > > Ok, looks like you took your Linux configuration from your host (or the > configuration system did so). Please use the default configuration > coming with L4Linux by starting with 'make x86-native_defconfig'. And > then those errors won't occur. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 2 > Date: Wed, 19 Sep 2007 00:17:25 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: l4linux starting problem > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070918221725.GE19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Tue Sep 18, 2007 at 17:34:07 +0800, ???? wrote: > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. > > l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ14) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. > > l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ15) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. > > l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ11) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12. > > l4lx | acquire_irq: Error attaching to IRQ 12 > > l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ12) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > l4lx | acquire_irq: Error attaching to IRQ 1 > > l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ1) > > > > And the dope when starting after following message then dead. > > > > Checking non-root filesystems: > > fsck 1.39 (29-May-2006) > > /dev/hda10:clean, 135991/667808 files,510175/1333387 blocks > > Mounting non-root local filesystems: > > kjournald starting. Commit interval 5 seconds > > EXT3 FS on hda10, internal journal > > EXT3-fs: mounted filesystem with ordered data mode. > > /dev/hda10 on /home type ext3(rw) > > Using /etc/random-seed to initialize /dev/urandom. > > > > How can I solve this problem?Anybody who knows please help me,Thanks! > > Well, userland starts, can't be too bad. Is that Ubuntu? Does a login > prompt appear when you press Enter a bit? > I wonder how the bootup looks like on native Linux (with X disabled). > > No,I use the slackware 12.0,the l4linux system dead when output above > message,so when press enter there is no response,the native Linux when > bootup after this will indicate message: INIT:enter runlevel 3. Best Regards! Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 3 > Date: Wed, 19 Sep 2007 00:19:29 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: the problems of l4linux > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070918221929.GF19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Tue Sep 18, 2007 at 22:02:16 +0000, chenggh wrote: > > Hi: > > I boot l4dope with l4linux. The dope seems ok but l4linux doesn't > start > > completely. I am not sure whether it is l4 problem or linux problem. > Please > > help me. > > > > The l4 boot log > > l4dope | Frame buffer base: 0x4000000 > > l4dope | Resolution: 1024x768x16 > > l4dope | Bytes per scanline: 2048 > > l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 > res=0:0 > > l4lx | ======> L4Linux 2.6 starting... <======== > > l4lx | Linux version 2.6.22-l4 (root@darkstar) (gcc version 4.1.2) #1 > Tue > > Se > > l4lx : p 18 16:36:23 CST 2007 > > l4lx | Binary name: vmlinuz > > l4lx | Kernel command line (5 args): earlyprintk=yes video=l4fb > init=1 > > mem=6 > > l4lx : 4M root=/dev/hda2 > > l4lx | Image: 00400000 - 007a3000 [3724 KiB]. > > l4lx | Areas: Text: 00400000 - 006ad000 > [2740k | Initdata: > > 006cc000 - 00700000 [208kB] > > l4lx | BSS: 00702000 - 007a0f00 [635kB] > > l4lx | l4lx_thread_create: Created thread 10.03 (tamer0) > > l4lx | Tamer0 is 10.03 > > l4lx | Using tamed mode. > > l4lx | Connecting to l4io server. > > l4lx | l4env_linux_startup thread 4. > > l4lx | l4lx_thread_create: Created thread 10.04 (cpu0) > > l4lx | main thread will be 10.04 > > l4lx | l4env_register_pointer_section: addr = 00400000 size = 3149824 > > l4lx | sec-w-init: virt: 0x00400000 to 0x00700fff [3076 KiB] > > l4lx | Noncontiguous region for sec-w-init > > l4lx | sec-w-init: Number of physical regions: 3, 3149824 Bytes > > l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x01218000, > Size: 1630208 > > l4lx | sec-w-init: 2: Phys: 0x01419000 to 0x01500000, Size: > 946176 > > l4lx | sec-w-ini startup message. > > l4lx | Main thread running, waiting... > > l4lx | setup_l4env_memory: Forcing superpages for main memory > > l4lx | Main memory size: 64MB > > l4lx | Got 2048kB of ISA DMA memory. > > l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] > > l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes > > l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, > Size: 2097152 > > l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] > > l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes > > l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: > 67108864 > > l4lx | Filling lower ptabs... > > l4lx | Done (1594 entries). > > l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) > > l4lx | Jumpinl4lx | idler0d_create: Created threadl4lx | > Startil4dope > > | SharedMem(allo0 > > l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) > > l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) > > l4lx | l4lx_iRQ 17. > > l4lx |startup_hw: Starting IRQ16) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. > > l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. > > l4lx tup_hw: Starting IRQ thread for IRQ 13. > > l4lx | l4lx_ting IRQ thread for IRQ 12. > > l4lx | acquire_irq: Error attaching to IRQ 12 > > l4lx | l4lx_thread_create: Created thread 10.0f (IRQ12) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. > > l4lx | l4lx_thread_create: Created thread 10.10 (IRQ11) > > l4lx | l4lx_irq_dev_startp_hw: Starting IRQ thread | > > l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 9. > > l4lx | l4lx_thread_create: Created thread 10.12 (IRQ9) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 8. > > l4lx | l4lx_thread_create: Created thread 10.13 (IRQ8) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 7. > > l4lx | l4lx_thread_create: Created thread 10.14 (IRQ7) > > l4lx | l4lx_irq_dev_startup_hw: Starting thread for IRQ 6. > > l4lx | l4lx_thread_create: Created thread 10.15 (IRQ6) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 5. > > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > > l4lx | acquire_irq: Error attaching to IRQ 2 > > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > > l4lx | acquire_irq: Error attaching to IRQ 1 > > > > I don't know what these information stands for. Are all the > necessary > > interrupt threads ok? Or some of them is not ok. > > Seems ok. Some IRQ probing, 1, 2 and 12 are not allowed which is > perfectly ok. > > > the linux boot log > > ?????? > > EXTS FS on hda3, internal journal > > EXT-fs: mounted filesystem with orderred data mode > > /dev/hda3 on /home type ext3 (rw) > > using /ect/random-seed to initialize /dev/urandom > > > > The linux could stop here even I wait lot of time. It doesn't go > on. > > Looks the same as the other mail. Enter helps? Actually, what do you > expect to see? :) > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 4 > Date: Wed, 19 Sep 2007 09:01:38 +0000 > From: chenggh <chenggh04(a)st.lzu.edu.cn> > Subject: Re: the problems of l4linux > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <390158225.18632(a)st.lzu.edu.cn> > Content-Type: text/plain; charset="iso-8859-1" > > > Looks the same as the other mail. Enter helps? Actually, what do you > > expect to see? :) > Thanks. > I also read another mail with the same situation. I use Slackware > 12.0 not > Ubuntu because in Ubuntu there is a glibc bug which has been existed at > least > for more than half year - "undefined reference to __stack_chk_fail". This > bug > has been reported many times and has committed to the Ubuntu Bug > List. But > bug is as before. > The first question: > the l4 boot log is like this: > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > l4lx | acquire_irq: Error attaching to IRQ 2 > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > l4lx | acquire_irq: Error attaching to IRQ 1 > It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are > some errors > like "acquire_irq: Error attaching to IRQ x". But later attaching IRQ is > ok. > What is the matter? IRQ1 and IRQ12 are related with keyboard and monse, > IRQ2 > is related with cascade, IRQ9 is about acpi. I have removed these drivers > from linux. why is it also like this? > > > The second problem is: > The Linux booting stops at /ect/random-seed to initialize > /dev/urandom and > there is no login interface. I have checked the normal linux booting and > after the using /ect/random-seed to initialize /dev/urandom the linux will > finish booting kernel, enter the linux user space "INIT: Entering init X". > So I think it is still the problem of l4linux kernel not the > special linux > distribution. Is it right? > Thank you very much. > Cheng > Guanghui > > > > ------------------------------ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > End of l4-hackers Digest, Vol 53, Issue 22 > ****************************************** >

2 1

Re: the problems of l4linux
by chenggh 19 Sep '07

19 Sep '07

> Looks the same as the other mail. Enter helps? Actually, what do you > expect to see? :) Thanks. I also read another mail with the same situation. I use Slackware 12.0 not Ubuntu because in Ubuntu there is a glibc bug which has been existed at least for more than half year - "undefined reference to __stack_chk_fail". This bug has been reported many times and has committed to the Ubuntu Bug List. But bug is as before. The first question: the l4 boot log is like this: l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. l4lx | acquire_irq: Error attaching to IRQ 2 l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. l4lx | acquire_irq: Error attaching to IRQ 1 It seems that when attaching IRQ1, IRQ2, IRQ9, IRQ12 there are some errors like "acquire_irq: Error attaching to IRQ x". But later attaching IRQ is ok. What is the matter? IRQ1 and IRQ12 are related with keyboard and monse, IRQ2 is related with cascade, IRQ9 is about acpi. I have removed these drivers from linux. why is it also like this? The second problem is: The Linux booting stops at /ect/random-seed to initialize /dev/urandom and there is no login interface. I have checked the normal linux booting and after the using /ect/random-seed to initialize /dev/urandom the linux will finish booting kernel, enter the linux user space "INIT: Entering init X". So I think it is still the problem of l4linux kernel not the special linux distribution. Is it right? Thank you very much. Cheng Guanghui

1 0

Re: the problems of l4linux
by Adam Lackorzynski 19 Sep '07

19 Sep '07

On Tue Sep 18, 2007 at 22:02:16 +0000, chenggh wrote: > Hi: > I boot l4dope with l4linux. The dope seems ok but l4linux doesn't start > completely. I am not sure whether it is l4 problem or linux problem. Please > help me. > > The l4 boot log > l4dope | Frame buffer base: 0x4000000 > l4dope | Resolution: 1024x768x16 > l4dope | Bytes per scanline: 2048 > l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 > l4lx | ======> L4Linux 2.6 starting... <======== > l4lx | Linux version 2.6.22-l4 (root@darkstar) (gcc version 4.1.2) #1 Tue > Se > l4lx : p 18 16:36:23 CST 2007 > l4lx | Binary name: vmlinuz > l4lx | Kernel command line (5 args): earlyprintk=yes video=l4fb init=1 > mem=6 > l4lx : 4M root=/dev/hda2 > l4lx | Image: 00400000 - 007a3000 [3724 KiB]. > l4lx | Areas: Text: 00400000 - 006ad000 [2740k | Initdata: > 006cc000 - 00700000 [208kB] > l4lx | BSS: 00702000 - 007a0f00 [635kB] > l4lx | l4lx_thread_create: Created thread 10.03 (tamer0) > l4lx | Tamer0 is 10.03 > l4lx | Using tamed mode. > l4lx | Connecting to l4io server. > l4lx | l4env_linux_startup thread 4. > l4lx | l4lx_thread_create: Created thread 10.04 (cpu0) > l4lx | main thread will be 10.04 > l4lx | l4env_register_pointer_section: addr = 00400000 size = 3149824 > l4lx | sec-w-init: virt: 0x00400000 to 0x00700fff [3076 KiB] > l4lx | Noncontiguous region for sec-w-init > l4lx | sec-w-init: Number of physical regions: 3, 3149824 Bytes > l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x01218000, Size: 1630208 > l4lx | sec-w-init: 2: Phys: 0x01419000 to 0x01500000, Size: 946176 > l4lx | sec-w-ini startup message. > l4lx | Main thread running, waiting... > l4lx | setup_l4env_memory: Forcing superpages for main memory > l4lx | Main memory size: 64MB > l4lx | Got 2048kB of ISA DMA memory. > l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] > l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes > l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 > l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] > l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes > l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 > l4lx | Filling lower ptabs... > l4lx | Done (1594 entries). > l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) > l4lx | Jumpinl4lx | idler0d_create: Created threadl4lx | Startil4dope > | SharedMem(allo0 > l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) > l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) > l4lx | l4lx_iRQ 17. > l4lx |startup_hw: Starting IRQ16) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. > l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. > l4lx tup_hw: Starting IRQ thread for IRQ 13. > l4lx | l4lx_ting IRQ thread for IRQ 12. > l4lx | acquire_irq: Error attaching to IRQ 12 > l4lx | l4lx_thread_create: Created thread 10.0f (IRQ12) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. > l4lx | l4lx_thread_create: Created thread 10.10 (IRQ11) > l4lx | l4lx_irq_dev_startp_hw: Starting IRQ thread | > l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 9. > l4lx | l4lx_thread_create: Created thread 10.12 (IRQ9) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 8. > l4lx | l4lx_thread_create: Created thread 10.13 (IRQ8) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 7. > l4lx | l4lx_thread_create: Created thread 10.14 (IRQ7) > l4lx | l4lx_irq_dev_startup_hw: Starting thread for IRQ 6. > l4lx | l4lx_thread_create: Created thread 10.15 (IRQ6) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 5. > l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. > l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. > l4lx | acquire_irq: Error attaching to IRQ 2 > l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) > l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. > l4lx | acquire_irq: Error attaching to IRQ 1 > > I don't know what these information stands for. Are all the necessary > interrupt threads ok? Or some of them is not ok. Seems ok. Some IRQ probing, 1, 2 and 12 are not allowed which is perfectly ok. > the linux boot log > ¡£¡£¡£ > EXTS FS on hda3, internal journal > EXT-fs: mounted filesystem with orderred data mode > /dev/hda3 on /home type ext3 (rw) > using /ect/random-seed to initialize /dev/urandom > > The linux could stop here even I wait lot of time. It doesn't go on. Looks the same as the other mail. Enter helps? Actually, what do you expect to see? :) Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

l4linux starting problem
by 丁莹 19 Sep '07

19 Sep '07

Hi,all: I have meet a problem when I starting l4linux-2.6.22,the error message get from serial port as follow: 4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.22-l4 (root@licy03) (gcc version 4.1.2) #6 Tue Sep l4lx : 18 16:16:49 CST 2007 l4lx | Binary name: vmlinuz l4lx | Kernel command line (5 args): earlyprintk=yes mem=64M video=l4fb root l4lx : =/dev/hda9 ro l4lx | Image: 00400000 - 007ac000 [3760 KiB]. l4lx | Areas: Text: 00400000 - 006ae000 [2744kB] (a bit longer) l4lx | Data: 006ae000 - 006cbf9c [119kB] l4lx | Initdata: 006ce000 - 00709000 [236kB] l4lx | BSS: 0070a000 - 007a9200 [636kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer0) l4lx | Tamer0 is 0f.03 l4lx | Using tamed mode. l4lx | Connecting to l4io server. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (cpu0) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 00400000 size = 3850240 l4lx | sec-w-init: virt: 0x00400000 to 0x007abfff [3760 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 4, 3850240 Bytes l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x01215000, Size: 1617920 l4lx | sec-w-init: 2: Phys: 0x01419000 to 0x01500000, Size: 946176 l4lx | sec-w-init: 3: Phys: 0x01345000 to 0x01400000, Size: 765952 l4lx | sec-w-init: 4: Phys: 0x01281000 to 0x01300000, Size: 520192 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x0a800000 to 0x0e800000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1584 entries). l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) l4lx | Jumping over 4x 'hlt' at 0x6d6eab l4lx | idler0: utcb=0xbff00400 0f.04 l4lx | l4lx_thread_create: Created thread 0f.06 (idler) l4lx | Starting L4FB via DOpE l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 l4dope | input: AT Raw Set 2 keyboard on isa0060/serio0 l4dope | input: PC Speaker l4dope | input: L4 input event injector l4dope | L4 input event injector: IRQ handler up l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 l4dope | connect "AT Raw Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.raw=100000, id=69, size=800 l4dope | SharedMem(get_adr): address = 0x6000 l4dope | SharedMem(alloc): hl.raw=100000, id=6a, size=800 l4dope | SharedMem(get_adr): address = 0x7000 l4dope | SharedMem(alloc): hl.raw=100000, id=6b, size=800 l4dope | SharedMem(get_adr): address = 0xd000 l4dope | SharedMem(alloc): hl.raw=100000, id=6c, size=800 l4dope | SharedMem(get_adr): address = 0xe000 l4dope | SharedMem(alloc): hl.raw=100000, id=6d, size=800 l4dope | SharedMem(get_adr): address = 0xf000 l4dope | SharedMem(alloc): hl.raw=100000, id=6f, size=800 l4dope | SharedMem(get_adr): address = 0x16000 l4dope | SharedMem(alloc): hl.raw=100000, id=70, size=800 l4dope | SharedMem(get_adr): address = 0x17000 l4dope | SharedMem(alloc): hl.raw=100000, id=75, size=484 l4dope | SharedMem(get_adr): address = 0x21000 l4dope | dope: paddr=f0000000 size=131072KiB l4dope | Mapped video memory at f0000000 to 08000000+000000 [131072kB] via L4I l4dope : O l4dope | mapping: vaddr=0x8000000 size=134217728(0x8000000) offset=0(0x0) l4dope | Frame buffer base: 0x8000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4dope | SharedMem(alloc): hl.raw=100000, id=80, size=96000 l4dope | SharedMem(get_adr): address = 0x400000 l4lx | l4lx_thread_create: Created thread 0f.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 0f.09 (L4DOpEinput) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. l4lx | l4lx_thread_create: Created thread 0f.0a (IRQ14) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. l4lx | l4lx_thread_create: Created thread 0f.0b (IRQ15) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. l4lx | l4lx_thread_create: Created thread 0f.0c (IRQ11) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 12. l4lx | acquire_irq: Error attaching to IRQ 12 l4lx | l4lx_thread_create: Created thread 0f.0d (IRQ12) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. l4lx | acquire_irq: Error attaching to IRQ 1 l4lx | l4lx_thread_create: Created thread 0f.0e (IRQ1) And the dope when starting after following message then dead. Checking non-root filesystems: fsck 1.39 (29-May-2006) /dev/hda10:clean, 135991/667808 files,510175/1333387 blocks Mounting non-root local filesystems: kjournald starting. Commit interval 5 seconds EXT3 FS on hda10, internal journal EXT3-fs: mounted filesystem with ordered data mode. /dev/hda10 on /home type ext3(rw) Using /etc/random-seed to initialize /dev/urandom. How can I solve this problem?Anybody who knows please help me,Thanks! Best Regards!

2 1

the problems of l4linux
by chenggh 19 Sep '07

19 Sep '07

Hi: I boot l4dope with l4linux. The dope seems ok but l4linux doesn't start completely. I am not sure whether it is l4 problem or linux problem. Please help me. The l4 boot log l4dope | Frame buffer base: 0x4000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.22-l4 (root@darkstar) (gcc version 4.1.2) #1 Tue Se l4lx : p 18 16:36:23 CST 2007 l4lx | Binary name: vmlinuz l4lx | Kernel command line (5 args): earlyprintk=yes video=l4fb init=1 mem=6 l4lx : 4M root=/dev/hda2 l4lx | Image: 00400000 - 007a3000 [3724 KiB]. l4lx | Areas: Text: 00400000 - 006ad000 [2740k | Initdata: 006cc000 - 00700000 [208kB] l4lx | BSS: 00702000 - 007a0f00 [635kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer0) l4lx | Tamer0 is 10.03 l4lx | Using tamed mode. l4lx | Connecting to l4io server. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (cpu0) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 00400000 size = 3149824 l4lx | sec-w-init: virt: 0x00400000 to 0x00700fff [3076 KiB] l4lx | Noncontiguous region for sec-w-init l4lx | sec-w-init: Number of physical regions: 3, 3149824 Bytes l4lx | sec-w-init: 1: Phys: 0x0108a000 to 0x01218000, Size: 1630208 l4lx | sec-w-init: 2: Phys: 0x01419000 to 0x01500000, Size: 946176 l4lx | sec-w-ini startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1594 entries). l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | Jumpinl4lx | idler0d_create: Created threadl4lx | Startil4dope | SharedMem(allo0 l4lx | l4lx_thread_create: Created thread 10.08 (DOpE refresher) l4lx | l4lx_thread_create: Created thread 10.09 (L4DOpEinput) l4lx | l4lx_iRQ 17. l4lx |startup_hw: Starting IRQ16) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 15. l4lx | l4lx_thread_create: Created thread 10.0c (IRQ15) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 14. l4lx tup_hw: Starting IRQ thread for IRQ 13. l4lx | l4lx_ting IRQ thread for IRQ 12. l4lx | acquire_irq: Error attaching to IRQ 12 l4lx | l4lx_thread_create: Created thread 10.0f (IRQ12) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 11. l4lx | l4lx_thread_create: Created thread 10.10 (IRQ11) l4lx | l4lx_irq_dev_startp_hw: Starting IRQ thread | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 9. l4lx | l4lx_thread_create: Created thread 10.12 (IRQ9) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 8. l4lx | l4lx_thread_create: Created thread 10.13 (IRQ8) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 7. l4lx | l4lx_thread_create: Created thread 10.14 (IRQ7) l4lx | l4lx_irq_dev_startup_hw: Starting thread for IRQ 6. l4lx | l4lx_thread_create: Created thread 10.15 (IRQ6) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 5. l4lx | l4lx_thread_create: Created thread 10.16 (IRQ5) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 4. l4lx | l4lx_thread_create: Created thread 10.17 (IRQ4) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 3. l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 2. l4lx | acquire_irq: Error attaching to IRQ 2 l4lx | l4lx_thread_create: Created thread 10.19 (IRQ2) l4lx | l4lx_irq_dev_startup_hw: Starting IRQ thread for IRQ 1. l4lx | acquire_irq: Error attaching to IRQ 1 I don't know what these information stands for. Are all the necessary interrupt threads ok? Or some of them is not ok. the linux boot log 。。。 EXTS FS on hda3, internal journal EXT-fs: mounted filesystem with orderred data mode /dev/hda3 on /home type ext3 (rw) using /ect/random-seed to initialize /dev/urandom The linux could stop here even I wait lot of time. It doesn't go on. the menu.lst title L4LinuxDope root (hd0,1) kernel /boot/L4/l4dopelinux/bootstrap modaddr 0x06000000 module /boot/L4/l4dopelinux/main -nowait -nokdb -serial -comspeed 115200 -comport 1 module /boot/L4/l4dopelinux/sigma0 module /boot/L4/l4dopelinux/roottask task modname "bmodfs" attached 4 modules module /boot/L4/l4dopelinux/events module /boot/L4/l4dopelinux/names module /boot/L4/l4dopelinux/log module /boot/L4/l4dopelinux/dm_phys --isa=0x00800000 -v --events module /boot/L4/l4dopelinux/simple_ts -t 300 --events module /boot/L4/l4dopelinux/rtc --events module /boot/L4/l4dopelinux/l4io --events module /boot/L4/l4dopelinux/omega0 --l4io module /boot/L4/l4dopelinux/l4dope --l4io --menubar --transparency module /boot/L4/l4dopelinux/loader --fprov=BMODFS linux26.cfg module /boot/L4/l4dopelinux/bmodfs module /boot/L4/l4dopelinux/libld-l4.s.so module /boot/L4/l4dopelinux/vmlinuz module /boot/L4/l4dopelinux/linux26.cfg module /boot/L4/l4dopelinux/libloader.s.so vbeset 0x117 506070 There is attachment which includes l4linux configuration. Thanks. Cheng Guanghui

1 0

Re: launch benchmark
by chenggh 18 Sep '07

18 Sep '07

> I use this bootloader: > title Fiasco, Console, Loader, Tiny Shell (run) > root (hd0,2) > kernel /boot/fiasco_mod/bootstrap -modaddr 0x02000000 > module /boot/fiasco_mod/fiasco -nowait -serial_esc -comspeed 115200 > -comport 1 module /boot/fiasco_mod/sigma0 > module /boot/fiasco_mod/roottask task modname "bmodfs" attached 3 modules > module /boot/fiasco_mod/names > module /boot/fiasco_mod/log > module /boot/fiasco_mod/dm_phys > module /boot/fiasco_mod/l4io > module /boot/fiasco_mod/con -vbemode 0x117 > module /boot/fiasco_mod/simple_ts -t 300 > module /boot/fiasco_mod/bmodfs > module /boot/fiasco_mod/run > module /boot/fiasco_mod/libloader.s.so > module /boot/fiasco_mod/libld-l4.s.so > module /boot/fiasco_mod/loader --fprov=BMODFS run > > I have to compare l4 with ecos. I want to use lmbench, bonnie++ and > AIM-suite9, my questions are: - How can I use those benchmarks when I boot > Fiasco? I think lmbench, bonnie++ and AIM-suite9 are not suitable when you compare l4/fiasco with ecos although they are real-time operating systems. L4 itself is not linux binary compatible but l4linux could provide full linux binary comptability. And these benchmark tools must run on the linux-binary-compatible system such as BSD,UNIX, etc. So we could compare l4linux with linux by using lmbench, bonnie++ and AIM-suite9. Although ecos could provide many linux APIs but it is still not linux binary compatible. In common we can't compile these tools on the ecos so the benchmark is impossible. Additonal lmbench, bonnie++ and AIM-suite9 are designed for the general purpose operating system. From the result we could know the average performance of the system. Therefore, if you want to compare l4 with ecos you could take these two system as real-time systems and you should get some data showing real-time performance such as jitter, responsing time, etc. But there is no benchmark tool which could cover these two platforms : l4 and ecos. So you have to write your application for this goal. Thanks Cheng Guanghui

1 0

Re: launch benchmark
by chenggh 18 Sep '07

18 Sep '07

On Tuesday 18 September 2007 07:34, Davide Fasoli wrote: > > Where do I put the benchmark to use it in L4 Fiasco console? > > How can I launch the benchmark in the L4 Fiasco console? > > What benchmark is that? What requirements does it have? > The benchmark is lmbench, bonnie++ and AIM-suite9 > Maybe what you say is my paper named "General Performance Assesement of the L4/Fiasco Microkernel". In this paper I use lmbench, bonnie++ and AIM-suite9. But I don't use lmbench, bonnie++ and AIM-suite9 to test the Fiasco itself but test the the performace loss between l4linux-2.6.16 and linux-2.6.16. In this benchmark I login into l4linux with a console because in this way we could ignore the effection of graphic interface for performance loss. It is not complex but only a confiugration problem. If you want to login l4linux with console you could use the configuration file like this: modpath "(hd0,2)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=256M" root=/dev/hda3" all_sects_writable Is this clear? Thanks. Cheng Guanghui

1 0

launch benchmark
by Davide Fasoli 18 Sep '07

18 Sep '07

> > How can I launch the benchmark in the L4 Fiasco console? > > What benchmark is that? What requirements does it have? > The benchmark is lmbench, bonnie++ and AIM-suite9 > Maybe what you say is my paper named "General Performance Assesement of the L4/Fiasco Microkernel". In this paper I use lmbench, bonnie++ and AIM-suite9. But I don't use lmbench, bonnie++ and AIM-suite9 to test the Fiasco itself but test the the performace loss between l4linux-2.6.16 and linux-2.6.16. In this benchmark I login into l4linux with a console because in this way we could ignore the effection of graphic interface for performance loss. It is not complex but only a confiugration problem. If you want to login l4linux with console you could use the configuration file like this: modpath "(hd0,2)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=256M" root=/dev/hda3" all_sects_writable Is this clear? Thanks. Cheng Guanghui > > Where do I put the benchmark to use it in L4 Fiasco console? I use this bootloader: title Fiasco, Console, Loader, Tiny Shell (run) root (hd0,2) kernel /boot/fiasco_mod/bootstrap -modaddr 0x02000000 module /boot/fiasco_mod/fiasco -nowait -serial_esc -comspeed 115200 -comport 1 module /boot/fiasco_mod/sigma0 module /boot/fiasco_mod/roottask task modname "bmodfs" attached 3 modules module /boot/fiasco_mod/names module /boot/fiasco_mod/log module /boot/fiasco_mod/dm_phys module /boot/fiasco_mod/l4io module /boot/fiasco_mod/con -vbemode 0x117 module /boot/fiasco_mod/simple_ts -t 300 module /boot/fiasco_mod/bmodfs module /boot/fiasco_mod/run module /boot/fiasco_mod/libloader.s.so module /boot/fiasco_mod/libld-l4.s..so module /boot/fiasco_mod/loader --fprov=BMODFS run I have to compare l4 with ecos. I want to use lmbench, bonnie++ and AIM-suite9, my questions are: - How can I use those benchmarks when I boot Fiasco? - Where can I put those benchmarks for use them when I boot Fiasco? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

1 0

Re: launch benchmark
by Davide Fasoli 18 Sep '07

18 Sep '07

> > How can I launch the benchmark in the L4 Fiasco console? > > What benchmark is that? What requirements does it have? > The benchmark is lmbench, bonnie++ and AIM-suite9 > Maybe what you say is my paper named "General Performance Assesement of the L4/Fiasco Microkernel". In this paper I use lmbench, bonnie++ and AIM-suite9. But I don't use lmbench, bonnie++ and AIM-suite9 to test the Fiasco itself but test the the performace loss between l4linux-2.6.16 and linux-2.6.16. In this benchmark I login into l4linux with a console because in this way we could ignore the effection of graphic interface for performance loss. It is not complex but only a confiugration problem. If you want to login l4linux with console you could use the configuration file like this: modpath "(hd0,2)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=256M" root=/dev/hda3" all_sects_writable Is this clear? Thanks. Cheng Guanghui > > Where do I put the benchmark to use it in L4 Fiasco console? I use this bootloader: title Fiasco, Console, Loader, Tiny Shell (run) root (hd0,2) kernel /boot/fiasco_mod/bootstrap -modaddr 0x02000000 module /boot/fiasco_mod/fiasco -nowait -serial_esc -comspeed 115200 -comport 1 module /boot/fiasco_mod/sigma0 module /boot/fiasco_mod/roottask task modname "bmodfs" attached 3 modules module /boot/fiasco_mod/names module /boot/fiasco_mod/log module /boot/fiasco_mod/dm_phys module /boot/fiasco_mod/l4io module /boot/fiasco_mod/con -vbemode 0x117 module /boot/fiasco_mod/simple_ts -t 300 module /boot/fiasco_mod/bmodfs module /boot/fiasco_mod/run module /boot/fiasco_mod/libloader.s.so module /boot/fiasco_mod/libld-l4.s.so module /boot/fiasco_mod/loader --fprov=BMODFS run I have to compare l4 with ecos. I want to use lmbench, bonnie++ and AIM-suite9, my questions are: - How can I use those benchmarks when I boot Fiasco? - Where can I put those benchmarks for use them when I boot Fiasco? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

launch benchmark
by Davide Fasoli 18 Sep '07

18 Sep '07

> Where do I put the benchmark to use it in L4 Fiasco console? > How can I launch the benchmark in the L4 Fiasco console? What benchmark is that? What requirements does it have? The benchmark is lmbench, bonnie++ and AIM-suite9 Davide Fasoli L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

launch benchmark
by Davide Fasoli 18 Sep '07

18 Sep '07

I'm sorry for my mistake. I've found a benchmark to use. I've got a questions: Where do I put the benchmark to use it in L4 Fiasco console? How can I launch the benchmark in the L4 Fiasco console? Thanks for your help. Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

L4 benchmaks
by Davide Fasoli 14 Sep '07

14 Sep '07

Because in the last discussion ("ipcmon error") I requested if there are benchmarks to compare L4 with eCos, and they asked me for what I needed them. ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

l4 benchmarks
by Davide Fasoli 14 Sep '07

14 Sep '07

I'd like to measure: - execution time; - system time; - memory consumption; Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

L4 benchmarks
by Davide Fasoli 14 Sep '07

14 Sep '07

No, I haven't any chance...I'm sorry Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

ipcmon
by Davide Fasoli 13 Sep '07

13 Sep '07

Thankyou for your help, L4 is ready. I've a questions, there are some benchmark can I use with L4 and eCos, for comparative test? Thanks a lot. Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

3 2

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

Because, the file was rewrited several time with this output: /* A few distributions ship their GCC with the stack protector feature enabled * by default. This code below fixes linking error when compiled with these * compilers * * Affected distributions (incomplete list): * - Ubuntu 6.10, 7.04 */ void __stack_chk_fail_local (void); void __stack_chk_fail_local (void) { } --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

1 0

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

If I recompiled l4/pkg/ I received in output: /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:30: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:46: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:62: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:78: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:94: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:110: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:126: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:142: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:158: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:174: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here make[4]: *** [libssp-fake.o] Error 1 make[4]: Leaving directory `/home/david/tudos/l4/microkernel/pkg/crtx/lib/src-c++/OBJ-x86_686' make[3]: *** [/home/david/tudos/l4/microkernel/pkg/crtx/lib/src-c++/OBJ-x86_686] Error 2 make[3]: Leaving directory `/home/david/tudos/l4/pkg/crtx/lib/src-c++' make[2]: *** [src-c++] Error 2 make[2]: Leaving directory `/home/david/tudos/l4/pkg/crtx/lib' make[1]: *** [lib] Error 2 make[1]: Leaving directory `/home/david/tudos/l4/pkg/crtx' make: *** [crtx.lib] Error 2 By the way if i re-compiled in l4/pkg/ipcmon I received: /usr/lib/gcc/i486-linux-gnu/4.1.2/libsupc++.a(cp-demangle.o): In function `d_demangle': (.text+0x3fb7): undefined reference to `__stack_chk_fail_local' make[3]: *** [ipcmon] Error 1 make[3]: Leaving directory `/home/david/tudos/l4/microkernel/pkg/ipcmon/server/src/OBJ-x86_686-l4v2' make[2]: *** [/home/david/tudos/l4/microkernel/pkg/ipcmon/server/src/OBJ-x86_686-l4v2] Error 2 make[2]: Leaving directory `/home/david/tudos/l4/pkg/ipcmon/server/src' make[1]: *** [src] Error 2 make[1]: Leaving directory `/home/david/tudos/l4/pkg/ipcmon/server' make: *** [server] Error 2 --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

3 2

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

I re-compiled and I received in output this: /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:30: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:46: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:62: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:78: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:94: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:110: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:126: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:142: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:158: error: redefinition of __stack_chk_fail_local /home/david/tudos/l4/pkg/crtx/lib/src-c++/libssp-fake.c:14: error: previous definition of __stack_chk_fail_local was here make[5]: *** [libssp-fake.o] Error 1 make[4]: *** [/home/david/tudos/l4/microkernel/pkg/crtx/lib/src-c++/OBJ-x86_686] Error 2 make[3]: *** [src-c++] Error 2 make[2]: *** [lib] Error 2 make[1]: *** [crtx.lib] Error 2 make: *** [pkg] Error 2 --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

2 1

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

The problem subsist. Davide Fasoli --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

2 1

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

Could the problem be that lib/src-c++/libssp-fake.c isn't in the directory lib/src-c++/? --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

1 0

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

when I do: $> sudo patch -p3 < stack-guard-fix.diff I receive in output this: patching file lib/src-c++/libssp-fake.c patching file lib/src-c++/Makefile Hunk #1 FAILED at 5. 1 out of 1 hunk FAILED -- saving rejects to file lib/src-c++/Makefile.rej What can I do? --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

2 1

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

The option "-fno-stack-protector" is already present. one request: Where do I put the patch? Thanks. --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

2 1

ipcmon error
by Davide Fasoli 13 Sep '07

13 Sep '07

While I Compile the L4 system libraries and support servers, I receive in output this error message: /usr/lib/gcc/i486-linux-gnu/4.1.2/libsupc++.a(cp-demangle.o): In function `d_demangle': (.text+0x3fb7): undefined reference to `__stack_chk_fail_local' make[5]: *** [ipcmon] Error 1 make[4]: *** [/home/david/tudos/l4/microkerne1/pkg/ipcmon/server/src/OBJ-x86_686-l4v2] Error 2 make[3]: *** [src] Error 2 make[2]: *** [server] Error 2 make[1]: *** [ipcmon.bin] Error 2 make: *** [pkg] Error 2 What's the problem? Thanks for your help. Davide Fasoli --------------------------------- --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

3 2

Re: roottask boot panic
by huang 12 Sep '07

12 Sep '07

hi,dear Adam: thanks a lot for your time and effort! You are right! But is there any difference if I build the binaries in one run or not? I still have another problem that may have the same reason as this one: If I unpack the fiasco kernel first and build it, I can run the hello(many_thread,many_tasks...) example successfully. But when I unpack the l4env and build again, the hello package can not pass the compilation processs. I can not find the reason. can you give me some advice? best wishes! >From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> >To: l4-hackers(a)os.inf.tu-dresden.de >Subject: Re: roottask boot panic >Date: Thu6 Sep 2007 10:01:42 +0200 > > >On Wed Sep 05, 2007 at 09:47:29 +0800, huang wrote: >> I met the problem of roottask boot panic, do you know what's the reason? >> The output is: >> >> Roottask. >> Roottask boot panic: invalid KIP magic 00000001 >> [Esc] reboot, [k] kdebug, [M] memory map, [r] region map >> >> and my menu.lst is: >> title hello world >> kernel (hd0,0)/fiasco/bootstrap >> modaddr 0x02000000 >> module (hd0,0)/fiasco/fiasco -nokdb -nowait >> module (hd0,0)/fiasco/sigma0 >> module (hd0,0)/fiasco/roottask >> module (hd0,0)/fiasco/log >> module (hd0,0)/fiasco/names >> module (hd0,0)/fiasco/dm_phys >> module (hd0,0)/fiasco/names_demo > >I just tried your binaries and I don't get your panic with Qemu. But I >get another error later which seems to indicate that your binaries are >not built in the same run. Is that correct? > > >Adam >-- >Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ 　　　　　　　　huang 　　　　　　　　learnl4(a)sina.com 　　　　　　　　　　2007-09-12

2 1

TIMEOUT question
by huang 12 Sep '07

12 Sep '07

hi,dear all: I have a question about l4_ipc_sleep()! I want to make a stop between two ipc operation, so i used l4_ipc_sleep(), but it did not work! The code is : ... static void sleep(unsigned exp) { l4_ipc_sleep(l4_ipc_timeout(1,exp,1,exp)); } ... int main(int argc, char **argv) { ... for(;;) { ... sleep(4); } return 0; } I think sleep(4) should make a stop about 4 seconds, but the the call returned immediately. What's the problem in my code? thanks for your help! best wishes! 　　　　　　huang 　　　　　　　　learnl4(a)sina.com 　　　　　　　　　　2007-09-12

3 2

What is the difference between l4dm_mem_allocate, l4slab_alloc, malloc
by chenggh 12 Sep '07

12 Sep '07

Hi: In the l4vfs source code I am sure that the malloc function could be used in the L4 programming. But I also find two functions named l4dm_mem_allocate and l4slab_alloc. It seems that both of them could also allocate memory as malloc does. What is the difference between the 3 functions? Which one is fastest? Please help me. Thank you. Cheng Guanghui

2 1

L4linux is currently working with l4fb (Dope) or not?
by Tiago Lopes 07 Sep '07

07 Sep '07

Hello again, After spending a week trying all configs I could find, I'm (again) asking for help. I'm using an unmodified Opentc June snapshot and trying to get L4linux and dope working. Dope e running fine and L4linux is started, but it seems that L4linux cannot find the l4fb, and so the system boots and writes fine to the terminal, but not to dope screen... Is this config actually supported? Someone could give me a working config? This is my config files and output: Any help is much appreciated! Tiago Lopes FILES: Grub config: ----------------------------------------------------------------------------------> default 0 timeout 1 set ROOT := (cd) set SERIAL ?= "-serial -serial_esc -comspeed 115200 -comport 1" set FIASCOARGS := "-nokdb -nowait $(SERIAL)" title = test kernel $(ROOT)/tcb/bootstrap modaddr 0x02000000 module $(ROOT)/tcb/fiasco $(FIASCOARGS) module $(ROOT)/tcb/sigma0 module $(ROOT)/tcb/roottask -configfile task modname "bmodfs" attached 5 modules module $(ROOT)/tcb/roottask.config module $(ROOT)/tcb/events module $(ROOT)/tcb/names --events module $(ROOT)/tcb/dm_phys --events module $(ROOT)/tcb/simple_ts --events -t 300 module $(ROOT)/tcb/rtc --events module $(ROOT)/tcb/ore --events module $(ROOT)/tcb/l4io --events module $(ROOT)/tcb/l4dope --events module $(ROOT)/tcb/loader --events --fprov=BMODFS l4linux.cfg module $(ROOT)/tcb/bmodfs module $(ROOT)/tcb/libloader.s.so module $(ROOT)/tcb/libld-l4.s.so module $(ROOT)/tcb/l4linux.cfg module $(ROOT)/userland/l4linux2.6.21 module $(ROOT)/userland/drops-rd.rd vbeset 0x117 <---------------------------------------------------------------------------------- l4linux.cfg: ----------------------------------------------------------------------------------> sleep 2 task "l4linux2.6.21" "mem=128M root=/dev/ram load_ramdisk=1 ramdisk_size=16384 l4env_rd=drops-rd.rd lang=en video=l4fb earlyprintk=yes console=ttyLv0" all_sects_writable allow_vga <---------------------------------------------------------------------------------- Serial output: ----------------------------------------------------------------------------------> Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2007 TU Dresden Rev: rUNKNOWN compiled with gcc 4.1.2 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_FINE_GRAINED_CPUTIME is on 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: AuthenticAMD (6:8:0:0) Model: Athlon (Thoroughbred) at 698 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 1000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Command line found: "(cd)/tcb/roottask -configfile task modname "bmodfs" attached 5 modules" 409150kB ( 399MB) total RAM (reported by bootloader) 368704kB ( 361MB) received RAM from Sigma0 40096kB ( 40MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 A B C D E F ] Roottask: Parsing config file. configured task 0x02 (): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x04 (): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (events): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (names): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (dm_phys): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (simple_ts): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (rtc): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:10 small:ff mods:0 configured task 0x00 (l4io): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (ore): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (l4dope): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (loader): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (l4linux2.6.21): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:10 small:ff mods:0 Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:5 Roottask: Loading 15 modules. #05: loading "(cd)/tcb/events" from [0812c000-0816e66c] to [01540000-01548c10][01549000-0155e5d0] entry at 00062368 via trampoline page code symbols at [18ffe000-19000000] (8kB), lines at [18ff7000-18ffe000] (28kB) #06: loading "(cd)/tcb/names --events" from [0816f000-081ae253] to [002d0000-002d5e6a][002d6000-002e1000] entry at 00063370 via trampoline page code symbols at [18ff5000-18ff7000] (8kB), lines at [18fef000-18ff5000] (24kB) #07: loading "(cd)/tcb/dm_phys --events" from [081af000-0823b38c] to [01500000-015121ca][01513000-0151d000] entry at 00064374 via trampoline page code symbols at [18fea000-18fef000] (20kB), lines at [18fdd000-18fea000] (52kB) #08: loading "(cd)/tcb/simple_ts --events -t 300" from [0823c000-08287d04] to [01400000-014080ea][01409000-01418608] entry at 0006537c via trampoline page code symbols at [18fdb000-18fdd000] (8kB), lines at [18fd3000-18fdb000] (32kB) #09: loading "(cd)/tcb/rtc --events" from [08288000-082b8ec1] to [01080000-010840e0][01085000-0108a000] entry at 00066370 via trampoline page code symbols at [18fd1000-18fd3000] (8kB), lines at [18fcc000-18fd1000] (20kB) #0a: loading "(cd)/tcb/ore --events" from [082b9000-084aaada] to [01800000-018371f9][01838000-01867000] entry at 00067370 via trampoline page code symbols at [18fc3000-18fcc000] (36kB), lines at [18f9a000-18fc3000] (164kB) #0b: loading "(cd)/tcb/l4io --events" from [084ab000-08703e28] to [00b80000-00ba22a5][00ba3000-00c0a000] entry at 00069370 via trampoline page code symbols at [18f48000-18f9a000] (328kB), lines at [18f2e000-18f48000] (104kB) #0c: loading "(cd)/tcb/l4dope --events" from [08704000-08871e76] to [01b00000-01b411a1][01b42000-01b83000] entry at 0006a374 via trampoline page code symbols at [18f20000-18f2e000] (56kB), lines at [16ed9000-16f05000] (176kB) #0d: loading "(cd)/tcb/loader --events --fprov=BMODFS l4linux.cfg" from [08872000-0894a9e4] to [01300000-01324ef9][01325000-01343000] entry at 0006b38c via trampoline page code symbols at [18f1a000-18f20000] (24kB), lines at [18f01000-18f1a000] (100kB) #0e: loading "(cd)/tcb/bmodfs" from [0894b000-089ea5d0] to [01220000-01235659][01236000-0124d000] passing module (cd)/tcb/libloader.s.so [ 089eb000-08a89c02 ] passing module (cd)/tcb/libld-l4.s.so [ 08a8a000-08b039c9 ] passing module (cd)/tcb/l4linux.cfg [ 08b04000-08b0420d ] passing module (cd)/userland/l4linux2.6.21 [ 08b05000-096b4aad ] passing module (cd)/userland/drops-rd.rd [ 096b5000-0a6b5000 ] entry at 0006c438 via trampoline page code symbols at [16ed4000-16ed9000] (20kB), lines at [16ec2000-16ed4000] (72kB) names | Starting thread listening for `exit' events ROOT: Sending ports 0070-0070 to task #09 ROOT: Sending ports 0080-0080 to task #09 ROOT: Sending ports 0071-0071 to task #09 *simplets| Configured for 300 tasks. *l4dope | DOpE(init): using events mechanism *io | Enabling events support. *bmodfs | Passed the following modules: *bmodfs | module "(cd)/tcb/libloader.s.so" (636kB) *bmodfs | module "(cd)/tcb/libld-l4.s.so" (487kB) *bmodfs | module "(cd)/tcb/l4linux.cfg" (1kB) *bmodfs | module "(cd)/userland/l4linux2.6.21" (11967kB) *bmodfs | module "(cd)/userland/drops-rd.rd" (16384kB) ROOT: Sending ports 0cfb-0cfb to task #0b ROOT: Sending ports 0cf8-0cfb to task #0b ROOT: Sending ports 0cfe-0cff to task #0b *io | PCI: Using configuration type 1 *io | PCI: Probing PCI hardware *io | PCI: Probing PCI hardware (bus 00) ROOT: Sending ports 0cfc-0cff to task #0b *io | PCI: Cannot allocate resource region 4 of device 00:07.1 *io | Limiting direct PCI/PCI transfers. *io | 00000000-ffffffff : PCI mem *io | e8000000-ebffffff : Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX H *io : ost bridge *io | ec000000-ec7fffff : VMware Inc [VMware SVGA II] PCI Display Adapter *io | ec800000-ec800fff : LSI Logic / Symbios Logic 53c1030 PCI-X Fusion- *io : MPT Dual Ultra320 SCSI *io | f0000000-f7ffffff : VMware Inc [VMware SVGA II] PCI Display Adapter *io | 0000-ffff : PCI IO *io | 0cf8-0cff : PCI conf1 *io | 1000-103f : Intel Corporation 82371AB/EB/MB PIIX4 ACPI *io | 1040-105f : Intel Corporation 82371AB/EB/MB PIIX4 ACPI *io | 1060-106f : VMware Inc [VMware SVGA II] PCI Display Adapter *io | 1070-107f : Intel Corporation 82371AB/EB/MB PIIX4 IDE *io | 1080-10ff : LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual *io : Ultra320 SCSI *io | 1400-147f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] *io | Available IRQs=[ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f ] *rtc | Date:04.09.2007 Time:21:45:27 *l4dope | L4INPUT native mode activated *l4dope | L4INPUT: !!! W A R N I N G !!! *l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. *l4dope | L4INPUT: !!! W A R N I N G !!! ROOT: Sending ports 0060-006f to task #0b *loader | sleeping for 2000 ms *l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 *l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 *l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 *l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 *l4dope | input: PC Speaker *l4dope | input: L4 input event injector *loader | l4linux2.6.21: Starting application using libld-l4.s.so *loader | l4linux2.6.21,#f: Loading binary *l4dope | L4 input event injector: IRQ handler up *l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 *l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 *l4dope | connect "PC Speaker", isa0061/input0 *l4dope | connect "L4 input event injector", l4/sys *l4dope | SharedMem(alloc): hl.raw=e0000, id=43, size=800 *l4dope | SharedMem(get_adr): address = 0x6000 *l4dope | SharedMem(alloc): hl.raw=e0000, id=44, size=800 *l4dope | SharedMem(get_adr): address = 0x7000 *l4dope | SharedMem(alloc): hl.raw=e0000, id=45, size=800 *l4dope | SharedMem(get_adr): address = 0xd000 *l4dope | SharedMem(alloc): hl.raw=e0000, id=46, size=800 *l4dope | SharedMem(get_adr): address = 0xe000 *l4dope | SharedMem(alloc): hl.raw=e0000, id=47, size=800 *l4dope | SharedMem(get_adr): address = 0xf000 *l4dope | SharedMem(alloc): hl.raw=e0000, id=49, size=800 *l4dope | SharedMem(get_adr): address = 0x16000 *l4dope | SharedMem(alloc): hl.raw=e0000, id=4a, size=800 *l4dope | SharedMem(get_adr): address = 0x17000 *l4dope | dope: paddr=f0000000 size=16384KiB *l4dope | Mapped video memory at f0000000 to 03000000+000000 [16384kB] via L4IO *l4dope | mapping: vaddr=0x3000000 size=16777216(0x1000000) offset=0(0x0) *l4dope | Frame buffer base: 0x3000000 *l4dope | Resolution: 1024x768x16 *l4dope | Bytes per scanline: 2048 *l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 *loader | l4linux2.6.21,#f: Loading ldso *loader | l4linux2.6.21,#f: Starting libld-l4.s.so at 00013800 via 0000cc04 *ore | l4dde_mm_init(): Using ... *ore | 16 MB at 0x00180000 (vmem) *ore | 16 MB in 1 regions (kmem) *ore | pcnet32.c:v1.30h 06.24.2004 tsbogend(a)alpha.franken.de ROOT: Sending ports 1400-141f to task #0b *ore | pcnet32: PCnet/PCI II 79C970A at 0x1400, 00 0c 29 f9 37 6a assigned I *ore : RQ 11. *ore | eth0: registered as PCnet/PCI II 79C970A *ore | pcnet32: 1 cards_found. *ore | main(): initialized DDELinux2.4 *ore | main(): loopback: 0 *ore | device lo entered promiscuous mode *ore | device eth0 entered promiscuous mode *ore | main(): Initialized 2 network devices. *ore | Device = lo, IRQ = 0, MAC = 00:00:00:00:00:00 *ore | Device = eth0, IRQ = 11, MAC = 00:0C:29:F9:37:6A *ore | main(): Registering 'ORe' at names... *ore | main(): Ready for service. *l4lx | ======> L4Linux 2.6 starting... <======== *l4lx | Linux version 2.6.21-l4 (tjcl@fx242) (gcc version 4.1.2) #4 Mon Sep 3 *l4lx : 00:47:41 WEST 2007 *l4lx | Binary name: l4linux2.6.21 *l4lx | Kernel command line (9 args): mem=128M root=/dev/ram load_ramdisk=1 r *l4lx : amdisk_size=16384 l4env_rd=drops-rd.rd lang=en video=l4fb earlyprintk *l4lx : =yes console=ttyLv0 *l4lx | Image: 00400000 - 00683000 [2572 KiB]. *l4lx | Areas: Text: 00400000 - 005e9000 [1956kB] (a bit longer) *l4lx | Data: 005e9000 - 005fe2cc [84kB] *l4lx | Initdata: 00602000 - 006260a0 [144kB] *l4lx | BSS: 00628000 - 00680900 [354kB] *l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) *l4lx | Using tamed mode. ROOT: Sending all ports (for cli/sti) to task #0d *l4lx | Got 65536 out of 65536 I/O ports *l4lx | l4lx_thread_create: Created thread 0f.04 (server) *l4lx | main thread will be 0f.04 *l4lx | l4env_register_pointer_section: addr = 00600000 size = 536576 *l4lx | sec-w-init: virt: 0x00600000 to 0x00682fff [524 KiB] *l4lx | sec-w-init: Number of physical regions: 1, 536576 Bytes *l4lx | sec-w-init: 1: Phys: 0x006d0000 to 0x00753000, Size: 536576 *l4lx | l4env_linux_startup thread 4. *l4lx | Main thread running, waiting... *l4lx | main thread: received startup message. *l4lx | setup_l4env_memory: Forcing superpages for main memory *l4lx | Main memory size: 128MB *l4lx | Main memory: virt: 0x00800000 to 0x087fffff [131072 KiB] *l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes *l4lx | Main memory: 1: Phys: 0x0a800000 to 0x12800000, Size: 134217728 *l4lx | Filling lower ptabs... *l4lx | Done (1338 entries). *l4lx | l4env_rd_path: drops-rd.rd *l4lx | Loading: drops-rd.rd *l4lx | INITRD: Size of RAMdisk is 16384KiB *l4lx | RAMdisk from 08800000 to 09800000 [16384KiB] Linux version 2.6.21-l4 (tjcl@fx242) (gcc version 4.1.2) #4 Mon Sep 3 00:47:41 WEST 2007 CPU: Vendor unknown, using generic init. CPU: Your system may be unstable. dm_phys: 0000000000800000 - 0000000008800000 (usable) 128MB memory available. INITRD: 08800000 - 09800000 Zone PFN ranges: DMA 0 -> 512 Normal 512 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 Allocating PCI resources starting at 10000000 (gap: 08800000:f7800000) Built 1 zonelists. Total pages: 34544 Kernel command line: mem=128M root=/dev/ram load_ramdisk=1 ramdisk_size=16384 l4env_rd=drops-rd.rd lang=en video=l4fb earlyprintk=yes console=ttyLv0 Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) Detected 698.657 MHz processor. Console: colour dummy device 80x25 l4ser_init_ports l4ser: input not enabled! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 129620k/139264k available (1726k kernel code, 1312k reserved, 314k data, 144k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0x10000000 - 0x18000000 ( 128 MB) lowmem : 0x00000000 - 0x08800000 ( 136 MB) .init : 0x00602000 - 0x006260a0 ( 144 kB) .data : 0x005af8c4 - 0x005fe2cc ( 314 kB) .text : 0x00400000 - 0x005af8c4 (1726 kB) l4lx_irq_timer_startup(0) *l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) timer_irq_thread: Starting timer IRQ thread. Calibrating delay using timer specific routine.. 1464.63 BogoMIPS (lpj=7323198) Mount-cache hash table entries: 512 Compat vDSO mapped to 0040d000. CPU: AuthenticAMD mobile AMD Athlon(tm) XP 1800+ stepping 00 NET: Registered protocol family 16 Setting up standard PCI resources SCSI subsystem initialized NET: Registered protocol family 2 Time: tsc clocksource has been installed. *l4lx | l4lx_thread_create: Created thread 0f.06 (Idler) IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd Clocksource tsc unstable (delta = 114219382 ns) Time: jiffies clocksource has been installed. INITRD: Freeing memory. io scheduler noop registered (default) L4 serial driver l4ser_init_ports l4ser: input not enabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize *l4lx | Creating 1 ORe device(s). *l4lx | Opening device eth0 at ORe instance ORe *l4lx | l4ore_open(): called *l4lx | l4ore_open(): descriptor: 0 *l4lx | ore_lookup_server(): ORe server ORe = A.02 *l4lx | ore_do_open(): called *ore | __init_mac(): Allocating physical MAC address to client. *ore | __init_mac(): MAC = 00:0C:29:F9:37:6A *l4lx | ore_do_open(): opened. worker = A.07 eth0: L4Ore card found with 00:0C:29:F9:37:6A, IRQ 11 SCSI Media Changer driver v0.25 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 16384KiB [1 disk] into ram disk... done. EXT2-fs warning: checktime reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). INIT: version 2.84 booting Loading /etc/console/boottime.kmap.gz Activating swap. System time was Tue Sep 4 21:46:40 UTC 2007. Setting the System Clock using the Hardware Clock as reference... hwclock is unable to get I/O port access: the iopl(3) call failed. System Clock set. System local time is now Tue Sep 4 21:46:43 UTC 2007. Checking all file systems... fsck 1.27 (8-Mar-2002) Setting kernel variables. Loading the saved-state of the serial devices... Mounting local filesystems... nothing was mounted Setting up IP spoofing protection: rp_filter. Configuring network interfaces: eth0: Overwriting IRQ type for IRQ 11 with l4ore type! *l4lx | l4x_ore_irq_startup *l4lx | l4lx_thread_create: Created thread 0f.07 (L4OreRcv) eth0: interface up. eth0: Overwriting IRQ type for IRQ 11 with l4ore type! *l4lx | l4x_ore_irq_startup *l4lx | l4lx_thread_create: Created thread 0f.07 (L4OreRcv) eth0: interface up. Operation failed. done. No IP found! at /etc/rcS.d/S40sethostname line 30. Starting portmap daemon: portmap. Setting the System Clock using the Hardware Clock as reference... hwclock is unable to get I/O port access: the iopl(3) call failed. System Clock set. Local time: Tue Sep 4 23:48:14 CEST 2007 Cleaning: /tmp /var/lock /var/run. INIT: Entering runlevel: 2 No user config loaded! <----------------------------------------------------------------------------------

4 6

roottask boot panic
by huang 07 Sep '07

07 Sep '07

dear all: I met the problem of roottask boot panic, do you know what's the reason? The output is: Roottask. Roottask boot panic: invalid KIP magic 00000001 [Esc] reboot, [k] kdebug, [M] memory map, [r] region map and my menu.lst is: title hello world kernel (hd0,0)/fiasco/bootstrap modaddr 0x02000000 module (hd0,0)/fiasco/fiasco -nokdb -nowait module (hd0,0)/fiasco/sigma0 module (hd0,0)/fiasco/roottask module (hd0,0)/fiasco/log module (hd0,0)/fiasco/names module (hd0,0)/fiasco/dm_phys module (hd0,0)/fiasco/names_demo Best wishes! 　　　　　　　　huang 　　　　　　　　learnl4(a)sina.com 　　　　　　　　　　2007-09-05

4 5

Re: l4-hackers Digest, Vol 53, Issue 4
by chenggh 06 Sep '07

06 Sep '07

> > The find version of my slackware 10.2 is : > > GNU find version 4.1.7 > > I just looked it up, the -L option has been introduced to find in late > 2004. I think that it is reasonable nowadays that one could have a find > installed that has this option. > > To work around this you can remove the -L option in l4/pkg/Makefile, it > will work nevertheless for you. Another solution is to update the find package. the find version more than 4.2.28 is ok. You could download the new find package from this link (http://ftp.gnu.org/pub/gnu/findutils/). Thanks. Cheng Guanghui

1 0

Re: l4-hackers Digest, Vol 53, Issue 4
by 丁莹 06 Sep '07

06 Sep '07

> On Tue Sep 04, 2007 at 11:10:20 +0800, ???? wrote: > > > > The config options I used are as same as before,so I don't > > > know > > > > what have happened.And I used the linux distribution is slackware > 10.2, > > > > gcc-3.4.6,make-3.81,bison-2.3. > > > > Everybody who knows this problem please hlep me.Thanks! > > > > > > Can you show me the last 100 lines of the output of > > > 'make -C l4 O=./build', please? That would give me more hints on what > > > could be going wrong. > > > > > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > find: invalid predicate `-L' > > make[1]: Leaving directory `/mnt/tudos/l4/pkg' > > make: Leaving directory `/mnt/tudos/l4' > > there are missing a lot of things after compiling ,I don't know > why . > > There are quite a few error messages which explain quite well that find > is complaining about the -L option and that might lead to the situation > that find isn't work quite as expected and thus things go wrong. > Can I please know your find version? > > find --version > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ The find version of my slackware 10.2 is : GNU find version 4.1.7

2 1

Re: l4-hackers Digest, Vol 53, Issue 2
by 丁莹 04 Sep '07

04 Sep '07

2007/9/4, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de>: > > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: why there is no bin and lib directory under build > directory after I compiled the L4 (Adam Lackorzynski) > 2. Re: why the function just declare,but no implement. > (Adam Lackorzynski) > 3. roottask problem?? help!!! (huang) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 Sep 2007 00:32:53 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: why there is no bin and lib directory under build > directory after I compiled the L4 > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070903223253.GB19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Mon Sep 03, 2007 at 09:39:39 +0800, ???? wrote: > > I have get a tudos from svn a few days ago,but when I have > > compiled it,there is no bin and lib derictory under tudos/l4/build/.And > In > > the /tudos/l4/build/include derictory ,there is only a l4 directory > which > > containning just a one file,but all compile process are all right. > > Of course,when I use this L4env to compile the l4linux-2.6.21 > ,there > > is a lot of error,you can seeing the error informantion from the > attachment. > > The compiler instructor I used as follow: > > cd tudos > > make -C l4 config O=./build > > make -C l4 O=./build > > The config options I used are as same as before,so I don't > know > > what have happened.And I used the linux distribution is slackware 10.2, > > gcc-3.4.6,make-3.81,bison-2.3. > > Everybody who knows this problem please hlep me.Thanks! > > Can you show me the last 100 lines of the output of > 'make -C l4 O=./build', please? That would give me more hints on what > could be going wrong. Ok,the output of 'make -C l4 O=./build is as follow: ... Making kern_cnt.o ... Making jdb_bt-ia32-ux.o ... Making tb_entry.o ... Making tb_entry-ia32-ux.o ... Making tb_entry_output.o ... Making jdb_exit_module.o ... Making jdb_tbuf_show.o ... Making jdb_console_buffer.o ... Making virq.o ... Making push_console.o ... Making jdb_timeout.o ... Making jdb_halt_thread.o ... Making jdb_tbuf_events.o ... Making jdb_kern_info_kmem_alloc.o ... Making jdb_thread_names.o ... Making loadcnt.o ... Making jdb_utcb.o ... Making jdb_bts.o ... Making jdb_entry_frame-ia32-ux.o ... Making jdb_space.o ... Making jdb_disasm.o ... Making jdb_gzip.o ... Making jdb_regex.o ... Making dump_tcboffsets ... Making tcboffset.o ==> Linking tcboffset.bin ./dump_tcboffsets tcboffset.bin > tcboffset.h.new mv tcboffset.h.new tcboffset.h ... Making entry-ia32-ux.o ... Making entry-ia32.o ... Making shortcut-ia32-ux.o ... Making sys_call_page-asm.o ... Making disasm.o ... Making i386-dis.o ... Making dis-buf.o ==> Archiving into libdisasm.a ==> Linking kernel.image ==> Linking main ... Generating checksum for main text section ... Generating checksum for main data section ... Writing checksum into main ... Making Symbols ... Making Lines make[3]: Leaving directory `/mnt/tudos/kernel/fiasco/build' make[2]: Leaving directory `/mnt/tudos/kernel/fiasco/build' make[1]: Leaving directory `/mnt/tudos/kernel/fiasco' if [ -r pkg/Makefile ]; then PWD=/mnt/tudos/pkg make -C pkg; fi find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' find: invalid predicate `-L' make[1]: Entering directory `/mnt/tudos/l4/pkg' install -d /mnt/tudos/l4/build/pkg/ echo '# automatically created -- modifications will be lost' > /mnt/tudos/l4/build/pkg/Makefile echo 'SRC := /mnt/tudos/l4/pkg' >> /mnt/tudos/l4/build/pkg/Makefile echo 'OBJ := /mnt/tudos/l4/build' >> /mnt/tudos/l4/build/pkg/Makefile echo '.PHONY: x $(MAKECMDGOALS)' >> /mnt/tudos/l4/build/pkg/Makefile echo 'x:' >> /mnt/tudos/l4/build/pkg/Makefile echo ' $(MAKE) -C $(SRC) O=$(OBJ)' >> /mnt/tudos/l4/build/pkg/Makefile echo '$(MAKECMDGOALS):' >> /mnt/tudos/l4/build/pkg/Makefile echo ' $(MAKE) -C $(SRC) O=$(OBJ) $@' >> /mnt/tudos/l4/build/pkg/Makefile make[1]: Leaving directory `/mnt/tudos/l4/pkg' make: Leaving directory `/mnt/tudos/l4' there are missing a lot of things after compiling ,I don't know why . Best Regards! ding Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 2 > Date: Tue, 4 Sep 2007 00:34:18 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: why the function just declare,but no implement. > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070903223418.GC19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Mon Sep 03, 2007 at 17:00:00 +0800, ???? wrote: > > Hi,everyone: > > When I used latest version of L4 to compile the l4linux-2.6.22 > ,it > > is following error message appeared. > > > > In file included from arch/l4/kernel/arch-i386/dispatch.c:586: > > arch/l4/kernel/arch-i386/../dispatch.c: In function > `l4x_user_dispatcher': > > arch/l4/kernel/arch-i386/../dispatch.c:362: sorry, unimplemented: > inlining > > failed in call to 'l4x_dispatch_suspend': function not considered for > > inlining > > arch/l4/kernel/arch-i386/../dispatch.c:506: sorry, unimplemented: called > > from here > > make[1]: *** [arch/l4/kernel/arch-i386/dispatch.o] error 1 > > make: *** [arch/l4/kernel/arch-i386] error 2 > > > > so I check the function dispatch.c,the function l4x_dispatch_suspend is > > empty indeed.Maybe there is something wrong,but I don't know what have > > happened.Everyone who knows this problem please help me,thanks! > > The L4 and l4linux are all downloaded from svn today,and my linux > > distribution is ubuntu 6.06. > > Well, l4x_dispatch_suspend is not empty at all, at least not in my copy > of the source. Are you sure? > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 3 > Date: Tue, 4 Sep 2007 09:47:17 +0800 > From: "huang" <learnl4(a)sina.com> > Subject: roottask problem?? help!!! > To: "l4-hackers" <l4-hackers(a)os.inf.tu-dresden.de> > Message-ID: <20070904014637.B789F3B5B51(a)smtp.sina.com.cn> > Content-Type: text/plain; charset="gb2312" > > hi,dear all: > > When I tried to use the l4env nameserver "names" to help doing sth, I > found it doesn't work. For example, the logserver "log" can not > register at nameserver, so it fall asleep, so does names_demo. I examed > and tested the names.c, and I modified a few lines of code in main() > such as: > > ... > if(rmgr_init()) > printf("roottask service unavailable!\n"); > else > printf("roottask service init successfully!\n"); > ... > > then I rebuilded names, and tested again with modules listed in menu.lst: > > title hello world > kernel (hd0,0)/fiasco/bootstrap > modaddr 0x02000000 > module (hd0,0)/fiasco/fiasco -nokdb -nowait > module (hd0,0)/fiasco/sigma0 > module (hd0,0)/fiasco/roottask > module (hd0,0)/fiasco/names > module (hd0,0)/fiasco/names_demo > > the output screen is in the attachement roottask.jpg, the key output is > names | roottask service unavailable! > > Is this really caused by roottask?? > > In the manual tut.pdf, the menu.lst is as below: > > title Hi world, server version > kernel (nd)/tftpboot/yourname/bin/x86_586/l4v2/bootstrap > modaddr 0x02000000 > module (nd)/tftpboot/yourname/bin/fiasco -nokdb -nowait > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/sigma0 > module (nd)/tftpboot/yourname/bin/x86_586/l4vs/roottask > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/log > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/names > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/dm_phys > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiserver > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiclient > > I found the line of roottask is different from other lines in "l4vs", > while others are "l4v2". What is the difference? > > best wishes! > > > > ????????huang > ????????learnl4(a)sina.com > ??????????2007-09-04 >

2 1

Re: l4-hackers Digest, Vol 53, Issue 2
by 丁莹 04 Sep '07

04 Sep '07

2007/9/4, l4-hackers-request(a)os.inf.tu-dresden.de < l4-hackers-request(a)os.inf.tu-dresden.de>: > > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: why there is no bin and lib directory under build > directory after I compiled the L4 (Adam Lackorzynski) > 2. Re: why the function just declare,but no implement. > (Adam Lackorzynski) > 3. roottask problem?? help!!! (huang) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 Sep 2007 00:32:53 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: why there is no bin and lib directory under build > directory after I compiled the L4 > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070903223253.GB19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Mon Sep 03, 2007 at 09:39:39 +0800, ???? wrote: > > I have get a tudos from svn a few days ago,but when I have > > compiled it,there is no bin and lib derictory under tudos/l4/build/.And > In > > the /tudos/l4/build/include derictory ,there is only a l4 directory > which > > containning just a one file,but all compile process are all right. > > Of course,when I use this L4env to compile the l4linux-2.6.21 > ,there > > is a lot of error,you can seeing the error informantion from the > attachment. > > The compiler instructor I used as follow: > > cd tudos > > make -C l4 config O=./build > > make -C l4 O=./build > > The config options I used are as same as before,so I don't > know > > what have happened.And I used the linux distribution is slackware 10.2, > > gcc-3.4.6,make-3.81,bison-2.3. > > Everybody who knows this problem please hlep me.Thanks! > > Can you show me the last 100 lines of the output of > 'make -C l4 O=./build', please? That would give me more hints on what > could be going wrong. Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 2 > Date: Tue, 4 Sep 2007 00:34:18 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: why the function just declare,but no implement. > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070903223418.GC19315(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Mon Sep 03, 2007 at 17:00:00 +0800, ???? wrote: > > Hi,everyone: > > When I used latest version of L4 to compile the l4linux-2.6.22 > ,it > > is following error message appeared. > > > > In file included from arch/l4/kernel/arch-i386/dispatch.c:586: > > arch/l4/kernel/arch-i386/../dispatch.c: In function > `l4x_user_dispatcher': > > arch/l4/kernel/arch-i386/../dispatch.c:362: sorry, unimplemented: > inlining > > failed in call to 'l4x_dispatch_suspend': function not considered for > > inlining > > arch/l4/kernel/arch-i386/../dispatch.c:506: sorry, unimplemented: called > > from here > > make[1]: *** [arch/l4/kernel/arch-i386/dispatch.o] error 1 > > make: *** [arch/l4/kernel/arch-i386] error 2 > > > > so I check the function dispatch.c,the function l4x_dispatch_suspend is > > empty indeed.Maybe there is something wrong,but I don't know what have > > happened.Everyone who knows this problem please help me,thanks! > > The L4 and l4linux are all downloaded from svn today,and my linux > > distribution is ubuntu 6.06. > > Well, l4x_dispatch_suspend is not empty at all, at least not in my copy > of the source. Are you sure? I'm sorry,I have made a mistake.Yes,the l4x_dispatch_suspend is surely no empty,it may be some error of gcc to compile the inline function,I search the error message from the Internet,they says the problem might be that a function was declared with two different inlining attributes.So,I think it maybe the gcc's matter,but after I re-install the gcc-3.4.6 and compile the l4linux-2.6.22,the some error massage appearing,so I don't know why,maybe it have something to do with another compiler enviroment,but I don't know what. Best Regards! ding Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Message: 3 > Date: Tue, 4 Sep 2007 09:47:17 +0800 > From: "huang" <learnl4(a)sina.com> > Subject: roottask problem?? help!!! > To: "l4-hackers" <l4-hackers(a)os.inf.tu-dresden.de> > Message-ID: <20070904014637.B789F3B5B51(a)smtp.sina.com.cn> > Content-Type: text/plain; charset="gb2312" > > hi,dear all: > > When I tried to use the l4env nameserver "names" to help doing sth, I > found it doesn't work. For example, the logserver "log" can not > register at nameserver, so it fall asleep, so does names_demo. I examed > and tested the names.c, and I modified a few lines of code in main() > such as: > > ... > if(rmgr_init()) > printf("roottask service unavailable!\n"); > else > printf("roottask service init successfully!\n"); > ... > > then I rebuilded names, and tested again with modules listed in menu.lst: > > title hello world > kernel (hd0,0)/fiasco/bootstrap > modaddr 0x02000000 > module (hd0,0)/fiasco/fiasco -nokdb -nowait > module (hd0,0)/fiasco/sigma0 > module (hd0,0)/fiasco/roottask > module (hd0,0)/fiasco/names > module (hd0,0)/fiasco/names_demo > > the output screen is in the attachement roottask.jpg, the key output is > names | roottask service unavailable! > > Is this really caused by roottask?? > > In the manual tut.pdf, the menu.lst is as below: > > title Hi world, server version > kernel (nd)/tftpboot/yourname/bin/x86_586/l4v2/bootstrap > modaddr 0x02000000 > module (nd)/tftpboot/yourname/bin/fiasco -nokdb -nowait > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/sigma0 > module (nd)/tftpboot/yourname/bin/x86_586/l4vs/roottask > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/log > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/names > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/dm_phys > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiserver > module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiclient > > I found the line of roottask is different from other lines in "l4vs", > while others are "l4v2". What is the difference? > > best wishes! > > > > ????????huang > ????????learnl4(a)sina.com > ??????????2007-09-04 >

2 1

roottask problem?? help!!!
by huang 04 Sep '07

04 Sep '07

hi,dear all: When I tried to use the l4env nameserver "names" to help doing sth, I found it doesn't work. For example, the logserver "log" can not register at nameserver, so it fall asleep, so does names_demo. I examed and tested the names.c, and I modified a few lines of code in main() such as: ... if(rmgr_init()) printf("roottask service unavailable!\n"); else printf("roottask service init successfully!\n"); ... then I rebuilded names, and tested again with modules listed in menu.lst: title hello world kernel (hd0,0)/fiasco/bootstrap modaddr 0x02000000 module (hd0,0)/fiasco/fiasco -nokdb -nowait module (hd0,0)/fiasco/sigma0 module (hd0,0)/fiasco/roottask module (hd0,0)/fiasco/names module (hd0,0)/fiasco/names_demo the output screen is in the attachement roottask.jpg, the key output is names | roottask service unavailable! Is this really caused by roottask?? In the manual tut.pdf, the menu.lst is as below: title Hi world, server version kernel (nd)/tftpboot/yourname/bin/x86_586/l4v2/bootstrap modaddr 0x02000000 module (nd)/tftpboot/yourname/bin/fiasco -nokdb -nowait module (nd)/tftpboot/yourname/bin/x86_586/l4v2/sigma0 module (nd)/tftpboot/yourname/bin/x86_586/l4vs/roottask module (nd)/tftpboot/yourname/bin/x86_586/l4v2/log module (nd)/tftpboot/yourname/bin/x86_586/l4v2/names module (nd)/tftpboot/yourname/bin/x86_586/l4v2/dm_phys module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiserver module (nd)/tftpboot/yourname/bin/x86_586/l4v2/hiclient I found the line of roottask is different from other lines in "l4vs", while others are "l4v2". What is the difference? best wishes! 　　　　　　　　huang 　　　　　　　　learnl4(a)sina.com 　　　　　　　　　　2007-09-04

2 1

why the function just declare,but no implement.
by 丁莹 04 Sep '07

04 Sep '07

Hi,everyone: When I used latest version of L4 to compile the l4linux-2.6.22,it is following error message appeared. In file included from arch/l4/kernel/arch-i386/dispatch.c:586: arch/l4/kernel/arch-i386/../dispatch.c: In function `l4x_user_dispatcher': arch/l4/kernel/arch-i386/../dispatch.c:362: sorry, unimplemented: inlining failed in call to 'l4x_dispatch_suspend': function not considered for inlining arch/l4/kernel/arch-i386/../dispatch.c:506: sorry, unimplemented: called from here make[1]: *** [arch/l4/kernel/arch-i386/dispatch.o] error 1 make: *** [arch/l4/kernel/arch-i386] error 2 so I check the function dispatch.c,the function l4x_dispatch_suspend is empty indeed.Maybe there is something wrong,but I don't know what have happened.Everyone who knows this problem please help me,thanks! The L4 and l4linux are all downloaded from svn today,and my linux distribution is ubuntu 6.06. Best Regards!

2 1

why there is no bin and lib directory under build directory after I compiled the L4
by 丁莹 04 Sep '07

04 Sep '07

Hi,everyone: I have get a tudos from svn a few days ago,but when I have compiled it,there is no bin and lib derictory under tudos/l4/build/.And In the /tudos/l4/build/include derictory ,there is only a l4 directory which containning just a one file,but all compile process are all right. Of course,when I use this L4env to compile the l4linux-2.6.21,there is a lot of error,you can seeing the error informantion from the attachment. The compiler instructor I used as follow: cd tudos make -C l4 config O=./build make -C l4 O=./build The config options I used are as same as before,so I don't know what have happened.And I used the linux distribution is slackware 10.2, gcc-3.4.6,make-3.81,bison-2.3. Everybody who knows this problem please hlep me.Thanks! Best Regards!

2 1

Re: about compile environment
by sunshine007 03 Sep '07

03 Sep '07

chenggh04 wrote: > > On Wednesday 15 August 2007 02:19, sunshine007 wrote: >> Thanks adam, >> >> but now i have problem with booting the L4linux by remote serial console. >> i follow the pdf kickstart. >> but, i still got error like this (after i reboot the machine): >> Using IPI shortcut mode >> List of all partitions >> No file system could not mount root, tried : >> kernel panic - not syncing >> VFS : unable to mount root fs on unknown block (0,0) > These information shows that your Fiasco has no problem and it could drag > the > booting of L4Linux. But the L4Linux can't find or mount the root file > system. > If VFS can't mount root fs with unknown blocks. First you should check > your > l4linux configuration with the filesystem type as ext2, ext3, etc. > Basically > you should compile the ext2 or ext3 into the linux kernel not compile as > modules. > > cheng, > sorry , i could not understand what u meant ? so, how to check myl4linux > configuration ? using cfdisk ? > i checked, my partition /sda3 , FS type is Linux ext2. > so, actually this can be solved or not. or i need to reformat my hardisk ? > sorrry i can't get u. :,( > > >> my menu.lst : >> #L4linux >> title L4Linux-2.6/Fiasco+dope >> root (hd0,2) >> kernel /boot/L4linux/bootstrap >> modaddr 0x02000000 >> module /boot/L4linux/fiasco -nowait -nokdb -serial_esc -comspeed 115200 >> -comport 1 >> module /boot/L4linux/sigma0 >> module /boot/L4linux/roottask task modname "bmodfs" attached 4 modules >> module /boot/L4linux/events >> module /boot/L4linux/names --events >> module /boot/L4linux/log --events >> module /boot/L4linux/dm_phys --isa=0x00800000 -v --events >> module /boot/L4linux/simple_ts -t 300 --events >> module /boot/L4linux/rtc --events >> module /boot/L4linux/l4io --noirq --events module >> module /boot/L4linux/loader --fprov=BMODFS linux26.cfg >> module /boot/L4linux/bmodfs >> module /boot/L4linux/vmlinuz >> module /boot/L4linux/linux26.cfg >> module /boot/L4linux/libloader.s.so >> module /boot/L4linux/libld-l4.s.so >> #end l4linux > Here, your root partition is located in /dev/hda3 >> #linux26.cfg >> modpath "(hd0,2)/boot/L4linux" >> task "vmlinuz" "earlyprintk=yes console=ttyS1,115200 init=1 mem=256M >> root=/dev/sda3" >> all_sects_writable >> > Here, your l4linux kernel image is located in /dev/hda3 but root > partitition > is located in /dev/sda3. > > But cheng, > how can u know my l4linux kernel image is located in /dev/hda3 ? > modpath (hd0,2) means /dev/hda3 ? > more confius now %-| > >> # fdisk -l >> >> Disk /dev/sda: 250.0 GB, 250000000000 bytes >> 255 heads, 63 sectors/track, 30394 cylinders Units = cylinders of 16065 * >> 512 = 8225280 bytes >> >> Device Boot Start End Blocks Id System >> /dev/sda1 1 5 40131 de Dell Utility >> /dev/sda2 * 6 2616 20972857+ 7 HPFS/NTFS >> /dev/sda3 2617 26931 195310237+ 83 Linux >> /dev/sda4 26932 30394 27816547+ 82 Linux swap >> >> It is i wrongly typed the root partition? >> > But there is no devive named /dev/hda3. So may you should replace > /dev/sda3 > with /dev/hda3. You can try. > Best regards. > Cheng Guanghui > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > -- View this message in context: http://www.nabble.com/about-compile-environment-tf4247269.html#a12155981 Sent from the L4 mailing list archive at Nabble.com.

2 2

Re: Maybe it is a bug or missing some libraries. please help me
by Bjoern Doebel 31 Aug '07

31 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Chenggh, > when I compile the latest version L4 I encouter these problems: > > /home/L4/tudos/l4/pkg/ipcmon/server/src/components.cc:13:18: error: vector: No > such file or directory > [..] vector is defined in l4/pkg/uclibc++ - which you should checkout and build. If you did so and it still does not work, it will be interesting to get the complete build output for l4/pkg/ipcmon/server that you get by running "make V=1". > My first opinion is that I miss some libraries and I install almost C++ > related libraries but the error is also. Another reason is it is indeed a > bug. But I am not sure. > OS: Ubuntu-7.04 > gcc-4.1 > g++-4.1 > Please help me to resolve this problem. Works for me with g++ 4.1.3 20070629 (prerelease) (Debian 4.1.2-13). Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG184xP5ijxgQLUNkRAjayAJ9+8hanmLC+sv1bclXki2gj12TLSwCgkH73 Chk63QZvIHn7fEywyraASeE= =ZM8F -----END PGP SIGNATURE-----

1 0

Basic L4-Linux setup & run
by Tiago Lopes 31 Aug '07

31 Aug '07

Hello, This is my first contact with L4 mKernel so forgive my limited knowledge on this subject. I've compiled dice, fiasco and L4env and starting to run some servers with trusted grub (grabbed the code from the latest OpenTC snapshot). But after reading all the L4-linux how-to's, I still cannot start L4-linux under "dope" or "con". I've noticed these docs looks aged, and some options are not accepted with current code base (--l4io, --noirq, etc). So, there is something I'm missing here... So far i can load everything (including dope server and l4-linux loads fine), but I can't see something like a system console, only plain and empty dope screen... I was especting some small dope window showing the l4-linux boot progress and maybe a console. Someone could show me the light please? Thanks :) Tiago Lopes Here is my config: --- start menu.lst ----------------------------------------------------- default 0 timeout 1 set ROOT := (cd) set SERIAL ?= "-serial -serial_esc -comspeed 115200 -comport 1" set FIASCOARGS := "-nokdb -nowait $(SERIAL)" title = test kernel $(ROOT)/tcb/bootstrap modaddr 0x02000000 module $(ROOT)/tcb/fiasco $(FIASCOARGS) module $(ROOT)/tcb/sigma0 -v module $(ROOT)/tcb/roottask -sigma0 -configfile task modname "bmodfs" attached 7 modules module $(ROOT)/tcb/roottask.config module $(ROOT)/tcb/events module $(ROOT)/tcb/names --events module $(ROOT)/tcb/log module $(ROOT)/tcb/dm_phys -v --events module $(ROOT)/tcb/simple_ts --events -t 384 module $(ROOT)/tcb/rtc --events module $(ROOT)/tcb/l4io --events module $(ROOT)/tcb/ore --events module $(ROOT)/tcb/l4dope --events module $(ROOT)/tcb/bmodfs module $(ROOT)/tcb/libloader.s.so module $(ROOT)/tcb/libld-l4.s.so module $(ROOT)/tcb/task_config.cfg # module $(ROOT)/tcb/con module $(ROOT)/tcb/run module $(ROOT)/tcb/proxygon module $(ROOT)/userland/l4linux2.6.21 module $(ROOT)/userland/drops.rd module $(ROOT)/tcb/loader --events --fprov=BMODFS task_config.cfg vbeset 0x117 --- end menu.lst ------------------------------------------------------ --- start roottask.config -------------------------------------------- #!roottask task sigma0 boot_priority 0xA0 task roottask boot_priority 0xA0 task modname "events" boot_priority 0xA0 task modname "names" boot_priority 0xA0 task modname "log" allow_cli boot_priority 0xA0 task modname "dm_phys" boot_priority 0xA0 task modname "simple_ts" boot_priority 0xA0 task modname "rtc" allow_cli task modname "l4io" allow_cli boot_priority 0xA0 task modname "ore" allow_cli boot_priority 0xA0 task modname "l4dope" allow_cli boot_priority 0xA0 task modname "bmodfs" boot_priority 0xA0 task modname "loader" allow_cli boot_priority 0xA0 --- end roottask.config -------------------------------------------- --- start task_config.cfg------------------------------------------- verbose 0 sleep 10 task "l4linux2.6.21" "mem=128M root=/dev/ram load_ramdisk=1 ramdisk_size=16384 l4env_rd=drops.rd video=l4fb:800x600@16 ,xpos:214,ypos:140,refreshsleep:75,title:LegacyLinux" all_sects_writable allow_vga allow_cli --- end task_config.cfg -------------------------------------------- --- start serial output ------------------------------------------------ Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2007 TU Dresden Rev: rUNKNOWN compiled with gcc 4.1.2 for Intel Pentium Performance-critical config option(s) detected: CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off CONFIG_FINE_GRAINED_CPUTIME is on 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: AuthenticAMD (6:8:0:0) Model: Athlon (Thoroughbred) at 696 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 1000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Command line found: "(cd)/tcb/roottask -sigma0 -configfile task modname "bmodfs" attached 7 modules" 409150kB ( 399MB) total RAM (reported by bootloader) 367424kB ( 359MB) received RAM from Sigma0 41376kB ( 41MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 A B C D E F ] Roottask: Parsing config file. configured task 0x02 (): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x04 (): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (events): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (names): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (log): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (dm_phys): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (simple_ts): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (rtc): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:10 small:ff mods:0 configured task 0x00 (l4io): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (ore): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (l4dope): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:a0 small:ff mods:0 configured task 0x00 (loader): vm_offs:0 irq:ffff lmcp:ffff allow_cli:1 mcp:ff prio:a0 small:ff mods:0 Roottask: Parsing command line config. configured task 0x00 (bmodfs): vm_offs:0 irq:ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:7 Roottask: Loading 18 modules. #05: loading "(cd)/tcb/events" from [0212c000-0216e66c] to [01540000-01548c10][01549000-0155e5d0] entry at 00062368 via trampoline page code symbols at [18ffe000-19000000] (8kB), lines at [18ff7000-18ffe000] (28kB) #06: loading "(cd)/tcb/names --events" from [0216f000-021ae253] to [002d0000-002d5e6a][002d6000-002e1000] entry at 00063370 via trampoline page code symbols at [18ff5000-18ff7000] (8kB), lines at [18fef000-18ff5000] (24kB) #07: loading "(cd)/tcb/log" from [021af000-021eb905] to [00400000-004068aa][00407000-00439848] entry at 00064368 via trampoline page code symbols at [18fed000-18fef000] (8kB), lines at [18fe7000-18fed000] (24kB) #08: loading "(cd)/tcb/dm_phys -v --events" from [021ec000-0227838c] to [01500000-015121ca][01513000-0151d000] entry at 00065378 via trampoline page code symbols at [18fe2000-18fe7000] (20kB), lines at [18fd5000-18fe2000] (52kB) #09: loading "(cd)/tcb/simple_ts --events -t 384" from [02279000-022c4d04] to [01400000-014080ea][01409000-01418608] entry at 0006637c via trampoline page code symbols at [18fd3000-18fd5000] (8kB), lines at [18fcb000-18fd3000] (32kB) #0a: loading "(cd)/tcb/rtc --events" from [022c5000-022f5ec1] to [01080000-010840e0][01085000-0108a000] entry at 00067370 via trampoline page code symbols at [18fc9000-18fcb000] (8kB), lines at [18fc4000-18fc9000] (20kB) #0b: loading "(cd)/tcb/l4io --events" from [022f6000-0254ee28] to [00b80000-00ba22a5][00ba3000-00c0a000] entry at 00069370 via trampoline page code symbols at [18f72000-18fc4000] (328kB), lines at [18f58000-18f72000] (104kB) #0c: loading "(cd)/tcb/ore --events" from [0254f000-0272f014] to [01800000-01832019][01833000-01862000] entry at 0006a370 via trampoline page code symbols at [18f4f000-18f58000] (36kB), lines at [18f29000-18f4f000] (152kB) #0d: loading "(cd)/tcb/l4dope --events" from [02730000-0289de76] to [01b00000-01b411a1][01b42000-01b83000] entry at 0006b374 via trampoline page code symbols at [18f1b000-18f29000] (56kB), lines at [16ed9000-16f05000] (176kB) #0e: loading "(cd)/tcb/bmodfs" from [0289e000-0293d5d0] to [01220000-01235659][01236000-0124d000] passing module (cd)/tcb/libloader.s.so [ 0293e000-029dcc02 ] passing module (cd)/tcb/libld-l4.s.so [ 029dd000-02a569c9 ] passing module (cd)/tcb/task_config.cfg [ 02a57000-02a57319 ] passing module (cd)/tcb/run [ 02a58000-02aa5ee1 ] passing module (cd)/tcb/proxygon [ 02aa6000-02b6bcbb ] passing module (cd)/userland/l4linux2.6.21 [ 02b6c000-0371baad ] passing module (cd)/userland/drops.rd [ 0371c000-0471c000 ] entry at 0006c47c via trampoline page code symbols at [18f16000-18f1b000] (20kB), lines at [18f04000-18f16000] (72kB) #0f: loading "(cd)/tcb/loader --events --fprov=BMODFS task_config.cfg" from [0471c000-047f49e4] to [01300000-01324ef9][01325000-01343000] entry at 0006d390 via trampoline page code symbols at [16ed3000-16ed9000] (24kB), lines at [16eba000-16ed3000] (100kB) names | Starting thread listening for `exit' events ROOT: Sending ports 0070-0070 to task #0a ROOT: Sending ports 0080-0080 to task #0a ROOT: Sending ports 0071-0071 to task #0a rtc | Date:29.08.2007 Time:18:16:01 simplets| Configured for 384 tasks. DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x19000000 (from L4 kernel info page) DMphys | using 0x00100000-0x19000000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x0009f000 -- -- RESERVED DMphys | 0x00100000-0x00161000 -- -- RESERVED DMphys | 0x00161000-0x001c6000 -- -- DENIED DMphys | 0x001c6000-0x002d0000 0 12 MAPPED DMphys | 0x002d0000-0x002e1000 -- -- DENIED DMphys | 0x002e1000-0x00400000 0 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c0a000 -- -- DENIED DMphys | 0x00c0a000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x0124d000 -- -- DENIED DMphys | 0x0124d000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01343000 -- -- DENIED DMphys | 0x01343000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x01419000 -- -- DENIED DMphys | 0x01419000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x0155f000 -- -- DENIED DMphys | 0x0155f000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x01862000 -- -- DENIED DMphys | 0x01862000-0x01b00000 0 12 MAPPED DMphys | 0x01b00000-0x01b83000 -- -- DENIED DMphys | 0x01b83000-0x01c00000 0 12 MAPPED DMphys | 0x01c00000-0x02800000 0 22 MAPPED DMphys | 0x02800000-0x0293e000 0 12 MAPPED DMphys | 0x0293e000-0x0471c000 -- -- DENIED DMphys | 0x0471c000-0x04800000 0 12 MAPPED DMphys | 0x04800000-0x16c00000 0 22 MAPPED DMphys | 0x16c00000-0x16eba000 0 12 MAPPED DMphys | 0x16eba000-0x18ef0000 -- -- DENIED DMphys | 0x18f00000-0x18f04000 0 12 MAPPED DMphys | 0x18f04000-0x19000000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 340552KB total, 340552KB free, 32KB reserved DMphys | 0x001c6000-0x002d0000 ( 1064KB, 1MB) free DS: DMphys | 0x002e1000-0x00400000 ( 1148KB, 1MB) free DS: DMphys | 0x0043a000-0x00b80000 ( 7448KB, 7MB) free DS: DMphys | 0x00c0a000-0x01080000 ( 4568KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x0124d000-0x01300000 ( 716KB, 1MB) free DS: DMphys | 0x01343000-0x01400000 ( 756KB, 1MB) free DS: DMphys | 0x01419000-0x01500000 ( 924KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x0155f000-0x01800000 ( 2692KB, 3MB) free DS: DMphys | 0x01862000-0x01b00000 ( 2680KB, 3MB) free DS: DMphys | 0x01b83000-0x0293e000 ( 14060KB, 14MB) free DS: DMphys | 0x0471c000-0x16eba000 (302712KB, 296MB) free DS: DMphys | 0x18f00000-0x18f04000 ( 16KB, 0MB) free DS: io | Enabling events support. l4dope | DOpE(init): using events mechanism ROOT: Sending ports 0cfb-0cfb to task #0b ROOT: Sending ports 0cf8-0cfb to task #0b ROOT: Sending ports 0cfe-0cff to task #0b bmodfs | Passed the following modules: io | PCI: Using configuration type 1 bmodfs | module "(cd)/tcb/libloader.s.so" (636kB) io | PCI: Probing PCI hardware bmodfs | module "(cd)/tcb/libld-l4.s.so" (487kB) io | PCI: Probing PCI hardware (bus 00) ROOT: Sending ports 0cfc-0cff to task #0b bmodfs | module "(cd)/tcb/task_config.cfg" (1kB) io | PCI: Cannot allocate resource region 4 of device 00:07.1 bmodfs | module "(cd)/tcb/run" (312kB) io | Limiting direct PCI/PCI transfers. bmodfs | module "(cd)/tcb/proxygon" (792kB) io | 00000000-ffffffff : PCI mem bmodfs | module "(cd)/userland/l4linux2.6.21" (11967kB) io | e8000000-ebffffff : Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX H bmodfs | module "(cd)/userland/drops.rd" (16384kB) io : ost bridge loader | sleeping for 10000 ms io | ec000000-ec7fffff : VMware Inc [VMware SVGA II] PCI Display Adapter io | ec800000-ec800fff : LSI Logic / Symbios Logic 53c1030 PCI-X Fusion- io : MPT Dual Ultra320 SCSI io | f0000000-f7ffffff : VMware Inc [VMware SVGA II] PCI Display Adapter io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | 1000-103f : Intel Corporation 82371AB/EB/MB PIIX4 ACPI io | 1040-105f : Intel Corporation 82371AB/EB/MB PIIX4 ACPI io | 1060-106f : VMware Inc [VMware SVGA II] PCI Display Adapter io | 1070-107f : Intel Corporation 82371AB/EB/MB PIIX4 IDE io | 1080-10ff : LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual io : Ultra320 SCSI io | 1400-147f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] io | Available IRQs=[ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f ] l4dope | L4INPUT native mode activated ore | l4dde_mm_init(): Using ... l4dope | L4INPUT: !!! W A R N I N G !!! ore | 16 MB at 0x00180000 (vmem) l4dope | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. ore | 16 MB in 1 regions (kmem) l4dope | L4INPUT: !!! W A R N I N G !!! ROOT: Sending ports 0060-006f to task #0b ore | main(): initialized DDELinux2.4 l4dope | serio: i8042 AUX port at 0x60,0x64 irq 12 ore | main(): loopback: 0 l4dope | serio: i8042 KBD port at 0x60,0x64 irq 1 ore | device lo entered promiscuous mode l4dope | input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 ore | main(): Initialized 1 network devices. l4dope | input: AT Translated Set 2 keyboard on isa0060/serio0 ore | Device = lo, IRQ = 0, MAC = 00:00:00:00:00:00 l4dope | input: PC Speaker ore | main(): Registering 'ORe' at names... l4dope | input: L4 input event injector ore | main(): Ready for service. l4dope | L4 input event injector: IRQ handler up l4dope | a0060/serio1/input0 l4dope | connect "ImPS/2 Generic Wheel Mouse", isa0060/serio1/input0 l4dope | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4dope | connect "PC Speaker", isa0061/input0 l4dope | connect "L4 input event injector", l4/sys l4dope | SharedMem(alloc): hl.raw=100000, id=43, size=800 l4dope | SharedMem(get_adr): address = 0x6000 l4dope | SharedMem(alloc): hl.raw=100000, id=44, size=800 l4dope | SharedMem(get_adr): address = 0x7000 l4dope | SharedMem(alloc): hl.raw=100000, id=45, size=800 l4dope | SharedMem(get_adr): address = 0xd000 l4dope | SharedMem(alloc): hl.raw=100000, id=46, size=800 l4dope | SharedMem(get_adr): address = 0xe000 l4dope | SharedMem(alloc): hl.raw=100000, id=47, size=800 l4dope | SharedMem(get_adr): address = 0xf000 l4dope | SharedMem(alloc): hl.raw=100000, id=49, size=800 l4dope | SharedMem(get_adr): address = 0x16000 l4dope | SharedMem(alloc): hl.raw=100000, id=4a, size=800 l4dope | SharedMem(get_adr): address = 0x17000 l4dope | dope: paddr=f0000000 size=16384KiB l4dope | Mapped video memory at f0000000 to 03000000+000000 [16384kB] via L4IO l4dope | mapping: vaddr=0x3000000 size=16777216(0x1000000) offset=0(0x0) l4dope | Frame buffer base: 0x3000000 l4dope | Resolution: 1024x768x16 l4dope | Bytes per scanline: 2048 l4dope | Current video mode is 1024x768 red=11:5 green=5:6 blue=0:5 res=0:0 loader | l4linux2.6.21: Starting application using libld-l4.s.so loader | l4linux2.6.21,#10: Loading binary loader | l4linux2.6.21,#10: Loading ldso loader | l4linux2.6.21,#10: Starting libld-l4.s.so at 00013800 via 0000cbf0 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (tjcl@fx242) (gcc version 4.1.2) #3 Wed Aug 2 l4lx : 2 16:43:46 WEST 2007 l4lx | Binary name: l4linux2.6.21 l4lx | Kernel command line (6 args): mem=128M root=/dev/ram load_ramdisk=1 r l4lx : amdisk_size=16384 l4env_rd=drops.rd video=l4fb:800x600@16 ,xpos:214,yp l4lx : os:140,refreshsleep:75,title:LegacyLinux l4lx | Image: 00400000 - 00683000 [2572 KiB]. l4lx | Areas: Text: 00400000 - 005e9000 [1956kB] (a bit longer) l4lx | Data: 005e9000 - 005fe2cc [84kB] l4lx | Initdata: 00602000 - 006260a0 [144kB] l4lx | BSS: 00628000 - 00680900 [354kB] l4lx | l4lx_thread_create: Created thread 10.03 (tamer) l4lx | Using tamed mode. ROOT: Sending all ports (for cli/sti) to task #0f l4lx | Got 65536 out of 65536 I/O ports l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 10.04 (server) l4lx | main thread will be 10.04 l4lx | l4env_register_pointer_section: addr = 00600000 size = 536576 l4lx | sec-w-init: virt: 0x00600000 to 0x00682fff [524 KiB] l4lx | sec-w-init: Number of physical regions: 1, 536576 Bytes l4lx | sec-w-init: 1: Phys: 0x0093e000 to 0x009c1000, Size: 536576 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 128MB l4lx | Main memory: virt: 0x00800000 to 0x087fffff [131072 KiB] l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes l4lx | Main memory: 1: Phys: 0x06800000 to 0x0e800000, Size: 134217728 l4lx | Filling lower ptabs... l4lx | Done (1338 entries). l4lx | l4env_rd_path: drops.rd l4lx | Loading: drops.rd l4lx | INITRD: Size of RAMdisk is 16384KiB l4lx | RAMdisk from 08800000 to 09800000 [16384KiB] l4lx | l4lx_thread_create: Created thread 10.05 (timer.i0) l4lx | l4lx_thread_create: Created thread 10.06 (Idler) l4lx | Creating 1 ORe device(s). l4lx | Opening device eth0 at ORe instance ORe l4lx | l4ore_open(): called l4lx | l4ore_open(): descriptor: 0 l4lx | ore_lookup_server(): ORe server ORe = C.02 l4lx | ore_do_open(): called ore | [C.2] ore/server/src/clients.c:215:setup_connection(): ore | Error: no device found. l4lx | ore_do_open(): opened. worker = 7FF.7F l4lx | [10.4] ore/lib/client/lib.c:181:l4ore_open(): l4lx | Error: ore_open() returned INVALID_ID --- end serial output ------------------------------------------------

2 3

Re: some questions in the l4 config
by Adam Lackorzynski 30 Aug '07

30 Aug '07

On Wed Aug 29, 2007 at 21:33:45 +0000, chenggh wrote: > Thanks. There are still some questions about the l4 config > > In the drops home directory we could use `make -C l4 config O=./build` to > enter the l4 configuration interface. There are some options I don't > understand as following: > Target Architecture --- > (x86) Target Architecture > This option is ok and there are 3 options to be chosen. > CPU type: "586" > This option is confused because it depends on our input. For example If my > cpu is pentim4 can I input p4 in the CPU type? In this place is there > avaiable small cpu type set? You can basically put there what you want. It only affects gcc optimization settings. For pentium4 it would be pentium4. > (L4.V2) ABI > (X) L4.V2 > ( ) L4.X2 > ( ) L4.Sec.(V2.emu) > ( ) Linux > There are four options to be chosen. L4.v2, L4.X2 and L4.sec > are explained in other documents. But I choose Linux in this place what can > we do? The ABI name would be set to linux. I think it's unused nowadays. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: some questions in the l4 config
by chenggh 29 Aug '07

29 Aug '07

Thanks. There are still some questions about the l4 config In the drops home directory we could use `make -C l4 config O=./build` to enter the l4 configuration interface. There are some options I don't understand as following: Target Architecture --- (x86) Target Architecture This option is ok and there are 3 options to be chosen. CPU type: "586" This option is confused because it depends on our input. For example If my cpu is pentim4 can I input p4 in the CPU type? In this place is there avaiable small cpu type set? (L4.V2) ABI (X) L4.V2 ( ) L4.X2 ( ) L4.Sec.(V2.emu) ( ) Linux There are four options to be chosen. L4.v2, L4.X2 and L4.sec are explained in other documents. But I choose Linux in this place what can we do? Thanks. Cheng Guanghui

1 0

some questions in the l4 config
by chenggh 29 Aug '07

29 Aug '07

Hi: In the drops home directory we could use `make -C l4 config O=./build` to enter the l4 configuration interface. There are some options I don't understand as following: Target Architecture --- (x86) Target Architecture // This is ok and there are 3 options to be chosen. CPU type: "586" //This option is confused because it depends on our input. For example If my cpu is pentim4 can I input p4 in the CPU type? In this place is there avaiable small cpu type set? (L4.V2) ABI (X) L4.V2 ( ) L4.X2 ( ) L4.Sec.(V2.emu) ( ) Linux There are four options to be chosen. L4.v2, L4.X2 and L4.sec are explained in other documents. But I choose Linux in this place what can we do? Advances: [*] Use system-call entry code in the KIP (absolute) [ ] Use hierarchical task system (EXPERIMENTAL) [ ] Enable RELEASE flag [ ] Do not build anything outside l4 directory Please also explain these 4 options. Thans very much. Cheng Guanghui

2 1

Re: bug report
by chenggh 29 Aug '07

29 Aug '07

> Thank you for your bug report. The installed version of bison is to old. > Please find attached a patch that fixes bison version detection. (You > will have to rerun 'make -f Makefile.drops' in the dice directory.) What is the distribution you used? I use the Ubuntu6.06 with default bison version 2.1. Is the bison 2.3 ok? Thanks. Cheng Guanghui

2 1

bug report
by chenggh 29 Aug '07

29 Aug '07

ranlib libfe.a make[5]: Leaving directory `/home/L4/tudos/dice/src/fe' Making all in parser make[5]: Entering directory `/home/L4/tudos/dice/src/parser' Making all in idl make[6]: Entering directory `/home/L4/tudos/dice/src/parser/idl' bison --report=all -d idl-parser.yy idl-parser.yy:2.1-8: invalid directive: `%require' idl-parser.yy:2.10-15: syntax error, unexpected string make[6]: *** [idl-parser.tab.cc] Error 1 make[6]: Leaving directory `/home/L4/tudos/dice/src/parser/idl' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/L4/tudos/dice/src/parser' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/L4/tudos/dice/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/L4/tudos/dice' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/L4/tudos/dice' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/L4/tudos/dice' make: *** [../dice] Error 2 make: Leaving directory `/home/L4/tudos/l4' OS: Ubuntu6.06 bison (GNU Bison) 2.1 This l4 is downloaded on 2007-08-27. Thanks. Cheng Guanghui

2 1

Re: The ultimate HOW-TO
by Bjoern Doebel 27 Aug '07

27 Aug '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 skitmax81(a)yahoo.it wrote: > Bjoern Doebel wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> >>> PS. For a test, could you please post the entry to add at the menu.lst >>> file >>> to try booting L4Linux? >>> Maybe everything is still working.. &-( >> Did you have a look at >> http://os.inf.tu-dresden.de/L4/LinuxOnL4/use-2.6.shtml >> ? >> .... >> > Quoted from: > http://www.nabble.com/The-ultimate-HOW-TO-tf4192072.html#a12351172 > > ------------------------------------------------------------------------------------------------------ > > Yes, I've read the page, but, because I'm newbie, I don't understand how to have a standalone > setup without DOpE.. I would like to have a simple console where compile/build and run <i>lmbench</i> As Adam already pointed out, you shouldn't even use DOpE when doing a benchmark. So let's sum it up: * Build Fiasco and the hello server. Then run it and make sure that the red (performance-critical) warnings at Fiasco bootup are gone. * Build the L4Env packages needed for L4Linux, namely those that appear in the menu.lst which can be found on the "Using L4Linux" page you already know. * Build L4Linux. Disable DOpE support, disable networking and sound stuff, enable VGA text console and hard disk support. * Put all the binaries obtained so far into the boot directory where GRUB gets its modules from, e.g., where your (SUSe?) Linux kernel is. * Create a loader config file for L4Linux, just like the one on the L4Linux page and put it in the same location. You don't have to use a ramdisk, but can just put a "root=/dev/hda1" or something similar there. Basically, you should be able to use your native Linux environment from HD with L4Linux, too. * Add a menu.lst entry such as the one on the L4Linux page to your GRUB menu.lst. Which of the above points is unclear to you? > I'm not intereste to have networking or sound or other stuffs, only a simple console Linux-like.. it's > for a course and I'm a bit frustrated.. two months and no results.. sigh! :-(( Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG0v6tP5ijxgQLUNkRApeUAJ9jKk/U6xdywJ4Ih1FH4XeWiMT+cgCfXelx LCnf2fk5w8zcNoyxIwOnJm0= =11yE -----END PGP SIGNATURE-----

1 0

Re: The ultimate HOW-TO
by chenggh 25 Aug '07

25 Aug '07

> > API Version: (87) experimental > > Sigma0 config ip:001048a8 sp:002c9760 > > Roottask config ip:00110000 sp:00000000 > > Starting kernel /DROPS/kernel/fiasco/build/fiasco at 0030082c > > > > Comport 0x0001 is not accepted by the uart driver! > > > > Welcome to Fisco (ia32)! > > DD-L4(v2)/ia32 microkernel (C) 1998-2007 TU Dresden > > Rev: rUNKNOWN compiled with gcc 4.1.0 for Intel Pentium [ ] > > Performance-critical config option(s) detected: > > CONFIG_NDEBUG is off > > > > Enabling special fully nested mode for PIC > > > > Assertion failed: '0' > > in /DROPS/kernel/fiasco/src/abi/kip.cpp:126 > > at f00175d1 > > > > Press any key to reboot. > > Founded the option and set it on, I see that the output is something like > #06.. but it reboots and I can't read so fast! > The result is that I can't be more exahustive in the explaination so I > answer: How to have a log file to read the outputs? In the grub/menu.lst you could do like this: module /boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 Then you could receive the boot message in another machine with connection to the l4 machine by ttyS0 (com1) with comspeed 115200 like this: minicom -m -s -C logfile Good luck to you. Cheng Guanghui

1 0

Re: The ultimate HOW-TO
by chenggh 25 Aug '07

25 Aug '07

> Founded the option and set it on, I see that the output is something like > #06.. but it reboots and I can't read so fast! > The result is that I can't be more exahustive in the explaination so I > answer: How to have a log file to read the outputs? In the grub/menu.lst you could do like this: module /boot/L4Linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 Then you could receive the boot message by the ttyS0 (com1) with comspeed 115200. Good luck. Cheng Guanghui

2 1

Re: about compile environment
by chenggh 15 Aug '07

15 Aug '07

On Wednesday 15 August 2007 02:19, sunshine007 wrote: > Thanks adam, > > but now i have problem with booting the L4linux by remote serial console. > i follow the pdf kickstart. > but, i still got error like this (after i reboot the machine): > Using IPI shortcut mode > List of all partitions > No file system could not mount root, tried : > kernel panic - not syncing > VFS : unable to mount root fs on unknown block (0,0) These information shows that your Fiasco has no problem and it could drag the booting of L4Linux. But the L4Linux can't find or mount the root file system. If VFS can't mount root fs with unknown blocks. First you should check your l4linux configuration with the filesystem type as ext2, ext3, etc. Basically you should compile the ext2 or ext3 into the linux kernel not compile as modules. > my menu.lst : > #L4linux > title L4Linux-2.6/Fiasco+dope > root (hd0,2) > kernel /boot/L4linux/bootstrap > modaddr 0x02000000 > module /boot/L4linux/fiasco -nowait -nokdb -serial_esc -comspeed 115200 > -comport 1 > module /boot/L4linux/sigma0 > module /boot/L4linux/roottask task modname "bmodfs" attached 4 modules > module /boot/L4linux/events > module /boot/L4linux/names --events > module /boot/L4linux/log --events > module /boot/L4linux/dm_phys --isa=0x00800000 -v --events > module /boot/L4linux/simple_ts -t 300 --events > module /boot/L4linux/rtc --events > module /boot/L4linux/l4io --noirq --events module > module /boot/L4linux/loader --fprov=BMODFS linux26.cfg > module /boot/L4linux/bmodfs > module /boot/L4linux/vmlinuz > module /boot/L4linux/linux26.cfg > module /boot/L4linux/libloader.s.so > module /boot/L4linux/libld-l4.s.so > #end l4linux Here, your root partition is located in /dev/hda3 > #linux26.cfg > modpath "(hd0,2)/boot/L4linux" > task "vmlinuz" "earlyprintk=yes console=ttyS1,115200 init=1 mem=256M > root=/dev/sda3" > all_sects_writable > Here, your l4linux kernel image is located in /dev/hda3 but root partitition is located in /dev/sda3. > # fdisk -l > > Disk /dev/sda: 250.0 GB, 250000000000 bytes > 255 heads, 63 sectors/track, 30394 cylinders Units = cylinders of 16065 * > 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 1 5 40131 de Dell Utility > /dev/sda2 * 6 2616 20972857+ 7 HPFS/NTFS > /dev/sda3 2617 26931 195310237+ 83 Linux > /dev/sda4 26932 30394 27816547+ 82 Linux swap > > It is i wrongly typed the root partition? > But there is no devive named /dev/hda3. So may you should replace /dev/sda3 with /dev/hda3. You can try. Best regards. Cheng Guanghui

1 0

about compile environment
by huang 15 Aug '07

15 Aug '07

hi,dear Adam: Could you give me some advices about the operating system on which we can build fiasco and l4env? I have used some different linux such as suse 9 and fedora core 3, fedora core 6 and so on, there always some problem ocurred while building or booting the l4 components. What operating system are you using now? And what operating systems are fully tested for the l4 system? Best regards! huang

6 9

about input in hello
by huang 11 Aug '07

11 Aug '07

hi,dear all: if I want to get some input in the "hello" example, what should I do? I simply use "scanf()", but it does not work! my main.c is as below: #include <l4/sys/types.h> #include <l4/sys/syscalls.h> #include <l4/sys/ipc.h> #include <stdio.h> int main(int argc, char **argv) { l4_threadid_t th; l4_msgdope_t result; l4_umword_t d1, d2; int choice; printf("Hello World\n"); th = l4_myself(); for (;;) { printf("hello: My thread-id is %x.%x\n", th.id.task, th.id.lthread); scanf("%d",&choice); if(choice==0) return 0; } }

2 1

Re: I have a problem, when run Fiasco-UX
by chenggh 10 Aug '07

10 Aug '07

On Friday 10 August 2007 09:27, xiaosan Huang wrote: > Hi, > > I am a new learner of Fiasco-UX. I followed the steps on > http://os.inf.tu-dresden.de/Studium/MkK/uebung/. Everything was ok before > I typed the command : > > ./fiasco -l name -l log -l dm_phys -l hello > > The error information is as follows: > > Fiasco-UX on Linux 2.6.19(i686) > > Mapped 64MB Memory +0 KB Framebuffer + 0 MB Input Area on FD3 > > > > Failed to open file : sigma0 Do you have the sigma0 application in the current directory? cheng

1 0

Re: I have a problem, when run Fiasco-UX
by Udo A. Steinberg 10 Aug '07

10 Aug '07

On Fri, 10 Aug 2007 17:27:34 +0800 xiaosan Huang (XH) wrote: XH> The error information is as follows: XH> XH> Fiasco-UX on Linux 2.6.19(i686) XH> Mapped 64MB Memory +0 KB Framebuffer + 0 MB Input Area on FD3 XH> Failed to open file : sigma0 XH> XH> What is the problem? Please help me. The Problem is that Fiasco-UX cannot find the sigma0 binary file. You can either: * copy sigma0 into the directory where you start Fiasco-UX * create a symlink named "sigma0" in that directory, pointing to the file * specify -S parameter with the full path of sigma0 For some more details, have a look at: http://os.inf.tu-dresden.de/fiasco/ux/using.shtml Cheers, - Udo

1 0

I have a problem, when run Fiasco-UX
by xiaosan Huang 10 Aug '07

10 Aug '07

Hi, I am a new learner of Fiasco-UX. I followed the steps on http://os.inf.tu-dresden.de/Studium/MkK/uebung/. Everything was ok before I typed the command : ./fiasco -l name -l log -l dm_phys -l hello The error information is as follows: Fiasco-UX on Linux 2.6.19(i686) Mapped 64MB Memory +0 KB Framebuffer + 0 MB Input Area on FD3 Failed to open file : sigma0 What is the problem? Please help me. Xiaosan Huang

1 0

L4.sec status ping
by Ernst Rohlicek jun. 07 Aug '07

07 Aug '07

Hello everyone, I would just like to ask about the current status or some roadmap for L4.sec? Is it actively being worked on? Reason is: I need to choose a microkernel to start working on an experimental operating system within this year I need some facts for decision-making - and I would prefer a capability-based one like L4.sec. Thank you, Ernst Rohlicek jun.

7 16

Status of idl4?
by Jonathan S. Shapiro 06 Aug '07

06 Aug '07

Just as a sanity check, I ran a trivial IDL file through idl4. The generated server header does not provide any obvious means to get the reply send, because the message block is passed **by value**. Is this intentional? Is DICE now preferred? -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

2 1

NMI during irq_interrupt() issue
by Stefan Scheler 05 Aug '07

05 Aug '07

Hello, I implemented a statistical profiler for fiasco using performance monitoring counters (nmi handler is attached to handle_slow_trap()). It works fairly well for "mathematical" workloads but as soon as interrupt activity gets involved to a greater extent, the system freezes. For example, keeping a button pressed while sampling will freeze the machine within a few seconds. The NMI watchdog does not trigger during that freeze. Higher sampling rates also cause these freezes. So imho there seems to be a problem when irq_interrupt() or Irq::hit() is interrupted by an NMI. What do you think? Any hints on how to fix this or on how to debug this will be greatly appreciated. Thanks in advance. I will happily provide further information if needed. -- Stefan Scheler

3 4

[DICE] Compilation error with two flexpages
by Clermont, Nicolas 01 Aug '07

01 Aug '07

Hi everybody, I am currently playing with flexpages. I have written simple client/server application which sends data to each other using flexpages. I have written a simple IDL file for the server interface. The first version was the following : library test_server { interface worker { int send_data([in] flexpage page, [out, max_is(4096)] char reply[]); }; }; The client sends data through the flexpage, and the server replies using string ipc. This way the DICE generated code compiles without error, and my application works. Then I wanted the server to reply also through a flexpage, but another one than the page provided by the client application. So I modify my IDL this way : library test_server { interface worker { int send_data([in] flexpage page, [out, in] flexpage reply); }; }; I use [out, in] because this way the client can first assign the snd_base before sending the request. After modifying my client lib and the component function accordingly, I get a compile error in a DICE generated file : /home/nico/build-tudos/pkg/test_server/idl/OBJ-x86-l4v2/test_server_worker-s erver.c: In function `test_server_worker_wait_any': /home/nico/build-tudos/pkg/test_server/idl/OBJ-x86-l4v2/test_server_worker-s erver.c:91: error: `_dice_tmp_offset' undeclared (first use in this function) /home/nico/build-tudos/pkg/test_server/idl/OBJ-x86-l4v2/test_server_worker-s erver.c:91: error: (Each undeclared identifier is reported only once /home/nico/build-tudos/pkg/test_server/idl/OBJ-x86-l4v2/test_server_worker-s erver.c:91: error: for each function it appears in.) /home/nico/build-tudos/pkg/test_server/idl/OBJ-x86-l4v2/test_server_worker-s erver.c: In function `test_server_worker_reply_and_wait': /home/nico/build-tudos/pkg/test_server/idl/OBJ-x86-l4v2/test_server_worker-s erver.c:172: error: `_dice_tmp_offset' undeclared (first use in this function) What I see in the generated file : filter_server_worker_wait_any (...) { ... if (l4_ipc_fpage_received(_dice_result)) { _dice_tmp_offset = 0; while ((_dice_msg_buffer->_word._word[0][_dice_tmp_offset++] != 0) && (_dice_msg_buffer->_word._word[0][_dice_tmp_offset++] != 0)) /* empty */; /* skip zero fpage */ _dice_tmp_offset += 2; _dice_opcode = _dice_msg_buffer->_word._word[0]; } else _dice_opcode = _dice_msg_buffer->_word._word[0]; return _dice_opcode; } The _dice_tmp_offset is not declared, the second error (line 172) is about the same thing (it is exactly the same code in reply_and_wait()). So I have tried to declare _dice_tmp_offset as an unsigned int, then I have : /home/clermont/build-tudos/pkg/filter_server/idl/OBJ-x86-l4v2/filter_server_ worker-server.c: In function `filter_server_worker_wait_any': /home/clermont/build-tudos/pkg/filter_server/idl/OBJ-x86-l4v2/filter_server_ worker-server.c:92: error: subscripted value is neither array nor pointer /home/clermont/build-tudos/pkg/filter_server/idl/OBJ-x86-l4v2/filter_server_ worker-server.c:92: error: subscripted value is neither array nor pointer (The line 92 is the one with while(...)). Indeed after looking the code I find it really strange, as _word[0] is a register.... More _dice_tmp_offset is incremented by two after the while loop and never used after... I really don't understand this code... If I only set the reply flexpage as [in], I have the same behavior... Am I doing something wrong ? Could it be a bug in DICE ? Is it permitted to use one in-flexpage and one out-flexpage for the same function ? Is there something special to do ? Thanks, -- nico

2 1

Re: about l4linux on fiasco-UX
by Adam Lackorzynski 29 Jul '07

29 Jul '07

On Wed Jul 25, 2007 at 16:49:51 +0800, kashin Lin wrote: > 2007/7/25, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > > > > > >On Tue Jul 24, 2007 at 10:10:23 +0800, kashin Lin wrote: > >> 2007/7/24, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > >> > > >> > > >> >On Sun Jul 22, 2007 at 23:09:10 +0800, kashin Lin wrote: > >> >> 2007/7/22, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > >> >> > > >> >> > > >> >> >On Sun Jul 22, 2007 at 01:00:44 +0800, kashin Lin wrote: > >> >> >> 2007/7/21, kashin Lin <kashin08(a)gmail.com>: > >> >> >> > > >> >> >> > > >> >> >> > > >> >> >> >2007/7/21, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > >> >> >> >> > >> >> >> >> > >> >> >> >> On Fri Jul 20, 2007 at 15:54:06 +0800, kashin Lin wrote: > >> >> >> >> > when i runed l4linux on fiasco-UX by "./lx con", it stoped > >> >> >> >> > after following messages: > >> >> >> >> > >> >> >> >> We need to find out by adding earlyprintk=keep to the L4Linux > >> >kernel > >> >> >> >> command line. Then there should be more text. > >> >> >> > > >> >> >> > > >> >> >> > >> >> >> > >> >> >> Here are the results after adding "earlyprintk=keep" : > >> >> > > >> >> >> >con | vc[1] 640x480@16, bpl:1280, gmode:0x15, evprt:E.03save:0 > >> >> >> >run | contxt_init(): 640x462, cols:80, lines:33, > >sb_lines:1033 > >> >> >> >l4lx | INITRD: Size of RAMdisk is 16384KiB > >> >> >> >l4lx | RAMdisk from 03400000 to 04400000 [16384KiB] > >> >> >> >[ 0.000000] Linux version 2.6.21-l4 (kashin08@kashin08-desktop > >) > >> >(gcc > >> >> >> >version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #1 Fri Jul 20 12:14:47 CST > >> >2007 > >> >> >> >[ 0.000000] CPU: Vendor unknown, using generic init. > >> >> >> >[ 0.000000] CPU: Your system may be unstable. > >> >> >> >[ 0.000000] dm_phys: 0000000000800000 - 0000000003400000 > >> >(usable) > >> >> >> >[ 0.000000] 44MB memory available. > >> >> >> >[ 0.000000] INITRD: 03400000 - 04400000 > >> >> >> >[ 0.000000] Zone PFN ranges: > >> >> >> >[ 0.000000] DMA 0 -> 512 > >> >> >> >[ 0.000000] Normal 512 -> 13312 > >> >> >> >[ 0.000000] early_node_map[1] active PFN ranges > >> >> >> >[ 0.000000] 0: 0 -> 13312 > >> >> >> >[ 0.000000] Allocating PCI resources starting at 10000000 > >(gap: > >> >> >> >03400000:fcc00000) > >> >> >> >[ 0.000000] Built 1 zonelists. Total pages: 13208 > >> >> >> >[ 0.000000] Kernel command line: mem=44M earlyprintk=keep > >> >root=1:0 > >> >> >> >load_ramdisk=1 ramdisk_size=16384 l4env_rd=../../../test_lx/rd1 > >> >> >> >panicblink=0 > >> >> >> >lang=us > >> >> >> >[ 0.000000] Initializing CPU#0 > >> >> >> >[ 0.000000] PID hash table entries: 256 (order: 8, 1024 bytes) > >> >> >> >[ 0.000000] Detected 2010.311 MHz processor. > >> >> >> >[ 1236.204905] keeping early console > >> >> >> >l4lx | panic: going to sleep forever, bye > >> >> > > >> >> >Can you please post your .config? > >> >> > >> >> > >> >> following is the content of my ".config". (also in attached file) > >> > > >> >So many options enabled... Can you please use the ux default > >> >configuration for a start? (arch/l4/configs/x86-ux_defconfig, > >> >make x86-ux_defconfig will also do). > >> > >> > >> after using "make x86-ux_defconfig", it still doesn't work. > >> but the error messages are different this time : > > > >Ok, different. Can you please add showpfexc=1 to the L4Linux kernel > >command line and post the last part of log again?! There should be more > >output then. Then please look up the code at the PC that is printed, or > >send me (only me) your vmlinuz file. > > > following are the messages after i added "showpfexc=1". > NET: Registered protocol family 16 > l4lx | EX: F.04: pc = 0040acf5 trapno = 0xd err = 0x402 > Setting up standard PCI resources > l4lx | EX: F.04: pc = 0040acf5 trapno = 0xd err = 0x402 > l4lx | EX: F.04: pc = 00408d36 trapno = 0xd err = 0x0 > Trap: 13: 0000 [#1] It's trapping on segment access, I wonder how this can happen. What's the version of your host Linux kernel? > another question i want to ask : > according to "l4-kickstart.pdf", there are some configuration options should > been enable. > for instance: > > Graphics support > <*> Support for frame buffer devices > Console display driver support ---> > [ ] VGA text console > < > MDA text console (dual-headed) (EXPERIMENTAL) > <*> Framebuffer Console support > [*] Framebuffer Console Rotation > [ ] Select compiled-in fonts > > but the default configuration in "arch/l4/configs/x86-ux_defconfig" doesn't > obey that. x86-ux_defconfig enables all of the three options, or do you mean that the pdf says other options should be enabled? > should i follow the "l4-kickstart.pdf" or arch/l4/configs/x86-ux_defconfig > is fine? x86-ux_defconfig, this should always be the most recent version. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 3

Writing about L4 and the future Information Society
by John van V. 29 Jul '07

29 Jul '07

Hello all, I am presently starting to write about L4; I was an admin in financial technology from 1999 to 2002 and I specifically worked to integrate OSs to enable the workforces of the world, and I also attempted to help talented youth learn to operate systems, and also hoped to help impoverished nations join the Information Society. Here is my personal website where my writing will be presented. You can see my motivations: http://thinman.com (it is presently in its "capstone degree project" format, which earned me an A. I will be attempting to evolve it in the near future into a mix of operating systems, hardware platforms, education, and fine art to create the kind of mental diversity we find in a healthy society. In 2000, I strongly felt that Linux needed to evolve, and that new OSs needed to be introduced to the public domain. I looked at ExOS, and I liked it a lot, but it had the problem of being tied to only a single CPU architecture. In 2002 I got fired along w/ all my technology collaborators and fellow club members because of the tech crash, and then I also started to suffer the traumatic after affects from being a volunteer rescuer during the terror attack on the World Trade Center on 9/11/2001. Probably a hundred or more people I knew were killed, including 1/2 of my local fire department whom I knew personally. Also former coworkers of mine as well as many of the Sun techs and sales staff I knew had perished. The Sybase meeting rooms that had been frequent meeting places for my various clubs has also been destroyed. What I did afterwards to get past my grief issues was become a long haul truck driver, and I drove the roads of the US for a few years, which actually was an incredibly enlightening experience. In 2005, when I was about to start investing in my own truck fleet, I had an epiphany -- to teach middle school kids science, and especially technology. I believe that middle school and high school students, from my experiences, are the best potential technology core from the perspective of the future-- and they work for free. Also, I should mention that many people are saying that OS development in general has slowed to a near halt. This appears to me to be so, though all of you involved in L4 are not to blame! I feel that L4, as the leading new OS, can be a focus for, or perhaps locus of, all the things we need to do, and all the reflections we need to make based on the nearly two decades of successful, yet ultimately heartbreaking experiences, in the new Information Society. Any comments would be greatly appreciated. Thanks in advance, John -- Empathy http://thinman.com/empathy Photography http://thinman.com/photography Technology http://thinman.com

2 1

problem about using Fiasco-UX
by 王涛 27 Jul '07

27 Jul '07

Hi all. after i built the kernel ,first i prepare as follow: Mkdir fiasco_test Cp kernel.image fiasco_test/fiasco Cp irq0 fiasco_test/ Cp roottask fiasco_test/ Cp sigma0-ux fiasco_test Cp bootstrap fiasco_test/ then ./fiasco i got the error message: Loading Module 0x00090000-0x00096cc4 [sigma0-ux] Loading Module 0x00120000-0x002bd9f4 [roottask] Bootstrapping... [1;32mWelcome to Fiasco(ux)! [0;32mDD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Tue Oct 17 17:00:30 2006 compiled with gcc 4.1.1 for Intel Pentium[0m CPU: GenuineIntel (F:4:7:0) Model: Pentium D (Smithfield) at 2792 MHz 128 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: 24576 bytes (6 pages) segmentation fault Fiasco-UX on Linux 2.6.18-1.2798.fc6 (i686) gcc/g++ version:4.1.1 i will appreciate that you can help me solve the problem

2 1

About build fiasco for xScale
by kashin Lin 25 Jul '07

25 Jul '07

Hi~ When i cross-compile fiasco for xScale, it says 'kernel.image': No such file. i checked the files in kernel/fiasco/build. no file named "kernel.image" but there is a file named "fiasco.image". i am not sure what's the relationship between them. how to fix it? following is part of the output message: make[3]: Entering directory `/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/build' Checking compiler config... unchanged. make[3]: Leaving directory `/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/build' make srcdir=/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/src objbase=/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/build -f /home/kashin08/L4Linux/L4_ARM/kernel/fiasco/src/Makefile.sub2 all make[3]: Entering directory `/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/build' -e ... Generating version information Checking initcalls arm-linux-nm: 'kernel.image': No such file start (_initcall_start) or end (_initcall_end) symbol not found! at /home/kashin08/L4Linux/L4_ARM/kernel/fiasco/src/../tool/checkinitcalls line 67. make[3]: *** [Checkinitcalls] Error 1 make[3]: Leaving directory `/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/build' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/kashin08/L4Linux/L4_ARM/kernel/fiasco/build' make[1]: *** [build] Error 2 make[1]: Leaving directory `/home/kashin08/L4Linux/L4_ARM/kernel/fiasco' make: *** [../kernel/fiasco] Error 2

2 9

about l4linux on fiasco-UX
by kashin Lin 24 Jul '07

24 Jul '07

Hi~ according to http://os.inf.tu-dresden.de/fiasco/ux/status.shtml, it says one of the differences between native fiasco and fiasco-UX is : Port I/O and I/O flexpages. so is it possible to run a multimedia application in l4linux on fiasco-UX? (ex: jpeg, mp3 ... etc) this kind of application seems that it could access hardware directly( ex: speaker or monitor )? i am not sure is this guessing right.

3 13

About download GRUB
by kashin Lin 24 Jul '07

24 Jul '07

Hi~ according to this website " http://os.inf.tu-dresden.de/drops/download.html", the GRUB to boot l4linux/fiasco is not the normal version. but it can't be downloaded from SVN now. how can i get that?

2 1

About build of L4Linux
by 林和宏 22 Jul '07

22 Jul '07

Hello. I am a university student in japan. I have a question about an error in building L4Linux 2.6. I want to run L4Linux with L4Ka::Pistachio on an IA32 architecture machine. I got a following error when I tried to make L4Linux. ------------------------------------------------------------- ..... LD .tmp_vmlinux1 KSYM .tmp_kallsyms1.S AS .tmp_kallsyms1.o LD .tmp_vmlinux2 KSYM .tmp_kallsyms2.S AS .tmp_kallsyms2.o LD .tmp_vmlinux3 KSYM .tmp_kallsyms3.S AS .tmp_kallsyms3.o CHK include/linux/version.h *** Error: Headers not exportable for this architecture (l4) <--- this error make[1]: *** [headers_install] error 1 make: *** [vmlinux] error 2 ------------------------------------------------------------- My build way is based on the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml). First, I download the source of L4Linux 2.6 and the l4linux-2.6-env module using SVN repository. [root@lin root]# svn co http://svn.tudos.org/repos/l4linux/trunk l4linux-2.6 [root@lin root]# svn co -N http://svn.tudos.org/repos/tudos/trunk tudos [root@lin tudos]# ./repomgr checkout l4linux-2.6-env The directory structure is following. tudos/ - build/ - dice/ - l4/ - l4linux-2.6/ - repomgr - tools Next, I configure and make L4 enviroment. [root@lin tudos]# make -C l4 O=/root/tudos/build/ config [root@lin tudos]# make -C l4 O=/root/tudos/build/ In DROPS Configuration Tool, I set the path to the DROPS tree. Other parameters are default. Paths and Directories ---> DROPS_STDDIR: "/root/tudos/" Finally, I go to the l4linux-2.6 directory and configure and make. [root@lin l4linux-2.6]# make menuconfig [root@lin l4linux-2.6]# make I change a lot of parameters in L4Linux kernel configuration to avoid many other errors in start and end of make sequence. L4Linux configuration ---> - (/root/tudos/build/) L4 tree build directory Proccessor type and features ---> - [ ] Symmetric multi-proccessing support - Subarchitecture Type (PC-compatible) ---> - [ ] HPET Timer Support - Preemption Model (No Forced Preemption (Server)) ---> - [ ] Local APIC support on uniproccessors - [ ] Machine Check Exception - High Memory Support (off) ---> - [ ] MTRR (Memory Type Range Register) support - [ ] kexec system call Power Management option (APIC, APM) ---> - [ ] Power Management support Bus option (PCI, PCMCIA, EISA, MCA, ISA) ---> - [*] PCI access support PCI access mode (Direct) ---> File systems ---> - Pseudo filesystems ---> - [ ] HugeTLB file system support The error massage may be printed by l4linux-2.6/Makefile (line 928). If there is not file "include/asm-$(ARCH)/Kbuild", it print the error in make. But I seem not to exist Kbuild in include/asm-l4 direcory ... What is the cause of the error ? I think that some settings about L4 environment are lacked. But I cannot understand the sure way to build L4Linux and its environment yet... Please help me ! Thanks and best regards, Lin

5 31

about build l4linux
by kashin Lin 19 Jul '07

19 Jul '07

Hi~ when i issue make to build l4linux in directory l4linux-2.6/, i got some error message: kashin08@kashin08-desktop:~/L4Linux/L4_x86/l4linux-2.6$ make CHK include/linux/version.h CHK include/linux/utsrelease.h CC arch/l4/kernel/asm-offsets.s In file included from include/linux/irqflags.h:46, from include/asm-l4/l4-arch/asm/system.h:507, from include/asm-l4/l4-arch/asm/processor.h:18, from include/asm-l4/i386-arch/asm/atomic.h:5, from include/linux/crypto.h:20, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/irqflags.h: in function 「raw_irqs_disabled_flags」： include/asm-l4/l4-arch/asm/irqflags.h:168: Error：「L4_IRQ_DISABLED」 not declare In file included from include/asm-l4/l4-arch/asm/suspend.h:7, from include/linux/suspend.h:5, from arch/l4/kernel/asm-offsets.c:12: include/asm-l4/i386-arch/asm/i387.h: in function 「save_init_fpu」： include/asm-l4/i386-arch/asm/i387.h:101: Error：「l4lx_fpu_enabled」 not declare make[1]: *** [arch/l4/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 my gcc and g++ and make version are: gcc 4.1.2 g++ 4.1.2 make 3.81 how to fix it? i have tried to trace the code and think this error should never appear.

2 9

building l4linux
by kashin Lin 15 Jul '07

15 Jul '07

Hi~ i have some questions again. my building sequence is : ====================================== in l4_all/kernel/fiasco 1. make BUILDDIR=../../build/fiasco in l4_all/build/fiasco 2. make menuconfig in l4_all/l4 3. make config O=../build/l4env 4. make O=../build/l4env ====================================== my questions : 1. when i issue make in l4/ to build the L4 userland, does it automatic build fiasco subsequently？ 2. if yes, is its default output path for fiasco l4_all/kernel/fiasco/build? ( after the operations mentioned above, i find there are some new files in l4_all/kernel/fiasco/build ) but my configuration for fiasco is in l4_all/build/fiasco, is this auto build operation based on my config? or i should set BUILDDIR to l4_all/kernel/fiasco/build? when config l4linux: according to http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml, there are some options we shouldn't enable ex: like ACPI, SMP, preemption, apic/ioapic, HPET, highmem, MTRR, MCE, power management and similar. 1. does those options are default unable? or we should unable manually? 2. what does "similar" mean? thanks for answering.

2 5

problem when booting l4linux
by junioraozhi＠sina.com 13 Jul '07

13 Jul '07

Hi all! I need your help again. I have built the fiasco,l4env,l4linux on my fedora core 5. But there are someting wrong with booting l4linux,it says "The running kernel does not have the l4lx segments " and goes to jdb. The following is the log when booting ,and also the configuration file ,menu.list  Thx!     >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>                LOG                >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>   Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2007 TU Dresden Rev: r121 compiled with gcc 4.1.0 for Intel Pentium Performance-critical config option(s) detected:   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:3:0) Model: Pentium 4E (Prescott/Nocona) at 3000 MHz    128 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) 2048 KB L2 U Cache (8-way associative, 64 bytes per line)   Freeing init code/data: 20480 bytes (5 pages)   Calibrating timer loop... done. SIGMA0: Hello!   KIP @ 1000   Found Fiasco: KIP syscalls: yes   allocated 4KB for maintenance structures     Roottask.   Command line found: "/boot/l4linux/roottask task modname "bmodfs" attached 4 modules"     507454kB ( 495MB) total RAM (reported by bootloader)   461396kB ( 451MB) received RAM from Sigma0    25504kB (  25MB) reserved RAM for RMGR   Received I/O ports 0000-ffff   Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 A B C D E F 10 11 ]   Roottask: Parsing command line config.   configured task 0x00 (bmodfs):     vm_offs:0 irq:3ffff lmcp:ffff allow_cli:0 mcp:ff prio:10 small:ff mods:4   Roottask: Loading 14 modules. #05: loading "/boot/l4linux/events"      from [06121000-06161f16] to [01540000-01548b30][01549000-0155e5d0]      entry at 0005b370 via trampoline page code      symbols at [1c841000-1c843000] (8kB), lines at [1c83b000-1c841000] (24kB) #06: loading "/boot/l4linux/names --events"      from [06162000-0619fc75] to [002d0000-002d5eca][002d6000-002e1000]      entry at 0005c378 via trampoline page code      symbols at [1c839000-1c83b000] (8kB), lines at [1c834000-1c839000] (20kB) #07: loading "/boot/l4linux/log --events"      from [061a0000-061db22f] to [00400000-0040688a][00407000-00439848]      entry at 0005d374 via trampoline page code      symbols at [1c832000-1c834000] (8kB), lines at [1c82c000-1c832000] (24kB) #08: loading "/boot/l4linux/loader --fprov=BMODFS linuz26.cfg"      from [061dc000-062ade15] to [01300000-01324d9d][01325000-01343000]      entry at 0005e388 via trampoline page code      symbols at [1c826000-1c82c000] (24kB), lines at [1c80f000-1c826000] (92kB) #09: loading "/boot/l4linux/dm_phys --isa=0x00800000 -v --events"      from [062ae000-06337fa6] to [01500000-0151218a][01513000-0151d000]      entry at 0005f38c via trampoline page code      symbols at [1c80a000-1c80f000] (20kB), lines at [1c7fe000-1c80a000] (48kB) #0a: loading "/boot/l4linux/simple_ts -t 300 --events"      from [06338000-06381ed6] to [01400000-0140814a][01409000-01418608]      entry at 00061380 via trampoline page code      symbols at [1c7fc000-1c7fe000] (8kB), lines at [1c7f5000-1c7fc000] (28kB) #0b: loading "/boot/l4linux/rtc --events"      from [06382000-063b1cd7] to [01080000-010840c0][01085000-0108a000]      entry at 00062374 via trampoline page code      symbols at [1c7f3000-1c7f5000] (8kB), lines at [1c7ef000-1c7f3000] (16kB) #0c: loading "/boot/l4linux/l4io --noirq --events"      from [063b2000-066098e5] to [00b80000-00ba21b1][00ba3000-00c0b000]      entry at 0006337c via trampoline page code      symbols at [1c79c000-1c7ef000] (332kB), lines at [1c784000-1c79c000] (96kB) #0d: loading "/boot/l4linux/l4dope --l4io "      from [0660a000-06772ae0] to [01b00000-01b40fe5][01b41000-01b82000]      entry at 00064378 via trampoline page code      symbols at [1c776000-1c784000] (56kB), lines at [1c74c000-1c776000] (168kB) #0e: loading "/boot/l4linux/bmodfs"      from [06773000-0680f912] to [01220000-0123559d][01236000-0124d000]      passing module /boot/l4linux/vmlinuz26               [ 06810000-07752e29 ]      passing module /boot/l4linux/linuz26.cfg             [ 07753000-0775307a ]      passing module /boot/l4linux/libloader.s.so          [ 07754000-077f182c ]      passing module /boot/l4linux/libld-l4.s.so           [ 077f2000-0786a8f1 ]      entry at 00065420 via trampoline page code      symbols at [1c747000-1c74c000] (20kB), lines at [1c737000-1c747000] (64kB)   log     | /boot/l4linux/log: unrecognized option `--events' log     | Unrecognized option: - ? log     | Usage: /boot/l4linux/log <options>. Option list: log     |  [ -h | --help ]          - this help log     |  [ -v | --verbose ]       - verbose mode log     |  [ -l | --local ]         - flush to local console log     |  [ -L | --nolocal ]       - do not flush to local console log     |  [ -s | --comport num ]   - flush to specified serial interface (0) log     |  [ -e | --serial-esc ]    - enter kdebug on esc on serial log     |  [ -b | --buffer num ]    - buffered mode (0) log     |  [ --flushprio num ]      - priority of flusher thread (0x20) log     |  [ -p | --prio num ]      - priority of main thread (0x20) names   | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc     | Date:09.07.2007 Time:08:54:28 DMphys  | DMphys memory map: DMphys  |   phys. memory 0x00000000-0x1eff0000 (from L4 kernel info page) DMphys  |   using 0x00100000-0x1eff0000 DMphys  |        Memory area      Pool  PS  Flags DMphys  |   0x00000000-0x0009f000  --   --  RESERVED  DMphys  |   0x00100000-0x00161000  --   --  RESERVED  DMphys  |   0x00161000-0x001cc000  --   --  DENIED DMphys  |   0x001cc000-0x002d0000   7   12  MAPPED  DMphys  |   0x002d0000-0x002e1000  --   --  DENIED DMphys  |   0x002e1000-0x00400000   7   12  MAPPED  DMphys  |   0x00400000-0x0043a000  --   --  DENIED DMphys  |   0x0043a000-0x00a17000   7   12  MAPPED  DMphys  |   0x00a17000-0x00b80000   0   12  MAPPED  DMphys  |   0x00b80000-0x00c0b000  --   --  DENIED DMphys  |   0x00c0b000-0x01080000   0   12  MAPPED  DMphys  |   0x01080000-0x0108a000  --   --  DENIED DMphys  |   0x0108a000-0x01220000   0   12  MAPPED  DMphys  |   0x01220000-0x0124d000  --   --  DENIED DMphys  |   0x0124d000-0x01300000   0   12  MAPPED  DMphys  |   0x01300000-0x01343000  --   --  DENIED DMphys  |   0x01343000-0x01400000   0   12  MAPPED  DMphys  |   0x01400000-0x01419000  --   --  DENIED DMphys  |   0x01419000-0x01500000   0   12  MAPPED  DMphys  |   0x01500000-0x0151c000  --   --  RESERVED  DMphys  |   0x0151c000-0x01540000   0   12  MAPPED  DMphys  |   0x01540000-0x0155f000  --   --  DENIED DMphys  |   0x0155f000-0x01b00000   0   12  MAPPED  DMphys  |   0x01b00000-0x01b82000  --   --  DENIED DMphys  |   0x01b82000-0x01c00000   0   12  MAPPED  DMphys  |   0x01c00000-0x06800000   0   22  MAPPED  DMphys  |   0x06800000-0x06810000   0   12  MAPPED  DMphys  |   0x06810000-0x0786b000  --   --  DENIED DMphys  |   0x0786b000-0x07c00000   0   12  MAPPED  DMphys  |   0x07c00000-0x1c400000   0   22  MAPPED  DMphys  |   0x1c400000-0x1c737000   0   12  MAPPED  DMphys  |   0x1c737000-0x1eff0000  --   --  DENIED DMphys  |  DMphys  | DMphys memory pools: DMphys  |  pool 0 (Default memory pool): DMphys  |  size: 437160KB total, 437160KB free,  32KB reserved DMphys  |   0x00a17000-0x00b80000 (  1444KB,    1MB) free DS: DMphys  |   0x00c0b000-0x01080000 (  4564KB,    4MB) free DS: DMphys  |   0x0108a000-0x01220000 (  1624KB,    2MB) free DS: DMphys  |   0x0124d000-0x01300000 (   716KB,    1MB) free DS: DMphys  |   0x01343000-0x01400000 (   756KB,    1MB) free DS: DMphys  |   0x01419000-0x01500000 (   924KB,    1MB) free DS: DMphys  |   0x0151c000-0x01540000 (   144KB,    0MB) free DS: DMphys  |   0x0155f000-0x01b00000 (  5764KB,    6MB) free DS: DMphys  |   0x01b82000-0x06810000 ( 78392KB,   77MB) free DS: DMphys  |   0x0786b000-0x1c737000 (342832KB,  335MB) free DS: DMphys  |  pool 7 (ISA DMA memory pool): DMphys  |  size:   8192KB total,   8192KB free,   0KB reserved DMphys  |   0x001cc000-0x002d0000 (  1040KB,    1MB) free DS: DMphys  |   0x002e1000-0x00400000 (  1148KB,    1MB) free DS: DMphys  |   0x0043a000-0x00a17000 (  6004KB,    6MB) free DS: bmodfs  | Passed the following modules: bmodfs  |   module "/boot/l4linux/vmlinuz26" (15628kB) bmodfs  |   module "/boot/l4linux/linuz26.cfg" (1kB) bmodfs  |   module "/boot/l4linux/libloader.s.so" (631kB) bmodfs  |   module "/boot/l4linux/libld-l4.s.so" (483kB) loader  | vmlinuz26: Starting application using libld-l4.s.so loader  | vmlinuz26,#f: Loading binary loader  | vmlinuz26,#f: Loading ldso loader  | Capability support not enabled. loader  | vmlinuz26,#f: Starting libld-l4.s.so at 00013870 via 0000cc54 l4dope  | /boot/l4linux/l4dope: unrecognized option `--l4io' l4dope  | DOpE(init): unknown option! io      | /boot/l4linux/l4io: unrecognized option `--noirq' io      | Enabling events support. io      | PCI: Using configuration type 1 io      | PCI: Probing PCI hardware io      | PCI: Probing PCI hardware (bus 00) io      | PCI: Ignoring BAR0-3 of IDE controller 00:1f.2 io      | Transparent bridge - Intel Corporation 82801 PCI Bridge io      | 00000000-ffffffff : PCI mem io      |   e0000000-efffffff : Intel Corporation 82865G/PE/P DRAM Controller/H io      : ost-Hub Interface io      |   f0000000-f7ffffff : Intel Corporation 82865G Integrated Graphics Co io      : ntroller io      |   f9000000-f90000ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/ io      : 8139C+ io      |   f9001000-f9001fff : Intel Corporation 82801EB/ER (ICH5/ICH5R) integ io      : rated LAN Controller io      |   fa000000-fa07ffff : Intel Corporation 82865G Integrated Graphics Co io      : ntroller io      |   fa080000-fa0803ff : Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2  io      : EHCI Controller io      |   fa081000-fa0811ff : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 io      :  Audio Controller io      |   fa082000-fa0820ff : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 io      :  Audio Controller io      | 0000-ffff : PCI IO io      |   0cf8-0cff : PCI conf1 io      |   1400-141f : Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Control io      : ler io      |   a000-a0ff : Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ io      |   a400-a43f : Intel Corporation 82801EB/ER (ICH5/ICH5R) integrated LA io      : N Controller io      |   b000-b01f : Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Cont io      : roller #1 io      |   b400-b41f : Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Cont io      : roller #2 io      |   b800-b81f : Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Cont io      : roller #3 io      |   bc00-bc1f : Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Cont io      : roller #4 io      |   c000-c007 : Intel Corporation 82865G Integrated Graphics Controller io      |   dc00-dcff : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio C io      : ontroller io      |   e000-e03f : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio C io      : ontroller io      |   f000-f00f : Intel Corporation 82801EB (ICH5) SATA Controller io      | Available IRQs=[ <!0> 1 <!2> 3 <!4> 5 6 7 8 9 a b c d e f 10 11 ] l4dope  | L4INPUT native mode activated l4dope  | L4INPUT:                !!! W A R N I N G !!! l4dope  | L4INPUT:  Please, do not use Fiasco's "-esc" with L4INPUT. l4dope  | L4INPUT:                !!! W A R N I N G !!! ROOT: Sending ports 0060-006f to task #0c l4dope  | serio: i8042 AUX port at 0x60,0x64 irq 12 l4dope  | serio: i8042 KBD port at 0x60,0x64 irq 1 l4lx    | ======> L4Linux 2.6 starting... <======== l4lx    | Linux version 2.6.21-l4 (root@lgh-FC5) (gcc version 4.1.0 20060304 (R l4lx    : ed Hat 4.1.0-3)) #19 Wed Jul 4 10:19:59 CST 2007 l4lx    | Binary name: vmlinuz26 l4lx    | Kernel command line (4 args): earlyprintk=yes mem=256M video=l4fb roo l4lx    : t=/dev/sda7 l4lx    | The running kernel does not have the l4lx    |       segments l4lx    | feature enabled!       --kernel feature missing!--------------------------------IP: 0040163b       [l4lx.main] (f.02) jdb:        >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> the config file "linuz26.config"  >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>   verbose 0 task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb root=/dev/sda7"     all_sects_writable     allow_cli     allow_vga     >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>       the menu.list of grub       >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>   title L4Linux26/Fiasco+dope         root (hd0,6)         kernel /boot/l4linux/bootstrap         modaddr 0x06000000         module /boot/l4linux/main -nowait -nokdb -serial_esc -comspeed 115200 -c omport 1         module  /boot/l4linux/sigma0         module  /boot/l4linux/roottask task modname "bmodfs" attached 4 modules         module  /boot/l4linux/events         module  /boot/l4linux/names --events         module  /boot/l4linux/log --events         module  /boot/l4linux/loader --fprov=BMODFS linuz26.cfg         module  /boot/l4linux/dm_phys --isa=0x00800000 -v --events         module  /boot/l4linux/simple_ts -t 300 --events         module  /boot/l4linux/rtc --events         module  /boot/l4linux/l4io --noirq --events         module  /boot/l4linux/l4dope --l4io         module  /boot/l4linux/bmodfs                 module  /boot/l4linux/vmlinuz26                 module  /boot/l4linux/linuz26.cfg                 module  /boot/l4linux/libloader.s.so                 module  /boot/l4linux/libld-l4.s.so         vbeset  0x117 506070         boot ------------------------------------------------------------------- MOTONBA篮球赛招募( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2007/mail_zhuiyu_20070709.ht… ) =================================================================== 注册新浪2G免费邮箱（ http://mail.sina.com.cn/chooseMode.html ）

2 1

Run L4linux on ARM platform
by kashin Lin 12 Jul '07

12 Jul '07

Hi~ i am a new hand to do this... so i really need some help & suggestions. this is my GOAL : run ( port ) L4linux on ARM platform (ARM920T-S3C2410) ( the link of that platform : PreSOCes-C in http://www.microtime.com.tw/English/PreSOC.htm ) i have some question: 1. i know L4Linux must run with l4(fiasco) & l4env.but when i want to download L4Linux from http://os.inf.tu-dresden.de/drops/download.html , instead of module " l4linux", svn only has module "l4linux-2.6-env". so i am confused that is this module(l4linux-2.6-env) contains L4Linux + fiasco + l4env or just L4Linux or not at all??? or give me a suggestion about what i should download to achieve my goal 2. to achieve my goal, i guess the process should be: cross-compile source code to image → load the image to target platform → modify bootloader to boot from l4linux → finish is this process right ? should i modify any file before cross-compiling l4linux? are there any thing i should take care about? thanks for any suggestions. i really need your help. thank you~

2 13

Installation for a dummy..
by ComputerScienceStudent 09 Jul '07

09 Jul '07

I'm an universitary computer science student and I've to do some benchmarks on microkernel's OS. Because I'd not ever install, or try to do something similar, a OS like this, before I try to do an installation by my own, I prefer to ask someone who is a specialist in these stuff. I've to install L4 on my portable computer: in this machine I've already installed Windows XP and Suse10.2. Now, the question is: do I have to install L4 on Suse? Is there anothr way like install L4Linux? I understand that L4Linux is the L4 microkernel with the Linux kernel over it.. so I think that installing this distribution I can hold my old OSs on the the computer and simply I will create an entry in the bootloader to select the new one. Please, someone help me.. I'm in crisis.. :-| -- View this message in context: http://www.nabble.com/Installation-for-a-dummy..-tf4011030.html#a11390720 Sent from the L4 mailing list archive at Nabble.com.

2 4

Re: help, L4env build problem
by Bjoern Doebel 09 Jul '07

09 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > I have solved the probblem I raised before, That's due > to the error system time in my SUSE linux. Thanks a lot > for your help and time! > > but here is another question: > > when I build the l4env, the error message is : > > if [ -r ../dice/Makefile.drops ]; then \ > make -C ../dice -f Makefile.drops; \ > fi > make[1]: Entering directory `/home/fiasco/snapshot-200706/dice' > make all -f GNUmakefile > make[2]: Entering directory `/home/fiasco/snapshot-200706/dice' > make all-recursive > make[3]: Entering directory `/home/fiasco/snapshot-200706/dice' > Making all in libltdl > make[4]: Entering directory `/home/fiasco/snapshot-200706/dice/libltdl' > make all-am > make[5]: Entering directory `/home/fiasco/snapshot-200706/dice/libltdl' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory `/home/fiasco/snapshot-200706/dice/libltdl' > make[4]: Leaving directory `/home/fiasco/snapshot-200706/dice/libltdl' > Making all in src > make[4]: Entering directory `/home/fiasco/snapshot-200706/dice/src' > Making all in be > make[5]: Entering directory `/home/fiasco/snapshot-200706/dice/src/be' > Making all in l4 > make[6]: Entering directory `/home/fiasco/snapshot-200706/dice/src/be/l4' > Making all in v2 > make[7]: Entering directory `/home/fiasco/snapshot-200706/dice/src/be/l4/v2' > Making all in ia32 > make[8]: Entering directory `/home/fiasco/snapshot-200706/dice/src/be/l4/v2/ia32' > if g++ -DHAVE_CONFIG_H -I. -I. -I../../../../.. -Wall -I../../../../../src > -Wunused -Wunused-parameter -Wall -W -Wcast-align -Wcast-qual > -Wconversion -Wformat=2 -Wmissing-format-attribute -Wpointer-arith > -Wshadow -Wwrite-strings -Wstrict-aliasing=2 -g -O2 -MT V2IA32ClassFactory.o > -MD -MP -MF ".deps/V2IA32ClassFactory.Tpo" -c -o V2IA32ClassFactory.o > V2IA32ClassFactory.cpp; \ > then mv -f ".deps/V2IA32ClassFactory.Tpo" ".deps/V2IA32ClassFactory.Po"; > else rm -f ".deps/V2IA32ClassFactory.Tpo"; exit 1; fi > cc1plus: error: unrecognized option `-Wstrict-aliasing=2' This is the problem. Your C++ compiler does not understand the - -Wstrict-aliasing option. Please find out what compiler you are using by running $> g++ -v and post the output here again. > make[8]: *** [V2IA32ClassFactory.o] Error 1 > make[8]: Leaving directory `/home/fiasco/snapshot-200706/dice/src/be/l4/v2/ia32' > make[7]: *** [all-recursive] Error 1 > make[7]: Leaving directory `/home/fiasco/snapshot-200706/dice/src/be/l4/v2' > make[6]: *** [all-recursive] Error 1 > make[6]: Leaving directory `/home/fiasco/snapshot-200706/dice/src/be/l4' > make[5]: *** [all-recursive] Error 1 > make[5]: Leaving directory `/home/fiasco/snapshot-200706/dice/src/be' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory `/home/fiasco/snapshot-200706/dice/src' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/home/fiasco/snapshot-200706/dice' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/home/fiasco/snapshot-200706/dice' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/home/fiasco/snapshot-200706/dice' > make: *** [../dice] Error 2 > > please give me some suggestions! Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGkecsP5ijxgQLUNkRAgL9AJ9OqH03E4z6T36mRie6vJDYB7AQXgCfRWh/ 7uKMfkqcBcfV9koBsNdsQuc= =z76d -----END PGP SIGNATURE-----

1 0

Re: help, L4env build problem
by Bjoern Doebel 09 Jul '07

09 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > I created a directory "fiasco" in "/home" and uncompressed the > "source-2007-06-30.tar.bz2" in this directory, then I entered > the directory "/home/fiasco/snapshot-200706/l4" as root . First of all there is no reason to build anything as root. > In this directory, I ran the command > "DROPS_STDDIR=/home/fiasco/snapshot-200706/ \ make oldconfig", Why would you do that? Please follow the build instructions for the snapshot which are available from http://os.inf.tu-dresden.de/opentc/2007_june_inst.xml > the make process began to execute, but it won't > terminate. I have logged the output of make process in file > "build.log" as in the attachment. Please help me > to analyse what is the reason that caused this problem. Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGkeYAP5ijxgQLUNkRAl5NAJ46K+WHpyChh1c/dTFTWvU2DxuJxwCdHYxV /ImsnTR9TcbO6xEq8I2ZN04= =T5q1 -----END PGP SIGNATURE-----

1 0

building l4 for mips64
by Antoine Amirault 09 Jul '07

09 Jul '07

HI! I'm always trying to build l4 for mips64. I've decided to try to correct errors i obtain during the compilation. I've repaired some of them but now I'm stuck. I think I've understand the problem, but I don't know how to solve it. When compiling, I got this error : /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc: In function `threadid_t sys_exchange_registers(threadid_t, word_t, word_t, word_t, word_t, word_t, threadid_t, bool)': /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: error: data type of 'pgr' isn't suitable for a register /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: error: register name given for non-register variable 'pgr' /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: confused by earlier errors, bailing out make[1]: *** [src/api/v4/exregs.o] Error 1 I've found in syscall.h where this function is declared. I got this code : #define return_exchange_registers(result, control, sp, ip, flags, pager, handle) \ { \ register word_t ctrl asm("$4") = control; /* a0 */ \ register word_t sp_r asm("$5") = sp; /* a1 */ \ register word_t ip_r asm("$6") = ip; /* a2 */ \ register word_t flg asm("$7") = flags; /* a3 */ \ register threadid_t pgr asm("$8") = pager; /* t0 */ \ register word_t hdl asm("$9") = handle; /* t1 */ \ \ __asm__ __volatile__ ( \ "" : : "r" (ctrl), "r" (sp_r), "r" (ip_r), \ "r" (flg), "r" (pgr), "r" (hdl) \ ); \ return (result); \ } I think that it's impossible to store a threadid_t in a register so i tried to cast it to word_t but after i got this error message : /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc: In function `threadid_t sys_exchange_registers(threadid_t, word_t, word_t, word_t, word_t, word_t, threadid_t, bool)': /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: error: expected primary-expression before "register" /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: error: expected `;' before "register" /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: error: `pgr' undeclared (first use this function) /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:333: error: (Each undeclared identifier is reported only once for each function it appears in.) /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:352: error: expected primary-expression before "register" /home/antoine/Final/pistachio/kernel/src/api/v4/exregs.cc:352: error: expected `;' before "register" make[1]: *** [src/api/v4/exregs.o] Error 1 Maybe my idea is not good or I haven't really understand the problem. Any ideas? Thanks Antoine

1 0

help, L4env build problem
by huang 07 Jul '07

07 Jul '07

hi dear all: I have some problems while building the l4env. I downloaded the snapshot "source-2007-06-30.tar.bz2" from http://os.inf.tu-dresden.de/opentc/download.xml and I tried to build the whole l4 environment in SUSE linux 9.3. But it seems something wrong. The build process is a dead loop, it seems will never stop. I don't know what's the reason. Can you tell me what should I do? By the way: I can build the L4 kernel successfully. thanks a lot for your help and suggestions! Best regards! Huang ======= 2007-07-06 18:00:02 您在来信中写道：======= >Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > >To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > >You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of l4-hackers digest..." > >Today's Topics: > > 1. Re: Run L4linux on ARM platform (kashin Lin) > 2. Re: [L4LINUX] Is there a loop in revision 32 ? (Adam Lackorzynski) > 3. Re: Run L4linux on ARM platform (Adam Lackorzynski) > >------------------------------------------------------------ >From: "kashin Lin" <kashin08(a)gmail.com> >To: l4-hackers(a)os.inf.tu-dresden.de >Subject: Re: Run L4linux on ARM platform >Date: Thu5 Jul 2007 23:31:38 +0800 > >2007/7/5, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: >> >> >> On Thu Jul 05, 2007 at 00:15:15 +0800, kashin Lin wrote: >> >> > 2. as you metioned above, i should adapt the configuration of fiasco >> > to my target platform, >> > but... (1) when do i do this? before make anything? >> >> Not only the configuration but also the code. You probably need to >> write a e.g. UART driver for your platform. As I said, I don't know >> which UART is used on your board. Can you tell which type of UART is >> used there? > > > >There is a UART (RS232 port) which can communicate with PC. >how to add that UART driver in fiasco? >are there any other platform dependent things that need to touch the code? > >thanks for your reply > >Adam >> -- >> Adam adam(a)os.inf.tu-dresden.de >> Lackorzynski http://os.inf.tu-dresden.de/~adam/ >> >> _______________________________________________ >> l4-hackers mailing list >> l4-hackers(a)os.inf.tu-dresden.de >> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >> > >------------------------------------------------------------ >------------------------------------------------------------ >From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> >To: l4-hackers(a)os.inf.tu-dresden.de >Subject: Re: [L4LINUX] Is there a loop in revision 32 ? >Date: Thu5 Jul 2007 19:16:02 +0200 > >Hi, > >On Thu Jul 05, 2007 at 13:18:32 +0200, Clermont, Nicolas wrote: >> Here it is : > >Looks good to me. You could try a sysrq-t and see if there's something >interesting. Also booting with initcall_debug=1 could also squeeze out >some more info. Otherwise I'll try getting the public repo up to date >again to see further. > > > >Adam >-- >Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > >------------------------------------------------------------ >------------------------------------------------------------ >From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> >To: l4-hackers(a)os.inf.tu-dresden.de >Subject: Re: Run L4linux on ARM platform >Date: Thu5 Jul 2007 19:23:16 +0200 > > >On Thu Jul 05, 2007 at 23:31:38 +0800, kashin Lin wrote: >> 2007/7/5, Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: >> > >> > >> >On Thu Jul 05, 2007 at 00:15:15 +0800, kashin Lin wrote: >> > >> >> 2. as you metioned above, i should adapt the configuration of fiasco >> >> to my target platform, >> >> but... (1) when do i do this? before make anything? >> > >> >Not only the configuration but also the code. You probably need to >> >write a e.g. UART driver for your platform. As I said, I don't know >> >which UART is used on your board. Can you tell which type of UART is >> >used there? >> >> >> >> There is a UART (RS232 port) which can communicate with PC. >> how to add that UART driver in fiasco? > >You need to add a new platform. Basically you can do the same thing as >it's done with the integrator platform. The UART implementation goes to >src/lib/uart/arm, and need to be hooked in >src/kern/arm/kernel_uart-arm.cpp. > >> are there any other platform dependent things that need to touch the code? > >Most likely. The PIC implementation goes to src/kern/arm/pic-arm.cpp, >and the timer goes to src/kern/arm/timer-arm.cpp. Other files to look at >are Modules.arm to specify the label to build under and probably >rules.cml to add a new platform. The CPU specific things may also need >adaptions. > > > >Adam >-- >Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > >------------------------------------------------------------ >_______________________________________________ >l4-hackers mailing list >l4-hackers(a)os.inf.tu-dresden.de >http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > = = = = = = = = = = = = = = = = = = = = 　　　　　　　　致礼！　　　　　　　　huang 　　　　　　　　learnl4(a)sina.com 　　　　　　　　　　2007-07-07

2 1

RE: [L4LINUX] Is there a loop in revision 32 ?
by Clermont, Nicolas 06 Jul '07

06 Jul '07

Here it is : # # Automatically generated make config: don't edit # Linux kernel version: 2.6.21-l4 # Thu Jul 5 13:11:07 2007 # # # L4Linux configuration # CONFIG_L4=y CONFIG_L4_LINUX=y CONFIG_L4_OBJ_TREE="/home/clermont/build-tudos" CONFIG_L4_L4ENV=y CONFIG_L4_ARCH_X86=y # CONFIG_L4_ARCH_ARM is not set CONFIG_HZ=100 CONFIG_PHYSICAL_START=0x0 # CONFIG_L4_USERPRIV_ONLY is not set # # L4 build options # CONFIG_L4_MK_CPU_X86="586" # # IRQ Handling # # CONFIG_L4_IRQ_SINGLE is not set CONFIG_L4_IRQ_OMEGA0=y # CONFIG_L4_IRQ_MULTI is not set # # Stub drivers # CONFIG_L4_EXTERNAL_RTC=y # CONFIG_L4_BLK_DRV is not set # CONFIG_L4_PDSPBLK_DRV is not set CONFIG_L4_FB_DRIVER=y CONFIG_L4_FB_DRIVER_XF86IF=y # CONFIG_L4_OSHKOSH_DRV is not set # CONFIG_L4_ORE_DRV is not set CONFIG_L4_SERIAL=y CONFIG_L4_SERIAL_CONSOLE=y # CONFIG_L4_NEED_DSI is not set # CONFIG_L4_NEED_INET_NTOA is not set # CONFIG_L4_DROPSCON is not set # # Debugging options # # CONFIG_L4_DEBUG is not set # # Advanced options # CONFIG_L4_L4ENV_MEMSIZE=32 CONFIG_L4_TAMED=y # # Priority configuration # CONFIG_L4_PRIO_USER_PROCESS=10 CONFIG_L4_PRIO_IRQ_OFFSET=129 CONFIG_L4_PRIO_SERVER=100 # # Monitoring options (ferret) # # CONFIG_L4_FERRET_USER is not set # CONFIG_L4_FERRET_KERNEL is not set # CONFIG_L4_FERRET_SYSCALL_COUNTER is not set # CONFIG_L4_USE_L4VMM is not set # # # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_SEMAPHORE_SLEEPERS=y CONFIG_X86=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_DMI=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_IPC_NS is not set CONFIG_SYSVIPC_SYSCTL=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set # CONFIG_TASKSTATS is not set # CONFIG_UTS_NS is not set # CONFIG_AUDIT is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_SYSFS_DEPRECATED=y # CONFIG_RELAY is not set # CONFIG_BLK_DEV_INITRD is not set # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_EMBEDDED=y CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set # CONFIG_HOTPLUG is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_SLAB=y CONFIG_VM_EVENT_COUNTERS=y CONFIG_RT_MUTEXES=y # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # CONFIG_SLOB is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Block layer # CONFIG_BLOCK=y # CONFIG_LBD is not set # CONFIG_BLK_DEV_IO_TRACE is not set # CONFIG_LSF is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_AS=y # CONFIG_DEFAULT_DEADLINE is not set # CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="anticipatory" # # Processor type and features # # CONFIG_TICK_ONESHOT is not set # CONFIG_NO_HZ is not set # CONFIG_HIGH_RES_TIMERS is not set # CONFIG_SMP is not set CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_PARAVIRT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MCORE2 is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y # CONFIG_ARCH_HAS_ILOG2_U32 is not set # CONFIG_ARCH_HAS_ILOG2_U64 is not set CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_TSC=y # CONFIG_HPET_TIMER is not set CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set # CONFIG_VM86 is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # # Firmware Drivers # # CONFIG_EDD is not set # CONFIG_DELL_RBU is not set # CONFIG_DCDBAS is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_VMSPLIT_3G=y # CONFIG_VMSPLIT_3G_OPT is not set # CONFIG_VMSPLIT_2G is not set # CONFIG_VMSPLIT_1G is not set CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_SPARSEMEM_STATIC=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_RESOURCES_64BIT is not set CONFIG_ZONE_DMA_FLAG=1 # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set # CONFIG_KEXEC is not set # CONFIG_RELOCATABLE is not set CONFIG_PHYSICAL_ALIGN=0x100000 CONFIG_COMPAT_VDSO=y # # Power management options (ACPI, APM) # # CONFIG_PM is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set CONFIG_PCI_GODIRECT=y # CONFIG_PCI_GOANY is not set CONFIG_PCI_DIRECT=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # # PCCARD (PCMCIA/CardBus) support # # # PCI Hotplug Support # # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # # CONFIG_NETDEBUG is not set CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set # CONFIG_INET is not set # CONFIG_NETWORK_SECMARK is not set # CONFIG_NETFILTER is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_WAN_ROUTER is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # CONFIG_IEEE80211 is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set # # Connector - unified userspace <-> kernelspace linker # # CONFIG_CONNECTOR is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # # CONFIG_PNPACPI is not set # # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_CRYPTOLOOP is not set # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_CDROM_PKTCDVD is not set # CONFIG_ATA_OVER_ETH is not set # # Misc devices # # CONFIG_IBM_ASM is not set # CONFIG_SGI_IOC4 is not set # CONFIG_TIFM_CORE is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_IDE_MAX_HWIFS=4 CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y # CONFIG_IDEDISK_MULTI_MODE is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_IDE_TASK_IOCTL is not set # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y # CONFIG_BLK_DEV_CMD640 is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_IDEPCI_SHARE_IRQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set # CONFIG_IDEDMA_ONLYDISK is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_CS5535 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_JMICRON is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_IT8213 is not set # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_BLK_DEV_TC86C001 is not set # CONFIG_IDE_ARM is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set # CONFIG_BLK_DEV_HD is not set # # SCSI device support # # CONFIG_RAID_ATTRS is not set CONFIG_SCSI=y # CONFIG_SCSI_TGT is not set # CONFIG_SCSI_NETLINK is not set CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y # CONFIG_CHR_DEV_SG is not set # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # CONFIG_SCSI_SCAN_ASYNC is not set # # SCSI Transports # # CONFIG_SCSI_SPI_ATTRS is not set # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # CONFIG_SCSI_SAS_ATTRS is not set # CONFIG_SCSI_SAS_LIBSAS is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_AIC94XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_ARCMSR is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set # CONFIG_SCSI_HPTIOP is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_STEX is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_QLA_FC is not set # CONFIG_SCSI_QLA_ISCSI is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # CONFIG_SCSI_SRP is not set # # Serial ATA (prod) and Parallel ATA (experimental) drivers # CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_SATA_AHCI=y # CONFIG_SATA_SVW is not set CONFIG_ATA_PIIX=y # CONFIG_SATA_MV is not set # CONFIG_SATA_NV is not set # CONFIG_PDC_ADMA is not set # CONFIG_SATA_QSTOR is not set # CONFIG_SATA_PROMISE is not set # CONFIG_SATA_SX4 is not set # CONFIG_SATA_SIL is not set # CONFIG_SATA_SIL24 is not set # CONFIG_SATA_SIS is not set # CONFIG_SATA_ULI is not set # CONFIG_SATA_VIA is not set # CONFIG_SATA_VITESSE is not set # CONFIG_SATA_INIC162X is not set CONFIG_SATA_INTEL_COMBINED=y # CONFIG_PATA_ALI is not set # CONFIG_PATA_AMD is not set # CONFIG_PATA_ARTOP is not set # CONFIG_PATA_ATIIXP is not set # CONFIG_PATA_CMD64X is not set # CONFIG_PATA_CS5520 is not set # CONFIG_PATA_CS5530 is not set # CONFIG_PATA_CS5535 is not set # CONFIG_PATA_CYPRESS is not set # CONFIG_PATA_EFAR is not set # CONFIG_ATA_GENERIC is not set # CONFIG_PATA_HPT366 is not set # CONFIG_PATA_HPT37X is not set # CONFIG_PATA_HPT3X2N is not set # CONFIG_PATA_HPT3X3 is not set # CONFIG_PATA_IT821X is not set # CONFIG_PATA_IT8213 is not set # CONFIG_PATA_JMICRON is not set # CONFIG_PATA_TRIFLEX is not set # CONFIG_PATA_MARVELL is not set # CONFIG_PATA_MPIIX is not set # CONFIG_PATA_OLDPIIX is not set # CONFIG_PATA_NETCELL is not set # CONFIG_PATA_NS87410 is not set # CONFIG_PATA_OPTI is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_PATA_PDC_OLD is not set # CONFIG_PATA_RADISYS is not set # CONFIG_PATA_RZ1000 is not set # CONFIG_PATA_SC1200 is not set # CONFIG_PATA_SERVERWORKS is not set # CONFIG_PATA_PDC2027X is not set # CONFIG_PATA_SIL680 is not set # CONFIG_PATA_SIS is not set # CONFIG_PATA_VIA is not set # CONFIG_PATA_WINBOND is not set CONFIG_PATA_PLATFORM=y # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_SPI is not set # CONFIG_FUSION_FC is not set # CONFIG_FUSION_SAS is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # # CONFIG_I2O is not set # # Macintosh device drivers # # CONFIG_MAC_EMUMOUSEBTN is not set # # Network device support # CONFIG_NETDEVICES=y # CONFIG_DUMMY is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # PHY device support # # # Ethernet (10 or 100Mbit) # # CONFIG_NET_ETHERNET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SIS190 is not set # CONFIG_SKGE is not set # CONFIG_SKY2 is not set # CONFIG_SK98LIN is not set # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # CONFIG_QLA3XXX is not set # CONFIG_ATL1 is not set # # Ethernet (10000 Mbit) # # CONFIG_CHELSIO_T1 is not set # CONFIG_CHELSIO_T3 is not set # CONFIG_IXGB is not set # CONFIG_S2IO is not set # CONFIG_MYRI10GE is not set # CONFIG_NETXEN_NIC is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # # Userland interfaces # # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # # CONFIG_INPUT_KEYBOARD is not set # CONFIG_INPUT_MOUSE is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # # CONFIG_SERIO is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_VT_HW_CONSOLE_BINDING is not set # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # # CONFIG_SERIAL_8250 is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_HW_RANDOM is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_PC8736x_GPIO is not set # CONFIG_NSC_GPIO is not set # CONFIG_CS5535_GPIO is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # CONFIG_TELCLOCK is not set # # I2C support # # CONFIG_I2C is not set # # SPI support # # CONFIG_SPI is not set # CONFIG_SPI_MASTER is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # # CONFIG_HWMON is not set # CONFIG_HWMON_VID is not set # # Multifunction device drivers # # CONFIG_MFD_SM501 is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # # Graphics support # # CONFIG_BACKLIGHT_LCD_SUPPORT is not set CONFIG_FB=y CONFIG_FIRMWARE_EDID=y # CONFIG_FB_DDC is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_VESA is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_CYBLA is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # # CONFIG_VGA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set CONFIG_FONTS=y CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_FONT_6x11 is not set # CONFIG_FONT_7x14 is not set # CONFIG_FONT_PEARL_8x8 is not set # CONFIG_FONT_ACORN_8x8 is not set CONFIG_FONT_MINI_4x6=y # CONFIG_FONT_SUN8x16 is not set # CONFIG_FONT_SUN12x22 is not set # CONFIG_FONT_10x18 is not set # # Logo configuration # # CONFIG_LOGO is not set # # Sound # # CONFIG_SOUND is not set # # HID Devices # # CONFIG_HID is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y # CONFIG_USB is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # LED devices # # CONFIG_NEW_LEDS is not set # # LED drivers # # # LED Triggers # # # InfiniBand support # # CONFIG_INFINIBAND is not set # # EDAC - error detection and reporting (RAS) (EXPERIMENTAL) # # CONFIG_EDAC is not set # # Real Time Clock # # CONFIG_RTC_CLASS is not set # # DMA Engine support # # CONFIG_DMA_ENGINE is not set # # DMA Clients # # # DMA Devices # # # Auxiliary Display support # # # Virtualization # # CONFIG_KVM is not set # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set # CONFIG_EXT4DEV_FS is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # CONFIG_FS_POSIX_ACL is not set # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y # CONFIG_ZISOFS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_SYSCTL=y CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_TMPFS_POSIX_ACL is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_CONFIGFS_FS is not set # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set # CONFIG_OSF_PARTITION is not set # CONFIG_AMIGA_PARTITION is not set # CONFIG_ATARI_PARTITION is not set # CONFIG_MAC_PARTITION is not set CONFIG_MSDOS_PARTITION=y # CONFIG_BSD_DISKLABEL is not set # CONFIG_MINIX_SUBPARTITION is not set # CONFIG_SOLARIS_X86_PARTITION is not set # CONFIG_UNIXWARE_DISKLABEL is not set # CONFIG_LDM_PARTITION is not set # CONFIG_SGI_PARTITION is not set # CONFIG_ULTRIX_PARTITION is not set # CONFIG_SUN_PARTITION is not set # CONFIG_KARMA_PARTITION is not set # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set # CONFIG_NLS_ISO8859_1 is not set # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Instrumentation Support # # CONFIG_PROFILING is not set # CONFIG_KPROBES is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y # CONFIG_PRINTK_TIME is not set CONFIG_ENABLE_MUST_CHECK=y CONFIG_MAGIC_SYSRQ=y CONFIG_UNUSED_SYMBOLS=y # CONFIG_DEBUG_FS is not set # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set CONFIG_LOG_BUF_SHIFT=15 CONFIG_DETECT_SOFTLOCKUP=y # CONFIG_SCHEDSTATS is not set # CONFIG_TIMER_STATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set CONFIG_DEBUG_MUTEXES=y # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_LIST is not set CONFIG_FRAME_POINTER=y CONFIG_FORCED_INLINING=y # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_FAULT_INJECTION is not set # CONFIG_EARLY_PRINTK is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PAGEALLOC is not set # CONFIG_DEBUG_RODATA is not set # CONFIG_4KSTACKS is not set CONFIG_DOUBLEFAULT=y # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_MANAGER=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_XCBC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set # CONFIG_CRYPTO_GF128MUL is not set CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_PCBC=y # CONFIG_CRYPTO_LRW is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_FCRYPT is not set # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_TWOFISH_586 is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_CAMELLIA is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # CONFIG_CRYPTO_DEV_GEODE is not set # # Library routines # CONFIG_BITREVERSE=y # CONFIG_CRC_CCITT is not set # CONFIG_CRC16 is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_PLIST=y CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_BIOS_REBOOT=y CONFIG_KTIME_SCALAR=y -----Message d'origine----- De : l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] De la part de Adam Lackorzynski Envoyé : jeudi 5 juillet 2007 09:57 À : l4-hackers(a)os.inf.tu-dresden.de Objet : Re: [L4LINUX] Is there a loop in revision 32 ? Hi, On Wed Jul 04, 2007 at 17:21:33 +0200, Clermont, Nicolas wrote: > I have updated my l4 repositories yesterday, switching to L4Linux > revision > 32 and tudos revision 127. When booting L4Linux with TCP/IP enabled, > it blocks after printing "Registered protocol 2". When disabling > TCP/IP, it blocks after IDE probe. I have observed the same behavior > with revision 31, but didn't have the time at this time to investigate. I'm not seeing anything like this in my setup. Can you please post your L4Linux .config so that I can look over it? > This time I have tried to find the reason of this loop. I have > disabled TCP/IP and tried to see where L4Linux hangs. After IDE probe, > L4Linux goes through wait_for_completion(), which calls schedule(), > and then loops as need_resched label is always re-invocated. The last > thing displayed is the creation of the idler thread... > The problem with TCP/IP support enabled is different but maybe related > to the same source. the schedule() function is also called, but it > completes and so schedule. Then the idler thread is created and noting goes on. > > I have tried with different configurations, especially with protected > I/O and unprotected, but I get always the same behavior. > > This is the output I get trough the serial line with TCP/IP disabled > (l4linux also print on serial) : > > l4lx | ======> L4Linux 2.6 starting... <======== > l4lx | Linux version 2.6.21-l4 (clermont@L4-dev <mailto:clermont@L4-dev> > ) (gcc version 3.4.4 (Gentoo > l4lx : 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #59 Tue Jul 3 19:21:07 Local > tim > l4lx : e zone must be set--see zic manu > l4lx | Binary name: vmlinuz26 > l4lx | Kernel command line (5 args): console=ttyLv0 earlyprintk=yes > mem=128M > l4lx : root=/dev/hda1 video=l4fb:refreshsleep:200 > l4lx | Image: 00400000 - 00681000 [2564 KiB]. > l4lx | Areas: Text: 00400000 - 005e6000 [1944kB] (a bit longer) > l4lx | Data: 005e6000 - 005f9f7c [79kB] > l4lx | Initdata: 005fc000 - 00618260 [112kB] > l4lx | BSS: 0061a000 - 0067e840 [402kB] > names | 12.02: server_names_register(12.03 -> "l4lx.tamer") > l4lx | l4lx_thread_create: Created thread 12.03 (tamer) > l4lx | Using tamed mode. > ROOT: Sending all ports (for cli/sti) to task #0d > l4lx | Got 65536 out of 65536 I/O ports > names | 12.02: server_names_register(12.04 -> "l4lx.server") > l4lx | l4lx_thread_create: Created thread 12.04 (server) > l4lx | main thread will be 12.04 > l4lx | l4env_register_pointer_section: addr = 005e6000 size = 634880 > l4lx | sec-w-init: virt: 0x005e6000 to 0x00680fff [620 KiB] > l4lx | sec-w-init: Number of physical regions: 1, 634880 Bytes > l4lx | sec-w-init: 1: Phys: 0x01185000 to 0x01220000, Size: 634880 > l4lx | l4env_linux_startup thread 4. > l4lx | main thread: received startup message. > l4lx | Main thread running, waiting... > l4lx | setup_l4env_memory: Forcing superpages for main memory > l4lx | Main memory size: 128MB > l4lx | Got 2048kB of ISA DMA memory. > l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] > l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes > l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 > l4lx | Main memory: virt: 0x00c00000 to 0x08bfffff [131072 KiB] > l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes > l4lx | Main memory: 1: Phys: 0x14400000 to 0x1c400000, Size: > 134217728 > l4lx | Filling lower ptabs... > l4lx | Done (1883 entries). > Linux version 2.6.21-l4 (clermont@L4-dev <mailto:clermont@L4-dev> ) > (gcc version 3.4.4 (Gentoo 3.4.4-r1, s sp-3.4.4-1.0, pie-8.7.8)) #59 > Tue Jul 3 19:21:07 Local time zone must be set--se e zic manu > CPU: Vendor unknown, using generic init. > CPU: Your system may be unstable. > dm_phys: 0000000000c00000 - 0000000008c00000 (usable) > dm_phys: 0000000000800000 - 0000000000a00000 (usable) 132MB memory > available. > Zone PFN ranges: > DMA 0 -> 2560 > Normal 2560 -> 35840 > early_node_map[1] active PFN ranges > 0: 0 -> 35840 > Allocating PCI resources starting at 10000000 (gap: 00a00000:ff600000) > Built 1 zonelists. Total pages: 35560 Kernel command line: > console=ttyLv0 earlyprintk=yes mem=128M root=/dev/hda1 vide > o=l4fb:refreshsleep:200 Initializing CPU#0 PID hash table entries: > 1024 (order: 10, 4096 bytes) Detected 2800.514 MHz processor. > Console: colour dummy device 80x25 > l4ser_init_ports > l4ser: input not enabled! > Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) > Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) > Memory: 131700k/143360k available (1539k kernel code, 1344k reserved, > 484k data, 112k init, 0k highmem) virtual kernel memory layout: > fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) > vmalloc : 0x10000000 - 0x18000000 ( 128 MB) > lowmem : 0x00000000 - 0x08c00000 ( 140 MB) > .init : 0x005fc000 - 0x00618260 ( 112 kB) > .data : 0x00580cc4 - 0x005f9f7c ( 484 kB) > .text : 0x00400000 - 0x00580cc4 (1539 kB) > l4lx_irq_timer_startup(0) > names | 12.04: server_names_register(12.05 -> "l4lx.timer.i0") > l4lx | l4lx_thread_create: Created thread 12.05 (timer.i0) > timer_irq_thread: Starting timer IRQ thread. > Calibrating delay using timer specific routine.. 5603.19 BogoMIPS > (lpj=28015972) > Mount-cache hash table entries: 512 > Compat vDSO mapped to 0040e000. > CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 > NET: Registered protocol family 16 > PCI: Using configuration type 1 > Setting up standard PCI resources > SCSI subsystem initialized > PCI: Probing PCI hardware > PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: > region 0480-04bf claimed by ICH4 GPIO > PCI: Transparent bridge - 0000:00:1e.0 > PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0 > PCI: Bridge: 0000:00:03.0 > IO window: a000-afff > MEM window: fa000000-fa0fffff > PREFETCH window: disabled. > PCI: Bridge: 0000:00:1e.0 > IO window: b000-bfff > MEM window: f8000000-f9ffffff > PREFETCH window: 10000000-100fffff > io scheduler noop registered > Time: tsc clocksource has been installed. > io scheduler anticipatory registered (default) io scheduler deadline > registered io scheduler cfq registered > __ioremap: Requested region at fa180000 [0x400 Bytes] > __ioremap: Mapping physaddr fa180000 [0x400 Bytes, fa180000+000400] to > 08c00000+ > 000000 > l4lx | Starting L4FB via DOpE > names | 12.04: server_names_register(12.06 -> "l4lx.listener") > l4dope | SharedMem(alloc): hl.raw=100000, id=a1, size=96000 l4dope | > SharedMem(get_adr): address = 0x200000 > names | 12.04: server_names_register(12.07 -> "l4lx.DOpE refre") > l4lx | l4lx_thread_create: Created thread 12.07 (DOpE refresher) > names | 12.04: server_names_register(12.08 -> "l4lx.L4DOpEinpu") > l4lx | l4lx_thread_create: Created thread 12.08 (L4DOpEinput) > input: l4input key as /class/input/input0 > input: l4input mouse as /class/input/input1 > l4fb: DOpE framebuffer at 0x08c05000, size 600k > l4fb: mode is 640x480x16, linelength=1280, pages=0 > l4fb: directcolor: size=0:5:6:5, shift=0:11:5:0 > Console: switching to colour frame buffer device 80x30 > l4fb0: l4fb L4 frame buffer device (refresh: 200ms) > L4 serial driver > l4ser_init_ports > l4ser: input not enabled! > ttyLv0 at MMIO 0x1 (irq = 0) is a L4 > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > names | 12.04: server_names_register(12.09 -> "l4lx.Idler") > l4lx | l4lx_thread_create: Created thread 12.09 (Idler) > l4dope | SharedMem(alloc): hl.raw=100000, id=aa, size=280000 l4dope > | SharedMem(get_adr): address = 0x800000 > > Does somebody have a running L4Linux revision 32 ? Is it a known > problem, or could it be specific to my configuration, etc ... ? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

2 2

[L4LINUX] Is there a loop in revision 32 ?
by Clermont, Nicolas 05 Jul '07

05 Jul '07

Hi everybody, I got a problem with L4Linux but really don't know from where it comes, if I forgot to do something or if there is like a bug in L4Linux..... I have updated my l4 repositories yesterday, switching to L4Linux revision 32 and tudos revision 127. When booting L4Linux with TCP/IP enabled, it blocks after printing "Registered protocol 2". When disabling TCP/IP, it blocks after IDE probe. I have observed the same behavior with revision 31, but didn't have the time at this time to investigate. This time I have tried to find the reason of this loop. I have disabled TCP/IP and tried to see where L4Linux hangs. After IDE probe, L4Linux goes through wait_for_completion(), which calls schedule(), and then loops as need_resched label is always re-invocated. The last thing displayed is the creation of the idler thread... The problem with TCP/IP support enabled is different but maybe related to the same source. the schedule() function is also called, but it completes and so schedule. Then the idler thread is created and noting goes on. I have tried with different configurations, especially with protected I/O and unprotected, but I get always the same behavior. This is the output I get trough the serial line with TCP/IP disabled (l4linux also print on serial) : l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (clermont@L4-dev <mailto:clermont@L4-dev> ) (gcc version 3.4.4 (Gentoo l4lx : 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #59 Tue Jul 3 19:21:07 Local tim l4lx : e zone must be set--see zic manu l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): console=ttyLv0 earlyprintk=yes mem=128M l4lx : root=/dev/hda1 video=l4fb:refreshsleep:200 l4lx | Image: 00400000 - 00681000 [2564 KiB]. l4lx | Areas: Text: 00400000 - 005e6000 [1944kB] (a bit longer) l4lx | Data: 005e6000 - 005f9f7c [79kB] l4lx | Initdata: 005fc000 - 00618260 [112kB] l4lx | BSS: 0061a000 - 0067e840 [402kB] names | 12.02: server_names_register(12.03 -> "l4lx.tamer") l4lx | l4lx_thread_create: Created thread 12.03 (tamer) l4lx | Using tamed mode. ROOT: Sending all ports (for cli/sti) to task #0d l4lx | Got 65536 out of 65536 I/O ports names | 12.02: server_names_register(12.04 -> "l4lx.server") l4lx | l4lx_thread_create: Created thread 12.04 (server) l4lx | main thread will be 12.04 l4lx | l4env_register_pointer_section: addr = 005e6000 size = 634880 l4lx | sec-w-init: virt: 0x005e6000 to 0x00680fff [620 KiB] l4lx | sec-w-init: Number of physical regions: 1, 634880 Bytes l4lx | sec-w-init: 1: Phys: 0x01185000 to 0x01220000, Size: 634880 l4lx | l4env_linux_startup thread 4. l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 128MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x08bfffff [131072 KiB] l4lx | Main memory: Number of physical regions: 1, 134217728 Bytes l4lx | Main memory: 1: Phys: 0x14400000 to 0x1c400000, Size: 134217728 l4lx | Filling lower ptabs... l4lx | Done (1883 entries). Linux version 2.6.21-l4 (clermont@L4-dev <mailto:clermont@L4-dev> ) (gcc version 3.4.4 (Gentoo 3.4.4-r1, s sp-3.4.4-1.0, pie-8.7.8)) #59 Tue Jul 3 19:21:07 Local time zone must be set--se e zic manu CPU: Vendor unknown, using generic init. CPU: Your system may be unstable. dm_phys: 0000000000c00000 - 0000000008c00000 (usable) dm_phys: 0000000000800000 - 0000000000a00000 (usable) 132MB memory available. Zone PFN ranges: DMA 0 -> 2560 Normal 2560 -> 35840 early_node_map[1] active PFN ranges 0: 0 -> 35840 Allocating PCI resources starting at 10000000 (gap: 00a00000:ff600000) Built 1 zonelists. Total pages: 35560 Kernel command line: console=ttyLv0 earlyprintk=yes mem=128M root=/dev/hda1 vide o=l4fb:refreshsleep:200 Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) Detected 2800.514 MHz processor. Console: colour dummy device 80x25 l4ser_init_ports l4ser: input not enabled! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 131700k/143360k available (1539k kernel code, 1344k reserved, 484k data, 112k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0x10000000 - 0x18000000 ( 128 MB) lowmem : 0x00000000 - 0x08c00000 ( 140 MB) .init : 0x005fc000 - 0x00618260 ( 112 kB) .data : 0x00580cc4 - 0x005f9f7c ( 484 kB) .text : 0x00400000 - 0x00580cc4 (1539 kB) l4lx_irq_timer_startup(0) names | 12.04: server_names_register(12.05 -> "l4lx.timer.i0") l4lx | l4lx_thread_create: Created thread 12.05 (timer.i0) timer_irq_thread: Starting timer IRQ thread. Calibrating delay using timer specific routine.. 5603.19 BogoMIPS (lpj=28015972) Mount-cache hash table entries: 512 Compat vDSO mapped to 0040e000. CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 NET: Registered protocol family 16 PCI: Using configuration type 1 Setting up standard PCI resources SCSI subsystem initialized PCI: Probing PCI hardware PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO PCI quirk: region 0480-04bf claimed by ICH4 GPIO PCI: Transparent bridge - 0000:00:1e.0 PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0 PCI: Bridge: 0000:00:03.0 IO window: a000-afff MEM window: fa000000-fa0fffff PREFETCH window: disabled. PCI: Bridge: 0000:00:1e.0 IO window: b000-bfff MEM window: f8000000-f9ffffff PREFETCH window: 10000000-100fffff io scheduler noop registered Time: tsc clocksource has been installed. io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered __ioremap: Requested region at fa180000 [0x400 Bytes] __ioremap: Mapping physaddr fa180000 [0x400 Bytes, fa180000+000400] to 08c00000+ 000000 l4lx | Starting L4FB via DOpE names | 12.04: server_names_register(12.06 -> "l4lx.listener") l4dope | SharedMem(alloc): hl.raw=100000, id=a1, size=96000 l4dope | SharedMem(get_adr): address = 0x200000 names | 12.04: server_names_register(12.07 -> "l4lx.DOpE refre") l4lx | l4lx_thread_create: Created thread 12.07 (DOpE refresher) names | 12.04: server_names_register(12.08 -> "l4lx.L4DOpEinpu") l4lx | l4lx_thread_create: Created thread 12.08 (L4DOpEinput) input: l4input key as /class/input/input0 input: l4input mouse as /class/input/input1 l4fb: DOpE framebuffer at 0x08c05000, size 600k l4fb: mode is 640x480x16, linelength=1280, pages=0 l4fb: directcolor: size=0:5:6:5, shift=0:11:5:0 Console: switching to colour frame buffer device 80x30 l4fb0: l4fb L4 frame buffer device (refresh: 200ms) L4 serial driver l4ser_init_ports l4ser: input not enabled! ttyLv0 at MMIO 0x1 (irq = 0) is a L4 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx names | 12.04: server_names_register(12.09 -> "l4lx.Idler") l4lx | l4lx_thread_create: Created thread 12.09 (Idler) l4dope | SharedMem(alloc): hl.raw=100000, id=aa, size=280000 l4dope | SharedMem(get_adr): address = 0x800000 Does somebody have a running L4Linux revision 32 ? Is it a known problem, or could it be specific to my configuration, etc ... ? Thanks. -- Nico

2 1

mk/tmpl/inst
by Neal H. Walfield 04 Jul '07

04 Jul '07

mk/tmpl/inst correctly excludes CVS files, however, it does not exclude .svn files, which it ought since the code is now managed under svn. The attached patch corrects this deficiency. Neal Index: mk/tmpl/inst =================================================================== --- mk/tmpl/inst (revision 74) +++ mk/tmpl/inst (working copy) @@ -10,4 +10,4 @@ TARGETDIR="`pwd`" TOINSTALL="MAINTAINER Makefile idl include lib server examples doc ptest" -tar c -C $SRCDIR -f- --exclude=CVS $TOINSTALL | tar xvf - +tar c -C $SRCDIR -f- --exclude=CVS --exclude=.svn $TOINSTALL | tar xvf -

2 1

segment problem
by junioraozhi＠sina.com 03 Jul '07

03 Jul '07

Hi  all I have get the source code of fiasco,l4env,l4linux-2.6.21 via SVN ,and  compiled them succesfully. but when boot the l4linux , it says "the running kernel does not have the segments", "kernel feature missing "and went to jdb console. All my work is under the l4 document Why? thanks ------------------------------------------------------------------- 7月11日《变形金刚》首映电影票开抢了！( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2007/mail_zhuiyu_20070702.ht… ) =================================================================== 注册新浪2G免费邮箱（ http://mail.sina.com.cn/chooseMode.html ）

2 1

Re: l4 on mips
by Antoine.Amirault＠esial.uhp-nancy.fr 02 Jul '07

02 Jul '07

HI. Thanks for your answer. I answer you from another addresse because I'm currently in china and sometimes, gmail is not working well here. I hope you won't receive my 10 previous try ;). If i do that, the error is gone but unfortunately I experience another problem. Is it strange because it seems like syntax errors. It looks like that : make[1]: Entering directory `/home/antoine/Desktop/pistachio-build' ===> src/glue/v4-mips64/asmsyms.cc cd src/glue/v4-mips64/ && /home/antoine/Desktop/NICTA/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-build/include -I/home/antoine/Desktop/pistachio/kernel/include -I/home/antoine/Desktop/NICTA/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio-build/config/config.h -imacros /home/antoine/Desktop/pistachio/kernel/include/macros.h -include /home/antoine/Desktop/pistachio/kernel/include/config.h -include /home/antoine/Desktop/pistachio/kernel/include/types.h -fno-rtti -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-non-virtual-dtor -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -march=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc In file included from /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/space.h:42, from /home/antoine/Desktop/pistachio/kernel/include/api/v4/space.h:36, from /home/antoine/Desktop/pistachio/kernel/include/api/v4/tcb.h:41, from /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:34: /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:277: error: expected unqualified-id before '{' token /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h: In member function `void pgent_t::set_entry(space_t*, pgent_t::pgsize_e, void*, word_t, word_t, bool)': /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `readable' undeclared (first use this function) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: (Each undeclared identifier is reported only once for each function it appears in.) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `writable' undeclared (first use this function) In file included from /home/antoine/Desktop/pistachio/kernel/include/api/v4/tcb.h:674, from /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:34: /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h: In member function `void tcb_t::notify(void (*)())': /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h:393: error: ISO C++ forbids cast to non-reference type used as lvalue /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h: In member function `void tcb_t::notify(void (*)(word_t), word_t)': /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h:410: error: ISO C++ forbids cast to non-reference type used as lvalue /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h: In member function `void tcb_t::notify(void (*)(word_t, word_t), word_t, word_t)': /home/antoine/Desktop/pistachio/kernel/include/glue/v4-mips64/tcb.h:430: error: ISO C++ forbids cast to non-reference type used as lvalue /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc: At global scope: /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:41: warning: invalid access to non-static data member `utcb_t::mr' of NULL object /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:41: warning: (perhaps the `offsetof' macro was used incorrectly) /home/antoine/Desktop/pistachio/kernel/src/glue/v4-mips64/asmsyms.cc:41: warning: invalid access to non-static data member `utcb_t::mr' of NULL object This two warnings are repeated a lot of times, and after ===> src/generic/kmemory.cc cd src/generic/ && /home/antoine/Desktop/NICTA/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-build/include -I/home/antoine/Desktop/pistachio/kernel/include -I/home/antoine/Desktop/NICTA/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio-build/config/config.h -imacros /home/antoine/Desktop/pistachio/kernel/include/macros.h -include /home/antoine/Desktop/pistachio/kernel/include/config.h -include /home/antoine/Desktop/pistachio/kernel/include/types.h -fno-rtti -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-non-virtual-dtor -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -march=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio/kernel/src/generic/kmemory.cc In file included from /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/cache.h:38, from /home/antoine/Desktop/pistachio/kernel/include/platform/vr41xx/cache.h:36, from /home/antoine/Desktop/pistachio/kernel/src/generic/kmemory.cc:38: /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:277: error: expected unqualified-id before '{' token /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h: In member function `void pgent_t::set_entry(space_t*, pgent_t::pgsize_e, void*, word_t, word_t, bool)': /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `readable' undeclared (first use this function) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: (Each undeclared identifier is reported only once for each function it appears in.) /home/antoine/Desktop/pistachio/kernel/include/arch/mips64/pgent.h:293: error: `writable' undeclared (first use this function) make[1]: *** [src/generic/kmemory.o] Error 1 make[1]: Leaving directory `/home/antoine/Desktop/pistachio-build' make: *** [all] Error 2 I hope you could help me. I use the CVS Version and a cross compiler taken from the NICTA SIte 2007/7/2, Daniel Potts < danielp(a)ok-labs.com>: Hi Antoine, Sorry for the late reply, I hope you've made progress on this. We believe this is a problem with compiler flags changing in our compiler tools release, compared to those expected by the build system in Pistachio 0.4. Try editing kernel/Mk/Makeconf.mips and change mcpu=r4100 to march=4100, or something similar. Good luck, Daniel On 21/06/2007, at 4:36 PM, Antoine Amirault wrote: > Hi, > I'm student at ESIAL (a French engineering school) currently > doing an internship in Beijing. I have to simulate l4 on a mips > platform with qemu. > > I have downloaded pistachio and mips64-elf-3.4.4 from > http://ertos.nicta.com.au/software/prebuilt/binaries.pml > > When i compile the kernel i obtain the following messages : > > antoine@liama-desktop:~/Desktop/pistachio-0.4-aos/build$ make > make[1]: Entering directory `/home/antoine/Desktop/pistachio- > 0.4-aos/build' > ===> src/glue/v4-mips64/asmsyms.cc > cd src/glue/v4-mips64/ && > /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc > -nostdinc -I/home/antoine/Desktop/pistachio-0.4-aos/build/include > -I/home/antoine/Desktop/pistachio- 0.4-aos/kernel/include > -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio-0.4-aos /kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio- > 0.4-aos/kernel/src/glue/v4-mips64/asmsyms.cc > cc1plus: error: invalid option `cpu=r4100' > ===> src/api/v4/exregs.cc > cd src/api/v4/ && > /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc > -nostdinc -I/home/antoine/Desktop/pistachio- 0.4-aos/build/include > -I/home/antoine/Desktop/pistachio-0.4-aos/kernel/include > -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio-0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio-0.4-aos /kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio- > 0.4-aos/kernel/src/api/v4/exregs.cc > cc1plus: error: invalid option `cpu=r4100' > make[1]: *** [src/api/v4/exregs.o] Error 1 > make[1]: Leaving directory > `/home/antoine/Desktop/pistachio-0.4-aos/build' > make: *** [all] Error 2 > > Do you know how to solve this ? > Maybe i should use another compiler. > Thanks for your help > Antoine > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

1 0

l4 on mips
by Antoine Amirault 02 Jul '07

02 Jul '07

Hi, I'm student at ESIAL (a French engineering school) currently doing an internship in Beijing. I have to simulate l4 on a mips platform with qemu. I have downloaded pistachio and mips64-elf-3.4.4 from http://ertos.nicta.com.au/software/prebuilt/binaries.pml When i compile the kernel i obtain the following messages : antoine@liama-desktop:~/Desktop/pistachio-0.4-aos/build$ make make[1]: Entering directory `/home/antoine/Desktop/pistachio-0.4-aos/build' ===> src/glue/v4-mips64/asmsyms.cc cd src/glue/v4-mips64/ && /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-0.4-aos/build/include -I/home/antoine/Desktop/pistachio-0.4-aos/kernel/include -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio-0.4-aos /kernel/src/glue/v4-mips64/asmsyms.cc cc1plus: error: invalid option `cpu=r4100' ===> src/api/v4/exregs.cc cd src/api/v4/ && /opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/mips64-elf-gcc -nostdinc -I/home/antoine/Desktop/pistachio-0.4-aos/build/include -I/home/antoine/Desktop/pistachio-0.4-aos/kernel/include -I/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/mips64-elf/bin/../lib/gcc/mips64-elf/3.4.4/include -Umips64 -Uvr4181 -Uvr41xx -Uv4 -D__ARCH__=mips64 -D__CPU__=vr4181 -D__PLATFORM__=vr41xx -D__API__=v4 -imacros /home/antoine/Desktop/pistachio- 0.4-aos/build/config/config.h -imacros /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/macros.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/config.h -include /home/antoine/Desktop/pistachio- 0.4-aos/kernel/include/types.h -fno-builtin -fomit-frame-pointer -fno-exceptions -Wall -Wno-format -Wconversion -O3 -G 0 -mlong64 -mno-abicalls -non_shared -msplit-addresses -EL -mcpu=r4100 -mips3 -mabi=64 -Wa,-mabi=o64 -c /home/antoine/Desktop/pistachio-0.4-aos /kernel/src/api/v4/exregs.cc cc1plus: error: invalid option `cpu=r4100' make[1]: *** [src/api/v4/exregs.o] Error 1 make[1]: Leaving directory `/home/antoine/Desktop/pistachio-0.4-aos/build' make: *** [all] Error 2 Do you know how to solve this ? Maybe i should use another compiler. Thanks for your help Antoine

2 1

Fiasco@ARM - supported hardware
by Daniel Vandersee 01 Jul '07

01 Jul '07

Hello, how do you test L4 on an ARM platform? Do you have specific hardware for that purpose? You mentioned that you use ARM Integrator boards. As there are several integrator boards available: which one exactly do you use? Do you use other boards as well? I'm asking because I plan to buy an ARM board which is supported out of the box without the need to modify drivers. Do you additionally use software simulators to test L4? If so, which one do you use? I tried Skyeye to simulate an ARM integrator board as well as a SA1100-board but didn't get any output over the serial line. Qemu doesn't work either and terminates with the following error: "qemu: uncaught target signal 11 (Segmentation fault) - exiting". Kind regards, Daniel

2 5

Installing Generated Header Files
by Neal H. Walfield 01 Jul '07

01 Jul '07

Hi, I'm using BID and generating header files at compile time. I looked at the include role, however, as far as I can tell, it only installs files from the source tree, not from the object tree. The attached patch improves the include role-file to allow this mode of operation. The patch consists of two changes. First, before listing the directory, we change to $(INCSRC_DIR). (This also requires evaluating TARGET_CMD lazily, i.e., using a recursive variable, not a simple one, as INCSRC_DIR may be set later.) Second, an additional target has been added, headers, which can depend on generated header files. I also updated the documentation. The current patch doesn't allow installing header files from both the source directory and the object directory. This might be useful, however, it appears to require modifying the perl code, which I have done my best to forget. Thanks, Neal Index: mk/include.mk =================================================================== --- mk/include.mk (revision 74) +++ mk/include.mk (working copy) @@ -27,9 +27,9 @@ ifeq ($(origin TARGET),undefined) # use POSIX -print here -TARGET_CMD := find . -name '*.[ih]' -print +TARGET_CMD = (cd $(INCSRC_DIR); find . -name '*.[ih]' -print) else -TARGET_CMD := echo $(TARGET) +TARGET_CMD = echo $(TARGET) endif INSTALL_INC_PREFIX ?= l4/$(PKGNAME) INCSRC_DIR ?= $(SRC_DIR) @@ -64,7 +64,9 @@ } \ }' -all:: +headers:: + +all:: headers @$(TARGET_CMD) | $(call installscript,1) install:: Index: doc/bid-spec/spec.tex =================================================================== --- doc/bid-spec/spec.tex (revision 73) +++ doc/bid-spec/spec.tex (working copy) @@ -2274,22 +2274,32 @@ \subsubsection{Purpose} -The purpose of the include role is to install the local include-files -into the local install-tree or into the drops install-tree. The -role-file achieves two goals when managing include-files: +The purpose of the include role is to install all .h and .i under +INCSRC_DIR into the local install-tree or into the drops +install-tree. This role facilitates two goals with respect to managing +include-files: + \begin{enumerate} -\item The path where the include-files are to be found in is entirely +\item The path where the include-files are found is entirely defined by the package name and the target system of the include-files. -\item Once written, the makefile needs not to be modified, even if new - include files are added or old include files are removed from the package. +\item Once written, the make file need not be modified, even when new + include files are added or old include files are removed from the + package. \end{enumerate} The target system of an include file is determined by putting it into -a specific subdirectory. The role-file will install it accordingly -then. The following table defines the subdirectories depending on the -target systems. +a specific subdirectory. The role-file will then install it +accordingly. By default, INCSRC_DIR points is set to the source +directory. To install generated header files, set INCSRC_DIR to +§OBJ_DIR. There is currently no mechanism to exclude header files. +When generating header files, add them to the headers target (which +all depends on). + +The following table defines the subdirectories depending on the target +systems. + \begin{center} \begin{tabular}{|l|l|} \hline

2 1

memory overflow
by Antoine Amirault 29 Jun '07

29 Jun '07

Hi all! I'm trying to run l4 on qemu. I've successfully build the kernel and the user level code. I have followed the guide from l4ka : http://l4ka.org/projects/pistachio/ia32/gettingstarted.php and everything is running well except some little thing but i think it doesn't matter (like problem when unmounting,...). but whem i run qemu with qemu -fda fdimage.img, i got this message : Memory descriptor overflow (max=200, n=200) --- "KD# memdesc overflow" --- ---------------------------------------------9eip=f0102358, esp=f010ee400 --- then everything is locked> Do you know how i can solve that? Thanks. Antoine

1 0

How can Minix 3 be so small
by Hendrik Tews 27 Jun '07

27 Jun '07

Hi, I just noticed that the Minix 3 kernel is under 4000 lines. I couldn't easily find numbers for Pistachio, but I guess it is comparable to Fiasco, which is about 15.000 lines (without the kernel debugger). Could anybody explain why Fiasco is so big in comparison with Minix 3? From the difference in size I would expect that there is an essential difference in the feature set between Minix 3 and Fiasco. Or are the Minix lines just four times longer on average? Bye, Hendrik

8 8

RE: How can Minix 3 be so small
by Clermont, Nicolas 26 Jun '07

26 Jun '07

I have noticed that Minix3 only support one architecture (x86), and doesn't offers something like a HAL. Maybe this is one reason. -----Message d'origine----- De : l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] De la part de Hendrik Tews Envoyé : mardi 26 juin 2007 17:13 À : l4-hackers(a)os.inf.tu-dresden.de Objet : How can Minix 3 be so small Hi, I just noticed that the Minix 3 kernel is under 4000 lines. I couldn't easily find numbers for Pistachio, but I guess it is comparable to Fiasco, which is about 15.000 lines (without the kernel debugger). Could anybody explain why Fiasco is so big in comparison with Minix 3? From the difference in size I would expect that there is an essential difference in the feature set between Minix 3 and Fiasco. Or are the Minix lines just four times longer on average? Bye, Hendrik _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

1 0

clarification on explicit preemption points in Fiasco IPC
by Sergio Ruocco 26 Jun '07

26 Jun '07

Hi all, Forgive me if this is a silly question because it is documented somewhere, but I am unfamiliar with Fiasco source, and too in a hurry to go through all the Fiasco source code and cross-comare it with the documentation/papers/examples etc.... Skimming though Fiasco source code I checked out few weeks ago (the Doxygen online version is from 2005, out of date), I found 16 "Proc::preemption_point();" in the IPC path in the source file thread-ipc.cpp: [sergio 19:41 ~/Desktop/FIASCO/tudos/kernel/fiasco/src/kern]$ grep Proc::preemption_point thread-ipc.cpp | wc -l 16 Which tudos/kernel/fiasco/src/drivers/processor.cpp defines as: ... static inline void preemption_point() { sti(); irq_chance(); [ NOP NOP ] cli(); } ... My question is: As far as I know, Fiasco is entirely preemptable. Then why sprinkling the IPC path with Enable IRQs/NOP NOP/Disable IRQs ? Is there a document or a paper that discuss which parts of the kernel run with IRQs disabled / enabled ? Preemption disabled / enabled etc. ? Thanks in advance, Sergio -- Sergio Ruocco, PhD Research Fellow ruocco(a)disco.unimib.it / sergio.ruocco(a)gmail.com NOMADIS Lab. phone: +39-02-6448-7879 mobile, embedded real-time systems skype: 'sergioruocco' Università degli Studi di Milano-Bicocca, Italy

3 3

Re: 16-bit code and L4
by Valery V. Sedletski 25 Jun '07

25 Jun '07

On Mon, 25 Jun 2007 18:43:55 +1300 (MSD), Valery V. Sedletski wrote: >Yes, I see: > >L4_INLINE void >fiasco_gdt_set(void *desc, unsigned int size, > unsigned int entry_number_start, l4_threadid_t tid); > >It is privileged architecture-specific syscall, as I understood. And what means >"sanity checking" by the kernel? Does the kernel simply check that the descriptor >defines a valid segment, or, there are some additional chacks. For example, must >segments to be a non-overlapping, or not? (For 32-bit<-->16-bit thunking it is important >to have a possibility for the segments to be overlapping -- the code can be at the same >time to be in 16-bit segment and 32-bit segment). In segment.h header, there is an implementation of this function, through using LLDT instruction. (and not through using a special syscall). So, LLDT instruction is allowed for usermode programs, and the kernel intercept lldt instruction. -- Probably when this instruction is used in usermode program, the TRAP occurs, and the kernel handles this trap, modifying the LDT or GDT. Is this right? (I searched an fiasco_gdt_set() function in the source code and I found that L4Linux uses this function. So, it is, probably, was created for demands of L4Linux development?)

2 1

Re: 16-bit code and L4
by Valery V. Sedletski 25 Jun '07

25 Jun '07

> >I was working on allowing applications to use segmentation in >Pistachio as well. The modifications enabled apps to install segment >descriptors in a per address space LDT (after sanity checking by the >kernel of course). Modifying the GDT is not supported. > Is GDT modifying support planned in the future? > >By setting a thread in a special mode the kernel will never modify the >ES, FS, and GS of the thread. For optimization reasons the kernel >still retains the right to modify DS and SS though, so in effect these >can not be freely used by the app. Also, the kernel only allows data >segments to be installed --- no code or other segment types. > >It's been a while since I worked on this and got sidetracked by other >stuff, so I didn't completely finish the implementation yet. > > eSk > Is this documented somewhere? (It seems that it is not documented in L4 version X.2 API manual.) Maybe, it is in some source code documentation (Doxygen generated or alike)? > > > Thank you very much for your answer. WBR, Valery

1 0

Re: 16-bit code and L4
by Valery V. Sedletski 25 Jun '07

25 Jun '07

Thanks for answening so quickly. >> >Fiasco makes some GDT slots available to userland so that FS and GS can >> >be used with those. >> > >> >> And how to access these GDT descriptors from userland? Is this >> documented somewhere? Can usermode task change attributes of these >> descriptors (such as "16-bits" attribute)? Are they (descriptors) >> somehow mapped to requestor's address space or how else can usermode >> task modify these descriptors? Or, can usermode task only load >> selectors corresponding to these descriptors, but not modify >> descriptors itself? > >Userland can load descriptors that are sanity checked by the kernel and >then stored in the GDT. Using 16-bit segments should work too although I >never tried. Similar features are offered for the LDT. Our l4sys package >contains segment.h headers which describe the kernel interface. > Yes, I see: L4_INLINE void fiasco_gdt_set(void *desc, unsigned int size, unsigned int entry_number_start, l4_threadid_t tid); It is privileged architecture-specific syscall, as I understood. And what means "sanity checking" by the kernel? Does the kernel simply check that the descriptor defines a valid segment, or, there are some additional chacks. For example, must segments to be a non-overlapping, or not? (For 32-bit<-->16-bit thunking it is important to have a possibility for the segments to be overlapping -- the code can be at the same time to be in 16-bit segment and 32-bit segment). ... > >> And what about DS/ES? Can usermode task load these registers with >> another selector, as with FS/GS? > >Loading should work I guess but DS and ES are currently not restored on >exit to user. > so, if user restores these segments on exit, the loading should work? > > >Adam >-- >Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > >

1 0

Playing with ORe
by Marc CHALAND 22 Jun '07

22 Jun '07

Hi everybody, I did some experiments with ORe. I played with arping and I modified it to reply to ICMP from windows. I also added one option to ORe to prevent promiscuous mode when not necessary. cf attachment Best Regards

2 1

Thesis on verification of Fiasco's IPC implementation
by Erik Schierboom 22 Jun '07

22 Jun '07

Hi all, As some of you will probably already know, I have been working on the verification of (a part of) Fiasco's IPC implementation. This week I have finished my thesis and the result can be found at the following location: http://www.swyp.nl/thesis.pdf Thanks for all the help I have received. With regards, Erik Schierboom

1 0

Re: 16-bit code and L4
by Valery V. Sedletski 22 Jun '07

22 Jun '07

>On Thu Jun 21, 2007 at 03:55:24 +1300, Valery V. Sedletski wrote: >> >>> 2) Must all the segment registers be CS == DS == ES == FS == GS == SS == FLAT in L4 usermode >> >programs (in Intel >> >>> architecture implementation)? Or, there exist a possibility to use segments other than FLAT? >> >>> >> >>Fiasco preserves some of these segments (e.g., GS to support thread >> >>local storage). However, unless OS/2 makes use of these segments in >> >>32-bit mode there is no need to change these from a flat setting. >> > >> >It seems, that OS/2 does not use GS (GS seems to be always == 0), at least, in application programs. >> > >> >> But also FS is used to address a structure named Thread Info Block >> (TIB), it is also not flat (it has a limit=0x30) So, FS is used by >> OS/2 and programs depend on it. GS seems to be not used, and ES and DS >> are generally flat. > >Fiasco makes some GDT slots available to userland so that FS and GS can >be used with those. > And how to access these GDT descriptors from userland? Is this documented somewhere? Can usermode task change attributes of these descriptors (such as "16-bits" attribute)? Are they (descriptors) somehow mapped to requestor's address space or how else can usermode task modify these descriptors? Or, can usermode task only load selectors corresponding to these descriptors, but not modify descriptors itself? So it is with Fiasco, and what about Pistachio? (Is this mailing list the right place to ask such questions, or it is better to ask them at l4ka(a)ira.uka.de?) And what about DS/ES? Can usermode task load these registers with another selector, as with FS/GS? > > >Adam >-- >Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ >

3 2

Re: 16-bit code and L4
by Valery V. Sedletski 20 Jun '07

20 Jun '07

>>> 2) Must all the segment registers be CS == DS == ES == FS == GS == SS == FLAT in L4 usermode >programs (in Intel >>> architecture implementation)? Or, there exist a possibility to use segments other than FLAT? >>> >>Fiasco preserves some of these segments (e.g., GS to support thread >>local storage). However, unless OS/2 makes use of these segments in >>32-bit mode there is no need to change these from a flat setting. > >It seems, that OS/2 does not use GS (GS seems to be always == 0), at least, in application programs. > But also FS is used to address a structure named Thread Info Block (TIB), it is also not flat (it has a limit=0x30) So, FS is used by OS/2 and programs depend on it. GS seems to be not used, and ES and DS are generally flat.

2 1

16-bit code and L4
by Valery V. Sedletski 20 Jun '07

20 Jun '07

Would be someone so kind to answer some questions? These questions are about 16-bit instructions execution on intel processors in L4 usermode programs. First, excuse me for my bad English (it is not native for me). And first I'll try to explain the motivation. -- I am now trying to contribute to the project aiming to create an Opensource OS/2 clone. (osFree aka OS/3 project, http://www.osfree.org/) The goal now is to create OS/2 API implementation with binary compatibility with existing OS/2 (intel) applications. Also, it would be desirable to reuse existing OS/2 device driver base (if it is possible). We are planning to use L4 as a base for API implementation. The problem with existing OS/2 applications is that they are not pure 32-bit; there are many common 16-bit API's now (they are to be replaced with 32-bit analogues in new implementation); almost each LX format executable contains 16-bit fragments (thunks for calling 16-bit API's), though the most of each executable is 32-bit and uses 32-bit flat memory model. Also, most old OS/2 device drivers are 16-bit, they are still very common now (but newer drivers are 32-bit). Another problem is that many drivers and applications are available in binary-only form (so, they cannot be recompiled, as with Linux) 32-bit applications and drivers support can be made, for example, by implementing a converter of LX-executables to pure 32-bits. Also, 16-bit fragments can be executed in a virtual machine. Or, as another variant, it may be possible to execute these 16-bit parts on a real processor. The problem is only how to maintain correct segment registers values and how to add a 16-bit segment descriptor to GDT or LDT. The problem with L4 is that it doesn't expose segmentation to outside the kernel, it abstracts segmentation from usermode programs and only allows to use paging, but not segmentation. The reason is known: segmentation is not portable, it has no analogues on other architectures than intel one. So, the questions are: 1) There is L4Linux. It is mostly 32-bit. But as I know, the Linux kernel also contains some 16-bit parts, such as setup code (it works with BIOS routines and probes hardware), and also (as I heard) acpi suspend/wakeup code. So, it contains 16-bit segments. But doesn't it interfere with L4? How did the people porting Linux to the L4 microkernel solve the problem of 16-bit code? And doesn't it interfere with ELF format capabilities (it is pure 32/64-bit, as I understand)? 2) Must all the segment registers be CS == DS == ES == FS == GS == SS == FLAT in L4 usermode programs (in Intel architecture implementation)? Or, there exist a possibility to use segments other than FLAT? 3) Is it possible to cause the L4 kernel to create 16-bit segment descriptor on Intel architecture?

2 2

Re: Fiasco@ARM - supported hardware
by Daniel Vandersee 19 Jun '07

19 Jun '07

Hi Jorge, I just tried it and it doesn't work for me, too. If I break the program execution after a while it always stops at uart_write+72: > 0xb0002e30 <uart_write+64>: ldr r3, [r2, #32] > 0xb0002e34 <uart_write+68>: tst r3, #4 ; 0x4 > 0xb0002e38 <uart_write+72>: beq 0xb0002e30 <uart_write+64> > 0xb0002e3c <uart_write+76>: ldrb r3, [r0, r12] Did you got it running with skyeye? Attached you will find my skyeye configuration. Maybe you have an idea what goes wrong here? Thanks! Cheers, Daniel Jorge Torres schrieb: > Hi Daniel, > > Have you tried PXA borad with skyeye? > > Thanks, > > JOrge > > On 6/18/07, *Daniel Vandersee* < dvandersee(a)escrypt.com > <mailto:dvandersee@escrypt.com>> wrote: > > Hello, > > how do you test L4 on an ARM platform? Do you have specific hardware > for > that purpose? You mentioned that you use ARM Integrator boards. As there > are several integrator boards available: which one exactly do you use? > Do you use other boards as well? I'm asking because I plan to buy an > ARM > board which is supported out of the box without the need to modify > drivers. > > Do you additionally use software simulators to test L4? If so, which one > do you use? I tried Skyeye to simulate an ARM integrator board as well > as a SA1100-board but didn't get any output over the serial line. Qemu > doesn't work either and terminates with the following error: "qemu: > uncaught target signal 11 (Segmentation fault) - exiting". > > Kind regards, > Daniel > > > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de <mailto:l4-hackers@os.inf.tu-dresden.de> > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > cpu: xscale #cpu: pxa25x mach: pxa_lubbock #cpu: pxa27x #mach: pxa_mainstone mem_bank: map=I, type=RW, addr=0x40000000, size=0x0c000000 mem_bank: map=M, type=RW, addr=0xb0000000, size=0x10000000 #mem_bank: map=M, type=RW, addr=0xd0000000, size=0x00100000 #log: logon=1, logfile=/tmp/sk2.log, start=500000, end=1500000 #lcd:state=on,type=pxa,mod=gtk uart: mod=stdio

1 0

Re: L4Env Building Problem!
by Bjoern Doebel 14 Jun '07

14 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marius.bao wrote: >> Please enter l4/pkg/bootstrap/server/src, run "make V=1" and post the >> complete output here. >> > When I run "make V=1", the make process stops. The output is as follows: > ../../../../mk/Makeconf:120: *** need to give builddir with > O=.../builddir. Stop. Sure, then please run make V=1 O=<path_to_your_builddir> and post the complete output here. > Ps:The ../../../../ directory is l4. > I couldn't compile a package separately. When I want to compile a > single package, I have to enter the build directory to run "make", and > compile all the packages. I suffered a lot as the compile process > takes a long time. You can build (parts of) a single package in at least 2 ways: 1. use the O=<builddir> option when running make just as the error message above tells you. 2. Go to the builddir. There will be a subdirectory pkg with build dirs for all the packages. You can enter these and only build a single one. Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGcOTNP5ijxgQLUNkRAvWjAJ9ipIMpC2VA1et+nzf2JtJeqaWhLgCfRnb2 E0j6eVEgzO+AZVvOKDrSHL0= =c4iI -----END PGP SIGNATURE-----

1 0

Re: L4Env Building Problem!
by Marius.bao 13 Jun '07

13 Jun '07

Hi, >Could you find out which dice binary is used (run "make V=1" in one of >the idl directories, for instance tudos/l4/pkg/names/idl)? And then run >that binary with the --version option and post the output here? It turned out that i used an old version of DICE, I update to the latest version, and it works correctly. Thanks a lot :) when I compiled the bootstrap package, another problem occured: l4/pkg/bootstrap/server/src/startup.cc:215: undefined reference to `__cxa_guard_release' maybe my gcc is too old. my gcc version is gcc-3.4.2.6-fc3

2 1

L4Env Building Problem!
by Marius.bao 11 Jun '07

11 Jun '07

Hi, Thanks for previous information. I've checkouted l4env using: svn checkout -N http://svn.tudos.org/repos/tudos/trunk tudos cd l4 ./repomgr co l4env When I tried to compile l4env, errors occured in some idl file. eg: names.idl in names package import <l4/sys/types.h> import <l4/names/libnames.h> /** IDL interface of the name server. */ interface names { long register([in, string] char *name); long register_thread([in, string] char *name, [in] l4_threadid_t id); long unregister_thread([in, string] char *name, [in] l4_threadid_t id); long unregister_task([in] l4_threadid_t id); long query_name([in, string] char *name, [out] l4_threadid_t *id); long query_id([in] l4_threadid_t id, [out, string, prealloc_client, max_is(NAMES_MAX_NAME_LEN)] (*) char **name);modified ...... }; errors occured in the last function at the (*) line, the error information is as follows: unknown attribute dice: 1 Error(s) and 0 Warning(s) occured. when I modified the function into long query_id([in] l4_threadid_t id, [out, string] char **name); It compiles OK. I don't know what's the problem as I know little about the corba idl.

2 1

Re: l4-hackers Digest, Vol 50, Issue 7
by Erik Schierboom 09 Jun '07

09 Jun '07

> Message: 4 > Date: Fri, 8 Jun 2007 00:17:26 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > Subject: Re: Verify Fiasco assertion using pingpong > To: l4-hackers(a)os.inf.tu-dresden.de > Message-ID: <20070607221726.GN14071(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Thu Jun 07, 2007 at 13:17:09 +0200, eschierb(a)sci.kun.nl wrote: > >> Quoting Martin Pohlack <mp26(a)os.inf.tu-dresden.de>: >> >> >>> eschierb(a)sci.kun.nl wrote: >>> >>> [...] >>> >>> >>>> "/bin/bash: did_not_find_dice___please_install_dice: command not found" >>>> >>> Did you build Dice? It got moved recently in the SVN from l4/tools/dice >>> to tools/dice. I think you have to build it manually. >>> >>> Cheers, >>> Martin >>> >>> >> I believe I did, by invoking the following commands: >> >> " >> cd dice >> ./bootstrap >> ./configure >> ./make >> " >> > > When being in the l4 directory, does calling > ../dice/src/dice > work or not? I.e. is there a dice binary? > > > > Adam > Calling ../dice/src/dice does work so there is a DICE binary, but when I call "make O=/tmp/build" in the l4 directory I still get the following error: if [ -r ../dice/Makefile.drops ]; then \ make -C ../dice -f Makefile.drops; \ fi make[1]: Entering directory `/tmp/tudos/dice' ../l4/mk/Makeconf:155: Sorry, your object or source path became garbled. ../l4/mk/Makeconf:156: OBJ_BASE: /tmp/build ../l4/mk/Makeconf:157: SRC_BASE_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:158: SRC_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:159: OBJ_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:160: PKGDIR: ../l4/mk/Makeconf:161: L4DIR_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:162: PKGDIR_ABS: ../l4/mk/Makeconf:163: PKGDIR_OBJ: /tmp/tudos/dice ../l4/mk/Makeconf:164: *** Please investigate.. Stop. make[1]: Leaving directory `/tmp/tudos/dice' make: *** [../dice] Error 2

2 1

[Fwd: Re: L4 implementations]
by Sergio Ruocco 08 Jun '07

08 Jun '07

Forwarding my answer below as requested. Sergio -------- Original Message -------- Subject: Re: L4 implementations Date: Fri, 8 Jun 2007 23:15:41 +1200 From: Shams <shams(a)orcon.net.nz> To: <ruocco(a)disco.unimib.it> References: <f3op51$utv$1(a)sea.gmane.org> <4669154F.3020907(a)disco.unimib.it> Hi Sergio Thanks for the info Can you also please post this to the newsgroup so that other newbies can benefit from it too. Thanks Shams ----- Original Message ----- From: "Sergio Ruocco" <ruocco(a)disco.unimib.it> To: "Shams" <shams(a)orcon.net.nz> Sent: Friday, June 08, 2007 8:37 PM Subject: Re: L4 implementations Shams wrote: > Just a few questions which I am having a hard time understanding: For answers to these and other questions, and further information on the L4 microkernel API, its different implementations (Pistachio, Fiasco, OKL4 etc.), and the various OSes running on them (Iguana, DROPS etc.), see also the following web sites: http://en.wikipedia.org/wiki/L4_microkernel_family http://l4hq.org/kernels/ http://l4hq.org/docs/ http://l4hq.org/projects/os/ Pistachio http://l4ka.org/ Fiasco http://os.inf.tu-dresden.de/fiasco/ OKL4 http://www.ok-labs.com/products/ http://portal.ok-labs.com/ and this paper of mine: http://ertos.nicta.com.au/publications/papers/Ruocco_06.abstract.pml http://citeseer.ist.psu.edu/757180.html Best Regards, Sergio -- Sergio Ruocco, PhD Research Fellow sergio.ruocco(a)disco.unimib.it / gmail.com NOMADIS Lab. phone: +39-02-6448-7879 mobile, embedded real-time systems skype: 'sergioruocco' Università degli Studi di Milano-Bicocca, Italy

1 0

L4 implementations
by Shams 08 Jun '07

08 Jun '07

Hi I played with the demo cd and it works great.. Just a few questions which I am having a hard time understanding: 1. L4 is itself a API/ABI reference, right? 2. Are L4.Pistachio and L4.Fiasco are 2 different implementations of L4? 3. Is L4.Pistachio is the current official reference implementation? Do both of them only differ in internal code only? 3. What is the difference between L4.Pistachio and L4.Fiasco? Why are there 2 separate implementations ie. why not just one codebase? Are you able to merge these 2 together or plan to? 4. Is L4.Sec official and already in the process of being implemented? Is L4.Pistachio and L4.Fiasco going to be replaced by L4.Sec? Thanks Shams

6 15

Verify Fiasco assertion using pingpong
by eschierb＠sci.kun.nl 08 Jun '07

08 Jun '07

Hi, I am trying to achieve a very simple thing, which is to test an assertion in the Fiasco ICP path. More specifically, I want to add the following assertion to the sys_ipc() function: " // This assertion is added by us assert(!(state() & Thread_polling)); if (EXPECT_TRUE(have_send_part || have_receive_part)) ret = do_ipc(have_send_part, partner, have_receive_part, sender, t, regs); " As can be seen, I want to assert that the Thread_polling bit is not set before calling do_ipc(). I planned to do this by compiling the modified Fiasco kernel and the pingpong package. If the assertion would not fire after running the pingpong test suite, I would have at least some confidence that the assertion does not hold. I have already done something similar a while ago, but with the newer versions I cannot seem to get it working. The first problem was with the DICE compiler, if I used the latest version of the DICE compiler I got the "collect2: ld returned 1 exit status". I solved this by using the 3.1.1 DICE version. I then used the following commands: " svn co http://svn.tudos.org/repos/tudos/tags/dice/3.1.1 dice ./repomgr co hello cd dice ./bootstrap ./configure ./make cd .. cd l4/pkg svn up pingpong cd .. make O=/tmp/build config make O=/tmp/build " However, this resulted in the following error " if [ -r ../dice/Makefile.drops ]; then \ make -C ../dice -f Makefile.drops; \ fi make[1]: Entering directory `/tmp/tudos/dice' ../l4/mk/Makeconf:155: Sorry, your object or source path became garbled. ../l4/mk/Makeconf:156: OBJ_BASE: /tmp/build ../l4/mk/Makeconf:157: SRC_BASE_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:158: SRC_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:159: OBJ_DIR: /tmp/tudos/dice ../l4/mk/Makeconf:160: PKGDIR: ../l4/mk/Makeconf:161: L4DIR_ABS: /tmp/tudos/l4 ../l4/mk/Makeconf:162: PKGDIR_ABS: ../l4/mk/Makeconf:163: PKGDIR_OBJ: /tmp/tudos/dice ../l4/mk/Makeconf:164: *** Please investigate.. Stop. make[1]: Leaving directory `/tmp/tudos/dice' make: *** [../dice] Error 2 " As an alternative to the last three lines, I tried to issue the "make O=/tmp/build" command in the l4/pkg directory. This resulted in the following error: "/bin/bash: did_not_find_dice___please_install_dice: command not found" Any idea how this can be remedied? With regards, Erik Schierboom

3 3

Re: Hiworld Problem
by Bjoern Doebel 06 Jun '07

06 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, >> Did you checkout and build the L4 Environment (as requested in chapter >> 2 of >> the tutorial)? If so, generic_ts should be built and your application >> gets >> linked with it. > I followed http://os.inf.tu-dresden.de/drops/download.html using svn to > check > out the hello module. I think it contains everything necessary. I just > unzipped it and > compiled it. No it doesn't. The hello module includes the minimal stuff necessary to build an L4 application. As stated in the BID tutorial, chapter 1, please checkout the L4Env module and compile it. Thereafter everythin should work fine. Regards, Bjoern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGZqeyP5ijxgQLUNkRAjA8AJwIMFk71NoJrdjeGEkyBKmA/gTtkACePNgF lXoytPeJXVrx+EJK6qN/kf4= =pOPl -----END PGP SIGNATURE-----

1 0

Hiworld Problem
by Marius.bao 06 Jun '07

06 Jun '07

Hi all, I followed the tutoral--<<Building Infrastructure for DROPS (BID) Tutorial>>(http://os.inf.tu-dresden.de/l4env/doc/html/bid-tut/node3.html) to wirte my fisrt "hiworld" server. I've used the template, ˜/src/l4/pkg/hiworld> ../../mk/tmpl/inst The "hiworld" source file is as follows: #include <stdio.h> int main(int argc, char** argv){ printf("HiWorld"); return 0; } An error occured when I compiled the server. I think it might be a link error. /usr/bin/ld: cannot find -lgeneric_ts ==> Linking hiworld LD_PRELOAD=/home/hector/Develop/L4-2007/l4/tool/gendep/libgendep.so GENDEP_TARGET=hiworld GENDEP_BINARY=ld gcc -o hiworld /home/hector/Develop/L4-2007/l4/build/lib/x86_586/crt0.o main.o -Ttext=0x01800000 -L/home/hector/Develop/L4-2007/l4/build/lib/x86_586/l4v2 -L/home/drops/lib/x86_586/l4v2 -L/home/hector/Develop/L4-2007/l4/build/lib/x86_586 -L/home/drops/lib/x86_586 -L/home/hector/Develop/L4-2007/l4/build/lib -L/home/drops/lib -T/home/hector/Develop/L4-2007/l4/build/lib/x86_586/main_stat.ld -static -lgeneric_ts -ll4env -ll4rm -ldm_generic -ldm_mem -lthread -lsemaphore -llogserver_capsule -lnames -ll4util_root -ll4util -lsigma0 -lroot -ll4env -ll4env_err -ll4rm -ldm_generic -ldm_mem -lthread -lslab -ll4sys -nostdlib -Wl,--nostdlib -luc_c -luclibc_support -u mmap_anon -lc_be_simple_mem -lc_be_mmap -lc_be_mmap_util -lc_be_l4env_start_stop -lc_be_minimal_log_io -luc_be_simple_sleep -ll4env -llogserver_capsule -ll4rm -ldm_generic -ldm_mem -lthread -lgeneric_ts -luc_c /usr/lib/gcc/i386-redhat-linux/3.4.2/libgcc.a -luc_c -ll4sys -Ttext=0x01800000 -Wl,--warn-common -Wl,-gc-sections /usr/bin/ld: cannot find -lgeneric_ts collect2: ld returned 1 exit status make[6]: *** [hiworld] error 1 make[6]: Leaving directory `/home/hector/Develop/L4-2007/l4/build/pkg/hiworld/server/src/OBJ-x86_586-l4v2' make[5]: *** [/home/hector/Develop/L4-2007/l4/build/pkg/hiworld/server/src/OBJ-x86_586-l4v2] error 2 make[5]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg/hiworld/server/src' make[4]: *** [src] error 2 make[4]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg/hiworld/server' make[3]: *** [server] error 2 make[3]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg/hiworld' make[2]: *** [hiworld.bin] error 2 make[2]: Leaving directory `/home/hector/Develop/L4-2007/l4/pkg' make[1]: *** [pkg] error 2 make[1]: Leaving directory `/home/hector/Develop/L4-2007/l4' make: *** [x] error 2 I wonder how to write the makefile myself without using the template. When I compile the "Hiworld" server, what other files(source files,head files) should I need to include.

2 1

PANIC
by Davide Fasoli 01 Jun '07

01 Jun '07

the problem was the vbeset command, i used the --vbemode=0x117 option in the con module and l4 booted correctly, thanks a lot for helping me. ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

PANIC
by Davide Fasoli 01 Jun '07

01 Jun '07

2 1

double page-fault
by Davide Fasoli 31 May '07

31 May '07

this is my bootloader setup for booting fiasco title Fiasco, Console, Loader, Tiny Shell (run) root (hd0,2) kernel /boot/fiasco_mod/bootstrap -modaddr 0x02000000 module /boot/fiasco_mod/fiasco -nowait -serial_esc -comspeed 115200 -comport 1 module /boot/fiasco_mod/sigma0 module /boot/fiasco_mod/roottask module /boot/fiasco_mod/names --events module /boot/fiasco_mod/log --events module /boot/fiasco_mod/dm_phys --isa=0x00800000 -v --events module /boot/fiasco_mod/con module /boot/fiasco_mod/simple_ts -t 300 --events module /boot/fiasco_mod/tftp #The loader should load and start the minishell module /boot/fiasco_mod/loader module /boot/fiasco_mod/run vbset 0x117 boot it returns me an error of Double Page Fault, how can i fix it? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

region overlap
by Davide Fasoli 30 May '07

30 May '07

Now it starts, but it gives me a "region overlap error", i've tryed searching something about it and i've seen that the modaddr command is not a grub command, how can i make things work in a grub bootloader? i've heard about a single-image mode, how can i make it work? thanks in advance, Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

3 2

Re: perf_p6 error
by Davide Fasoli 30 May '07

30 May '07

Hi, thanks the problem is resolved. Davide Fasoli ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

1 0

perf_p6 error
by Davide Fasoli 30 May '07

30 May '07

Compiling it gives me that error: make[3]: Entering directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples' test -f perf/broken -o -f perf/obsolete || \ if [ -f perf/Makefile ] ; then PWD=/home/fasoz/soa/tudos/l4/pkg/l4util/examples/perf make -C perf ; fi make[4]: Entering directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples/perf' PWD=/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2 make -C /home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2 -f Makefile make[5]: Entering directory `/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2' ==> Linking perf_p6 LD_PRELOAD=/home/fasoz/soa/tudos/l4/prova/tool/gendep/libgendep.so GENDEP_TARGET=perf_p6 GENDEP_BINARY=ld ld -o perf_p6 /home/fasoz/soa/tudos/l4/prova/lib/x86_586/crt0.o p6.o -Ttext=0xa00000 -L/home/fasoz/soa/tudos/l4/prova/lib/x86_586/l4v2 -L/home/fasoz/soa/tudos/l4/prova/lib/x86_586 -L/home/fasoz/soa/tudos/l4/prova/lib -L/home/drops/lib/x86_586/l4v2 -L/home/drops/lib/x86_586 -L/home/drops/lib -T/home/fasoz/soa/tudos/l4/prova/lib/x86_586/main_stat.ld -static -lmain -ll4util -ll4sys -nostdlib -luc_c -luc_be_minimal_io -luc_be_l4_start_stop -lc_be_sigma0_mem -luc_c -luclibc_support -ll4util -lsigma0 -luc_c /usr/lib/gcc/i486-linux-gnu/4.1.2/libgcc.a -luc_c -ll4sys -Ttext=0xa00000 --warn-common -gc-sections /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(vfprintf.o): In function `vfprintf': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/stdio/_vfprintf.c:1948: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(wcrtomb.o): In function `wcrtomb': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/wchar/wchar.c:365: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(wcsnrtombs.o): In function `wcsnrtombs': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/misc/wchar/wchar.c:917: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(_fpmaxtostr.o): In function `_fpmaxtostr': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/stdio/_fpmaxtostr.c:769: undefined reference to `__stack_chk_fail' /home/fasoz/soa/tudos/l4/prova/lib/x86_586/libuc_c.a(_ppfs_parsespec.o): In function `_ppfs_parsespec': /home/fasoz/soa/tudos/l4/prova/pkg/uclibc/lib/uclibc/ARCH-all/libc/stdio/_vfprintf.c:1155: undefined reference to `__stack_chk_fail' make[5]: *** [perf_p6] Error 1 make[5]: Leaving directory `/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2' make[4]: *** [/home/fasoz/soa/tudos/l4/prova/pkg/l4util/examples/perf/OBJ-x86_586-l4v2] Error 2 make[4]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples/perf' make[3]: *** [perf] Error 2 make[3]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg/l4util/examples' make[2]: *** [examples] Error 2 make[2]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg/l4util' make[1]: *** [l4util.bin] Error 2 make[1]: Leaving directory `/home/fasoz/soa/tudos/l4/pkg' make: *** [pkg] Error 2 what about that error? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 2

Re: multiple compilations
by Davide Fasoli 30 May '07

30 May '07

If i compile without "/home/fasoz/soa/tudos/kernel/fiasco/src/boot/ia32/boot.S" gcc -c -MD -MP -MF .boot.S.d.new -o boot.o -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -DASSEMBLER gcc: unrecognized option `-MP' gcc: unrecognized option `-MF' gcc: .boot.S.d.new: linker input file unused since linking not done but, if I use: g++ -c -MD -MP -MF .boot.S.d.new -o boot.o -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -DASSEMBLER /home/fasoz/soa/tudos/kernel/fiasco/src/boot/ia32/boot.S it compiles, where can I modify the makefile??? ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

Re: multiple compilations
by Davide Fasoli 28 May '07

28 May '07

----- Messaggio originale ----- Da: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> A: l4-hackers(a)os.inf.tu-dresden.de Inviato: Lunedì 28 maggio 2007, 13:21:55 Oggetto: Re: multiple compilations On Mon May 28, 2007 at 11:04:55 +0000, Davide Fasoli wrote: > On Mon May 28, 2007 at 09:15:43 +0200, Davide Fasoli wrote: > > I've installed fiasco following the step of the howto I've found > > here(http://os.inf.tu-dresden.de/fiasco/use.html) from > > this(http://os.inf.tu-dresden.de/drops/download.html) repository, i've > > tried following the hints you gave me but still no results. > > I'm sure you exactly followed the howto but again, what Linux > distribution are you using? > > Ubuntu 6.10; > > I'd also like to know which version of gcc, > > gcc 2.95.2 > gcc 3.3 > gcc 3.4 > gcc 4.1 > > binutils > > No > > and make > > make 3.81 Ok, thanks. Can please issue 'make -C /home/fasoz/soa/tudos/kernel/fiasco/build V=1' and post the output? The output is this: make: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 make[1]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' Checking compiler config... .Compiler-config is unchanged unchanged. make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all make[1]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' if [ -d /home/fasoz/soa/tudos/kernel/fiasco/src/.svn ]; then \ v=`svnversion -nc /home/fasoz/soa/tudos/kernel/fiasco/src`; v=${v%[A-Z]}; \ echo "#define CODE_VERSION \"r${v#*:}\"" > version.h; \ else \ echo "#define CODE_VERSION \"rUNKNOWN\"" > version.h; \ fi -e ... Making kip.o g++ -c -MD -MP -MF .kip.cc.d.new -o kip.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip.cc -e ... Making kip-ia32.o g++ -c -MD -MP -MF .kip-ia32.cc.d.new -o kip-ia32.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip-ia32.cc -e ... Making kip-debug.o g++ -c -MD -MP -MF .kip-debug.cc.d.new -o kip-debug.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip-debug.cc -e ... Making kip-ia32-debug.o g++ -c -MD -MP -MF .kip-ia32-debug.cc.d.new -o kip-ia32-debug.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -fno-implement-inlines -mpreferred-stack-boundary=2 -mregparm=3 -march=i586 -fno-defer-pop -freg-struct-return -g -Wall -W -Wformat=2 -ffunction-sections -fomit-frame-pointer -gstabs+ -fno-rtti -fno-exceptions -fno-threadsafe-statics -Wno-non-virtual-dtor -O2 --param large-function-insns=10000 -fweb auto/kip-ia32-debug.cc -e ==> Archiving into libabi.a rm -f libabi.a ar crs libabi.a kip.o kip-ia32.o kip-debug.o kip-ia32-debug.o l4_types.o l4_types-iofp.o l4_types-32bit.o l4_types-debug.o l4_types-caps.o utcb-ia32-ux.o -e ... Making boot.o gcc -c -MD -MP -MF .boot.S.d.new -o boot.o \ -nostdinc -I/home/fasoz/soa/tudos/kernel/fiasco/src/types/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/types -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/drivers -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern/shared -I/home/fasoz/soa/tudos/kernel/fiasco/src/kern -I/home/fasoz/soa/tudos/kernel/fiasco/src/boot -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk/ia32 -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/libk -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/kern/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/amm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/gzip -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/disasm -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/perfctr -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/regex -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/ia32/include -I/home/fasoz/soa/tudos/kernel/fiasco/src/lib/minilibc/include -I. -Iauto -I/usr/lib/gcc/i486-linux-gnu/4.1.2//include -DASSEMBLER /home/fasoz/soa/tudos/kernel/fiasco/src/boot/ia32/boot.S gcc: cannot specify -o with -c or -S and multiple compilations make[1]: *** [boot.o] Error 1 make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make: *** [all] Error 2 make: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > Thanks. > > > Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> ha scritto: Hi, > > > > On Fri May 25, 2007 at 13:47:33 +0200, Davide Fasoli wrote: > > > when running this command from shell > > > > > > make O=/home/fasoz/soa/tudos/l4/prova > > > > > > where /home/fasoz/soa/tudos/l4/prova is the installation directory of l4, I had the following text as output: > > > > > > ... > > > make -C build > > > make[2]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 > > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > Checking compiler config... unchanged. > > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all > > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > -e ... Making kip.o > > > -e ... Making kip-ia32.o > > > -e ... Making kip-debug.o > > > -e ... Making kip-ia32-debug.o > > > -e ==> Archiving into libabi.a > > > -e ... Ma king boot.o > > > gcc: cannot specify -o with -c or -S and multiple compilations > > > make[3]: *** [boot.o] Error 1 > > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make[2]: *** [all] Error 2 > > > make[2]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > > make[1]: *** [build] Error 2 > > > make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco' > > > make: *** [../kernel/fiasco] Error 2 > > > > > > I was wondering about what can cause this error, i spent something > > > like 15 days on this without coping on... could you please help me? I > > > need to install l4 for an exam... > > > > Just plain building the kernel with the default setup works just fine > > for me. Which distribution are you using? > > And build with more output with "make V=1". Doing this in the > > kernel/fiasco/build directory is sufficient. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers thanks ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

Re: multiple compilations
by Davide Fasoli 28 May '07

28 May '07

Hi, ----- Messaggio originale ----- Da: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> A: l4-hackers(a)os.inf.tu-dresden.de Inviato: Lunedì 28 maggio 2007, 11:43:35 Oggetto: Re: multiple compilations Hi, On Mon May 28, 2007 at 09:15:43 +0200, Davide Fasoli wrote: > I've installed fiasco following the step of the howto I've found > here(http://os.inf.tu-dresden.de/fiasco/use.html) from > this(http://os.inf.tu-dresden.de/drops/download.html) repository, i've > tried following the hints you gave me but still no results. I'm sure you exactly followed the howto but again, what Linux distribution are you using? Ubuntu 6.10; I'd also like to know which version of gcc, gcc 2.95.2 gcc 3.3 gcc 3.4 gcc 4.1 binutils No and make make 3.81 are you using, and I'd like to see the build done with V=1. Thanks. > Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> ha scritto: Hi, > > On Fri May 25, 2007 at 13:47:33 +0200, Davide Fasoli wrote: > > when running this command from shell > > > > make O=/home/fasoz/soa/tudos/l4/prova > > > > where /home/fasoz/soa/tudos/l4/prova is the installation directory of l4, I had the following text as output: > > > > ... > > make -C build > > make[2]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > Checking compiler config... unchanged. > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all > > make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > -e ... Making kip.o > > -e ... Making kip-ia32.o > > -e ... Making kip-debug.o > > -e ... Making kip-ia32-debug.o > > -e ==> Archiving into libabi.a > > -e ... Ma king boot.o > > gcc: cannot specify -o with -c or -S and multiple compilations > > make[3]: *** [boot.o] Error 1 > > make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' > > make[1]: *** [build] Error 2 > > make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco' > > make: *** [../kernel/fiasco] Error 2 > > > > I was wondering about what can cause this error, i spent something > > like 15 days on this without coping on... could you please help me? I > > need to install l4 for an exam... > > Just plain building the kernel with the default setup works just fine > for me. Which distribution are you using? > And build with more output with "make V=1". Doing this in the > kernel/fiasco/build directory is sufficient. > Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers Thanks. Davide ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

multiple compilations
by Davide Fasoli 28 May '07

28 May '07

I'm writing this mail about some problem i had during the l4 microkernel installation.. when running this command from shell make O=/home/fasoz/soa/tudos/l4/prova where /home/fasoz/soa/tudos/l4/prova is the installation directory of l4, I had the following text as output: ... make -C build make[2]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub1 make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' Checking compiler config... unchanged. make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make srcdir=/home/fasoz/soa/tudos/kernel/fiasco/src objbase=/home/fasoz/soa/tudos/kernel/fiasco/build -f /home/fasoz/soa/tudos/kernel/fiasco/src/Makefile.sub2 all make[3]: Entering directory `/home/fasoz/soa/tudos/kernel/fiasco/build' -e ... Making kip.o -e ... Making kip-ia32.o -e ... Making kip-debug.o -e ... Making kip-ia32-debug.o -e ==> Archiving into libabi.a -e ... Ma king boot.o gcc: cannot specify -o with -c or -S and multiple compilations make[3]: *** [boot.o] Error 1 make[3]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco/build' make[1]: *** [build] Error 2 make[1]: Leaving directory `/home/fasoz/soa/tudos/kernel/fiasco' make: *** [../kernel/fiasco] Error 2 I was wondering about what can cause this error, i spent something like 15 days on this without coping on... could you please help me? I need to install l4 for an exam... thanks in advance Davide Fasoli --------------------------------- L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail

2 4

Can we install L4 on a "bare machine"?
by Marius.bao 26 May '07

26 May '07

Hi everybody, I have installed L4 under Linux successfully. Now I wonder can we install L4 on a "bare machine"--a computer which haven't installed any OS at all. If we can, then how to install it. If not, what extra job should I do to make it possible. As I'm thinking of that L4 is just a microkernel, it hasn't got a filesystem, if we want to install it on a "bare machine", how shall we manage the files.

2 1

Re: The boot error of L4Linux
by chenggh 24 May '07

24 May '07

On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > Hi: > > > When I boot the L4Linux there are some errors. In this mail there are > > > 2 attachments of linux26.cfg, grub configuration and boot log. Please > > > help me to check the boot log. > > > > The new boot log is as following: > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > 0x000 > > l4lx : 04000) > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > You probably need 'allow_vga' in your l4linux loader configuration file. The error is same when I add the "allow_vga" in linux26.cfg like this: modpath "(hd0,1)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M root=/dev/hda2" all_sects_writable allow_vga The boot log is : names | Starting threaistening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:17:44:03 DMphys | DMphys memory ap: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPhys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x000x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Wed Ma l4lx : y 23 16:40:01 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b7480 [429kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread wiection: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for mai memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x0E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thanks. cheng

1 0

Re: The boot error of L4Linux
by Christian Helmuth 24 May '07

24 May '07

Hi, On Thu, May 24, 2007 at 03:24:07PM +0000, chenggh wrote: > The error is same when I add the "allow_vga" in linux26.cfg like this: Any news since you followed Adam's suggestion (use one line per option)? If you were successful, the readers of this ML would benefit from your experiences. Cheers -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12

1 0

Re: The boot error of L4Linux
by chenggh 23 May '07

23 May '07

On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > Hi: > > > When I boot the L4Linux there are some errors. In this mail there are > > > 2 attachments of linux26.cfg, grub configuration and boot log. Please > > > help me to check the boot log. > > > > The new boot log is as following: > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > 0x000 > > l4lx : 04000) > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > You probably need 'allow_vga' in your l4linux loader configuration file. The error is same when I add the "allow_vga" in linux26.cfg like this: modpath "(hd0,1)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M root=/dev/hda2" all_sects_writable allow_vga The boot log is : names | Starting threaistening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:17:44:03 DMphys | DMphys memory ap: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPhys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x000x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Wed Ma l4lx : y 23 16:40:01 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b7480 [429kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread wiection: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for mai memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x0E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thanks. cheng

1 0

Re: The boot error of L4Linux
by chenggh 23 May '07

23 May '07

On Tuesday 22 May 2007 10:40, chenggh wrote: > Hi: > When I boot the L4Linux there are some errors. In this mail there are 2 > attachments of linux26.cfg, grub configuration and boot log. Please help me > to check the boot log. The new boot log is as following: names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:09:29:11 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPED DMphys | 0x00106000-0x00107000 -- -- DENIED DMphys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x009d6000-0x00b80000 ( 1704KB, 2MB) free DS: DMphys | 0x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Mon Ma l4lx : y 21 13:54:26 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b73a0 [428kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread will be 0e.04 l4lx | l4env_register_pointer_section: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thank you. cheng

1 0

RE: The boot error of L4Linux
by Clermont, Nicolas 23 May '07

23 May '07

Hi maybe adding the 'allow_cli' option in your l4linux.cfg ? -----Message d'origine----- De : l4-hackers-bounces(a)os.inf.tu-dresden.de [mailto:l4-hackers-bounces@os.inf.tu-dresden.de] De la part de chenggh Envoyé : mercredi 23 mai 2007 19:39 À : l4-hackers(a)os.inf.tu-dresden.de Objet : Re: The boot error of L4Linux On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > Hi: > > > When I boot the L4Linux there are some errors. In this mail there > > > are > > > 2 attachments of linux26.cfg, grub configuration and boot log. > > > Please help me to check the boot log. > > > > The new boot log is as following: > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > 0x000 > > l4lx : 04000) > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > l4lx | unhandled page fault > > You probably need 'allow_vga' in your l4linux loader configuration file. The error is same when I add the "allow_vga" in linux26.cfg like this: modpath "(hd0,1)/boot/L4Linux" task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M root=/dev/hda2" all_sects_writable allow_vga The boot log is : names | Starting threaistening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:17:44:03 DMphys | DMphys memory ap: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPhys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x000x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Wed Ma l4lx : y 23 16:40:01 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b7480 [429kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread wiection: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for mai memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x0E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thanks. cheng _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

2 1

Re: The boot error of L4Linux
by Adam Lackorzynski 23 May '07

23 May '07

On Wed May 23, 2007 at 17:39:09 +0000, chenggh wrote: > On Wednesday 23 May 2007 08:46, Adam Lackorzynski wrote: > > On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > > > On Tuesday 22 May 2007 10:40, chenggh wrote: > > > > Hi: > > > > When I boot the L4Linux there are some errors. In this mail there are > > > > 2 attachments of linux26.cfg, grub configuration and boot log. Please > > > > help me to check the boot log. > > > > > > The new boot log is as following: > > > > > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > > > 0x000 > > > l4lx : 04000) > > > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > > > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > > > l4lx | unhandled page fault > > > > You probably need 'allow_vga' in your l4linux loader configuration file. > The error is same when I add the "allow_vga" in linux26.cfg like this: > > modpath "(hd0,1)/boot/L4Linux" > task "vmlinuz26" "earlyprintk=yes console=ttyS1,115200 init=3 mem=64M > root=/dev/hda2" > all_sects_writable allow_vga Please give each option its own line: all_sects_writable allow_vga Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: The boot error of L4Linux
by chenggh 23 May '07

23 May '07

On Tuesday 22 May 2007 10:40, chenggh wrote: > Hi: > When I boot the L4Linux there are some errors. In this mail there are 2 > attachments of linux26.cfg, grub configuration and boot log. Please help me > to check the boot log. The new boot log is as following: names | Starting thread listening for `exit' events simplets| Configured for 300 tasks. rtc | Date:23.05.2007 Time:09:29:11 DMphys | DMphys memory map: DMphys | phys. memory 0x00000000-0x0dff0000 (from L4 kernel info page) DMphys | using 0x00100000-0x0dff0000 DMphys | Memory area Pool PS Flags DMphys | 0x00000000-0x00100000 -- -- RESERVED DMphys | 0x00100000-0x00106000 7 12 MAPPED DMphys | 0x00106000-0x00107000 -- -- DENIED DMphys | 0x00107000-0x00136000 7 12 MAPPED DMphys | 0x00136000-0x001be000 -- -- DENIED DMphys | 0x001be000-0x002d0000 7 12 MAPPED DMphys | 0x002d0000-0x002e3000 -- -- DENIED DMphys | 0x002e3000-0x00400000 7 12 MAPPED DMphys | 0x00400000-0x0043a000 -- -- DENIED DMphys | 0x0043a000-0x009d6000 7 12 MAPPED DMphys | 0x009d6000-0x00b80000 0 12 MAPPED DMphys | 0x00b80000-0x00c14000 -- -- DENIED DMphys | 0x00c14000-0x01080000 0 12 MAPPED DMphys | 0x01080000-0x0108a000 -- -- DENIED DMphys | 0x0108a000-0x01220000 0 12 MAPPED DMphys | 0x01220000-0x01257000 -- -- DENIED DMphys | 0x01257000-0x01300000 0 12 MAPPED DMphys | 0x01300000-0x01350000 -- -- DENIED DMphys | 0x01350000-0x01400000 0 12 MAPPED DMphys | 0x01400000-0x0141c000 -- -- DENIED DMphys | 0x0141c000-0x01500000 0 12 MAPPED DMphys | 0x01500000-0x0151c000 -- -- RESERVED DMphys | 0x0151c000-0x01540000 0 12 MAPPED DMphys | 0x01540000-0x01560000 -- -- DENIED DMphys | 0x01560000-0x01800000 0 12 MAPPED DMphys | 0x01800000-0x06400000 0 22 MAPPED DMphys | 0x06400000-0x06720000 0 12 MAPPED DMphys | 0x06720000-0x0798d000 -- -- DENIED DMphys | 0x0798d000-0x07c00000 0 12 MAPPED DMphys | 0x07c00000-0x0cc00000 0 22 MAPPED DMphys | 0x0cc00000-0x0cd2c000 0 12 MAPPED DMphys | 0x0cd2c000-0x0dff0000 -- -- DENIED DMphys | DMphys | DMphys memory pools: DMphys | pool 0 (Default memory pool): DMphys | size: 179632KB total, 179632KB free, 32KB reserved DMphys | 0x009d6000-0x00b80000 ( 1704KB, 2MB) free DS: DMphys | 0x00c14000-0x01080000 ( 4528KB, 4MB) free DS: DMphys | 0x0108a000-0x01220000 ( 1624KB, 2MB) free DS: DMphys | 0x01257000-0x01300000 ( 676KB, 1MB) free DS: DMphys | 0x01350000-0x01400000 ( 704KB, 1MB) free DS: DMphys | 0x0141c000-0x01500000 ( 912KB, 1MB) free DS: DMphys | 0x0151c000-0x01540000 ( 144KB, 0MB) free DS: DMphys | 0x01560000-0x06720000 ( 83712KB, 82MB) free DS: DMphys | 0x0798d000-0x0cd2c000 ( 85628KB, 84MB) free DS: DMphys | pool 7 (ISA DMA memory pool): DMphys | size: 8192KB total, 8192KB free, 0KB reserved DMphys | 0x00100000-0x00106000 ( 24KB, 0MB) free DS: DMphys | 0x00107000-0x00136000 ( 188KB, 0MB) free DS: DMphys | 0x001be000-0x002d0000 ( 1096KB, 1MB) free DS: DMphys | 0x002e3000-0x00400000 ( 1140KB, 1MB) free DS: DMphys | 0x0043a000-0x009d6000 ( 5744KB, 6MB) free DS: io | do_args(): Disabling internal IRQ handling. io | do_args(): Enabling events support. io | CPU supports 8 MTRRs. Allocated: io | 0: 00000000-08000000 ( 128MB) type WB io | 1: 08000000-0c000000 ( 64MB) type WB io | 2: 0c000000-0e000000 ( 32MB) type WB io | 3: d0000000-d8000000 ( 128MB) type WC io | 4: d8000000-d8800000 ( 8MB) type WC bmodfs | Passed the following modules: bmodfs | module "/boot/L4Linux/vmlinuz26" (17684kB) bmodfs | module "/boot/L4Linux/linux26.cfg" (1kB) bmodfs | module "/boot/L4Linux/libloader.s.so" (670kB) bmodfs | module "/boot/L4Linux/libld-l4.s.so" (505kB) io | PCI: Using configuration type 1 io | PCI: Probing PCI hardware io | PCI: Probing PCI hardware (bus 00) io | PCI: Via IRQ fixup io | PCI: Via IRQ fixup io | 00000000-ffffffff : PCI mem io | d0000000-d7ffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io | d8000000-dbffffff : PCI Bus #01 io | d8000000-dbffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | dc000000-ddffffff : PCI Bus #01 io | dc000000-dcffffff : VIA Technologies, Inc. VT8623 [Apollo CLE266] io : integrated CastleRock graphics io | de000000-de0000ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | de001000-de0010ff : VIA Technologies, Inc. USB 2.0 io | de002000-de0020ff : VIA Technologies, Inc. VT6102 [Rhine-II] io | 0000-ffff : PCI IO io | 0cf8-0cff : PCI conf1 io | d000-d0ff : VIA Technologies, Inc. VT6105 [Rhine-III] io | d400-d41f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r io | d800-d81f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#2) io | dc00-dc1f : VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controlle io : r (#3) io | e000-e00f : VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/ io : A/C PIPC Bus Master IDE io | e400-e4ff : VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Co io : ntroller io | e800-e8ff : VIA Technologies, Inc. VT6102 [Rhine-II] loader | vmlinuz26: Starting application using libld-l4.s.so loader | vmlinuz26,#e: Loading binary loader | vmlinuz26,#e: Loading ldso loader | Capability support not enabled. loader | vmlinuz26,#e: Starting libld-l4.s.so at 00013ea0 via 0000cf44 l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.21-l4 (root@darkstar) (gcc version 3.3.6) #1 Mon Ma l4lx : y 21 13:54:26 CST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (5 args): earlyprintk=yes console=ttyS1,115200 in l4lx : it=3 mem=64M root=/dev/hda2 l4lx | Image: 00400000 - 007ba000 [3816 KiB]. l4lx | Areas: Text: 00400000 - 006e9000 [2980kB] (a bit longer) l4lx | Data: 006e9000 - 007092cc [128kB] l4lx | Initdata: 0070c000 - 007490a0 [244kB] l4lx | BSS: 0074c000 - 007b73a0 [428kB] l4lx | l4lx_thread_create: Created thread 0e.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0e.04 (server) l4lx | main thread will be 0e.04 l4lx | l4env_register_pointer_section: addr = 006e9000 size = 401408 l4lx | sec-w-init: virt: 0x006e9000 to 0x0074afff [392 KiB] l4lx | sec-w-init: Number of physical regions: 1, 401408 Bytes l4lx | sec-w-init: 1: Phys: 0x01161000 to 0x011c3000, Size: 401408 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 64MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x04bfffff [65536 KiB] l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes l4lx | Main memory: 1: Phys: 0x08c00000 to 0x0cc00000, Size: 67108864 l4lx | Filling lower ptabs... l4lx | Done (1473 entries). l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result 0x000 l4lx : 04000) l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault Thank you. cheng

1 0

Re: The boot error of L4Linux
by Adam Lackorzynski 23 May '07

23 May '07

On Wed May 23, 2007 at 09:21:11 +0000, chenggh wrote: > On Tuesday 22 May 2007 10:40, chenggh wrote: > > Hi: > > When I boot the L4Linux there are some errors. In this mail there are 2 > > attachments of linux26.cfg, grub configuration and boot log. Please help me > > to check the boot log. > The new boot log is as following: > > l4lx | L4RM: no fpage received (page fault -- asked pager C.03, result > 0x000 > l4lx : 04000) > l4lx | L4RM: [PF] read at 0x000a0000, ip 00000000, src E.04 > l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > l4lx | unhandled page fault You probably need 'allow_vga' in your l4linux loader configuration file. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

RE: [NITPICKER] Porting X.org 1.1.1 to use NitPicker
by Clermont, Nicolas 22 May '07

22 May '07

Hi Norman, > Hi Nicolas, > > I managed to reproduce your issue with the non-working refresh of the > X11 windows with Xorg of the latest Debian unstable. The problem was > an API change of the shadowfb Module of Xorg from version 7.0 to the current version. I updated the drivers ovlscreen_drv.so and lxevent_drv.so in: > > overlay_wm/examples/xf86screen/ and > overlay_wm/examples/xf86input/ Wondeful ! Thanks a lot Norman, I was going to test your proposed solutions (just coming back from holiday). I'll update from Dresden svn and have a try of your updates to see if all work for me. > Frank Mehnert's up-to-date PSLIM driver in 'l4con/examples/xf86_stub' > was a very good reference for finding the problem. The updated drivers > should be available at our public SVN repository soon. Thanks for the tip, I will have a look. > > So we have started with a Linux installation (Gentoo Linux), after > > what we have installed Fiasco, L4Env and L4Linux (2.6.20, next > > 2.6.21, on top on our recently installed Gentoo, reusing its > > filesystem). To test our installation, we first use L4Con, but the > > mouse moves were extremely slow; so next we use DOpE, and it was > > cool, all worked (network and hard disk via L4Linux, not Ore... Oh > > is there exist a multiplexer, as Ore, for hard disk ?). But of > > course, the desktop-in-window aproach does > > To my knowledge, there is no hard-disk multiplexer available. Maybe my next step ... ;) > > not fully satisfied us, we want a fullscreen aproach so we start > > investigating on NitPicker. > > > > The problem is that all tutorials related to NitPicker + X.org are > > based on a quite-old version of X.org, before the X.org team adopted > > the modular approach. So we decide to port the last X.org (1.1.1) to > > use NitPicker, following instructions found at > > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002774.html > > > > First we compiled the nitpicker-client ovlwm server, nitovlwm. Then > > we install into the L4Linux the lxevent program, started after Linux > > kernel boot, with creation of /dev/lxevent, and the ovltrack > > program, started via .xinitrc. We had to change a little the > > Makefile of ovltrack by adding the -Bdynamic option in LIBS. We > > compiled and generated lxevent_drv.o (X.org mouse driver in > > xorg.conf). The last step was generating the X.org screen driver, > > ovlscreen_drv.o. The changes toward previous versions occurs at this > > step, as now X.org is modular and consists in several small > > packages. But after resolving a lot of include path problems, > > importing the needed X.org package to compile the driver, we got the > > driver ovlscreen_drv.o compiled and copy it into the L4Linux filesystem, modifying xorg.conf to use this driver. > > Also we use NitDope, so L4fb driver in L4Linux that creates /dev/fb0. > > I am amazed of how far you went on your own without even asking one > question. Respect! :-) Good luck with the updated drivers. > > Best regards > Norman Thanks Norman, it makes me great pleasure to read this from you (respect for your job, be it NitPicker, DOpE, Bastei, ... That's amazing ! ;)). Also thanks for your help and your time. I have no doubt that the updated drivers will work for me (I'll confirme you as soon as I have all the stuff working). Best regards, Nicolas

1 0

The boot error of L4Linux
by chenggh 22 May '07

22 May '07

Hi: When I boot the L4Linux there are some errors. In this mail there are 2 attachments of linux26.cfg, grub configuration and boot log. Please help me to check the boot log. Thank you. cheng

2 1

What is the modifications of latest L4 packages?
by chenggh 21 May '07

21 May '07

Hi: Several months ago I downloaded the l4 packages which are much more packages than them now. This was the snapshot of l4 pkg directory several months ago. In total there are 100 directories. COPYING dm_generic/ input/ linux-24-headers/ oskit_support_l4env/ slab/ CVS/ dm_mem/ ipreg/ linux-26-headers/ overlay_wm/ socket_linux/ Makefile dm_phys/ l4con/ loader/ pci/ stepper_motor/ arm_drivers/ dmon/ l4env/ local_socks/ petze/ tftp/ bootstrap/ dope/ l4ide/ lock/ pingpong/ thread/ c++-examples/ dsi/ l4io/ log/ presenter/ thread_linux/ cpu_reserve/ dsi_example/ l4rm/ log_net/ proxygon/ uclibc/ crtx/ dsi_staticfs/ l4sys/ lxfuxlibc/ qt3/ uclibc++/ cxx/ events/ l4util/ names/ rmgr/ uclibc_r/ cxx_linux_io/ exec/ l4vfs/ nethub/ roottask/ verner/ cxx_log_io/ flips/ ldso/ nitpicker/ rt_mon/ x86emu/ dde_linux/ generic_blk/ libc_backends_l4env/ omega0/ rtc/ zlib/ dde_linux26/ generic_fprov/ libc_support/ ore/ semaphore/ demangle/ generic_io/ libpng/ oskit10_support/ serial/ dice_hello/ generic_ts/ libsigma0/ oskit10_support_l4env/ sigma0/ dietlibc/ hello/ libstdc++/ oskit10_support_l4env_full/ signal/ dietlibc_r/ hello_cxx/ libvfb/ oskit_support/ simple_ts/ But now there are only 47 directories as following: COPYING dm_generic/ generic_fprov/ l4io/ libc_backends_l4env/ log/ roottask/ slab/ zlib/ Makefile dm_mem/ generic_io/ l4rm/ libc_support/ lxfuxlibc/ rtc/ tftp/ bootstrap/ dm_phys/ generic_ts/ l4sys/ libsigma0/ names/ semaphore/ thread/ crtx/ dope/ input/ l4util/ linux-24-headers/ omega0/ serial/ uclibc/ cxx/ events/ l4con/ ldso/ loader/ pci/ sigma0/ uclibc_r/ demangle/ generic_blk/ l4env/ libc_backends/ lock/ proxygon/ simple_ts/ x86emu/ What is the modifications of L4 architectures and what is the aim ? But there is no new version of Fiasco to be published. Thanks. cheng

1 0

Re: What is the modifications of latest L4 packages?
by Adam Lackorzynski 21 May '07

21 May '07

On Mon May 21, 2007 at 21:17:00 +0000, chenggh wrote: > Several months ago I downloaded the l4 packages which are much more packages > than them now. > This was the snapshot of l4 pkg directory several months ago. In total there > are 100 directories. We have removed packages that are obsolete and not needed anymore, like the oskit* packages. > But now there are only 47 directories as following: There are 83 directories in l4/pkg in the svn. You can check out everything if you like. > What is the modifications of L4 architectures and what is the aim ? But We're working on the project and things evolve and change, new packages come, old packages go. > there is no new version of Fiasco to be published. Not today. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by Adam Lackorzynski 21 May '07

21 May '07

On Sun May 20, 2007 at 10:15:13 +0000, chenggh wrote: > On Saturday 19 May 2007 10:06, Stefan Kalkowski wrote: > > On Saturday 19 May 2007 12:01, chenggh wrote: > > > Hi: > > > Now I have the new problem. the make menuconfig is ok but when i make > > > the kernel there are some problems like this: > > > > > > root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ > > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > > determine L4 source directory. Configuration missing?. Stop. > > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > > determine L4 source directory. Configuration missing?. Stop. > > > > as one can read, you didn't configure your kernel correctly. You have to > > specify your L4 source tree when configuring L4Linux. Lately, that's what > > the one error message above says to you. > No, it is not my error of configuration but the system warning which is an > error itself. When I make menuconfig there also is the same error. So the > most important error is second one : > make[1]: *** No rule to make target > `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by > `archprepare'. Stop. > make: *** [_all] Error 2 I have modified a few things in this area now, hope it's better. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by chenggh 20 May '07

20 May '07

On Sunday 20 May 2007 10:15, you wrote: > On Saturday 19 May 2007 10:06, Stefan Kalkowski wrote: > > On Saturday 19 May 2007 12:01, chenggh wrote: > > > Hi: > > > Now I have the new problem. the make menuconfig is ok but when i make Sorry, It is my fault. Now it is ok Thank you very much. cheng

1 0

Re: Kernel configuration missing ?
by chenggh 20 May '07

20 May '07

On Saturday 19 May 2007 10:06, Stefan Kalkowski wrote: > On Saturday 19 May 2007 12:01, chenggh wrote: > > Hi: > > Now I have the new problem. the make menuconfig is ok but when i make > > the kernel there are some problems like this: > > > > root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > determine L4 source directory. Configuration missing?. Stop. > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > determine L4 source directory. Configuration missing?. Stop. > > as one can read, you didn't configure your kernel correctly. You have to > specify your L4 source tree when configuring L4Linux. Lately, that's what > the one error message above says to you. No, it is not my error of configuration but the system warning which is an error itself. When I make menuconfig there also is the same error. So the most important error is second one : make[1]: *** No rule to make target `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [_all] Error 2 Do you use the l4linux-2.6.20 or l4linux-2.6.21 ?. I have ever used l4linux-2.6.1x and they have no problems. But when I use l4linux-2.6.20 or l4linux-2.6.21 they have many problems. > > GEN /home/L4/tudos/l4linux-2.6.20/build/Makefile > > HOSTLD scripts/kconfig/conf > > scripts/kconfig/conf -s arch/l4/Kconfig > > /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not > > determine L4 source directory. Configuration missing?. Stop. > > make[1]: *** No rule to make target > > `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by > > `archprepare'. Stop. > > make: *** [_all] Error 2

1 0

9th Real Time Linux Workshop, Linz, Austria, Nov 2-4 2007
by Nicholas Mc Guire 20 May '07

20 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 9th Real-Time Linux Workshop November 2-4, 2007 Institute for Measurement Technology Johannes Kepler University of Linz CALL FOR PAPERS General Following the meetings of developers and users at the previous 8 successful real-time Linux workshops held in Vienna, Orlando, Milano, Boston, and Valencia, Singapur, Lille, and Lanzhou the Real-Time Linux Workshop for 2007 will come back to Europa, to be held at the Institute for Measurement Technology, Johannes Kepler University of Linz, Austria. Embedded and real-time Linux is continuously growing player in the embedded appliance market world wide. Embedded systems in automation control, measurement and multimedia have been continuously moving towards 32bit systems, opening the door for the use of full featured OS like GNU/Linux on COTS based systems. With real-time capabilities being a common demand for embedded systems the soft and hard real-time variants are an important extension to the versatile GNU/Linux GPOS. Authors are invited to submit original work dealing with general topics related to real-time Linux research, experiments and case studies, as well as issues of integration of real-time and embedded Linux. A special focus will be on industrial case studies. Topics of interest include, but are not limited to: * Modifications and variants of the GNU/Linux operating system extending it's real-time capabilities * Contributions to real-time Linux variants, drivers and extensions. * User-mode real-time concepts, implementation and experience * Real-time Linux applications, in academia, research and industry * Real-time Linux in measurement and data-aquisition systems * Signal processing with Linux/real-time Linux. * Work in progress reports, covering recent developments * Educational material on real-time Linux. * Tools for embedding Linux or real-time Linux and embedded real-time Linux applications * RTOS core concepts, RT-safe synchronization mechanisms * Analysis and Benchmarking methods and results of real-time GNU/Linux variants. * Debugging techniques and tools, both for code and temporal debugging of core RTOS components, drivers and real-time applications * Real-time realted extensions to development environments * RT-Linux in safety-critical systems Registration In order to participate to the workshop, please register on the Registration Page at: http://www.realtimelinuxfoundation.org/events/events.html Venue: Johannes Kepler University,Linz, Austria http://www.realtimelinuxfoundation.org/events/ws-2007/venue.html Accommodation: http://www.realtimelinuxfoundation.org/events/ws-2007/hotels.html Important dates: August 11, 2007 Abstract submission September 15, 2007 Notification of acceptance October 13, 2007 Final paper Nov 2-3 Workshop Organization committee: * Prof. Bernhard ZAGAR, (JKU, AUSTRIA) * Prof. Li LIAN , (LZU, CHINA) * Dr. Peter WURMSDOBLER , (RTLF, USA) * Prof. Nicholas MCGUIRE , (LZU, CHINA) Program committee: Prof. Dr. Bernhard Zagar (Johannes Kepler Universit�t Linz, AUSTRIA) Prof. Li Lian (SISE, Lanzhou University, CHINA) Prof. Dr. Paolo Mantegazza (Dipartimento di Ingegneria Aerospaziale, ITALY) Prof. Dr. Alfons Crespo (Universidad Polit�cnica de Valencia,SPAIN) Prof. Dr. Ismael Ripoll (Universidad Polit�cnica de Valencia,SPAIN) Ing. Pavel Pisa (Czech Technical University, CZECH REPUBLIC) Dr. Miguel Masmano Tello (Universidad Polit�cnica de Valencia,SPAIN) Dr. Zhang Feng, Director of Mobile OS Lab (LCR Lenovo, CHINA) Prof. Hanzalek Zdenek (Czech Technical University, CZECH REPUBLIC) Ing. Michael Rumpler (Thales Group, AUSTRIA) Ing. Philippe Gerum (ADEOS Maintainer, Xenomai, FRANCE) Prof. Xing Li (Tsinghua University, CERNET Center,CHINA) Prof. Hongan Wang (Institute of Software, Intelligence Engineering Lab, Chinese Academy of Sciences, CHINA) Dr. Chen Maoke, (Tsinghua University, CHINA) Dr. Chen Yu, (Tsinghua University, CHINA) Dr. Bin Hu, (Computing Department of Computing, Business School, University of Central England,UNITED KINGDOM) Dr. Lei Wang, (School of Computer Science,Beijing University of Aeronautics and Astronautics,CHINA) Prof. Roberto Bucher (University of Applied Sciences of Southern Switzerland Dept. Innovative Technologies, SWITZERLAND) Ing. Klaus Reichl (Thales Group, AUSTRIA) Dr. Don W. Carr (Universidad de Guadalajara, Guadalajara, MEXICO) Thomas Gleixner (Linutronix, RT-Preempt, GERMANY) Tim Bird (Sony, USA) Ing. Christoph Stueckjuergen (Siemens CT SE 2, GERMANY) Prof. Marting Terbuc (University of Maribor, SLOVENIA) Prof. Matthias Sturm (University of Leibzig, GERMANY) Prof. Ahmet Onat (Sabanci University, TURKEY) Dr. Qingguo ZHOU (DSLab, Lanzhou University, CHINA) Dr. Peter Wurmsdobler (Real Time Linux Foundation, USA) Prof. Nicholas Mc Guire (DSLAb, Lanzhou University, CHINA) Workshop organizers: * Institute for Measurement Technology ,Johannes Kepler University of Linz Austria http://www.emt.uni-linz.ac.at/ * Real-Time Linux Foundation Inc. USA http://www.realtimelinuxfoundation.org * School for Information Science and Engineering (SISE), University of Lanzhou China http://www.lzu.edu.cn * Distributed and Embedded Systems Lab, University of Lanzhou, China http://dslab.lzu.edu.cn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFGT9ASnU7rXZKfY2oRAiKDAKCcVjEgdbRzBoaBkDPaElwqHS7QggCfWdMA au/utUVnuxyHPoVX03jdK1k= =5T3L -----END PGP SIGNATURE-----

1 0

[NITPICKER] Porting X.org 1.1.1 to use NitPicker
by Clermont, Nicolas 19 May '07

19 May '07

Hi everybody, We are working on L4, currently especially on the graphical aspect. As we love NitPicker (NitPicker is cool ;)), we want to use it to run L4Linux on top on it. So we have started with a Linux installation (Gentoo Linux), after what we have installed Fiasco, L4Env and L4Linux (2.6.20, next 2.6.21, on top on our recently installed Gentoo, reusing its filesystem). To test our installation, we first use L4Con, but the mouse moves were extremely slow; so next we use DOpE, and it was cool, all worked (network and hard disk via L4Linux, not Ore... Oh is there exist a multiplexer, as Ore, for hard disk ?). But of course, the desktop-in-window aproach does not fully satisfied us, we want a fullscreen aproach so we start investigating on NitPicker. The problem is that all tutorials related to NitPicker + X.org are based on a quite-old version of X.org, before the X.org team adopted the modular approach. So we decide to port the last X.org (1.1.1) to use NitPicker, following instructions found at http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002774.html <http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002774.html> First we compiled the nitpicker-client ovlwm server, nitovlwm. Then we install into the L4Linux the lxevent program, started after Linux kernel boot, with creation of /dev/lxevent, and the ovltrack program, started via .xinitrc. We had to change a little the Makefile of ovltrack by adding the -Bdynamic option in LIBS. We compiled and generated lxevent_drv.o (X.org mouse driver in xorg.conf). The last step was generating the X.org screen driver, ovlscreen_drv.o. The changes toward previous versions occurs at this step, as now X.org is modular and consists in several small packages. But after resolving a lot of include path problems, importing the needed X.org package to compile the driver, we got the driver ovlscreen_drv.o compiled and copy it into the L4Linux filesystem, modifying xorg.conf to use this driver. Also we use NitDope, so L4fb driver in L4Linux that creates /dev/fb0. Then we boot our L4-based system, NitPicker, NitDOpE and L4Linux, all start, all was right. The problems come when starting X.org. Indeed, X.org started, the window manager also (WindowMaker), in fact all works... excepts refresh ! Indeed when moving the mouse on a L4Linux window, the window content is not refreshed, resulting in an unusable window. But clicking outside the window forces the refresh. We know that with DOpE, the refresh is automatic, periodic and so it was working for us. But with NitPicker, we know that the refresh only occurs if a change is made in the client. What we don't know is how this refresh is done, who is responsible for it (ovlscreen, ovltrack, nitovlwm ?), and which are the impacts of using a modular X.org in this process.... Is someone can give us some tips on how to make the refresh to occur ? Or details about event forwarding ? Is there other changes to be made that we missed ? Any help will be grateful appreciated. Thanks. -- Nicolas Clermont

2 2

Re: Kernel configuration missing ?
by chenggh 19 May '07

19 May '07

Hi: Now I have the new problem. the make menuconfig is ok but when i make the kernel there are some problems like this: root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. GEN /home/L4/tudos/l4linux-2.6.20/build/Makefile HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s arch/l4/Kconfig /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. make[1]: *** No rule to make target `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [_all] Error 2 It seems the process of making l4linux-2.6.20 is very different from the process of making linux-2.6.20. What is the problem ? strange warning. strange error. cheng

2 1

Re: Kernel configuration missing ?
by chenggh 18 May '07

18 May '07

Hi: Now I have the new problem. the make menuconfig is ok but when i make the kernel there are some problems like this: root@darkstar:/home/L4/tudos/l4linux-2.6.20# make O=./build/ /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. GEN /home/L4/tudos/l4linux-2.6.20/build/Makefile HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s arch/l4/Kconfig /home/L4/tudos/l4linux-2.6.20/arch/l4/Makefile.l4conf:24: *** Could not determine L4 source directory. Configuration missing?. Stop. make[1]: *** No rule to make target `/home/L4/tudos/l4linux-2.6.20/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [_all] Error 2 It seems the process of making l4linux-2.6.20 is very different from the process of making linux-2.6.20. What is the problem ? strange warning. strange error. cheng

1 0

Re: Kernel configuration missing ?
by chenggh 18 May '07

18 May '07

> > I use the slackware 10.2 with make 3.80 and gcc 3.3.6. What version are > > you using? Maybe I need to update the make. > > With 3.80 it breaks for me as well, 3.81 works. I need to do something > about this anyway, so let me see... Thank you , Adam. I update the make in my machine to 3.81. Now it is ok. cheng

1 0

Re: Kernel configuration missing ?
by Adam Lackorzynski 18 May '07

18 May '07

On Fri May 18, 2007 at 08:06:04 +0000, chenggh wrote: > > HOSTCC scripts/kconfig/lxdialog/checklist.o > > .. > > l4linux-2.6$ make O=./build/ > > L4 source directory: /path/to/l4 > > make -C /path/to/l4 -f .../l4linux-2.6/arch/l4/Makefile.l4conf > > O=/path/to/l4-obj-dir L4X_LOOP_CHECK=1 > > OUTPUT=.../l4linux-2.6/build/Makeconf.l4conf GEN > > l4linux-2.6/build/Makeconf.l4conf > > GEN l4linux-2.6/build/Makefile > > HOSTLD scripts/kconfig/conf > > scripts/kconfig/conf -s arch/l4/Kconfig > > Creating asm-l4/api-l4env -> asm/api symlink > > Creating asm-l4/l4lxapi/impl symlink > > Creating asm-l4/l4x-i386 -> asm/l4x symlink > > .. > > > > As said, I'll try to fix the error message inbetween. > > > > Maybe it's the make version. Which version are you using? > > root@darkstar:~# make --version > GNU Make 3.80 > Copyright (C) 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > > I use the slackware 10.2 with make 3.80 and gcc 3.3.6. What version are you > using? Maybe I need to update the make. With 3.80 it breaks for me as well, 3.81 works. I need to do something about this anyway, so let me see... Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by chenggh 18 May '07

18 May '07

> HOSTCC scripts/kconfig/lxdialog/checklist.o > .. > l4linux-2.6$ make O=./build/ > L4 source directory: /path/to/l4 > make -C /path/to/l4 -f .../l4linux-2.6/arch/l4/Makefile.l4conf > O=/path/to/l4-obj-dir L4X_LOOP_CHECK=1 > OUTPUT=.../l4linux-2.6/build/Makeconf.l4conf GEN > l4linux-2.6/build/Makeconf.l4conf > GEN l4linux-2.6/build/Makefile > HOSTLD scripts/kconfig/conf > scripts/kconfig/conf -s arch/l4/Kconfig > Creating asm-l4/api-l4env -> asm/api symlink > Creating asm-l4/l4lxapi/impl symlink > Creating asm-l4/l4x-i386 -> asm/l4x symlink > .. > > As said, I'll try to fix the error message inbetween. > > Maybe it's the make version. Which version are you using? root@darkstar:~# make --version GNU Make 3.80 Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I use the slackware 10.2 with make 3.80 and gcc 3.3.6. What version are you using? Maybe I need to update the make. Thanks. cheng

1 0

Re: Kernel configuration missing ?
by chenggh 17 May '07

17 May '07

On Wednesday 16 May 2007 21:57, you wrote: > Hi, > > On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > > I download the newest source page neened for L4Linux and Fiasco. The > > L4Dir is dice/ kernel/ l4/ l4linux-2.6/ > > the compilations of fiasco kernel and l4 packages is ok and when i > > enter the l4linux I input make menuconfig. There are some errors like > > this: > > > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > > configuration missing. Stop. > > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 > > It's true that there's this irritating message but it should generally > work. Does for me like this: > > $ cd l4linux-2.6 > $ mkdir /tmp/builddir > $ make O=/tmp/builddir menuconfig > ... configure path to l4-obj-dir etc... > $ make O=/tmp/builddir There is still the problem in my machine like this: root@darkstar:/home/L4/tudos/l4linux-2.6# make O=./build/ menuconfig /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. make[1]: *** [/home/L4/tudos/l4linux-2.6/build/Makeconf.l4conf] Error 2 make: *** [menuconfig] Error 2 I think it is possible to miss some configuration files. But I don't know which file is missing. Thank you. cheng

1 0

logging to cvs problem
by Jorge Torres 17 May '07

17 May '07

Hi l4-hackers, I have a problem once I try to log in to os.inf.tu-dresden.de CVS, as suggested on http://www.inf.tu-dresden.de/index.php?node_id=1514&ln=en I get this: $ cvs -d:pserver:guest@os.inf.tu-dresden.de:/home/remote-cvs login Logging in to :pserver:guest@os.inf.tu-dresden.de:2401/home/remote-cvs CVS password: <guest> cvs [login aborted]: connect to os.inf.tu-dresden.de(141.76.48.99):2401 failed: Connection refused Does anyone know why this may be? Thank you very much, Jorge

2 1

Re: Kernel configuration missing ?
by Adam Lackorzynski 17 May '07

17 May '07

On Thu May 17, 2007 at 09:34:32 +0000, chenggh wrote: > On Wednesday 16 May 2007 21:57, you wrote: > > Hi, > > > > On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > > > I download the newest source page neened for L4Linux and Fiasco. The > > > L4Dir is dice/ kernel/ l4/ l4linux-2.6/ > > > the compilations of fiasco kernel and l4 packages is ok and when i > > > enter the l4linux I input make menuconfig. There are some errors like > > > this: > > > > > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > > > configuration missing. Stop. > > > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 > > > > It's true that there's this irritating message but it should generally > > work. Does for me like this: > > > > $ cd l4linux-2.6 > > $ mkdir /tmp/builddir > > $ make O=/tmp/builddir menuconfig > > ... configure path to l4-obj-dir etc... > > $ make O=/tmp/builddir > There is still the problem in my machine like this: > > root@darkstar:/home/L4/tudos/l4linux-2.6# make O=./build/ menuconfig > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > configuration missing. Stop. > make[1]: *** [/home/L4/tudos/l4linux-2.6/build/Makeconf.l4conf] Error 2 > make: *** [menuconfig] Error 2 This works just fine for me: l4linux-2.6$ mkdir build l4linux-2.6$ make O=./build/ menuconfig .../l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc GEN /path/to/l4linux-2.6/build/Makefile HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/lxdialog/checklist.o ... l4linux-2.6$ make O=./build/ L4 source directory: /path/to/l4 make -C /path/to/l4 -f .../l4linux-2.6/arch/l4/Makefile.l4conf O=/path/to/l4-obj-dir L4X_LOOP_CHECK=1 OUTPUT=.../l4linux-2.6/build/Makeconf.l4conf GEN l4linux-2.6/build/Makeconf.l4conf GEN l4linux-2.6/build/Makefile HOSTLD scripts/kconfig/conf scripts/kconfig/conf -s arch/l4/Kconfig Creating asm-l4/api-l4env -> asm/api symlink Creating asm-l4/l4lxapi/impl symlink Creating asm-l4/l4x-i386 -> asm/l4x symlink ... As said, I'll try to fix the error message inbetween. Maybe it's the make version. Which version are you using? Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Re: Kernel configuration missing ?
by chenggh 17 May '07

17 May '07

On Wednesday 16 May 2007 21:57, you wrote: > Hi, > > On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > > I download the newest source page neened for L4Linux and Fiasco. The > > L4Dir is dice/ kernel/ l4/ l4linux-2.6/ > > the compilations of fiasco kernel and l4 packages is ok and when i > > enter the l4linux I input make menuconfig. There are some errors like > > this: > > > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > > configuration missing. Stop. > > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 > > It's true that there's this irritating message but it should generally > work. Does for me like this: > > $ cd l4linux-2.6 > $ mkdir /tmp/builddir > $ make O=/tmp/builddir menuconfig > ... configure path to l4-obj-dir etc... > $ make O=/tmp/builddir There is still the problem in my machine like this: root@darkstar:/home/L4/tudos/l4linux-2.6# make O=./build/ menuconfig /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. make[1]: *** [/home/L4/tudos/l4linux-2.6/build/Makeconf.l4conf] Error 2 make: *** [menuconfig] Error 2 I think it is possible to miss some configuration files. But I don't know which file is missing. Thank you. cheng

1 0

Re: Kernel configuration missing ?
by Adam Lackorzynski 16 May '07

16 May '07

Hi, On Wed May 16, 2007 at 20:07:26 +0000, chenggh wrote: > I download the newest source page neened for L4Linux and Fiasco. The L4Dir is > dice/ kernel/ l4/ l4linux-2.6/ > the compilations of fiasco kernel and l4 packages is ok and when i enter the > l4linux I input make menuconfig. There are some errors like this: > > /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel > configuration missing. Stop. > make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 It's true that there's this irritating message but it should generally work. Does for me like this: $ cd l4linux-2.6 $ mkdir /tmp/builddir $ make O=/tmp/builddir menuconfig ... configure path to l4-obj-dir etc... $ make O=/tmp/builddir > Former I downloaded the source page by cvs and all of them is ok. But this > time I get it by svn there are some problem. please help me. That shouldn't make a difference. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Kernel configuration missing ?
by chenggh 16 May '07

16 May '07

Hi: I download the newest source page neened for L4Linux and Fiasco. The L4Dir is dice/ kernel/ l4/ l4linux-2.6/ the compilations of fiasco kernel and l4 packages is ok and when i enter the l4linux I input make menuconfig. There are some errors like this: /home/L4/tudos/l4linux-2.6/arch/l4/Makefile.l4conf:10: *** Kernel configuration missing. Stop. make: *** [/home/L4/tudos/l4linux-2.6/Makeconf.l4conf] Error 2 Former I downloaded the source page by cvs and all of them is ok. But this time I get it by svn there are some problem. please help me. Thanks. cheng

1 0

Simple questions
by Ernesto Bascon 16 May '07

16 May '07

Hi L4 hackers! I am very new to Fiasco and want to know several basic things: 1. Is L4Env targeted to develop OS personalities other than L4Linux? 2. Is DROPS built on top of L4Env? 3. Is there any C++ standard library implementation on top of L4Env? If not, what should be needed to have it? 4. Does Fiasco runs on AMD64/SMP machines? 5. Does Fiasco/UX runs on AMD64/SMP machines? Kind regards, Ernesto.

2 1

I have a question about L4Linux
by 차승준 15 May '07

15 May '07

Hello I’m a graduate student of CNU, in Korea My major is computer science, especially operating system(OS) May I ask some questions?? I have studied a operating system, micro kernel; l4linux So I downloaded its source code and analysis it I wonder how manage memory, in “Demand paging” Would mind please tell me where it “Demand paging” implementation and how it work in source code Best regards. SJ. Cha

5 9

Problem, when compiling Fiasco with JBD disabled.
by unruhig＠gmail.com 10 May '07

10 May '07

Hi, just checkouted Fiasco sources from SVN repo today and tried to build it. When disabling JBD in “make config”, the build fails: ... Making startup.o /usr/src/tudos/kernel/fiasco/src/kern/thread-pagefault.cpp: In member function ‘int Thread::handle_page_fault(Address, Mword, Mword, Return_frame*)’: /usr/src/tudos/kernel/fiasco/src/kern/thread-pagefault.cpp:162: error: ‘LOG_MSG_3VAL’ was not declared in this scope /usr/src/tudos/kernel/fiasco/src/kern/thread-pagefault.cpp:166: error: ‘LOG_MSG_3VAL’ was not declared in this scope make[1]: *** [startup.o] Error 1 With JBD enabled all goes ok. Can this be considered as a bug?

2 1

L4Linux without L4Loader
by Daniel Vandersee 06 May '07

06 May '07

Hi there, I wonder if it is possible to start L4Linux (possibly with some modifications) whether from GRUB directly or from a different loader than l4-loader. Is there a particular reason why L4Linux is linked against libloader.s.so? If it would not work out of the box: What has to be neccessarily provided by that (new) loader in oder to achieve that goal? Furthermore I did not manage to link L4Linux without libloader. I tried to replace libloader by those libs that were included by libloader itself, but always get undefined references: > arch/l4/kernel/built-in.o: In function `l4env_phys_to_virt': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:200: multiple definition of `l4env_infopage' > ../l4/lib/x86_586/l4v2/libl4env.p.a(startup.s.o):/home/user/src/otc_snapshot/l4/pkg/l4env/lib/src/startup.c:59: first defined here > lib/lib.a(string.o): In function `memcmp': > /home/user/src/otc_snapshot/l4linux-2.6/lib/string.c:553: multiple definition of `memcmp' > arch/l4/kernel/built-in.o:/home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/helper_dyn.c:43: first defined here > ld: Warning: size of symbol `memcmp' changed from 41 in arch/l4/kernel/built-in.o to 43 in lib/lib.a(string.o) > lib/lib.a(vsprintf.o): In function `vsnprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:258: multiple definition of `vsnprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:46: first defined here > ld: Warning: size of symbol `vsnprintf' changed from 38 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 1337 in lib/lib.a(vsprintf.o) > lib/lib.a(vsprintf.o): In function `snprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:537: multiple definition of `snprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:33: first defined here > ld: Warning: size of symbol `snprintf' changed from 39 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 40 in lib/lib.a(vsprintf.o) > lib/lib.a(vsprintf.o): In function `vsprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:587: multiple definition of `vsprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:42: first defined here > ld: Warning: size of symbol `vsprintf' changed from 35 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 41 in lib/lib.a(vsprintf.o) > lib/lib.a(vsprintf.o): In function `sprintf': > /home/user/src/otc_snapshot/l4linux-2.6/lib/vsprintf.c:604: multiple definition of `sprintf' > ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o):/home/user/src/otc_snapshot/l4/pkg/log/lib/src/sprintf.c:24: first defined here > ld: Warning: size of symbol `sprintf' changed from 36 in ../l4/lib/x86_586/l4v2/liblogserver.p.a(sprintf.s.o) to 41 in lib/lib.a(vsprintf.o) > arch/l4/lib/arch-i386/built-in.o: In function `l4x_proc_init': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/lib/arch-i386/../proc.c:(.text+0x0): multiple definition of `strstr' > arch/l4/kernel/built-in.o:/home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/helper_dyn.c:134: first defined here > ld: Warning: size of symbol `strstr' changed from 112 in arch/l4/kernel/built-in.o to 48 in arch/l4/lib/arch-i386/built-in.o > ../l4/lib/x86_586/l4v2/liblogserver.p.a(doprnt.s.o): In function `LOG_doprnt': > /home/user/src/otc_snapshot/l4/pkg/log/lib/src/doprnt.c:732: undefined reference to `__umoddi3' > /home/user/src/otc_snapshot/l4/pkg/log/lib/src/doprnt.c:733: undefined reference to `__udivdi3' > arch/l4/kernel/built-in.o: In function `setup_l4env_memory': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:(.text+0x2a4): undefined reference to `l4dm_mem_allocate' > arch/l4/kernel/built-in.o: In function `free': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:291: undefined reference to `l4dm_mem_release' > arch/l4/kernel/built-in.o: In function `l4x_map_below_mainmem': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:386: undefined reference to `l4rm_lookup' > arch/l4/kernel/built-in.o: In function `l4x_map_upage_myself': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:439: undefined reference to `l4rm_lookup' > arch/l4/kernel/built-in.o: In function `l4x_map_iomemory_from_sigma0': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:1549: undefined reference to `l4sigma0_map_iomem' > arch/l4/kernel/built-in.o: In function `l4env_virt_to_phys': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:165: undefined reference to `l4dm_mem_phys_addr' > arch/l4/kernel/built-in.o: In function `__cxa_atexit': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:251: undefined reference to `l4rm_lookup' > arch/l4/kernel/built-in.o: In function `l4x_mbm_request_ghost': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:362: undefined reference to `l4rm_area_release' > arch/l4/kernel/built-in.o: In function `l4env_free_initrd_mem': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/kernel/main.c:867: undefined reference to `l4dm_ds_list_all' > arch/l4/l4lxlib/l4env/lib.a(memory.o): In function `l4lx_memory_map_virtual_page': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/memory.c:23: undefined reference to `l4rm_lookup' > arch/l4/l4lxlib/l4env/lib.a(memory.o): In function `l4lx_memory_page_mapped': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/memory.c:66: undefined reference to `l4rm_lookup' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_number_allocate': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:65: undefined reference to `l4ts_allocate_task' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_number_free': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:142: undefined reference to `l4ts_free_task' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_create_pager': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:206: undefined reference to `l4ts_create_task' > arch/l4/l4lxlib/l4env/lib.a(task.o): In function `l4lx_task_delete': > /home/user/src/otc_snapshot/l4linux-2.6/arch/l4/l4lxlib/l4env/task.c:252: undefined reference to `l4ts_kill_task' > ../l4/lib/x86_586/l4v2/libio-ll.a(req_rel.o): In function `l4io_request_mem_region': > /home/user/src/otc_snapshot/l4/pkg/generic_io/lib/clientlib/req_rel.c:70: undefined reference to `l4rm_area_release' > /home/user/src/otc_snapshot/l4/pkg/generic_io/lib/clientlib/req_rel.c:70: undefined reference to `l4rm_area_release' > ../l4/lib/x86_586/l4v2/librtc.a(librtc.o): In function `init_done': > /home/user/src/otc_snapshot/l4/pkg/rtc/lib/client/librtc.c:33: undefined reference to `l4_scaler_tsc_to_ns' > /home/user/src/otc_snapshot/l4/pkg/rtc/lib/client/librtc.c:69: undefined reference to `l4_scaler_tsc_to_us' > /home/user/src/otc_snapshot/l4/pkg/rtc/lib/client/librtc.c:33: undefined reference to `l4_scaler_ns_to_tsc' > ../l4/lib/x86_586/l4v2/librtc.a(librtc.o): In function `l4rtc_get_seconds_since_1970': > /home/user/src/otc_snapshot/build/l4/include/x86/l4/util/rdtsc.h:268: undefined reference to `l4_scaler_tsc_to_ns' > /home/user/src/otc_snapshot/build/l4/include/x86/l4/util/rdtsc.h:268: undefined reference to `l4_scaler_tsc_to_ns' Especially I wasn't able to locate "__umoddi3" and "__udivdi3" in any library except of libloader. I modified l4linux-2.6/arch/l4/kernel/Makefile of the latest OTC snapshot as follows: > L4LIBS = -L$(L4OBJ)/lib/$(L4_MK_ARCH)_$(L4_MK_CPU)/$(L4_MK_API) \ > -L$(L4OBJ)/lib/$(L4_MK_ARCH)_$(L4_MK_CPU) \ > -L$(L4OBJ)/lib \ > -T../../l4/lib/x86_586/main_stat.ld --start-group -lroot.p -lsemaphore.p \ > -lgeneric_ts.p \ > -lloaderif.p \ > -ll4util_root.p \ > -ll4sys.p \ > -lthread.p \ > -ldm_generic.p \ > -ldm_mem.p \ > -ll4env_err.p \ > -ll4env.p \ > -lnames.p \ > -lgeneric_fprov.p \ > -llogserver.p \ > -lnames.p \ > -lc_be_minimal_log_io.p \ > -lc_be_simple_mem.p \ > -lc_be_mmap.p \ > -lc_be_mmap_util.p \ > -luclibc_support.p \ > -lthread.p \ > -lc_be_l4env_start_stop.p \ > -ll4rm.p \ > -lslab.p \ > -ll4util.p -lsigma0.p -llist_alloc.p --end-group \ > $(GCCLIB) Thanks in advance. Kind regards, Daniel

4 6

Fiasco built-in profiling
by Stefan Scheler 06 May '07

06 May '07

Hello, I'm currently trying to get fiasco's built-in profiling working. The problem is, as soon as roottask has been started, an error (mcount: tos overflow) occurs which apparently prevents profiling. Later on no gmon.out.uu is generated. Is that supposed to work? Or what am I doing wrong here? I attached a log showing the error message. From the JDB source code, it sounds like you can enable and disable kernel profiling from JDB. How can this be accomplished? Thanks for any help Stefan L4 Bootstrapper Scaning /bin/fiasco -profile -profstart -nokdb -nowait -serial -comport 1 -serial_esc Scaning /bin/sigma0 Scaning /bin/roottask Bootloader MMAP available [00000000,0009fc00) RAM (1) [0009fc00,000a0000) RAM (1) [000f0000,00100000) reserved (2) [ffb00000,00000000) reserved (2) [00100000,1fff0000) RAM (1) [1fff3000,20000000) ACPI (3) [1fff0000,1fff3000) ACPI NVS (4) Relocated mbi to [0x61000-0x611b3] Loading /bin/fiasco Loading /bin/sigma0 Loading /bin/roottask find kernel info page... found kernel info page at 0x1000 API Version: (87) experimental Sigma0 config ip:00094cd0 sp:00106100 Roottask config ip:00120000 sp:00109528 [00001000-00002000) /bin/fiasco [00002000-00052680) /bin/fiasco [00052680-0005add0) /bin/fiasco [0005b000-0005e861) /bin/fiasco [0005e880-00061000) /bin/fiasco [00090000-00099380) /bin/sigma0 [0009f000-00100000) BIOS area [00100000-00109764) bootstrap [00120000-001345d0) /bin/roottask [00135000-0013f9bb) /bin/roottask [001409c0-002be9f4) /bin/roottask [00300000-003017ec) /bin/fiasco [00302000-0038fce0) /bin/fiasco [03000000-03152c1d) Modules Memory [1fff0000-ffffffff) Deep Space Starting kernel /bin/fiasco at 003007e8 Welcome to Fiasco(ia32)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 4.1.1 for Pentium M Performance-critical config option(s) detected: CONFIG_SCHED_RTC is on CONFIG_ASSEMBLER_IPC_SHORTCUT is off CONFIG_PROFILE is on CONFIG_NO_FRAME_PTR is off CONFIG_JDB_ACCOUNTING is on Enabling special fully nested mode for PIC Using the RTC on IRQ 8 (1kHz) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter CPU: GenuineIntel (F:2:4:9) Model: Pentium 4 (Northwood/Prestonia) at 1992 MHz 64 Entry I TLB (4K or 4M pages) 64 Entry D TLB (4k or 4M pages) 12K µ-ops T Cache (8-way associative) 8 KB L1 D Cache (4-way associative, 64 bytes per line) 512 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 1000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures Roottask. Command line found: "/bin/roottask" mcount: tos overflow 523840kB ( 511MB) total RAM (reported by bootloader) 479676kB ( 469MB) received RAM from Sigma0 1816kB ( 2MB) reserved RAM for RMGR Received I/O ports 0000-ffff Attached irqs = [ <!0> 1 <!2> 3 <!4> 5 6 7 <!8> 9 A B C D E F ] Roottask: Loading 1 module. #05: loading "/bin/hello" from [0312d000-03152c1d] to [01000000-01002eea][01003000-010055c0] entry at 0005b064 via trampoline page code symbols at [1d6fa000-1d6fb000] (4kB), lines at [1d6f7000-1d6fa000] (12kB) hello: My thread-id is 5.0 hello: My thread-id is 5.0 hello: My thread-id is 5.0

3 5

Typed Words
by Jonathan S. Shapiro 30 Apr '07

30 Apr '07

This is a very small issue. If I understand the L4 specifications correctly, typed words provided by the sender are copied to the recipient. This allows the recipient to know what was sent. An observation: The transfer of typed words exposes sender-side address values to the receiver. This is a small security violation, since there is no valid use that the receiver can make of this information. It is probably not an important issue, except that we noticed an interaction with cross-model calls. If the IPC transport replaces these addresses with zero, it becomes possible to re-encode a 64-bit typed item word into a 32-bit typed item word without losing any useful information. This appears (to us) to be useful in the implementation of IPCs that cross from (e.g.) 64-bit sender to 32-bit receiver. It does not appear to us that the receiver loses any useful information if the sender address is zeroed or truncated. Have we missed something? shap -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

2 1

Typed items and the 'C' bit
by Jonathan S. Shapiro 30 Apr '07

30 Apr '07

The L4.x2 specification states: 1. The 'C' bits of typed items and the 't' field of IPW0 redundantly encode the number of typed items. This is intentional. 2. The sender ignores the 'C' bits, but sets them for the receiver. [This is required because the sender may set the C bits incorrectly, and the path in the kernel that interprets them must have a small, bounded number of iterations. If the kernel believes the 'C' bits of the type field, a very large number of iterations could be created and the receiver-side "frame" for words could be overwritten by the sender.] 3. The specifcation *alleges* that the C bit provides a performance advantage to the receiver in parsing the arguments. I am not convinced that [3] is true. The typed items have variable length, which means that the receiver must parse the type fields in order to iterate over them. The only complex case is string items having a non-zero 'c' (continue) bit, and the specification is explicit that for these cases the "type" field of the successor stringitem is entirely ignored. Question: does the 'C' bit provide a real advantage, or is it a historical curiosity? If there is an advantage, can somebody give an example? -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

2 1

IPC and Multiple Execution Models
by Jonathan S. Shapiro 30 Apr '07

30 Apr '07

On amd64 (and other architectures), multiple execution models are supported by the hardware. In the case of amd64, both 64-bit and 32-bit applications can be supported simultaneously. IPC across models presents some problems. When sending from 32-bit to 64-bit, registers are widened (good), but differences in alignment rules can mean that the 64-bit receiver and the 32-bit sender do not agree about the number and lengths of indirect strings. When sending from 64-bit to 32-bit, registers are truncated, and there can be difficulties with indirect strings because of differing alignment requirements. It is definitely possible for the IDL compiler to compile for both models, and to generate cross-model calls that will avoid these problems, but I have not found any "clean" solution. On platforms that support multiple execution architectures, how do L4 systems deal with this? If this is discussed in existing documents (perhaps the IDL compiler manual?) a pointer to the document is sufficient. Thanks! -- Jonathan S. Shapiro, Ph.D. Managing Director The EROS Group, LLC

3 2

getc()
by Peter Nguyen 30 Apr '07

30 Apr '07

Hi, I'm currently messing around with L4 at the moment. More specifically, i'm providing some facilities for profiling in L4 via sampling. Right now, i'm trying to implement an exception handler for the Performance Measurement Counters on the PowerPC architecture. In providing calls to these facilities via the pingpong root-task, i seem to run into problems with input. Essentially, while the root-task is waiting for user input, it seems as if the exception is not kicking in until i enter a character. The exception that should be handled is a performance monitor exception (where one of the counters overflow). Basically, the overflow takes place such that a significant amount of instructions have been executed when theoretically it should be signalled earlier. In accepting input, the root-task (which i didn't write myself) uses getc() to obtain such input. My question is basically whether getc() blocks everything and sits there until a character is received? I suspect that this is most certainly the case. If so, does anyone know whether there are other facilities available for provide an alternative means for providing input in an application. The reason why i am asking about whether getc() is a factor or not is that in providing an infinite loop, the exception/interrupt kicks in at the right time ie. when the counter overflows, the resulting counter value is slightly above the overflow value eg. the counter overflows when the contents of the register is 0x80000000. When the exception kicks in, the "final" value is 0x80000012 as opposed to a random value in the case with a root-task that requests input. Any help would be greatly appreciated. Peter N -- View this message in context: http://www.nabble.com/getc%28%29-tf3626544.html#a10126418 Sent from the L4 mailing list archive at Nabble.com.

3 6

Re: L4Linux without L4Loader
by Bjoern Doebel 26 Apr '07

26 Apr '07

Hi, > I didn't know about that patch. I just tried it and with some > modifications it builds fine. Thank you. Cool. :) > But additionally I want to load l4linux with our loader. As Christian > Helmuth stated in that thread, the loader has to emulate(?) an > L4env-environment in order to do that. What does that mean for our loader? Basically, the Loader sets up an L4Env infopage that contains some information about the application's environment. (See l4/pkg/l4env/include/env.h). I think you will be able to find the few locations where this is done in our Loader. If you have questions, feel free to ask. Regards, Bjoern

1 0

Debian package for Dice and DICE_INCDIR
by Neal H. Walfield 24 Apr '07

24 Apr '07

When using Adam's Debian package for dice [1], Dice's include files are installed in /usr/include. For L4 ENV to make use of them, I had to override DICE_INCDIR. This has the unfortunate effect of essentially making the system header files includable. This triggers the following error: LD_PRELOAD=/home/neal/src/tudos/build/tool/gendep/libgendep.so GENDEP_TARGET=helper_dyn.s.o GENDEP_BINARY=cc1 gcc-3.4 -c -DRAM_BASE=0x0 -DUSE_UCLIBC=y -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -DCONFIG_L4_CALL_SYSCALLS -DCONFIG_L4_ABS_SYSCALLS -I/home/neal/src/tudos/build/pkg/loader/idl/OBJ-x86-l4v2 -I/home/neal/src/tudos/build/include/x86/l4v2 -I/home/neal/src/tudos/build/include/l4v2 -I/home/neal/src/tudos/build/include/x86 -I/home/neal/src/tudos/build/include -I/usr/include -I/home/neal/src/tudos/l4/../install/include/x86/l4v2 -I/home/neal/src/tudos/l4/../install/include/l4v2 -I/home/neal/src/tudos/l4/../install/include/x86 -I/home/neal/src/tudos/l4/../install/include -nostdinc -I/home/neal/src/tudos/build/include/x86/uclibc -I/home/neal/src/tudos/build/include/uclibc -I/home/neal/src/tudos/build/include/uclibc++ -I/home/neal/src/tudos/l4/../install/include/x86/uclibc -I/home/neal/src/tudos/l4/../install/include/uclibc -I/home/neal/src/tudos/l4/../install/include/uclibc++ -I/usr/lib/gcc/i486-linux-gnu/3.4.6/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -fno-common -D__PIC__ -fPIC /home/neal/src/tudos/l4/pkg/loader/lib/runtime/helper_dyn.c -o helper_dyn.s.o /home/neal/src/tudos/l4/pkg/loader/lib/runtime/helper_dyn.c:70: error: syntax error before "__extension__" /home/neal/src/tudos/l4/pkg/loader/lib/runtime/helper_dyn.c:70: error: syntax error before '&&' token ... make[6]: *** [helper_dyn.s.o] Error 1 make[6]: Leaving directory `/home/neal/src/tudos/build/pkg/loader/lib/runtime/OBJ-x86_586-l4v2' As can be seen above -I/usr/include is present on the command line. This is due to the expansion of $(DICE_INCDIR). To work around this problem, the package could be changed to instead install the dice include files under /usr/include/dice such that setting DICE_INCDIR to /usr/include/dice would cause the dice header files to be made available for inclusion. Neal [1] http://os.inf.tu-dresden.de/~adam/dice/

2 1

Automated regression test suite for L4
by seth bollinger 18 Apr '07

18 Apr '07

Hello All, Is there an automated regression test suite for L4 that covers all (or most of) the features of the l4 kernel? Is there also an automated benchmarking suite? These would be great tools to have available for people who are porting the kernel to new platforms/dev boards, or for people who are looking to tweak/play with the kernel. Thanks, Seth

4 3

Fehler beim kompilieren...
by MHaeussi＠gmx.de 18 Apr '07

18 Apr '07

Hallo liebe Entwickler, ich habe ein Problem beim kompilieren von dem Kernel. Den Kernel will ich als Schulprojekt verwenden, dass sich mit "TPM unter Linux" beschäftigt. Grundidee ist auf dem Microkernel ein "normales" Suse Linux laufen zu lassen das fast alle TPM Funktionen unterstützt die es unter Windows gibt. Hoffentlich ist das überhaupt möglich ^^ Als er den Kompilierdurchlauf beendet habe ich 2 Fehler und es befindet sich kein Kernel im Verzeichnis. Leider kann ich mit den Fehlermeldungen nichts anfangen. Diese habe ich als Anhang beigefügt. Vorgegangen bin ich laut eurer Anleitung im Internet. lg Markus Häußler -- Markus Häußler "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

2 1

AIM Multiuser Benchmark - Suite VII
by Eduard Benes 12 Apr '07

12 Apr '07

Hello! As a part of my research I have to run macrobenchmarks on L4Linux and native Linux. I saw few papers related to performance testing of L4Linux, where this benchmark was used. The problem is that I'm not able to find (google) working version. Could somebody provide me tested (used,working) copy of this benchmark? Or are there any similar test that could be used instead of aim7? Thank you, Eduard Benes

2 1

Writing simple "hiworld" server using L4Env packages
by Eduard Benes 10 Apr '07

10 Apr '07

Hi! My goal is to create, using l4env pkgs, some simple servers that would run on top of microkernel and compare their performance when running on native Linux and on L4 ukernel. They should run single and more paraller "processes" that would do some simple numerical algorithms (sorting, Monter Carlo, ...) So, I would like to ask for help with creation of such servers. Better said, it can be few single servers without any clients. (integer/float data types? forks? mallocs? time measurement? ...) Is there available l4env "programming tutorial", some notes from lectures provided at TU-Dresden, or some more advanced "example" server code that could be modified without much knowledge of l4env specifics? I've found the BID tutorial, but for me it would be more helpful to know what basic functions, libraries, data types can be used, and how. (e.g. the hello world example could be modified) Could someone please show me the right way to go? I'm running out of time, so I would really appreciate all help :) Right now I'm working on benchmarking L4Linux and native Linux to get idea of the overhead. And It would be interesting to get idea of the performance when apps/servers are running on L4 kernel without the L4Linux overhead. Thank you, Eduard Benes

3 2

Re: Writing simple "hiworld" server using L4Env packages
by chenggh 10 Apr '07

10 Apr '07

> Is there available l4env "programming tutorial", some notes from > lectures provided at TU-Dresden, or some more advanced "example" > server code that could be modified without much knowledge of l4env > specifics? Sorry, As i know there is not existing l4env programming tutorial. > I've found the BID tutorial, but for me it would be more helpful > to know what basic functions, libraries, data types can be used, > and how. (e.g. the hello world example could be modified) > Could someone please show me the right way to go? Yes, the BID tutorial is very helpful. But it could give you a small example about how the l4 application is created and running. > I'm running out of time, so I would really appreciate all help :) > Right now I'm working on benchmarking L4Linux and native Linux > to get idea of the overhead. And It would be interesting to > get idea of the performance when apps/servers are running on L4 > kernel without the L4Linux overhead. Do you aim at porting a Linux application on top of L4 kernel without L4Linux ? What is the function of your application? cheng

1 0

access to l4/pkg/ktest
by Hendrik Tews 08 Apr '07

08 Apr '07

Hi, would it be possible to put the ktest package into the public repository? If not, how can Erik Schierboom get access to ktest? [I suggested to Erik to put the properties that he is about to prove for the Fiasco IPC as assertions into the code and then run some IPC stress test. As IPC stress test I suggested to recompile linux inside l4linux with -j 100. However Marcus suggested to use pingpong and ktest instead. Any further suggestions for Fiasco IPC stress testing are of course most welcome.] Bye, Hendrik

2 1

Building L4Linux
by Eduard Benes 08 Apr '07

08 Apr '07

Hi, I run into problem compiling l4linux. I've been able to compile it many times before. But after few weeks while I was not with l4linux stuff, I run into problem when building it. I'm pretty sure it will be some "stupid" mistake I've made, but since I need to quickly finish some testing, I would really appreciate any advise... Here is configuration I use: Debian {sarge, etch}; gcc version: 3.{3,4}, l4linux-2.6-17 Everything is mainly based on chenggh's kickstart and tarball he provided. (http://os.inf.tu-dresden.de/pipermail/l4-hackers/2007/002732.html) < l4linux make log start > include/asm-l4/i386-arch/asm/alternative.h:7: error: syntax error before "u8" include/asm-l4/i386-arch/asm/alternative.h:7: warning: no semicolon at end of struct or union include/asm-l4/i386-arch/asm/alternative.h:8: warning: type defaults to `int' in declaration of `replacement' include/asm-l4/i386-arch/asm/alternative.h:8: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:9: error: syntax error before "cpuid" include/asm-l4/i386-arch/asm/alternative.h:9: warning: type defaults to `int' in declaration of `cpuid' include/asm-l4/i386-arch/asm/alternative.h:9: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:10: error: syntax error before "instrlen" include/asm-l4/i386-arch/asm/alternative.h:10: warning: type defaults to `int' in declaration of `instrlen' include/asm-l4/i386-arch/asm/alternative.h:10: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:11: error: syntax error before "replacementlen" include/asm-l4/i386-arch/asm/alternative.h:11: warning: type defaults to `int' in declaration of `replacementlen' include/asm-l4/i386-arch/asm/alternative.h:11: warning: data definition has no type or storage class include/asm-l4/i386-arch/asm/alternative.h:12: error: syntax error before "pad" include/asm-l4/i386-arch/asm/alternative.h:12: warning: type defaults to `int' in declaration of `pad' include/asm-l4/i386-arch/asm/alternative.h:12: warning: data definition has no type or storage class In file included from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/interrupt.h:9, from arch/l4/l4lxlib/l4env/irq_multi.c:12: include/asm-l4/l4-arch/asm/processor.h:154: error: `cpuid' redeclared as different kind of symbol include/asm-l4/i386-arch/asm/alternative.h:9: error: previous declaration of `cpuid' include/asm-l4/l4-arch/asm/processor.h:154: warning: `cpuid' was declared `extern' and later `static' make[1]: *** [arch/l4/l4lxlib/l4env/irq_multi.o] Error 1 make: *** [arch/l4/l4lxlib/l4env] Error 2 < l4linux make log end > Thank you, Eduard Benes

2 1

Re: hda : lost interrupt
by chenggh 03 Apr '07

03 Apr '07

On Tuesday 03 April 2007 11:47, you wrote: > Linux's that I have compiled l4 and l4linux , is in > /dev/hda1. But home folder is in /dev/hda3. And the l4 > codes and build directory is in /dev/hda3 > > I did not understand the root concept in the l4linux > coniguration. The root concept in l4linux is same as in linux. A simple root file system consists of different directories including /bin /etc /lib /dev/, etc. The root file system is different from root home directory. In other words the partition which is mounted into / is your choice. For example, the /etc/fstab of my machine is : /dev/hda2 swap swap defaults 0 0 /dev/hda3 / ext3 defaults 1 1 /dev/hda4 /home/ ext3 defaults 1 2 /dev/hdd2 /home/oldsystem ext3 defaults 1 2 If i set root file system it is /dev/hda3. I think it is enough. Good luck. cheng

2 1

Re: hda : lost interrupt
by chenggh 03 Apr '07

03 Apr '07

On Tuesday 03 April 2007 10:31, Burak OGUZ wrote: > Thanks for your help, > > Now it goes over lost interrupt error but this time it > says that > > Warning : unable to open an initial console > Kernel panic - not syncing : No init found try parsing > init= option to kernel > panic : going to sleep forever bye > > What do you think about this situation? Maybe it means that you set a wrong root file system. In your linux26.cfg you set root=/dev/hda1. Are you sure your root file system is located in /dev/hda1? cheng

3 2

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

I have started dmon log server to take logs but it gave no errors. I am totally confused about it. I think l4linux does not contain the driver for my block devices. I think that is why it gives lost interrupt error. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: chenggh <chenggh04(a)st.lzu.edu.cn> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, April 2, 2007 4:26:43 PM Subject: Re: hda : lost interrupt > l4lx | Done (1517 entries). > l4lx | l4lx_thread_create: Created thread 0f.05 > (timer.i0) > l4lx | panic: going to sleep forever, bye > > > I have booted it with 512m ram under qemu. If you have kernel panic message above it means your l4linux kernel encounters some problem. In this situation you should use a serial console to receive l4linux booting messages. These messages could help you find what is wrong. My booting log is like this: l4lx | Filling lower ptabs... l4lx | Done (1611 entries). l4lx | l4lx\_thread\_create: Created thread 10.05 (timer.i0) l4lx | l4lx\_thread\_create: Created thread 10.06 (Idler) maybe this could help you. Thank you. cheng _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail

1 0

Re: hda : lost interrupt
by chenggh 02 Apr '07

02 Apr '07

> l4lx | Done (1517 entries). > l4lx | l4lx_thread_create: Created thread 0f.05 > (timer.i0) > l4lx | panic: going to sleep forever, bye > > > I have booted it with 512m ram under qemu. If you have kernel panic message above it means your l4linux kernel encounters some problem. In this situation you should use a serial console to receive l4linux booting messages. These messages could help you find what is wrong. My booting log is like this: l4lx | Filling lower ptabs... l4lx | Done (1611 entries). l4lx | l4lx\_thread\_create: Created thread 10.05 (timer.i0) l4lx | l4lx\_thread\_create: Created thread 10.06 (Idler) maybe this could help you. Thank you. cheng

1 0

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

I have made dmon work. What should I report here? It gives no error but finally it logs : l4lx_thread_create: Created thread 0f.0a (IRQ14) l4lx_thread_create: Created thread 0f.0b (IRQ15) and it starts giving lost interrupt for hard disk and cdrom. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Burak OGUZ <burakoguzs(a)yahoo.com> To: Ronald Aigner <ra3(a)os.inf.tu-dresden.de>; l4-hackers(a)os.inf.tu-dresden.de Sent: Monday, April 2, 2007 3:33:31 PM Subject: Re: hda : lost interrupt Also I have changed the l4 linux configuration file. I think I should adjust linux configuration too. After changing my linux configuration to this : verbose 0 task "vmlinuz26" "earlyprintk=yes mem=256M video=l4fb" all_sects_writable allow_cli After changing the configuration l4linux started to give this error: l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Linux version 2.6.19-l4 (root@think) (gcc version 3.4.6) #1 Wed Mar 2 l4lx : 8 15:42:40 EEST 2007 l4lx | Binary name: vmlinuz26 l4lx | Kernel command line (3 args): earlyprintk=yes mem=256M video=l4fb l4lx | Image: 00400000 - 00790000 [3648 KiB]. l4lx | Areas: Text: 00400000 - 00696000 [2648kB] (a bit longer) l4lx | Data: 00696000 - 006e408c [312kB] l4lx | Initdata: 006e8000 - 00722000 [232kB] l4lx | BSS: 00724000 - 0078e300 [424kB] l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) l4lx | Using tamed mode. l4lx | l4env_linux_startup thread 4. l4lx | l4lx_thread_create: Created thread 0f.04 (server) l4lx | main thread will be 0f.04 l4lx | l4env_register_pointer_section: addr = 006e6000 size = 249856 l4lx | sec-w-init: virt: 0x006e6000 to 0x00722fff [244 KiB] l4lx | sec-w-init: Number of physical regions: 1, 249856 Bytes l4lx | sec-w-init: 1: Phys: 0x01191000 to 0x011ce000, Size: 249856 l4lx | main thread: received startup message. l4lx | Main thread running, waiting... l4lx | setup_l4env_memory: Forcing superpages for main memory l4lx | Main memory size: 256MB l4lx | Got 2048kB of ISA DMA memory. l4lx | ISA DMA memory: virt: 0x00800000 to 0x009fffff [2048 KiB] l4lx | ISA DMA memory: Number of physical regions: 1, 2097152 Bytes l4lx | ISA DMA memory: 1: Phys: 0x0043a000 to 0x0063a000, Size: 2097152 l4lx | Main memory: virt: 0x00c00000 to 0x10bfffff [262144 KiB] l4lx | Main memory: Number of physical regions: 1, 268435456 Bytes l4lx | Main memory: 1: Phys: 0x0d400000 to 0x1d400000, Size: 268435456 l4lx | Filling lower ptabs... l4lx | Done (1517 entries). l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) DMphys | ds 32, client F.00, rights 0x0003, has 0x0001 DMphys | [8.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): DMphys | DMphys: bad permissions l4lx | L4RM: dataspace at 0x00400000-0x00695fff, id 32 at 8.00 l4lx | L4RM: dataspace manager call failed ("permission denied") l4lx | L4RM: [PF] write at 0x00400038, ip 004101d0, src F.02 l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault --PANIC, 'g' for exit------------------------------------IP: a00b43dd (f.00) jdb: Best regards, -- burak() (ps: bf) METU CENG '06 ____________________________________________________________________________________ Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html

1 0

Re: hda : lost interrupt
by chenggh 02 Apr '07

02 Apr '07

On Monday 02 April 2007 12:33, Burak OGUZ wrote: > permission What is your choice of option in Fiasco configuration? [ ] Enable I/O port protection If you enable this option only kernel has full access to all I/O ports. As a result when l4lx could access some resources it has no enough rights. So there is "bad permission" or "permission denied" message. So If you run l4linux disenble this option. It is my opinin. You can try. Thanks cheng

1 0

Re: hda : lost interrupt
by Burak OGUZ 02 Apr '07

02 Apr '07

Sorry for the last e-mail I accidently pushed sent button.. The content of the bin folder doesn't contain 'isocreator' executable. And I am stuck in creating iso . I have tried to create iso with mkisofs but I could not succeed. Also I couldn't find dmon in the svn repos. Could you give the exact repo address for dmon so I can check it out. Best regards.. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Ronald Aigner <ra3(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Cc: Burak OGUZ <burakoguzs(a)yahoo.com> Sent: Friday, March 30, 2007 11:34:47 AM Subject: Re: hda : lost interrupt -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Burak, Burak OGUZ wrote on 29.03.2007 13:58 this: > My grub configuration does not contain -esc. ok. > How can I run my installed l4 over qemu? you could for instance create a bootable cd-rom image: 1. create a directory which will contain all the files of the iso-image. Lets call it iso 2. in the iso directory create a boot/grub directory 3. put the files you want to boot somewhere into the iso directory (preferably into boot/) 4. create the respective Grub entries in boot/grub/menu.lst (have a look at the demo-cd boot/grub/menu.lst for examples) 5. in the iso directory, call '$(L4DIR)/tool/bin/isocreator . image' 6. boot the image with 'qemu -serial stdio -cdrom image' You might want to check which VBE modes qemu supports. The option -serial stdio gives you the serial console in the terminal window where you started qemu. > Do you mean RS232 cable serial null modem cable? I am working L4 on laptop therefore I don't have a direct RS232 access. I can not maintain that logs now. Are there any other ways that can I collect that this log info? As an alternative you can obtain the package dmon from our SVN repository (if you do not have it already). In the dmon directory is a README how to use it. Dmon basically opens a dope window and collects all debug logging information. This way you can see the log output even if you do not have a serial null modem cable and a second computer to debug. On the downside you will have to copy the debug information by hand (write it down, type it into your email program...). HTH, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGDMun2sAx3Dtx9+YRAgXhAJ9uXDdr0TFG6z9BuNqXA3CzxzK7cwCfTBZc ngqJj+W6aLgjGQ7q6xJorkw= =IBss -----END PGP SIGNATURE----- ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html

2 5

Fiasco runtime error
by eschierb＠sci.kun.nl 30 Mar '07

30 Mar '07

Hi, For my verification of Fiasco I would like to test some of the assumptions I am making in the proof. One way to test these assumptions is to add these assumptions as assert() calls in the kernel and check if they fire when the kernel is running a stress-test. The idea is to create an L4Linux instance and run an IPC-intensive application on it. For the compilation of l4-env and Fiasco I followed the instructions on this webpage: http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml. However, when I tried to execute step 3 (Go to the l4 directory and call make config) the system complained: make config does not work: need to give builddir with O=.../buildir. Stop. Of course this was easy to correct but I thought Id notify you anyway. After compiling Fiasco and l4-env, I thought Id try out the hello module. I moved the fiasco, irq0 and ux-con files from the Fiasco build directory to the DROPS build directory after which I started Fiasco as follows: ./fiasco l hello This resulted in the following: Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: AuthenticAMD (6:6:2:0) Model: Athlon (Palomino) at 1160 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 39f5000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures --Interception--------------------------------------ESP:00096748 EIP:000907cf (2.00) jdb: As you can see we automatically entered the debugger, any attempt to continue (using the g command) failed. I compiled Fiasco with the following options: Target platform: UX Exception IPC: Y Handle and preserve segments: Y Graphical console: Y Generate inline code: Y I also tried to run a test of Fiasco using: ./fiasco T which indicates that something is wrong: Fiasco-UX on Linux 2.6.18-1.2798.fc6 (i686) Mapped 64 MB Memory + 0 KB Framebuffer + 0 MB Input Area on FD 3 Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2006 TU Dresden Rev: Thu Dec 21 08:55:14 2006 compiled with gcc 3.4.6 for Intel Pentium CPU: AuthenticAMD (6:6:2:0) Model: Athlon (Palomino) at 1160 MHz 16/256 Entry I TLB (4K pages) 8 Entry I TLB (4M pages) 32/256 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) 256 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. KERNEL: 2.0 (tcb=20080000) killed: Unhandled trap EAX 00000000 EBX 0000c000 ECX 039f5000 EDX 00000000 ESI 00000000 EDI 00000000 EBP 00000000 ESP bf9ee09c EIP 00002000 EFLAGS 00200246 CS 0002 SS 007b DS 007b ES 007b FS 0000 GS 0007 trap 13 (General Protection), error 00000402, from user mode (internal event regarding IDT gate descriptor no. 0x80) --Interception--------------------------------------ESP:20000790 EIP:0004ee8b (0.00) jdb: Do you have any idea what might be wrong? With regards, Erik Schierboom ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

3 3

Re: hda : lost interrupt
by Burak OGUZ 30 Mar '07

30 Mar '07

My grub configuration does not contain -esc. How can I run my installed l4 over qemu? Do you mean RS232 cable serial null modem cable? I am working L4 on laptop therefore I don't have a direct RS232 access. I can not maintain that logs now. Are there any other ways that can I collect that this log info? Best regards -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Christian Helmuth <ch12(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Thursday, March 29, 2007 2:04:23 PM Subject: Re: hda : lost interrupt Hi, On Thu, Mar 29, 2007 at 01:01:08AM -0700, Burak OGUZ wrote: > Also a warning complains about I should not use -esc in L4Input. As libinput has no chance to check Fiasco's command line, it always logs this message. Just make sure your Fiasco grub module line does not contain "-esc". Anyway, did you attach a serial null modem cable to your test box/virtual machine? Greets -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12 _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php

2 2

DROPS/TUD:OS repository moved to subversion
by Adam Lackorzynski 29 Mar '07

29 Mar '07

Hi all, the public DROPS/TUD:OS repository has been moved to subversion and is now available at the following URL: http://svn.tudos.org/repos/tudos/trunk L4Linux is available at: http://svn.tudos.org/repos/l4linux/trunk The repositories contain the common svn structure with trunk, tags and branches. To make it easier for you to check out selected parts of the archive we have written a script that knows different modules. Do the following to get the Fiasco kernel and the packages for the 'hello' program. $ svn checkout -N http://svn.tudos.org/repos/tudos/trunk tudos $ cd tudos $ ./repomgr co hello To show all the available modules, issue: $ ./repomgr modules The repositories are updated after a successful build that is run once a day. Note that the internal directory structure changed a bit, the 'kernel' and 'dice' directories have been moved out of the l4 directory. The old public CVS repository will still be available for some time. It is not updated anymore. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 2

Re: hda : lost interrupt
by Burak OGUZ 29 Mar '07

29 Mar '07

There was an error, which was caused by removal of the vbeset command from grub. Also a warning complains about I should not use -esc in L4Input. -- burak() (ps: bf) METU CENG '06 ----- Original Message ---- From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Sent: Wednesday, March 28, 2007 8:49:09 PM Subject: Re: hda : lost interrupt On Wed Mar 28, 2007 at 08:01:09 -0700, Burak OGUZ wrote: > I have successfully booted the L4 and saw the dope. However, while > L4Linux is booting up it gives "hda : lost interrupt" for my hard disk > and "hdc : lost interrupt" for my cd-rom. I have applied whatever says > in the l4-kickstart manual except l4exec because I have read that it > is deprecated. > > Also same problem has occured when I have booted up with live CD. 'lost interrupt' indicates that there's some problem with the interrupt handling on your system. Can you maybe show us the log output that comes on the serial console and your menu.lst? You may also use e.g. qemu and compare the serial output of both systems to see if there's some significant difference which might indicate a problem. For testing purposes you may also comment out the vbeset command in the menu.lst as well as the line that loads dope. With this change you'll see the debug output directly on the screen. Look for messages that might indicate an error. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html

2 1

2025

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