- l4-hackers - example.com Site

twiddler compile problem
by Jayesh Salvi 26 Feb '05

26 Feb '05

I am facing problems with getting twiddler to compile. I have binutils-2.15.92.0.2-5. Here is the error. I have header files in place, I think this is linking problem but I have /usr/lib/libbfd.a and /usr/lib/libopcodes.a. [jayesh@orion twiddler]$ make gcc -W -Wall -g -O2 -DTARGET_X86=1 -lbfd -lopcodes -o twiddler_x86 twiddler.c /tmp/ccKfu4xD.o(.text+0x4a): In function `disasm_section': /home/jayesh/l4/tool/twiddler/twiddler.c:158: undefined reference to `bfd_get_section_contents' /tmp/ccKfu4xD.o(.text+0x180):/home/jayesh/l4/tool/twiddler/twiddler.c:127: undefined reference to `print_insn_i386' /tmp/ccKfu4xD.o(.text+0x31d): In function `main': /home/jayesh/l4/tool/twiddler/twiddler.c:223: undefined reference to `bfd_init' /tmp/ccKfu4xD.o(.text+0x335):/home/jayesh/l4/tool/twiddler/twiddler.c:74: undefined reference to `init_disassemble_info' /tmp/ccKfu4xD.o(.text+0x341):/home/jayesh/l4/tool/twiddler/twiddler.c:226: undefined reference to `bfd_openr' /tmp/ccKfu4xD.o(.text+0x359):/home/jayesh/l4/tool/twiddler/twiddler.c:231: undefined reference to `bfd_check_format' /tmp/ccKfu4xD.o(.text+0x36b):/home/jayesh/l4/tool/twiddler/twiddler.c:231: undefined reference to `bfd_check_format' /tmp/ccKfu4xD.o(.text+0x380):/home/jayesh/l4/tool/twiddler/twiddler.c:233: undefined reference to `bfd_map_over_sections' /tmp/ccKfu4xD.o(.text+0x388):/home/jayesh/l4/tool/twiddler/twiddler.c:237: undefined reference to `bfd_close' /tmp/ccKfu4xD.o(.text+0x424):/home/jayesh/l4/tool/twiddler/twiddler.c:227: undefined reference to `bfd_perror' collect2: ld returned 1 exit status make: *** [twiddler_x86] Error 1 Any suggestions? -- Jayesh

3 2

IPC Timeouts
by Ronald Aigner 26 Feb '05

26 Feb '05

Hi, I am directing this question to both, the Karlsruhe and the Dresden, L4 mailing list, because I know both are working on new L4 specifications. (Background:) I am working with L4 in Dresden on real-time systems, which become fairly complex lately. One of the questions, which began to bother me more and more, is: What is the use of finite IPC timeouts? Ideally sending an IPC should be immediate (zero timeout) or should be performed eventually (infinite timeout). The only (useful) application of finite timeouts, I have seen so far, is the combination of multiple tasks in a single threaded server. That is waiting for IPC and for a regularly appearing timer event. (This sometimes implied adjusting the IPC timeout by the time used between the IPC waits.) Otherwise the use of finite timeouts is rather inconvenient, since the time used for the timeout depends on the whole surrounding system (software and hardware) and is thus impractical. I'm personally convinced that you do not need finite IPC timeouts. A single bit differentiating zero and infinte timeouts should be sufficient. To imitate the concurrent waiting for an IPC or timer event one could set up a timer with the kernel and inculde the "timer-source" into the receive scope of the wait IPC. Timer events can be dropped if the receiver is not ready. This would also simplify the tasks using IPC timeouts as timer event source. Coming back to my questions: What is the use of finite timeouts? Or maybe the question should be: Would it simplify kernel (and user land) design if seperating the concepts of finite timeouts and IPC? If you have reasons to include finite timeouts into future versions of the L4 Specification, please convince me. Thanks, Ron. -- Ronald Aigner ra3(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/

8 20

Linking a L4 library with a L4Linux app?
by Leon Brits 25 Feb '05

25 Feb '05

Hi all, I've been using a common library linked between three tasks in L4. I need to link this library with an application in L4Linux too also share info like the three L4 tasks has been doing. I've tried almost every variation off the Makefile I could think off, but the compiler always complain about stuff regarding library L4RM and L4DM_[MEM/PHYS] which I must include. The library also uses Semaphore- and Threads libraries. Any suggestions/reference/examples as to what to do to change a complex L4 library to be linked into a Linux application would be appreciated. Thanx Leon

4 12

deprecated practices in grub package - cause problem with gcc 3.4.2
by Jayesh Salvi 24 Feb '05

24 Feb '05

I recently installed Fedora Core 3 and tried to compile the grub package for L4 using gcc 3.4.2, I got some trivial compilation errors. Upon trying the compilation on different machine with gcc 3.1 I found some code following deprecated practices that escapes as warnings in < 3.4.2 but throws compilation errors with 3.4.2. Here are three such case I found in the grub package. If this is indeed the case it might be helpful to make the necessary changes to the repository code. ------------------------------------------------------------------------ ------------------------------------------------------------------ 1) stage2/builtins.c for gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3): builtins.c:886: error: missing terminating " character builtins.c:887: error: `Version' undeclared (first use in this function) builtins.c:887: error: (Each undeclared identifier is reported only once builtins.c:887: error: for each function it appears in.) builtins.c:887: error: syntax error before ':' token builtins.c:887:20: invalid suffix "x" on integer constant for gcc version 3.1: builtins.c:886:20: warning: multi-line string literals are deprecated 2)stage2/fsys_reiserfs.c for gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3): typedef unsigned int __u32; __u32 long j_mount_id; gives this error: fsys_reiserfs.c:115: error: long, short, signed or unsigned used invalidly for `j_mount_id' gcc version 3.1:allows it 3)stage2/smp-imps.c For switch-case construct: switch(i){ Case 1: break; ... Default: } 3.1 gives: warning: deprecated use of label at end of compound statement 3.4.2 will not allow this: smp-imps.c:437: error: label at end of compound statement ------------------------------------------------------------------------ ------------------------------------------------------------------ After changing the files and getting over the compilation errors I get some linking errors. Here is the trace: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../stage1 -Wall -Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -malign-jumps=1 -malign-loops=1 -malign-functions=1 -Wundef -Os -fno-builtin -nostdinc -DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DFSYS_EXT2FS=1 -DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -DFSYS_VSTAFS=1 -DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-md5.o `test -f md5.c || echo './'`md5.c md5.c:1: warning: -malign-loops is obsolete, use -falign-loops md5.c:1: warning: -malign-jumps is obsolete, use -falign-jumps md5.c:1: warning: -malign-functions is obsolete, use -falign-functions gcc -g -o pre_stage2.exec -nostdlib -Wl,-N -Wl,-Ttext -Wl,8200 pre_stage2_exec-asm.o pre_stage2_exec-bios.o pre_stage2_exec-boot.o pre_stage2_exec-builtins.o pre_stage2_exec-common.o pre_stage2_exec-char_io.o pre_stage2_exec-cmdline.o pre_stage2_exec-disk_io.o pre_stage2_exec-gunzip.o pre_stage2_exec-fsys_ext2fs.o pre_stage2_exec-fsys_fat.o pre_stage2_exec-fsys_ffs.o pre_stage2_exec-fsys_minix.o pre_stage2_exec-fsys_reiserfs.o pre_stage2_exec-fsys_vstafs.o pre_stage2_exec-hercules.o pre_stage2_exec-serial.o pre_stage2_exec-smp-imps.o pre_stage2_exec-stage2.o pre_stage2_exec-md5.o pre_stage2_exec-builtins.o(.text+0x138b): In function `install_func': /home/jayesh/grub/stage2/builtins.c:1801: undefined reference to `memcpy' pre_stage2_exec-builtins.o(.text+0x144b):/home/jayesh/grub/stage2/builti ns.c:1846: undefined reference to `memcpy' pre_stage2_exec-builtins.o(.text+0x2b17): In function `setup_func': /home/jayesh/grub/stage2/builtins.c:3672: undefined reference to `memcpy' collect2: ld returned 1 exit status make[2]: *** [pre_stage2.exec] Error 1 make[2]: Leaving directory `/home/jayesh/grub/stage2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jayesh/grub' make: *** [all] Error 2 My versions of gcc and ld are as follows: [jayesh@orion grub]$ ld -v GNU ld version 2.15.92.0.2 20040927 [jayesh@orion grub]$ gcc -v Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux Thread model: posix gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3) I am not sure what is wrong with the linking of memcpy function. Please advise. Thanks. Jayesh

2 1

Re: deprecated practices in grub package - cause problem with gcc 3.4.2
by Tiago João Portela Jorge 24 Feb '05

24 Feb '05

>I recently installed Fedora Core 3 and tried to compile the grub package >for L4 using gcc 3.4.2 don't use gcc 3.x to compile Grub. It has many things that aren't supported in earlier versions like strings in printfs scattered through several lines. My advice to you is use gcc 2.95. Also check if you have ncurses installed in your system. Use synaptic ;). It's easier. -- Tiago Jorge

1 0

OSKit socket example compilation problem
by Tiago Jorge 23 Feb '05

23 Feb '05

hello... As described in this paper*(**Using the OSKit as a base for L4 applications), i'm trying to use the oskit to have networking support in a L4 server. When i try to build the oskit example, built in the paper, pingreply.c, i get the following errors: * *PWD=/home/tiago/l4/pkg/testecom/server/src/OBJ-x86_586-l4v2 make -C OBJ-x86_586-l4v2 -f Makefile make[1]: Entrando no diretório `/home/tiago/l4/pkg/testecom/server/src/OBJ-x86_586-l4v2' ... Compiling main.o LD_PRELOAD=/home/tiago/l4/tool/gendep/libgendep.so GENDEP_TARGET=main.o GENDEP_BINARY=cpp0 gcc-2.95 -c -DRAM_BASE=0x0 -DSYSTEM_x86_586_l4v2 -DARCH_x86 -DCPUTYPE_586 -DL4API_l4v2 -I../../../idl/OBJ-x86-l4v2 -I../../../../../include/x86/l4v2 -I/home/tiago/drops/include/x86/l4v2 -I../../../../../include/l4v2 -I/home/tiago/drops/include/l4v2 -I../../../../../include/x86 -I/home/tiago/drops/include/x86 -I../../../../../include -I/home/tiago/drops/include -nostdinc -DOSKIT -I../../../../../../oskit10/freebsd/libc/include -I../../../../../../oskit10/freebsd/3.x/src/include -I../../../../../../oskit10/freebsd/3.x/src/sys -I../../../../../../oskit10 -I../../../../../include/c++/2.95 -I../../../../../include/c++/2.95/drops -I/home/tiago/drops/include/oskit10 -I/home/tiago/drops/include/oskit10/oskit/freebsd -I/home/tiago/drops/include/c++/2.95 -I/home/tiago/drops/include/c++/2.95/drops -I/usr/lib/gcc-lib/i386-linux/2.95.4/include -gstabs+ -g -O2 -fno-strict-aliasing -march=i586 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations /home/tiago/l4/pkg/testecom/server/src/main.c -o main.o In file included from ../../../../../../oskit10/oskit/c/netinet/in.h:46, from ../../../../../../oskit10/oskit/net/bootp.h:24, from /home/tiago/l4/pkg/testecom/server/src/bootp.h:30, from /home/tiago/l4/pkg/testecom/server/src/main.c:49: ../../../../../../oskit10/oskit/machine/endian.h:82: warning: `__word_swap_long' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:74: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/machine/endian.h:99: warning: `__byte_swap_long' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:91: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/machine/endian.h:107: warning: `__byte_swap_word' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:99: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/machine/endian.h:119: warning: `NTOHL' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:111: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/machine/endian.h:120: warning: `NTOHS' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:112: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/machine/endian.h:121: warning: `HTONL' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:113: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/machine/endian.h:122: warning: `HTONS' redefined /home/tiago/drops/include/oskit10/oskit/freebsd/machine/endian.h:114: warning: this is the location of the previous definition In file included from ../../../../../../oskit10/oskit/net/bootp.h:24, from /home/tiago/l4/pkg/testecom/server/src/bootp.h:30, from /home/tiago/l4/pkg/testecom/server/src/main.c:49: ../../../../../../oskit10/oskit/c/netinet/in.h:104: warning: `INADDR_ANY' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:258: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:105: warning: `INADDR_BROADCAST' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:260: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:124: warning: `IN_CLASSA' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:232: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:130: warning: `IN_CLASSB' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:238: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:136: warning: `IN_CLASSC' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:244: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:141: warning: `IN_CLASSD' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:249: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:147: warning: `IN_EXPERIMENTAL' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:255: warning: this is the location of the previous definition ../../../../../../oskit10/oskit/c/netinet/in.h:148: warning: `IN_BADCLASS' redefined ../../../../../../oskit10/freebsd/3.x/src/sys/netinet/in.h:256: warning: this is the location of the previous definition In file included from ../../../../../../oskit10/oskit/c/netinet/in.h:46, from ../../../../../../oskit10/oskit/net/bootp.h:24, from /home/tiago/l4/pkg/testecom/server/src/bootp.h:30, from /home/tiago/l4/pkg/testecom/server/src/main.c:49: ../../../../../../oskit10/oskit/machine/endian.h:70: parse error before `__extension__' ../../../../../../oskit10/oskit/machine/endian.h:70: parse error before `:' ../../../../../../oskit10/oskit/machine/endian.h:70: warning: type defaults to `int' in declaration of `__X' ../../../../../../oskit10/oskit/machine/endian.h:70: warning: data definition has no type or storage class ../../../../../../oskit10/oskit/machine/endian.h:70: parse error before `}' ../../../../../../oskit10/oskit/machine/endian.h:71: parse error before `__extension__' ../../../../../../oskit10/oskit/machine/endian.h:71: parse error before `:' ../../../../../../oskit10/oskit/machine/endian.h:71: warning: type defaults to `int' in declaration of `__X' ../../../../../../oskit10/oskit/machine/endian.h:71: warning: data definition has no type or storage class ../../../../../../oskit10/oskit/machine/endian.h:71: parse error before `}' ../../../../../../oskit10/oskit/machine/endian.h:72: parse error before `__extension__' ../../../../../../oskit10/oskit/machine/endian.h:72: parse error before `:' ../../../../../../oskit10/oskit/machine/endian.h:72: warning: type defaults to `int' in declaration of `__X' ../../../../../../oskit10/oskit/machine/endian.h:72: warning: data definition has no type or storage class ../../../../../../oskit10/oskit/machine/endian.h:72: parse error before `}' ../../../../../../oskit10/oskit/machine/endian.h:73: parse error before `__extension__' ../../../../../../oskit10/oskit/machine/endian.h:73: parse error before `:' ../../../../../../oskit10/oskit/machine/endian.h:73: warning: type defaults to `int' in declaration of `__X' ../../../../../../oskit10/oskit/machine/endian.h:73: warning: data definition has no type or storage class ../../../../../../oskit10/oskit/machine/endian.h:73: parse error before `}' In file included from ../../../../../../oskit10/oskit/net/bootp.h:24, from /home/tiago/l4/pkg/testecom/server/src/bootp.h:30, from /home/tiago/l4/pkg/testecom/server/src/main.c:49: ../../../../../../oskit10/oskit/c/netinet/in.h:96: redefinition of `struct in_addr' ../../../../../../oskit10/oskit/c/netinet/in.h:111: redefinition of `struct sockaddr_in' In file included from /home/tiago/l4/pkg/testecom/server/src/main.c:49: /home/tiago/l4/pkg/testecom/server/src/bootp.h:100: warning: function declaration isn't a prototype /home/tiago/l4/pkg/testecom/server/src/main.c:70: warning: no previous prototype for `fingerclient' /home/tiago/l4/pkg/testecom/server/src/main.c:141: warning: no previous prototype for `dateserver' /home/tiago/l4/pkg/testecom/server/src/main.c: In function `main': /home/tiago/l4/pkg/testecom/server/src/main.c:279: warning: implicit declaration of function `get_ipinfo' make[1]: ** [main.o] Erro 1 make[1]: Saindo do diretório `/home/tiago/l4/pkg/testecom/server/src/OBJ-x86_586-l4v2' make: ** [OBJ-x86_586-l4v2] Erro 2 * *The BID is including doubled headers. I've tried to create a costum mode in modes.inc and removing some include dirs but it didn't worked as well, so i have came back to l4env_freebsd. How can i solve this problem? thanks in advance Tiago Jorge ** * **

2 1

RE: problem with run-l4
by Jayesh Salvi 23 Feb '05

23 Feb '05

Twiddler doesn't compile. How do I get bfd.h and dis-asm.h ? Didn't find them in l4 source. Thenks Jayesh > > There's a little trick involved here. Such binaries need to be modified > for 2.6, use the tool in l4/tool/twiddler for that. > >

2 1

Problem: Running L4Linux under Fiasco-UX
by Stefan Kalkowski 23 Feb '05

23 Feb '05

Hi, i try to test L4Linux using Fiasco-UX. I'm using the script lx in l4/tool/runux and everything runs fine except when the kerneltask gets started. I get an unhanled trap with trapnumber 13. I don't know what that number means. here is my output: ./lx con /daten/fiasco/l4/kernel/fiasco/build/fiasco -m 256 -symbols /daten/fiasco/l4/kernel/fiasco/build/Symbols -lines /daten/fiasco/l4/kernel/fiasco/build/Lines -rmgr /daten/fiasco/l4/bin/x86_586/l4v2/rmgr-ux -symbols -lines task modname "L4Linux task" -sigma0 /daten/fiasco/l4/bin/x86_586/l4v2/sigma0-ux -fb_program /daten/fiasco/l4/kernel/fiasco/build/ux_con -irq0 /daten/fiasco/l4/kernel/fiasco/build/irq0 -t 32768 -G 640x480@16 -l /daten/fiasco/l4/bin/x86_586/l4v2/names -l /daten/fiasco/l4/bin/x86_586/l4v2/log -l /daten/fiasco/l4/bin/x86_586/l4v2/dm_phys -l /daten/fiasco/l4/bin/x86_586/l4v2/simple_ts -l /daten/fiasco/l4/bin/x86_586/l4v2/fuxfprov -n9 -l /daten/fiasco/l4/bin/x86_586/l4v2/rtc-ux -n10 -l /daten/fiasco/l4/bin/x86_586/l4v2/l4exec -l /daten/fiasco/l4/bin/x86_586/l4v2/con-ux -n12 -l /daten/fiasco/l4/bin/x86_586/l4v2/loader /daten/fiasco/l4/bin/x86_586/l4v2/run /daten/fiasco/l4/cfg/l4linux26.ux Fiasco-UX on Linux 2.6.8 (i686) Native Syscall Map: 0x1600 Mapped 256 MB Memory + 4096 KB Framebuffer + 4 MB Input Area on FD 3 Loading Module 0x00090000-0x00094e00 [/daten/fiasco/l4/bin/x86_586/l4v2/sigma0-ux] Loading Module 0x00100000-0x001c72c0 [/daten/fiasco/l4/bin/x86_586/l4v2/rmgr-ux] Copying Module 0x0ea66000-0x0ea8419f [/daten/fiasco/l4/kernel/fiasco/build/Symbols] Copying Module 0x0ea39000-0x0ea65d46 [/daten/fiasco/l4/kernel/fiasco/build/Lines] Copying Module 0x0ea2f000-0x0ea38174 [/daten/fiasco/l4/bin/x86_586/l4v2/names] Copying Module 0x0ea24000-0x0ea2e174 [/daten/fiasco/l4/bin/x86_586/l4v2/log] Copying Module 0x0ea0e000-0x0ea23174 [/daten/fiasco/l4/bin/x86_586/l4v2/dm_phys] Copying Module 0x0ea02000-0x0ea0d174 [/daten/fiasco/l4/bin/x86_586/l4v2/simple_ts] Copying Module 0x0e9dd000-0x0ea01174 [/daten/fiasco/l4/bin/x86_586/l4v2/fuxfprov] Copying Module 0x0e9d5000-0x0e9dc174 [/daten/fiasco/l4/bin/x86_586/l4v2/rtc-ux] Copying Module 0x0e9a8000-0x0e9d4174 [/daten/fiasco/l4/bin/x86_586/l4v2/l4exec] Copying Module 0x0e97f000-0x0e9a7174 [/daten/fiasco/l4/bin/x86_586/l4v2/con-ux] Copying Module 0x0e954000-0x0e97e174 [/daten/fiasco/l4/bin/x86_586/l4v2/loader] Bootstrapping... Welcome to Fiasco(ux)! DD-L4(v2)/x86 microkernel (C) 1998-2005 TU Dresden Rev: Thu Jan 27 21:21:35 2005 compiled with gcc 3.3.5 for Intel Pentium Starting Framebuffer: 640x480@16 CPU: AuthenticAMD (6:8:1:0) Model: Athlon (Thoroughbred) at 1243 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: 20480 bytes (5 pages) SIGMA0: Hello! Found Fiasco: KIP syscalls: yes. Allocated 68kB for maintenance structures. RMGR: Hello! running on Fiasco bootloader loaded 9 modules at 0e954000-0ea841a0 L4 symbols at 0e935000-0e9531a1 (120kB), lines at 0e908000-0e934d46 (179kB) total RAM size = 261120 KB (reported by bootloader) received 239296 KB RAM from sigma0 1108 KB reserved for RMGR received no I/O ports attached irqs = [ <!0> 1 2 3 4 5 6 7 8 9 a b c d e f ] RMGR: Parsing config. WARNING: couldn't find modname L4Linux task, only storing it's quota configured task 0x0e: [ m:0,ffffffff,ffffffff hm:0,ffffffff,ffffffff t:0,ffff,ffff i:ffff lmcp:ffff s:0,ff,ff mcp:ff prio:10 small:ff ] log_mask: 00000000, log_types: 00000000 RMGR: Starting tasks. #05: loading "/daten/fiasco/l4/bin/x86_586/l4v2/names " from 0ea2f000-0ea38174 to [ 00200000-00206d80 00207000-00210000 ] starting at entry 00200000 via trampoline page code 0000c470 #06: loading "/daten/fiasco/l4/bin/x86_586/l4v2/log" from 0ea24000-0ea2e174 to [ 00400000-00407040 00408000-0043d000 ] starting at entry 00400000 via trampoline page code 0000d46c #07: loading "/daten/fiasco/l4/bin/x86_586/l4v2/dm_phys " from 0ea0e000-0ea23174 to [ 01500000-01512860 01513000-0151d000 ] starting at entry 01500000 via trampoline page code 0000e470 #08: loading "/daten/fiasco/l4/bin/x86_586/l4v2/simple_ts " from 0ea02000-0ea0d174 to [ 01400000-01408660 01409000-01417000 ] starting at entry 01400000 via trampoline page code 0000f474 #09: loading "/daten/fiasco/l4/bin/x86_586/l4v2/fuxfprov" from 0e9dd000-0ea01174 to [ 00500000-00521d4b 00522000-0053e000 ] starting at entry 00500000 via trampoline page code 00010470 #0a: loading "/daten/fiasco/l4/bin/x86_586/l4v2/rtc-ux" from 0e9d5000-0e9dc174 to [ 01080000-010849a0 01085000-0108a000 ] starting at entry 01080000 via trampoline page code 00011470 #0b: loading "/daten/fiasco/l4/bin/x86_586/l4v2/l4exec" from 0e9a8000-0e9d4174 to [ 01100000-01129a6b 0112a000-01134000 ] starting at entry 01100000 via trampoline page code 00012470 #0c: loading "/daten/fiasco/l4/bin/x86_586/l4v2/con-ux " from 0e97f000-0e9a7174 to [ 00b00000-00b24a6b 00b25000-00b30000 ] starting at entry 00b00000 via trampoline page code 00013470 #0d: loading "/daten/fiasco/l4/bin/x86_586/l4v2/loader /daten/fiasco/l4/bin/x86_586/l4v2/run /daten/fiasco/l4/cfg/l4linux26.ux" from 0e954000-0e97e174 to [ 01300000-0132606b 01327000-01339000 ] starting at entry 01300000 via trampoline page code 000144b8 names | Fiasco detected, registering thread names at kernel fuxfprov| OSKit support: using 128KB at 0x00100000 as heap (growing) fuxfprov| File provider started, registered as 9.02 exec | OSKit support: using 4096KB at 0x00400000 as heap (growing) con | OSKit support: using 128KB at 0x00100000 as heap con | Character size is 8x14, font has 256 characters con | VESA reports 640x480@16 (0000) [4096kB] con | Color mapping: red=11:5 green=5:6 blue=0:5 res=0:0 con | No supported accelerated graphics card detected con | Mapping I/O video mem c0000000 => 00400000+000000 [4096kB] con | Using MMXEXT for colorspace transform con | l4input_init: start con | map_inputmemory: paddr = 0xc0400000 con | Input memory page mapped to 0x00c00000 loader | OSKit support: using 128KB at 0x00100000 as heap loader | Can't map tbuf status page (map=00004000, error=00 result=00004000) con | Started input interrupt thread C.03! con | Running as C.02. Video mode is 640x480@16. fuxfprov| open "/daten/fiasco/l4/bin/x86_586/l4v2/run" by D.02 loader | "/daten/fiasco/l4/bin/x86_586/l4v2/run" is a valid binary image loader | Setting libpath to /daten/fiasco/l4/bin/x86_586/l4v2/ exec | run: Loading exec | run: Merging psec 01310000-01312000 with psec 0130c000-01311000 exec | run: Has no symbols exec | run: Has no lines exec | libloader.s.so: Loading fuxfprov| open "/daten/fiasco/l4/bin/x86_586/l4v2//libloader.s.so" by B.02 exec | libloader.s.so: Saved 21713 bytes of symbols exec | libloader.s.so: Relocating to 0000e000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 000058d0 => 000138d0 exec | libloader.s.so: Setting section flag 0800 exec | run: Setting section flag 0800 loader | run: Starting l4env-style application loader | run,#f: Starting at l4loader_init (00014080) exec | run: Linking exec | run: Relocating entry 01300000 => 01300000 exec | run: Packed 17777 bytes of symbols exec | run: Packed 68105 bytes of lines loader | run,#f: Continue at l4env_init (00014090, libloader.s.so) fuxfprov| open "/daten/fiasco/l4/cfg/l4linux26.ux" by D.02 loader | sleeping for 2000 ms run | OSKit support: using 256KB at 0x00040000 as heap (growing) con | vc_loop(): vc[1] running as C.04 con | vc_open_out(): vc[1] 640x480@16, gmode:0x15 run | contxt_init(): 640x462, cols:80, lines:33, sb_lines:1033 exec | vmlinuz26.ux: Loading fuxfprov| open "/daten/fiasco/l4linux-2.6/vmlinuz26.ux" by B.02 exec | vmlinuz26.ux: Saved 768423 bytes of symbols exec | libloader.s.so: Relocating to 0000e000 exec | libloader.s.so: Linking exec | libloader.s.so: Relocating entry 000058d0 => 000138d0 exec | libloader.s.so: Setting section flag 0800 exec | vmlinuz26.ux: Setting section flag 0800 loader | vmlinuz26.ux: Starting l4env-style application loader | vmlinuz26.ux,#10: Starting at l4loader_init (00014080) exec | vmlinuz26.ux: Linking exec | vmlinuz26.ux: Relocating entry 003ff000 => 003ff000 exec | vmlinuz26.ux: Packed 616018 bytes of symbols exec | vmlinuz26.ux: Packed 1629285 bytes of lines loader | vmlinuz26.ux,#10: Continue at l4env_init (00014090, libloader.s.so) l4lx | crt0_construction called. l4lx | ======> L4Linux 2.6 starting... <======== l4lx | Binary name: vmlinuz26.ux l4lx | Kernel command line (9 args): mem=128M noreplacement no-hlt video=l4f l4lx : b:refreshsleep:2000 root=1:0 load_ramdisk=1 ramdisk_size=16384 l4env_ l4lx : rd=/daten/fiasco/drops-rd.rd panicblink=0 l4lx | My DMphys is at 07.00 l4lx | My region mapper is at 10.00 l4lx | My code starts at 0x003ff000 and ends at 0x006e2190 [2956 KiB]. l4lx | Semaphore thread ID: 10.01 l4lx | Areas: l4lx | Text: 003ff000 - 0060c000 [2100kB] (a bit longer) l4lx | Data: 0060c000 - 00651300 [276kB] l4lx | Initdata: 00654000 - 00684000 [192kB] l4lx | BSS: 00684008 - 006e2190 [376kB] l4lx | l4env_linux_startup thread 3. l4lx_thread_create: Created thread 10.03 (Linux server) l4lx | main thread will be 10.03 l4lx | l4env_register_pointer_section: addr = 3ff000 size = 2646016 l4lx | with-init: virt: 0x003ff000 to 0x00684fff [2584 KiB] l4lx | with-init: Number of physical regions: 1, 2646016 Bytes l4lx | with-init: 1: Phys: 0x00633000 to 0x008b9000, Size: 6089048 l4lx | main thread: received startup message. KERNEL: 10.3 (tcb=20401800) killed: Unhandled trap EAX 00000010 EBX 0060d0a0 ECX 00653f3c EDX 00080000 ESI 00200c01 EDI 00080000 EBP 00653fc4 ESP 00653f8c EIP 0065b31d EFLAGS 00210202 CS 0002 SS 007b DS 007b ES 007b FS 0000 GS 0000 trapno 13, error 00000000, from user mode (internal event regarding GDT entry no. 0x00) l4lx | Main thread running, waiting... when i diassembe the adress i get the following: --Interception--------------------------------------ESP:200007a0 EIP:000444aa (0.00) jdb: u task=10 addr=65b31d /daten/fiasco/l4/include/x86/l4/sys/utcb.h:97 0065b31d mov %gs:0x0,%eax /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:491 0065b323 movl $0x1,(%eax) /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:495 0065b329 call 0x65b200 <setup_stack> /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:496 0065b32e call 0x6547e0 <start_kernel> /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:497 0065b333 add $0x2c,%esp 0065b336 pop %ebx 0065b337 pop %esi 0065b338 pop %edi 0065b339 pop %ebp 0065b33a ret 0065b33b nop 0065b33c lea 0(%esi,1),%esi <l4x_l4io_init>: /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:501 0065b340 push %ebp /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:505 0065b341 xor %eax,%eax /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:501 0065b343 mov %esp,%ebp 0065b345 sub $0xc,%esp /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:505 0065b348 mov %eax,4(%esp,1) 0065b34c lea -4(%ebp),%eax /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:502 0065b34f movl $0xffffffff,-4(%ebp) /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:505 0065b356 mov %eax,(%esp,1) 0065b359 call 0x4d5890 <l4io_init> 0065b35e test %eax,%eax 0065b360 je 0x65b37d /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:506 0065b362 <enter_kdebug ("Error calling l4io_init!") /daten/fiasco/l4linux-2.6/arch/l4/kernel/main.c:507 0065b37d mov %ebp,%esp 0065b37f pop %ebp 0065b380 ret 0065b381 jmp 0x65b390 <fprov_load_initrd> 0065b383 nop dis: <0065b31d> task 10 [Headers] [AT&T] <Space>=lines mode but that doesn't help me. For any advice i would be very thankful greetings Stefan Kalkowski -- PGP-Schlüssel zu finden unter: https://www.inf.tu-dresden.de/~sk852421

2 1

dm_generic build problems
by Björn Fischer 23 Feb '05

23 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, when trying to build drops on my machine (Gentoo linux, gcc 3.3.5) I encountered the following errors: - ------------------------------- make[2]: Entering directory `/home/bjoern/cvs/l4/pkg/dm_generic/idl' PWD=/home/bjoern/cvs/l4/pkg/dm_generic/idl/OBJ-x86-l4v2 make -C OBJ-x86-l4v2 -f Makefile make[3]: Entering directory `/home/bjoern/cvs/l4/pkg/dm_generic/idl/OBJ-x86-l4v2' ~ ... Generating dm_generic-server.c LD_PRELOAD=/home/bjoern/cvs/l4/tool/gendep/libgendep.so GENDEP_TARGET="dm_generic-server.c dm_generic-server.h dm_generic-client.c dm_generic-client.h dm_generic-sys.h" GENDEP_BINARY=cpp0 GENDEP_DEPFILE=.dm_generic.idl.d CC=gcc false - -fforce-corba-alloc -fl4types -P-DRAM_BASE=0x0 -P-DSYSTEM_x86_l4v2 - -P-DARCH_x86 -P-DCPUTYPE_ -P-DL4API_l4v2 - -P-I../../../../include/x86/l4v2 - -P-I/home/bjoern/src/drops/include/x86/l4v2 - -P-I../../../../include/l4v2 -P-I/home/bjoern/src/drops/include/l4v2 - -P-I../../../../include/x86 -P-I/home/bjoern/src/drops/include/x86 - -P-I../../../../include -P-I/home/bjoern/src/drops/include -P-nostdinc - -P-DOSKIT -P-I../../../../../oskit10 - -P-I../../../../../oskit10/oskit/c - -P-I/home/bjoern/src/drops/include/oskit10 - -P-I/home/bjoern/src/drops/include/oskit10/oskit/c - -P-I/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/include ../dm_generic.idl make[3]: *** [dm_generic-server.c] Error 1 make[3]: Leaving directory `/home/bjoern/cvs/l4/pkg/dm_generic/idl/OBJ-x86-l4v2' make[2]: *** [OBJ-x86-l4v2] Error 2 make[2]: Leaving directory `/home/bjoern/cvs/l4/pkg/dm_generic/idl' make[1]: *** [idl] Error 2 make[1]: Leaving directory `/home/bjoern/cvs/l4/pkg/dm_generic' make: *** [dm_generic.headers] Error 2 bash-2.05b$ - --------------------------------- Since there is no error message I could react on (like "missing file xyz" or something) I just don't know how to handle this. Does anybody have an Idea about that? Many thanks and greetings Björn Fischer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCGe1QTpwRRbjCovARAtVeAKCS6ekiBf12nv8DfMdLaDRPTUdc7ACeKrUL BQv40p8thr3Vt6J1RJZufk8= =3rjt -----END PGP SIGNATURE-----

3 3

Re: Using the OSKit POSIX Thread Library
by Tiago João Portela Jorge 22 Feb '05

22 Feb '05

>>On Mon Feb 21, 2005 at 22:41:26 +0000, Tiago Jorge wrote: >> So if i want to use pthreads, i can't. >> Regarding to locks and to threads i can replace them by L4threads lib, that >> includes locks and threads. but what do you recommend to replace the usage >> of conditional variables? >I'm not really familiar with these things. What's the problem, or what >would you need to implement it? i have worked out a solution... but thank you anyway :) -- Tiago Jorge

1 0