- l4-hackers - OS Site

libgendep on Ubuntu 11.10
by Christian Helmuth 03 Apr '12

03 Apr '12

Hi, with current SVN (r38) I get the following error: gcc -fPIC -Wall -pedantic -g -m64 -c /plain/krishna/src/genode/genode.git/base-foc/contrib/l4/tool/gendep/deptrack.c -o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/deptrack.64.o gcc -fPIC -Wall -pedantic -g -m64 -c /plain/krishna/src/genode/genode.git/base-foc/contrib/l4/tool/gendep/syscall.c -o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/syscall.64.o mkdir -p /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64 gcc -m64 -shared -Wl,-soname,/plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64/libgendep.so -ldl -o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64/libgendep.so /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/deptrack.64.o /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/syscall.64.o /usr/local/genode-gcc/bin/genode-x86-gcc: symbol lookup error: /plain/krishna/build/genode.foc_x86_32/l4/tool/gendep/64/libgendep.so: undefined symbol: dlsym The attached patch fixed the issue for me and I'd like to share it here ;-) Greets -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 3

L4Android kernel didn't intialize L4 stack for the server thread.
by Mai, Haohui 03 Apr '12

03 Apr '12

Hi, It seems that I found a bug in the latest version of L4Android kernel. I'm familiar enough with the code base so your comments are highly appreciated. The main thread for L4Linux (i.e., the thread running l4x_server_loop()) didn't initialize l4x_stack before execution. Therefore, this thread crashes whenever it calls cli() / sti(). Calling vmalloc() and kmalloc() can reproduce this bug reliably. Here is a patch to fix this problem. ~Haohui --- a/arch/l4/kernel/main.c +++ b/arch/l4/kernel/main.c @@ -2501,6 +2501,8 @@ int __init_refok L4_CV main(int argc, char **argv) * for these areas so far */ //l4x_register_pointer_section(&_edata, 0, "data"); + l4x_stack_setup(current_thread_info(), l4_utcb(), 0); + /* Send start message to main thread. */ l4_ipc_send(l4lx_thread_get_cap(main_id), l4_utcb(), l4_msgtag(0, 0, 0, 0), L4_IPC_NEVER);

3 3

Question on sending capability through IPC
by Mai, Haohui 02 Apr '12

02 Apr '12

Hi, I'm a little bit confused by how Fiasco.OC sending capabilities through IPC. Particularly, it seems that one has to pack the capability in message register, rather than buffer register. Here is a code sending some capability to the client, which works with Fiasco.OC: l4_utcb_t * u = l4_utcb(); l4_utcb_mr_u(u)->mr[0] = ipc_id; l4_utcb_mr_u(u)->mr[1] = L4_ITEM_MAP; l4_utcb_mr_u(u)->mr[2] = l4_obj_fpage(cap, 0, L4_FPAGE_RWX).raw; l4_utcb_br_u(u)->bdr = 0; tag = l4_msgtag(label, 1, 1, 0); ipc_call(...); Notice that the capability is assigned into mr[1] and mr[2], but not br[1] and br[2]. It seems that this behavior is controlled by the constructor of L4_snd_item_iter, at kern/l4_buf_iter.cpp:52 explicit L4_snd_item_iter(Utcb const *utcb, unsigned offset) : _buf(&utcb->values[offset]), _max(&utcb->values[Utcb::Max_words]) {} My question is that whether this is the desired behavior? I didn't find any specification on this. ~Haohui

2 1

ARM and PCI?
by Stefan Fritsch 02 Apr '12

02 Apr '12

Hi, do you know what remains to be done to use PCI on ARM (e.g. Realview in qemu) with L4Re and IO? I guess that io needs some changes to support PCI-IO-Ports mapped into memory. Or should that already work? Cheers, Stefan

2 1

Granting flex pages in Fiasco.OC / L4Re
by Daniel Waddington 30 Mar '12

30 Mar '12

Hi, I am using l4_task_map to map flex pages to a child task. What I would like to do is grant a flex page to a child and remove the mapping from the parent. How do I do this? I have tried using l4_map_obj_control(0,1) for mr[3] on the task map call but this does not seem to help. Thanks in advance, Daniel

3 4

TUD:OS releases DDEKit/Linux
by Hannes Weisbach 30 Mar '12

30 Mar '12

Hi all, DDEKit/Linux was released! DDEKit/Linux uses the Device Driver Environment approach to run dde-linux-2.6 in Linux user space. This allows Linux device drivers to run in Linux user space, including interrupt handling and DMA support. DDEKit/Linux was evaluated using an Intel E1000E NIC and it was possible to saturate an 1GBit/s link. The source code, including dde-linux-2.6 and an E1000E-example are available for download at: http://os.inf.tu-dresden.de/ddekit Best regards, Hannes Weisbach

2 1

[l4linux+ankh] no eth0
by Timur 26 Mar '12

26 Mar '12

Hi all, i,m trying to bind l4linux to ankh. After launching with attached config files, l4linux doesn't see eth0 interface. What am i doing wrong? Log attached. [modules.list] entry L4Linux-mag-x86 roottask moe rom/l4lx-gfx.cfg module l4re module ned module l4lx-gfx.cfg module io module ankh module ankh.vbus module fb-drv module mag module x86-legacy.devs module l4lx-x86.io module vmlinuz module drops-rd.rd -- Galiullin Timur

4 5

Re: Issues with booting L4Linux
by Adam Lackorzynski 26 Mar '12

26 Mar '12

Hi On Thu Mar 22, 2012 at 18:28:17 +0100, Oliver Horst wrote: > I'm currently trying to setup a small test scenario where L4Linux runs in > parallel > with L4Android within Qemu. I managed to build and start L4Android and it > works fine. > However, I didn't succeeded with booting L4Linux, again the build process > worked out > flawlessly, but the boot process quits with the following message: > > vmlinuz | Invalid IO-Port access at pc = 005b9cec port=0x1f7 > vmlinuz | Page fault (non-resolved): pfa=1a8 pc=4947ad > Die message: Trap: 14 > vmlinuz | panic: going to sleep forever, bye This is the IDE driver trying to accses the hardware, and it is not allowed to do so. For your use-case, just disable everything with IDE in the config name in L4Linux. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

Trustzone & Fiasco.OC
by Stefan Kalkowski 23 Mar '12

23 Mar '12

Hello l4-hackers, I'd like to investigate the VM functionality for ARM's TrustZone in Fiasco.OC. I've read the paper of Torsten Frenzel et al. which covers experiments done with ARM TrustZone in Fiasco as a virtualization technique. In that paper they reference a VMM controlling the "normal world" VM(s), but unfortunately I cannot find it in the L4Re or L4Env tree. Is it publicly available, and if so could you please direct me to the right place? Thank you in advance & best regards Stefan -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 2

Issues with booting L4Linux
by Oliver Horst 22 Mar '12

22 Mar '12

Hi All, I'm currently trying to setup a small test scenario where L4Linux runs in parallel with L4Android within Qemu. I managed to build and start L4Android and it works fine. However, I didn't succeeded with booting L4Linux, again the build process worked out flawlessly, but the boot process quits with the following message: vmlinuz | Invalid IO-Port access at pc = 005b9cec port=0x1f7 vmlinuz | Page fault (non-resolved): pfa=1a8 pc=4947ad Die message: Trap: 14 vmlinuz | panic: going to sleep forever, bye I followed the diverse tutorials on the web and built Fiasco.OC, as well as L4Re with their default configurations. In case of L4Linux I tried the default configurations generated by the make targets 'x86-mp_vPCI_defconfig' and 'x86-native_defconfig', both with the same result as above. Please find attached my L4 startup files and the output log for the x86-mp_vPCI_defconfig variant. My Qemu execution command looks like the following: $ qemu -cdrom images/l4linux-x86.iso -boot d -m 512 -serial stdio -enable-kvm Do you have any suggestions how to solve this issue? Best Regards Oliver

1 0

how to start wget example?
by Timur 22 Mar '12

22 Mar '12

Hello! I use attached ankh.lua(defualt), ankh.vbus and wget.lua(default), and receive error http://paste.org.ru/?w335oj Thanks!

4 6

Fiasco.OC development status
by Robert Campbell 21 Mar '12

21 Mar '12

Hey guys, Is Fiasco.OC being actively developed(i.e new and on going research, new features) or is it just being maintained (small adjustments, bug fixes etc...)?

2 1

APIC trigger mode
by Sebastian Sumpf 20 Mar '12

20 Mar '12

Hi there, I have a question regarding the APIC-interrupt mode settings on x86. I see that one has to set the mode externally in Fiasco.OC using the 'l4_icu_set_mode' call. Also I had a look at Nova which seems to program these modes from within the kernel, using edge/high for IRQ 0-15 and level-low for IRQ 16-23. Would that be a valid assumption to program the modes for Fiasco.OC x86 also, or is there an other way to find out the interrupt-trigger modes of IRQs (other than the ones found in ACPI-MADT)? Why is it necessary to set these modes outside the kernel? Thanks a lot, Sebastian

3 3

help l4linux dma usage
by jangwoo 20 Mar '12

20 Mar '12

Hi all. I’m jangwoo. I have some question about l4linux DMA usage. Currently if use dma_alloc_coherent api, it works well. You kwow that “dma_alloc_coherent” get virt addr and phys addr concurrently. But most case of dma usage is to change virt addr into phys addr. Mostly virt addr comes from generic layer of linux kernel. Os it is hard to modify. So, I tried to call virt_to_phys(internal mapping l4x_virt_to_phys), but this function wasn’t direct mapping. I feel like delaying to sync between virt addr and phys addr.(when I check with Trace32) Anyway as “virt_to_phys” have these issues, DMA operation hit miss. Currently l4linux don’t support most dma function. how can I work DMA although it is expedient method? Please. p.s : Not support dma list dma_mmap, ___dma_single_cpu_to_dev, ___dma_page_cpu_to_dev, ___dma_page_dev_to_cpu, dma_map_sg, dma_sync_sg_for_cpu etc thanks all.

1 0

Ankh with l4Linux
by Shashi Sharma 15 Mar '12

15 Mar '12

Hi, I want to enable l4linux to use the Ankh server. But I dont know how to start l4linux so that it can bind to Ankh server. I enabled the l4ankh driver in l4linux. And Following is how I start the Ankh server and l4linux --Ankh----------- -- start ankh loader:startv( {caps = {ankh_service = ankh_clnt:svr(); -- session server vbus = ankh_vbus, -- the virtual bus shm = ankh_shm:m("rws")}, -- shm namespace read/writable log = {"ankh", "g"}, l4re_dbg = L4.Dbg.Warn }, "rom/ankh" ); --L4linux------------------- loader:start( { caps = { log = L4.Env.log:m("rws"), vbus = vbus_l4linux; rtc = rtc_caps.rtc; shm = ankh_shm:m("rws"); ankh = ankh_clnt:create(0,"debug,phys_mac,shm=shm,bufsize=16384"); }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/vmlinuz mem=128M earlyprintk=yes showpfexc=1 console=ttyLv0 tcp,nolock ip=192.168.0.200:192.168.0.115:192.168.0.1:255.255.255.0::eth0: l4x_rd=rom/drops-rd.rd root=1:0 ramdisk_size=20000 init=/bin/sh"); Thanks, Shashi

3 7

NFS boot
by Sartakov A. Vasily 15 Mar '12

15 Mar '12

Hello. I try to use NFS in l4linux and have problem. This happens on ARM and on X86: WARN: Page-fault above task size: pfa=bfdfeb40 pc=4007d760 l4linux | 0: 00009228 4017e2d8 0d696914 00008f38 4: 00000000 40095910 bfdff000 bfdfeb40 l4linux | 8: 40094fb0 00000000 40094fb0 0001702c 12: 00000070 bf977ea8 40083e58 4007d760 l4linux | CPSR: 20000010 Err: 00410007 Kernel panic - not syncing: Attempted to kill init! [<0012ebf8>] (unwind_backtrace+0x0/0xf4) from [<00482c70>] (panic+0x58/0x180) [<00482c70>] (panic+0x58/0x180) from [<00150ee0>] (do_exit+0x5b4/0x670) [<00150ee0>] (do_exit+0x5b4/0x670) from [<00150fd8>] (do_group_exit+0x3c/0xb0) [<00150fd8>] (do_group_exit+0x3c/0xb0) from [<0015bf88>] (get_signal_to_deliver+0x190/0x388) [<0015bf88>] (get_signal_to_deliver+0x190/0x388) from [<00128bb8>] (do_signal+0x88/0x5ac) [<00128bb8>] (do_signal+0x88/0x5ac) from [<0012c31c>] (l4x_user_dispatcher+0x1500/0x2574) [<0012c31c>] (l4x_user_dispatcher+0x1500/0x2574) from [<001276c0>] (kernel_execve+0x5c/0xc0) [<001276c0>] (kernel_execve+0x5c/0xc0) from [<00122558>] (init_post+0x98/0xcc) [<00122558>] (init_post+0x98/0xcc) from [<001001f0>] (kernel_init+0xe4/0x114) [<001001f0>] (kernel_init+0xe4/0x114) from [<00126c18>] (kernel_thread_exit+0x0/0x8) panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye If i boot from other source, I can successful mount NFS root, do one time ls and with next command i will get panic. -- Sartakov A. Vasily

2 1

Re: PowerPC support
by Adam Lackorzynski 05 Mar '12

05 Mar '12

Hi Oliver, On Wed Feb 29, 2012 at 10:11:06 +0100, Oliver Horst wrote: > I've read your reply to last year question about the PowerPC support of > FIASCO [1]. > Is there any progress to be noted on this topic? Unfortunately none. > Further, I'd like to know which actual processor board you targeted the > PowerPC > port to and with that which PowerPC ISA version do you intend to support? One is a 603e one, the other Qemu. At the current stage it probably does not play a big role. Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 2

Serial console with qemu/realview-eb
by Mehdi AICHOUCH 05 Mar '12

05 Mar '12

Hi Adam, By adding the option [kernel fiasco -serial_esc] to conf/module.list, the input of the L4Linux console is working great. Thank very much. Mehdi

1 0

page mapping in l4linux
by jangwoo 01 Mar '12

01 Mar '12

Hi all. I have question about mapping memory page in l4linux. I think “dma_map_page” function seem malfunction in below code. struct page *new_page; u32 linux_phys_addr; new_page = alloc_page(GFP_HIGHUSER | __GFP_ZERO | __GFP_NORETRY | __GFP_NOWARN | __GFP_COLD); linux_phys_addr = dma_map_page(NULL, new_page, 0, PAGE_SIZE, DMA_BIDIRECTIONAL); ////// PAGE_SIZE is 4KB _______________________________________________________________ new_page | linux_phys_addr | correct linux_phys_addr | ----------------|----------------------------|------------------------------ | 0xe54b20 0x325d9000 0x48b54b20 0xe54b40 0x325da000 0x48b54b40 0xe54b60 0x325db000 0x48b54b60 as H/W ram-base is 0x40000000, 0x30000000 base address can’t be mapped. Does anybody know a way to work dma_map_page? Best.

2 1

Serial console with qemu/realview-eb
by Mehdi AICHOUCH 01 Mar '12

01 Mar '12

Hi all, I have the same problem with the serial console in QEMU, I tested the same configuration as you. This my test command. [qemu-system-arm -M realview-eb -cpu arm926 -kernel bootstrap_L4Linux_ARM.elf -m 256 -nographic] All output are OK, but no input. I also tried to use the I/O C standard gets(char *) function, in the "hello" example, but I get an error compilation: "undefined reference to gets". Is there any solution or hint since the first post of the problem and after the answer of Julian. thank you in advance. Mehdi

2 1

PowerPC support
by Oliver Horst 29 Feb '12

29 Feb '12

Hi Adam, I've read your reply to last year question about the PowerPC support of FIASCO [1]. Is there any progress to be noted on this topic? Further, I'd like to know which actual processor board you targeted the PowerPC port to and with that which PowerPC ISA version do you intend to support? Best Regards Oliver [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004603.html

1 0

IRET returned message
by Julian Vetter 16 Feb '12

16 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everybody, can someone explain to me what it means when my L4Linux interrupts and jumps into JDB with the message: - ------------------------------------------------------ CPU 0 [f001239c]: IRET returned [ l4lx.cpu0] jdb: g ------------------------------------------------------ I sometimes get this message, and after that my system hangs and I can't jump back to L4Linux by hitting 'g' in the Debugger. Any help would be appreciated Cheers, Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPPNeTAAoJEOpGAeJlWp7qw9EH/31w3fA+nAvkbDwF2cjr9r47 qz991ninI6SksDh6OD05b/O/BxxB1fZyaSXAmrnewHVIcuP+bGfgplFnKqjfu4RA qo6PzcpGRCEZpsXYiAhqLxnygxpLTLOXtkFKs9VYfaIkPI4q2DQmSexpZBCTHr27 RY8QO2+eeluR4H8ik3NH9C01pGWmRJJU6Z46wRcIfE+0AZ8NvQBOn4RjYfrfTFbI sW1W7UdQiXc3TurvSzuvaL/tAkT7hpDQOlbEhwDO0SWA8KVtFIeWrKLZWMppglzB TxWGCp5w//LMuG/8DuECDr1C/4u9WwP2Gs/PshtEeLCCX9pqRF/fQfobbtsHlaQ= =7Ifo -----END PGP SIGNATURE-----

2 1

Memory sharing between user and kernel
by 안영호 15 Feb '12

15 Feb '12

Hello everyone, I’m trying to apply an asynchronous batch processing of IPC into l4/fiasco to increase the bandwidth of IPC. I think the main problem is the performance of IPC when virtualization is applied to mobile system. To increase the performance of IPC, I try to use the memory sharing between the address space of user library and that of kernel memory. There is a way to access user memory from kernel, but I couldn’t find any way to read kernel memory in user space. At first, I want to know whether it is meaningful to use an asynchronous batch processing of IPC, or not. Second, when my user library tries to use the virtual address of a kernel global variable by passing it to user address space, “unhandled exception: pc=xxxx” occurs. I think that region mapper makes that exception while it’s checking the range of virtual address. If I want to access kernel memory in user address space, what can I do? Maybe it causes security problems and it’s not proper for virtualization. However, in my opinion, some compromise will be needed for the future mobile virtualization system.

2 1

L4Linux direct access
by Riccardo Cecolin 09 Feb '12

09 Feb '12

I'm trying to make a l4linux system access the vga directly without mag, l4con or fbdrv. I compiled it using the default configuration with virtual pci bus enabled, x86-mp_vPCI_defconfig. I'm currently trying on qemu, i see that l4linux recognizes the pci devices and is able to mount the root fs from /dev/hda (i also tried with a ramdisk with same results) and loads the driver of the vga (vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none). But then i get a kernel panic because init (/bin/bash) exited (or didn't execute): l4linux | EX: 0: pc = 0041176a sp = 07829fac trapno = 0xd err/pfa = 0x402 Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: bash Not tainted 3.0.0-l4-svn23 #35 Looking at the binary at 0x41176a i see that the kernel is trying to execute execve but fails with trap 13. ... /src/l4linux/arch/l4/kernel/arch-x86/../../../x86/kernel/sys_i386_32.c:36 411765: b8 0b 00 00 00 mov $0xb,%eax 41176a: cd 80 int $0x80 My config files are the following ones and i also attached a full log, where is my setup wrong? ------ linux-x2.cfg ------ loader = L4.default_loader; local lxname = "vmlinuz"; vbus_l4linux = loader:new_channel(); loader:start({ caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, log = { "io", "red" }, }, "rom/io rom/x86-legacy.devs rom/l4lx-x86-x2.io"); loader:start({ caps = { log = L4.Env.log:m("rws"); vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Info, log = { "l4linux", "blue" }, }, "rom/" .. lxname .. " mem=120M earlyprintk=yes initcall_debug=1 showpfexc=1 root=/dev/hda init=/bin/bash", "allow_cli","all_sects_writable","allow_vga"); ------ l4lx-x86-x2.io ------ l4linux => new System_bus() { PCI0 => new PCI_bus() { host_bridge_dummy => new PCI_dummy_device(); pci_gfx[] => wrap(hw-root.match("PCI/CC_03")); pci_l4x[] => wrap(hw-root.match("PCI/CC_02,PCI/CC_01,PCI/CC_04")); } vgadev => wrap(hw-root.VGA); ps2dev => wrap(hw-root.PS2); } L4 Bootstrapper Build: #1 Fri Feb 3 12:59:44 CET 2012, x86-32, 4.4.5 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000012bfcfff: 306164kB Total RAM: 299MB Moving 11 modules to 1100000 with offset dee000 moving module 11 { 15bd000-25bd000 } -> { 23ab000-33ab000 } moving module 10 { 10d7000-15bcc8a } -> { 1ec5000-23aac8a } moving module 09 { 10d6000-10d612b } -> { 1ec4000-1ec412b } moving module 08 { 10d5000-10d53b7 } -> { 1ec3000-1ec33b7 } moving module 07 { 86a000-10d4428 } -> { 1658000-1ec2428 } moving module 06 { 869000-869278 } -> { 1657000-1657278 } moving module 05 { 66d000-868154 } -> { 145b000-1656154 } moving module 04 { 57e000-66cd17 } -> { 136c000-145ad17 } moving module 03 { 3ba000-57d9ee } -> { 11a8000-136b9ee } moving module 02 { 379000-3b9995 } -> { 1167000-11a7995 } moving module 01 { 312000-378a40 } -> { 1100000-1166a40 } Scanning /fiasco -serial_esc Scanning /sigma0 Scanning /moe rom/linux-x2.cfg Bootloader MMAP: [ 0, 9f400) RAM (1) [ 9f400, a0000) reserved (2) [ f0000, 100000) reserved (2) [ 100000, 12bfd000) RAM (1) [ 12bfd000, 12c00000) reserved (2) [ fffbc000, 100000000) reserved (2) Relocated mbi to [0x2dd000-0x2dd18e] Loading /fiasco Loading /sigma0 Loading /moe find kernel info page... found kernel info page at 0x400000 Regions of list regions [ 0, fff] { 1000} Arch BIOS [ 9f400, 9ffff] { c00} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10a1b3] { a1b4} Sigma0 /sigma0 [ 140000, 18b0df] { 4b0e0} Root /moe [ 2d0000, 2e13e7] { 113e8} Boot bootstrap [ 2dd000, 2dd28b] { 28c} Root Multiboot info [ 300000, 38ffff] { 90000} Kern /fiasco [ 400000, 46bfff] { 6c000} Kern /fiasco [ 136c000, 33aafff] { 203f000} Root Modules Memory [ 12bfd000, 12bfffff] { 3000} Arch BIOS [ fffbc000, ffffffff] { 44000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001dc sp:002dca38 Roottask config ip:001401c4 sp:00000000 Starting kernel /fiasco at 00300824 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2011 TU Dresden Rev: r38 compiled with gcc 4.4.5 for Intel Pentium Pro [] Build: #5 Mon Feb 6 17:25:11 CET 2012 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_FINE_GRAINED_CPUTIME is on Superpages: yes Kmem:: cpu page at 11406000 (4096Bytes) ACPI-Init ACPI: RSDP[0xf8850] r00 OEM:BOCHS. ACPI: RSDT[0x203fdd90] r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ffe70] r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203fdef0] r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203fde10] r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203fddd0] r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203fde10 IO-APIC[ 0]: struct: 0x203fde44 adr=fec00000 IO-APIC[ 0]: pins 24 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 IO-APIC: ovr[ 1] 05 -> 5 IO-APIC: ovr[ 2] 09 -> 9 IO-APIC: ovr[ 3] 0a -> a IO-APIC: ovr[ 4] 0b -> b Allocate cpu_mem @ 0xfdbfa000 Local APIC[00]: version=14 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the PIT (i8254) on IRQ 2 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. KERNEL: Warning: Buddy::alloc: Size mismatch: 1c000 v 20000 Absolute KIP Syscalls using: int 0x30 CPU[0:0]: GenuineIntel (6:2:3:0)[00000623] Model: QEMU Virtual CPU version 0.12.5 at 3309 MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 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: 28672 bytes (7 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:1000;9efff] [0:10b000;13ffff] [4:140000;18bfff] [0:18c000;2dcfff] [4:2dd000;2ddfff] [0:2de000;3fffff] [0:465000;136bfff] [4:136c000;33aafff] [0:33ab000;11404fff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:12bfd000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 248476 KByte free memory MOE: found RAM from 1000 to 11405000 MOE: allocated 276 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136c000-145ad17] [C:503000] l4re BOOTFS: [145b000-1656154] [C:504000] ned BOOTFS: [1657000-1657278] [C:505000] linux-x2.cfg BOOTFS: [1658000-1ec2428] [C:506000] io BOOTFS: [1ec3000-1ec33b7] [C:507000] x86-legacy.devs BOOTFS: [1ec4000-1ec412b] [C:508000] l4lx-x86-x2.io BOOTFS: [1ec5000-23aac8a] [C:509000] vmlinuz BOOTFS: [23ab000-33ab000] [C:50a000] drops-rd.rd MOE: cmdline: /moe rom/linux-x2.cfg MOE: Starting: rom/ned rom/linux-x2.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/linux-x2.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f8850 io | ACPI: RSDP 0xf8850 00014 (v00 BOCHS ) io | ACPI: RSDT 0x12bfdd90 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x12bffe70 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x12bfdf30 01EC4 (v01 BXPC BXDSDT 00000001 INTL 20100528) io | ACPI: FACS 0x12bffe00 00040 io | ACPI: SSDT 0x12bfdef0 00037 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x12bfde10 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x12bfddd0 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 254 Objects with 48 Devices 82 Methods 5 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 1 Objects with 0 Devices 0 Methods 0 Regions io | tbxface-0601 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0184 [02] Enable : Transition to ACPI mode successful io | evgpeblk-1129 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | /home/rkj/L4/fiasco-2012/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:57:AcpiOsInstallInterruptHandler: UNINPLEMENTED io | Completing Region/Field/Buffer/Package initialization:................. io | Initialized 5/5 Regions 0/0 Fields 8/8 Buffers 4/4 Packages (264 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 0 _STA executions (examined 51 objects) io | evgpeblk-1234 [03] EvInitializeGpeBlock : Found 0 Wake, Enabled 16 Runtime GPEs in this block io | ACPICA-Version:20091214, System in ACPI MODE, 32bit timer io | WARNING: device 'S2__' already assigned to an other virtual bus. io | WARNING: device 'PS2' already assigned to an other virtual bus. io | Ready. Waiting for request. l4linux | PH 0 (t: 1) offs=00001000 vaddr=00400000 vend=007ba000 l4linux | phys=00400000 ephys=007ba000 l4linux | f_sz=003ba000 memsz=003ba000 flgs=r-x l4linux | PH 1 (t: 1) offs=003bb000 vaddr=007ba000 vend=0091b000 l4linux | phys=007ba000 ephys=0091b000 l4linux | f_sz=0006e000 memsz=00161000 flgs=rw- l4linux | PH 2 (t: 4) offs=002e8b0c vaddr=006e7b0c vend=006e7b30 l4linux | phys=006e7b0c ephys=006e7b30 l4linux | f_sz=00000024 memsz=00000024 flgs=--- l4linux | Starting binary at 0x400000, argc=8 argv=0x80007f88 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa80006e0 l4linux | ======> L4Linux 2.6 starting... <======== l4linux | Linux version 3.0.0-l4-svn23 (rkj@harpoon) (gcc version 4.4.5 (Debian 4.4.5-8) ) #35 SMP Mon Feb 6 17:50:12 CET 2012 l4linux | Binary name: rom/vmlinuz l4linux | Linux kernel command line (7 args): mem=120M earlyprintk=keep initcall_debug=1 showpfexc=1 root=/dev/hda init=/bin/bash allow_cli l4linux | vcpu 0 gets tamer 0 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00400000 - 0091b000 [5228 KiB]. l4linux | Areas: Text: 00400000 - 007ba000 [3816kB] (a bit longer) l4linux | Data: 007ba000 - 007eb2a0 [196kB] l4linux | Initdata: 007ec000 - 00822000 [216kB] l4linux | BSS: 00828000 - 0090b000 [908kB] l4linux | gs=43 fs=43 l4linux | l4lx_thread_create: Created thread 415 (tamer0) (u:b3000400, sp:00849034) l4linux | Tamer0 is 415 l4linux | Using tamed mode. l4linux | l4lx_thread_create: Created thread 416 (nop) (u:b3000600, sp:00830418) l4linux | Device scan: l4linux | Device: l4linux | MEM: f0000000 - f1ffffff l4linux | MEM: f2000000 - f2000fff l4linux | Device: l4linux | PORT: 000001f0 - 000001f7 l4linux | PORT: 000003f6 - 000003f6 l4linux | IRQ: 0000000e - 0000000e l4linux | PORT: 00000170 - 00000177 l4linux | PORT: 00000376 - 00000376 l4linux | IRQ: 0000000f - 0000000f l4linux | PORT: 0000c000 - 0000c00f l4linux | Device: l4linux | IRQ: 0000000b - 0000000b l4linux | PORT: 0000c100 - 0000c1ff l4linux | MEM: f2020000 - f20200ff l4linux | Device: PNP0900 l4linux | PORT: 000003b0 - 000003bf l4linux | PORT: 000003c0 - 000003df l4linux | MEM: 000a0000 - 000bffff l4linux | Device: PNP0303 l4linux | PORT: 00000060 - 00000060 l4linux | PORT: 00000064 - 00000064 l4linux | IRQ: 00000001 - 00000001 l4linux | IRQ: 0000000c - 0000000c l4linux | l4x_fiasco_gdt_entry_offset = 9 l4linux | rtc not found l4linux | WARNING: RTC server does not seem there! l4linux | l4lx_thread_create: Created thread 418 (cpu0) (u:b3000800, sp:007bbff4) l4linux | main thread will be 418 l4linux | l4x_register_pointer_section: addr = 007ba000 size = 1445888 l4linux | section-with-init: virt: 0x7ba000 to 0x91afff [1412 KiB] l4linux | section-with-init: Phys: 0x0081f000 to 0x00980000, Size: 1445888 l4linux | l4x_linux_startup: thread 418. l4linux | Main thread running, waiting... l4linux | main thread: received startup message. l4linux | l4x_setup_memory: Forcing superpages for main memory l4linux | l4re_global_env: 0xb1007ef4 l4linux | Main memory size: 120MB l4linux | Main memory: virt: 0xc00000 to 0x83fffff [122880 KiB] l4linux | Main memory: Phys: 0x03400000 to 0x0ac00000, Size: 125829120 l4linux | Filling lower ptabs... l4linux | Page fault: addr = 00002002 pc = 007eee2a (rw) l4linux | Page fault: addr = 009fa002 pc = 007eee2a (rw) l4linux | Done (1532 entries). l4linux | l4x_register_pointer_section: addr = 007ba000 size = 1445888 l4linux | end: virt: 0x7ba000 to 0x91afff [1412 KiB] l4linux | end: Phys: 0x0081f000 to 0x00980000, Size: 1445888 l4linux | l4lx_thread_create: Created thread 41d (l4lx.ipi0) (u:b3000a00, sp:0089fff4) Linux version 3.0.0-l4-svn23 (rkj@harpoon) (gcc version 4.4.5 (Debian 4.4.5-8) ) #35 SMP Mon Feb 6 17:50:12 CET 2012 BIOS-provided physical RAM map: L4Lx-Memory: 0000000000000000 - 0000000000400000 (reserved) L4Lx-Memory: 0000000000400000 - 000000000091b000 (usable) L4Lx-Memory: 000000000091b000 - 0000000000c00000 (unusable) L4Lx-Memory: 0000000000c00000 - 0000000008400000 (usable) Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! last_pfn = 0x8400 max_arch_pfn = 0x100000 init_memory_mapping: 0000000000000000-0000000008400000 132MB LOWMEM available. mapped low ram: 0 - 08400000 low ram: 0 - 08400000 Zone PFN ranges: DMA 0x00000400 -> 0x00000000 Normal 0x00000000 -> 0x00008400 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000400 -> 0x0000091b 0: 0x00000c00 -> 0x00008400 Using APIC driver default Intel MultiProcessor Specification v1.0 Virtual Wire compatibility mode. Processors: 1 SMP: Allowing 1 CPUs, 0 hotplug CPUs Allocating PCI resources starting at 8400000 (gap: 8400000:f7c00000) setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1 PERCPU: Embedded 11 pages/cpu @07c00000 s20928 r0 d24128 u4194304 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 31771 Kernel command line: mem=120M earlyprintk=keep initcall_debug=1 showpfexc=1 root=/dev/hda init=/bin/bash allow_cli console [earlykdb0] enabled PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Initializing CPU#0 Memory: 121760k/135168k available (2973k kernel code, 6348k reserved, 1039k data, 216k init, 0k highmem) virtual kernel memory layout: fixmap : 0x00100000 - 0x001e7000 ( 924 kB) vmalloc : 0x08400000 - 0x10400000 ( 128 MB) lowmem : 0x00000000 - 0x08400000 ( 132 MB) .init : 0x007ec000 - 0x00822000 ( 216 kB) .data : 0x006e7548 - 0x007eb2a0 (1039 kB) .text : 0x00400000 - 0x006e7548 (2973 kB) Hierarchical RCU implementation. NR_IRQS:512 l4lx_irq_init: l4lx_irq_max = 512 l4linux | rtc not found Console: colour dummy device 80x25 console [tty0] enabled l4lx_irq_timer_startup(0) l4linux | l4lx_thread_create: Created thread 41f (timer.i0) (u:b3000c00, sp:008a1ff4) Detected 3309.724 MHz processor. Calibrating delay loop (skipped), value calculated using timer frequency.. 6619.44 BogoMIPS (lpj=33097240) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 SMP alternatives: switching to UP code timer_irq_thread: Starting timer IRQ thread. Freeing SMP alternatives: 24k freed CPU0: Intel QEMU Virtual CPU version 0.12.5 stepping 03 Performance Events: unsupported p6 CPU model 2 no PMU driver, software events only. Brought up 1 CPUs Total of 1 processors activated (6619.44 BogoMIPS). NET: Registered protocol family 16 bio: create slab <bio-0> at 0 vgaarb: loaded SCSI subsystem initialized PCI: L4 root bridge is device 17dd0 vgaarb: device added: PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none PCI: Using L4-IO for IRQ routing pci 0000:00:00.0: No interrupt pin configured for device 0000:00:00.0 pci 0000:00:01.0: No interrupt pin configured for device 0000:00:01.0 pci 0000:00:02.0: No interrupt pin configured for device 0000:00:02.0 L4IRQ: set irq type of 11 to 4 pci 0000:00:03.0: PCI INT A -> GSI 11 (level, high) -> IRQ 11 Switching to clocksource l4kipclk NET: Registered protocol family 2 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: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered UDP hash table entries: 128 (order: 0, 4096 bytes) UDP-Lite hash table entries: 128 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. platform rtc_cmos: registered platform RTC device (no PNP device found) msgmni has been set to 237 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) l4fb l4fb.0: look for capability 'fb' as goos session l4fb l4fb.0: init failed err=-2 initcall l4fb_init+0x0/0x17b returned with error code -2 L4 shared mem serial driver brd: module loaded l4bdds: No name given, not starting. Uniform Multi-Platform E-IDE driver piix 0000:00:02.0: IDE controller (0x8086:0x7010 rev 0x00) pci 0000:00:02.0: No interrupt pin configured for device 0000:00:02.0 piix 0000:00:02.0: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xc000-0xc007 ide1: BM-DMA at 0xc008-0xc00f l4linux | cpu0: utcb=0xb3000800 418 l4linux | l4lx_thread_create: Created thread 420 (idler0) (u:b3000e00, sp:008a3ff8) hda: QEMU HARDDISK, ATA DISK drive Switching to clocksource tsc hda: MWDMA2 mode selected hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive hdc: MWDMA2 mode selected l4lx_irq_dev_startup: creating IRQ thread for 14 (IRQ-cap 421000) l4linux | l4lx_thread_create: Created thread 422 (IRQ14) (u:10400000, sp:008a5ff4) l4linux | irq_thread: Started IRQ thread for IRQ 14 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 l4lx_irq_dev_startup: creating IRQ thread for 15 (IRQ-cap 423000) l4linux | l4lx_thread_create: Created thread 424 (IRQ15) (u:10400200, sp:008a7ff4) l4linux | irq_thread: Started IRQ thread for IRQ 15 ide1 at 0x170-0x177,0x376 on irq 15 ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports ide-gd driver 1.18 hda: max request size: 512KiB hda: 32768 sectors (16 MB) w/256KiB Cache, CHS=32/255/63 hda: cache flushes supported hda: unknown partition table ide-cd driver 5.00 ide-cd: hdc: ATAPI 4X CD-ROM drive, 512kB Cache cdrom: Uniform CD-ROM driver Revision: 3.20 e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI e1000: Copyright (c) 1999-2006 Intel Corporation. pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbogend(a)alpha.franken.de mousedev: PS/2 mouse device common for all mice TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type initcall lapic_insert_resource+0x0/0x35 returned with error code -1 Using IPI No-Shortcut mode async_waiting @ 1 async_continuing @ 1 after 0 usec EXT2-fs (hda): warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 3:0. async_waiting @ 1 async_continuing @ 1 after 0 usec Freeing unused kernel memory: 216k freed l4linux | EX: 0: pc = 0041176a sp = 07829fac trapno = 0xd err/pfa = 0x402 Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: bash Not tainted 3.0.0-l4-svn23 #35 Call Trace: [<006e4a29>] panic+0x57/0x14b [<0042ddd1>] do_exit+0x601/0x6c0 [<004839e2>] ? do_munmap+0x202/0x290 [<0042df60>] ? sys_exit_group+0x20/0x20 [<0042df73>] sys_exit+0x13/0x20 [<00406b13>] l4x_user_dispatcher+0xdd3/0x22c0 [<00409702>] l4_kernelinternal_execve+0x52/0xe0 [<00400569>] in_kernel_int80_helper+0x9/0x20 [<0041176c>] ? kernel_execve+0x1c/0x30 [<004001b7>] run_init_process+0x17/0x20 [<00400251>] init_post+0x91/0xb0 [<007ec1d5>] kernel_init+0x10e/0x116 [<007ec0c7>] ? parse_early_options+0x25/0x25 [<00409a99>] kernel_thread_start+0x29/0x30 panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye

2 5

Serial console with qemu/realview-eb
by Stefan Fritsch 07 Feb '12

07 Feb '12

Hi, I have some problems getting the serial console to work under qemu with ARM/realview-eb. I see the output from L4Linux but it does not get any input and also pressing escape does not enter jdb. I have tried qemu 1.0 and 0.12.5. I call it with qemu-system-arm -M realview-eb -nographic -m 256 -kernel .../l4re/obj/l4/arm-rv/images/bootstrap_L4Linux_ARM.elf Are there any options one need to pass with "-append"? "-append -serial_esc" does not make any difference. Any other ideas? L4 version is from l4re-snapshot-2011081207.tar.xz Output from qemu is below. Cheers, Stefan L4 Bootstrapper Build: #12 Thu Jan 26 11:26:11 CET 2012, 4.4.1 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod09: 014bc000-017bc000: ramdisk-arm.rd mod08: 01201000-014bb524: vmlinuz.arm mod07: 01200000-012000bd: arm-rv.io mod06: 0111a000-011ff124: io mod05: 01119000-01119189: l4lx.cfg mod04: 010c3000-011186dc: ned mod03: 010a8000-010c23c8: l4re mod02: 0106d000-010a7ba0: moe mod01: 01063000-0106c6f4: sigma0 mod00: 01015000-01062954: fiasco Moving 10 modules to 1100000 with offset eb000 moving module 10 { 14bc000-17bc000 } -> { 15a7000-18a7000 } moving module 09 { 1201000-14bb524 } -> { 12ec000-15a6524 } moving module 08 { 1200000-12000bd } -> { 12eb000-12eb0bd } moving module 07 { 111a000-11ff124 } -> { 1205000-12ea124 } moving module 06 { 1119000-1119189 } -> { 1204000-1204189 } moving module 05 { 10c3000-11186dc } -> { 11ae000-12036dc } moving module 04 { 10a8000-10c23c8 } -> { 1193000-11ad3c8 } moving module 03 { 106d000-10a7ba0 } -> { 1158000-1192ba0 } moving module 02 { 1063000-106c6f4 } -> { 114e000-11576f4 } moving module 01 { 1015000-1062954 } -> { 1100000-114d954 } Scanning fiasco Scanning sigma0 Scanning moe rom/l4lx.cfg Relocated mbi to [0x100f000-0x100f151] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 193f] { 940} Kern fiasco [ 2000, 5cfff] { 5b000} Kern fiasco [ 90000, 968f3] { 68f4} Sigma0 sigma0 [ 98000, 9e17b] { 617c} Sigma0 sigma0 [ 140000, 175d1f] { 35d20} Root moe [ 178000, 18ecf7] { 16cf8} Root moe [ 1000000, 10143eb] { 143ec} Boot bootstrap [ 100f000, 100f24e] { 24f} Root Multiboot info [ 1193000, 18a6fff] { 714000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:000900e0 sp:01013704 Roottask config ip:00140178 sp:00000000 Starting kernel fiasco at 00001000 Realview System ID: Rev=c HBI=140 Build=0 Arch=4 FPGA=00 Hello from Startup::stage2 Initialize page table Number of IRQs available at this GIC: 96 Vmem_alloc::init() Cache config: ON Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden Rev: rUNKNOWN compiled with gcc 4.4.1 for Realview [] Build: #3 Thu Jan 26 11:21:50 CET 2012 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:5d000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;175fff] [0:176000;177fff] [4:178000;18efff] [0:18f000;100efff] [4:100f000;100ffff] [0:1010000;1192fff] [4:1193000;18a6fff] [0:18a7000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 237772 KByte free memory MOE: found RAM from 5d000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [1193000-11ad3c8] [C:503000] l4re BOOTFS: [11ae000-12036dc] [C:504000] ned BOOTFS: [1204000-1204189] [C:505000] l4lx.cfg BOOTFS: [1205000-12ea124] [C:506000] io BOOTFS: [12eb000-12eb0bd] [C:507000] arm-rv.io BOOTFS: [12ec000-15a6524] [C:508000] vmlinuz.arm BOOTFS: [15a7000-18a7000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=00100000 vend=0041d8f4 l4linux | phys=00100000 ephys=0041d8f4 l4linux | f_sz=0029e39c memsz=0031d8f4 flgs=rwx l4linux | PH 1 (t: 4) offs=002a6378 vaddr=0039e378 vend=0039e39c l4linux | phys=0039e378 ephys=0039e39c l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x11c2f0, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa80006a0 l4linux | ======> L4Linux 2.6 starting... <======== l4linux | Linux version 3.0.0-l4 (fritsch@dev) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #2 Thu Jan 26 11:25:33 CET 2012 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (6 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00100000 - 00500000 [4096 KiB]. l4linux | Areas: Text: 00100000 - 00382000 [2568kB] (a bit longer) l4linux | Data: 00382000 - 00399460 [93kB] l4linux | Initdata: 00100000 - 0011b000 [108kB] l4linux | BSS: 0039e39c - 0041d8f4 [509kB] l4linux | Device scan: l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000400, v:b3000600, sp:00383ff0) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 00100000 size = 3268608 l4linux | section-with-init: virt: 0x100000 to 0x41d8f3 [3190 KiB] l4linux | section-with-init: Phys: 0x00255000 to 0x005728f4, Size: 3266804 l4linux | l4x_linux_startup: thread 413. l4linux | Main thread running, waiting... l4linux | main thread: received startup message. l4linux | l4x_setup_memory: Forcing superpages for main memory l4linux | l4re_global_env: 0xb1007f0c l4linux | Main memory size: 64MB l4linux | Main memory: virt: 0x500000 to 0x44fffff [65536 KiB] l4linux | Main memory: Phys: 0x01900000 to 0x05900000, Size: 67108864 l4linux | Filling lower ptabs... l4linux | Done (480 entries). l4linux | l4x_register_pointer_section: addr = 004ff000 size = 4096 l4linux | end: virt: 0x4ff000 to 0x4fffff [4 KiB] l4linux | end: Phys: 0x00574000 to 0x00575000, Size: 4096 l4linux | l4x_rd_path: rom/ramdisk-arm.rd l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0c600000 to 0c900000 [3072KiB] l4linux | l4lx_thread_create: Created thread 419 (timer.i0) (u:b3000800, v:00000000, sp:003b7ff4) Linux version 3.0.0-l4 (fritsch@dev) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #2 Thu Jan 26 11:25:33 CET 2012 CPU: Fiasco [860f0001] revision 1 (ARMvundefined/unknown), cr=00000000 CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache l4linux | timer_irq_thread: Starting timer IRQ thread. cpu_arm926_proc_init Machine: L4 Memory policy: ECC disabled, Data cache writeback arm926_flush_kern_cache_all() INITRD: 0c600000 - 0c900000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17271 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 0MB 68MB = 68MB total Memory: 64808k/64808k available, 4828k reserved, 0K highmem Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0x04600000 - 0x0c600000 ( 128 MB) lowmem : 0x00000000 - 0x04500000 ( 69 MB) modules : 0xff100000 - 0x00100000 ( 16 MB) .init : 0x00100000 - 0x0011b000 ( 108 kB) .text : 0x0011c000 - 0x003819e8 (2455 kB) .data : 0x00382000 - 0x00399460 ( 94 kB) .bss : 0x0039e39c - 0x0041d8f4 ( 510 kB) NR_IRQS:220 l4lx_irq_init: l4lx_irq_max = 220 l4lx_irq_dev_startup_timer(0) Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 315.80 BogoMIPS (lpj=1579008) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 bio: create slab <bio-0> at 0 Failed to create "l4x" debugfs directory: 1 Switching to clocksource kip NET: Registered protocol family 2 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 UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 210) is a L4 L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP cubic registered NET: Registered protocol family 17 RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) readonly on device 1:0. Freeing init memory: 108K /bin/sh: can't access tty; job control turned off #

2 2

Sharing I/O Memory
by Wesley Miaw 01 Feb '12

01 Feb '12

I have an L4 process requesting access to a large chunk (512MB) of physical RAM using l4sigma0_map_iomem(). I am not using l4sigma0_map_mem() because Fiasco is running in a different partition of physical RAM. I would like to then grant full read/write access to the same memory to a second L4 process, but I'm not sure how to do that. I believe from looking at the sigma0 code that any memory, I/O or RAM, can only be allocated to one L4 process at a time. It also doesn't look like clans have anything to do with this, other than the possibility of creating some shared memory for an IPC. But that's not really what I want to do, I want both L4 processes to directly access the memory. Is there some way to accomplish this? Thanks, -- Wesley Miaw wesley(a)wesman.net

2 7

RE: l4-hackers Digest, Vol 105, Issue 9
by jangwoo 29 Jan '12

29 Jan '12

Hi all. I have similar problem. Currently applications on linux can't use mmap of framebuffer(/dev/fb0). When apps access memory to get through mmap, it occurs page fault. Without goos, fbdrv of L4 cell, mag, l4fb drv in linux, etc on, Is there ways that it modify <linux lcd device driver> little bit as other linux device drivers In other words, could Apps use allocated memory in linux kernel? As a guide, Because of using dedicated frame buffer only in one cell(linux), it mustn't use things like goos, mag. thanks ------------------------------ Message: 1 Date: Tue, 24 Jan 2012 20:03:36 +0100 From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> To: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Fiasco.OC x86 IO port permission bitmap Message-ID: <20120124190336.GE2897(a)os.inf.tu-dresden.de> Content-Type: text/plain; charset=iso-8859-1 Hi, On Mon Jan 23, 2012 at 15:54:29 -0800, Daniel Waddington wrote: > I want to use the TSS I/O permission bit map to support fine grained > control of I/O access for user-level apps (x86 32 bit target). From > looking at the kernel code, I believe the bit map is switched out > per-process as part of the Context class (Space::_io_space) - > correct me if I am wrong. My query is how to set/clear the bits for > a given target task from a "root" task with sufficient privileges > (e.g., base caps and sigma0 caps). I could extend the kernel > scheduler protocol, but I don't want to do this if there is already > a clean way in place. IO-ports are handled similar to page-faults, i.e. they can be mapped to other tasks, and the pager receives io-page-faults when one of its clients accesses an IO-port without having it. For example look for L4_PROTO_IO_PAGE_FAULT and l4_iofpage(). Adam -- Adam adam(a)os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ ------------------------------ Message: 2 Date: Tue, 24 Jan 2012 13:12:03 -0800 From: Daniel Waddington <d.waddington(a)samsung.com> To: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> Cc: l4-hackers(a)os.inf.tu-dresden.de Subject: Re: Fiasco.OC x86 IO port permission bitmap Message-ID: <4F1F1EA3.7060309(a)samsung.com> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Hi Adam, I see. So it seems that you have to map all of the IO port space before getting IOPL raised to 3 (assuming Kconfig IO_PROT & !IO_PROT_3) and therefore the default mode of operation is a driver will map the whole space if it wants to use IO instructions directly. Is it right that you currently don't use the TSS IO bitmap to allow access to only specific IO ports with CPL > IOPL? Thanks Daniel On 01/24/2012 11:03 AM, Adam Lackorzynski wrote: > Hi, > > On Mon Jan 23, 2012 at 15:54:29 -0800, Daniel Waddington wrote: >> I want to use the TSS I/O permission bit map to support fine grained >> control of I/O access for user-level apps (x86 32 bit target). From >> looking at the kernel code, I believe the bit map is switched out >> per-process as part of the Context class (Space::_io_space) - >> correct me if I am wrong. My query is how to set/clear the bits for >> a given target task from a "root" task with sufficient privileges >> (e.g., base caps and sigma0 caps). I could extend the kernel >> scheduler protocol, but I don't want to do this if there is already >> a clean way in place. > IO-ports are handled similar to page-faults, i.e. they can be mapped to > other tasks, and the pager receives io-page-faults when one of its > clients accesses an IO-port without having it. For example look for > L4_PROTO_IO_PAGE_FAULT and l4_iofpage(). > > > Adam

3 2

Fiasco.OC x86 IO port permission bitmap
by Daniel Waddington 27 Jan '12

27 Jan '12

Hi, I want to use the TSS I/O permission bit map to support fine grained control of I/O access for user-level apps (x86 32 bit target). From looking at the kernel code, I believe the bit map is switched out per-process as part of the Context class (Space::_io_space) - correct me if I am wrong. My query is how to set/clear the bits for a given target task from a "root" task with sufficient privileges (e.g., base caps and sigma0 caps). I could extend the kernel scheduler protocol, but I don't want to do this if there is already a clean way in place. Thanks Daniel Waddington

2 4

Re: l4-hackers Digest, Vol 105, Issue 5
by Chen Tian 18 Jan '12

18 Jan '12

Hi Adam, I got another trace: Chen: caps_alloc for virt addr 0xf081f010 (index 0x1f01), new cap location 0xfec93000, [virt 0xf081f000-> mem 0xfec93000] in space 0xfedd7f08, s = 0x0 Chen: caps_alloc for virt addr 0xf081f000 (index 0x1f00), new cap location 0xfec92000, [virt 0xf081f000-> mem 0xfec92000] in space 0xfedd7f08, s = 0x0 thread 0xfed4c000: v_fabricate is false: (Obj_space) from [0xfedd7ef4/12], s_phys 0x0: 00001f01 size: 00000001 to [0xfedd7e9c/18] recv addr 0x1e8f KERNEL: Warning: nothing mapped: (Obj_space) from [0xfedd7ef4/12]: 00001f02 size: 00000001 to [0xfedd7e9c/18] recv addr 0x1e90 Chen: v_delete on cap 0xfecf33b4 for virt addr 0x1ef8 (entry addr 0xfec90f80) in space 0xfedd7f08 As you can see, the status variable "s" is Insert_OK for two invocations of caps_alloc. That means mem_space()->v_insert function is not safe either? Why two insertions are successful at the same time on the same virtual address? I have put a lock to protect l4_factory_create_xxx in my application and that seems to work. Best, Chen On Tue, Jan 17, 2012 at 3:00 AM, <l4-hackers-request(a)os.inf.tu-dresden.de>wrote: > 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: race condition in obj_space-virt.cpp ? (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 Jan 2012 23:54:07 +0100 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: race condition in obj_space-virt.cpp ? > Message-ID: <20120116225406.GA6550(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Fri Jan 13, 2012 at 16:37:06 -0800, Chen Tian wrote: > > Hello, > > > > I observed a race condition in Fiasco.OC. My environment is very > > complicated, but basically I have multiple threads, and each thread keep > > creating kernel object via l4_factory_create_xxxx and map the object to a > > new task. > > > > Here is the trace I got: > > Thanks, we're looking into this. > > > > 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 105, Issue 5 > ****************************************** >

2 1

race condition in obj_space-virt.cpp ?
by Chen Tian 16 Jan '12

16 Jan '12

Hello, I observed a race condition in Fiasco.OC. My environment is very complicated, but basically I have multiple threads, and each thread keep creating kernel object via l4_factory_create_xxxx and map the object to a new task. Here is the trace I got: //printed from obj_space-virt.cpp in function caps_alloc: Chen: caps_alloc for virt addr 0xf0826000 (index 0x2600), new cap location 0xfeb04000, [virt 0xf0826000-> mem 0xfeb04000] in space 0xfedd7f08 Chen: caps_alloc for virt addr 0xf0826010 (index 0x2601), new cap location 0xfeb05000, [virt 0xf0826000-> mem 0xfeb05000] in space 0xfedd7f08 Chen: v_insert cap 0xfed5a6a0 (index 0x2600 (entry addr 0xfeb04000) in space 0xfedd7f08 Chen: v_insert cap 0xfeb000b4 (index 0x2601) (entry addr 0xfeb05010) in space 0xfedd7f08 //printed from map_util thread 0xfed4c000: v_fabricate is false: (Obj_space) from [0xfedd7ef4/12], s_phys 0x0: 00002601 size: 00000001 to [0xfedd7e9c/18] recv addr 0x2541 // then I got KERNEL: Warning: nothing mapped: (Obj_space) from [0xfedd7ef4/12]: 00002602 size: 00000001 to [0xfedd7e9c/18] recv addr 0x2542 Omnicore Panic: task map failed! Basically, different object index (2600 and 2601) causes two different page to be created and mapped to the same cap_table virtual address 0xf0826000. Although one of the mapping will fail, but the current logic did not return the correct address. The fix I put in to solve this problem is to add the following lines after the switch statement in caps_alloc function: if (s != Insert_ok ) { Mapped_allocator::allocator()->q_unaligned_free(ram_quota(), Config::PAGE_SIZE, mem); mem= alien_lookup(virt & ~(Config::PAGE_SIZE/sizeof(Entry)-1)); } Please let me know if this is correct. Thanks. Even with this fix, I still got another kernel "nothing mapped error" when I ask each thread not only to create and map kernel objects, but also to delete objects using l4_task_unmap. If I do not use l4_task_unmap, everything is fine. I am still investigating why, but I got a feeling that there may be other race conditions on the cap_table related operations. Best, Chen

2 1

L4Re build system
by Ivan Loskutov 09 Jan '12

09 Jan '12

Hello, Hackers! I have some questions about L4Re build system 1. How to build library from *.cpp files? The library building if I rename *.cpp files to *.cc but it not easy. I tried to modify mk-files, see attached patch. *.cpp files compiled but don't linked correctly, *.cpp files added to linker command. 2. How to correct add prebuild and postbuild rules to Makefile for prog and library roles? Thanks. -- Best Regards, Ivan Loskutov

2 1

Initial environnement issue
by Julien SIMONE 02 Jan '12

02 Jan '12

Hi hackers, Everytime I try to get a new free utcb in using L4re_env()->first_free_utcb, this call returns 0xffffffff. I think there is something wrong with the utcb_area... Do you think I forgot to initialize anything? Any idea? Best regards, Julien.

2 1

openssl port
by Ivan Loskutov 02 Jan '12

02 Jan '12

Hello, Hackers! I ported OpenSSL 1.0.0e for L4Re http://dl.dropbox.com/u/8558928/openssl.tar.bz2 I tested it on x86 and ARM.

2 1

How to fix RAM size limit 256MB on realview-pbxa9 platform.
by e.fedotov 24 Dec '11

24 Dec '11

Hello, All! This post is about how to eliminate memory restriction 256MB in realview-pbxa9 platform (ARM Cortex A9 processor). The problem is that L4 bootstrap doesn't scan all RAM memory presented on this board. In QEMU source code for this platform (see hw/realview.c in QEMU source directory, function: realview_init) we can find that it can be 3 memory intervals in pbx a9: 1) base=0x00, size=min(sz, 256MB) This is "SDRAM1" 2) base=0x20000000, size=sz-512MB (appears when sz>512) This is called "core tile ram" 3) base=0x70000000, size=512 This is "SDRAM2", where sz is a total board memory, in QEMU specified via -m option. If that memory map is true (I have no pbx-a9 board operator's manual), we can make a simple patch to L4 bootstrap (file <genode>/base-foc/contrib/l4/pkg/bootstrap/server/src/platform/rv.cc), that extends a basic 256MB memory to 256MB+512MB by overloading setup_memory_map virtual function. /namespace { class Platform_arm_rv : public Platform_single_region_ram { bool probe() { return true; } //fix a memory limit 256MB in realview-pbxa9.platform. Adds another memory chip of 512MB. //WARNING: this fix works only if 512MB memory chip (or more) is present! //In case of QEMU you must run it with -m 512 or higher. void setup_memory_map(l4util_mb_info_t *, Region_list *ram, Region_list *) { ram->add(Region::n(0x0, 0x10000000, ".ram", Region::Ram)); //SDRAM as it defined in realview.c (QUEMU sources) ram->add(Region::n(0x70000000, 0x90000000, ".ram", Region::Ram)); //the second 512MB SDRAM //TODO: add more RAM regions if you need it according to the the platform map. } void init() { static L4::Uart_pl011 _uart(36,36); _uart.startup(0x10009000); set_stdio_uart(&_uart); } }; } REGISTER_PLATFORM(Platform_arm_rv); / This is an example patch, it would be more correct (if total RAM size is less then 512) to find total memory size first, then add the memory regions, regarding a total memory size. I hope it will be usefull. Best regards, and happy cristmas&new year. Evgeny Fedotov. Samsung Research Center, Moscow.

2 1

Build L4Re on amd64
by BratSinot aka Куршамбай 19 Dec '11

19 Dec '11

Hello there! I want build L4Re on my Slackware64 without multilib. How can i do that?

3 2

Building l4con lib and examples
by Adi Lima 15 Dec '11

15 Dec '11

Hi, I've been trying to build l4con/lib (actually what I need is libcon.a), but unfortunately I never be able to do it. I am using *l4re-snapshot-2011081207*, which I believe is the latest release. When I check the Makefiles inside the source tree, I found a few commented lines in client_con and contxt directory contains no sources (apparently the sources are being placed inside src directory). Is this package still active or will be removed in the future? Or, is there any way for me to build the package? I need libcon.a to build some test. Thanks. -- FX. J. Adi Lima Trivision Studio

2 1

Need help on l4_msgtag_has_error
by Chen Tian 10 Dec '11

10 Dec '11

Hello, Can some one tell me when a msg tag is set to the error code i.e., tag = 0x8000 ? I have a parent thread A, which creates a child thread B, and thread C is assigned as B's pager and exception handler. When thread A destroys B via l4_task_unmap, thread C is invoked and the tag returned from ipc_reply_and_wait cannot pass l4_msgtag_has_error check. This is very weird. When B dies, will it generate some sort of exceptions which will cause C to be invoked? If I ask thread C to ignore this IPC message, it seems fine because thread B is anyway destroyed. But I am still wondering if I did something logically wrong or the tag error can be safely ignored, especially in the situation I described above? Thanks. Chen

3 3

Using fbterminal with L4Con
by Adi Lima 09 Dec '11

09 Dec '11

Hi all, I finally able to run fbterminal after a bit struggling with some confusions, modifying example: x86-fb.cfg and replacing* ex_fb_spectrum* with * fbterminal* doesn't seem to work if we don't add "term = term:svr()" into fbterminal's caps, where term is defined as: term = loader:new_channel(). But now I want to put this terminal into L4Con, but don't know how to do it. L4con seem to accept different caps list compare to mag. The console appear, but the fbterminal doesn't. Someone help me please...? I attached my current test configuration... Do I miss something? -- FX. J. Adi Lima Trivision Studio

2 1

Cannot show fbterminal
by Adi Lima 06 Dec '11

06 Dec '11

Hi, I've been trying all day launching fbterminal using plain example x86-fb.cfg, and only replace ex_fb_spectrum with fbterminal, following suggestion from Adam (i found it in some old thread). Unfortunately I can't see any mag window for the fbterminal, maybe it failed to create one, or somethin else happened, but if I add a second mag window, containing ex_fb_spectrum, it shows. What do I miss? -- FX. J. Adi Lima Trivision Studio

2 1

l4shmnet bug fixed
by Matthias Petschick 02 Dec '11

02 Dec '11

Hello, there was a small bug in L4Linux's L4shm based network driver, which broke the driver on architectures where NET_IP_ALIGN != 0, e.g. on ARM. This resulted in insufficient data being allocated for the skb in l4x_l4shmc_interrupt, causing the subsequent skb_put to fail. See attached diff for details. Cheers, Matthias

2 1

Minimal Fiasco Testing Setup
by Bryce Cronkite-Ratcliff 02 Dec '11

02 Dec '11

Hi, I have a modified version of Fiasco, & I'd like to compare the performance of this modified kernel vs the original kernel. To that end, what is the minimal module set to provide a workable testing environment? I currently build L4-Linux Mag target, but I'd like to have as minimal a testing setup as possible -- perhaps just Fiasco, L4re, necessary services, and a terminal? Thanks! __Bryce

2 1

shmc bug fixes
by Stefan Fritsch 02 Dec '11

02 Dec '11

Hi, attached are some fixes for shmc: - fix various capability slot leaks in error paths - if l4re_ns_register_obj_srv() fails, return its error code to the caller and don't invent another one - use memory barriers in l4shmc_add_chunk() because l4shmc_get_chunk_to() walks the linked list without acquiring the lock - fix l4shmc_add_signal() freeing one of env's capabilities in an error path Cheers, Stefan

2 1

Getty over L4 shared memory
by Julian Vetter 01 Dec '11

01 Dec '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, is there a driver that does the same as the L4Shmnet driver but for serial console? I want to setup a communication between two Linux instances, one should provide a getty-service and the other instance should connect to it.. Thanks in advance. Cheers, Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO1OxrAAoJEOpGAeJlWp7qFmgIAJ7CZNIBQaNdn1s12p6fy9Rx OMGpKDkp2w/kgD6VZCxj7enzAFo/Z66YwiIVihKe00SM+13tllSr3AbRKWbhpa5F 33iFyI7wAnUnS3Y31DfOleMHlo2ekX7CoLQcD3yq3iuyB61XJRwQLMMY80gZ4dsS u6MFPNBplkG+pl0FuBS7sYXhasZefxB17Cikz/DHI+4ALt/lOQfKcO/Im36fLnoh YR1d0IfY7C9n8e5zNRkOT25KRHl1udJl/Uo14tYxYV/gyWU5jEwzq2tmfqMdZ71M E/sQmSRC68jOrJ1uWNfnz9qGdExNVSuXnR2JspcaeyR356jTIiXpSe0+E9OWZ18= =teF7 -----END PGP SIGNATURE-----

3 3

Genode OS Framework 11.11 released
by Stefan Kalkowski 29 Nov '11

29 Nov '11

Dear L4 hackers, we're pleased to announce the release of version 11.11 of the Genode OS Framework. Genode is an OS architecture that promises to align high security and robustness with dynamic application workloads. It is laid out to run on a number of different microkernels including Nova and Fiasco.OC. To name a few, version 11.11 features GDB debugging facility, the integration of the Vancouver virtual machine monitor, the support of running Android based on the work of the L4Android project, and the ability to execute complex command-line based UNIX software (i.e., VIM) natively on Genode. A short summary of the release-notes follows: * Support for user-level debugging via GDB * Applications and services * Vancouver virtual machine monitor on NOVA * VIM executed on the Noux runtime environment * Terminal emulator implementing the Linux termcap * TCP terminal * Platforms * Fiasco.OC updated to rev 38 * NOVA updated to version 0.4 * New IPC implementation for Linux * Improved support for hybrid Linux/Genode programs * L4Linux on Fiasco.OC * Integration of L4Android (for both x86_32 and ARM) * Stub drivers for block devices, NIC, UART * Device drivers * gPXE device driver environment upgraded to iPXE * Bidirectional UART driver for PL011 and i8250 * PL110 display driver * Support for ARM Versatile Express Cortex-A9x4 * Libc update to FreeBSD 8.2.0 * New unified tool chain based on GCC 4.6.1 You will find a more elaborative discussion of those topics in our comprehensive release-notes document for version 11.11: http://genode.org/documentation/release-notes/11.11 The new version is ready for download at our download page at Sourceforge and our public SVN repository: http://genode.org/download Regards -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Could not run L4Linux for testing
by Adi Lima 27 Nov '11

27 Nov '11

Hi, I was successfully build L4/Fiasco kernel, and run a few test including Hello World, and also compile and test my own simple program, but I'm having trouble running L4Linux (using kernel 3.0). Actually the kernel was loaded, but when the system execute /bin/sh inside the ramdisk-x86.rd (I get it from the snapshot), it says that it cannot access tty, and then the job control being turn off. I've been trying to follow the example from previous release, but they use rmgr, bmodfs, etc, which I could find on the new release. I've also tried the example from L4Linux Page<http://141.76.48.99/L4/LinuxOnL4/use.shtml>, but it doesn't work. Can you help with the initialization routine? Maybe some example? Thanks. -- FX. J. Adi Lima Trivision Studio

2 1

Re: omap3 usb platform and other
by Sartakov A. Vasily 27 Nov '11

27 Nov '11

got a working usb-host via OTGi will try to make a working EHCI, stay tuned 2011/11/15 giowck <giowckln(a)googlemail.com>: > Hi, > > thank you a lot! > > I will check this soon. > > Am 15.11.2011 11:15, schrieb Sartakov A. Vasily: >> >> Hallo >> This is a steps for get USB-otg work: >> 1. get svn' l4linux, l4re >> 2. cd l4linux directory apply patches: >> patch -p1<drivers.diff >> patch -p1<arch.diff >> 3. make setup >> 4. change .config on usb_config, add in it valid CONFIG_L4_OBJ_TREE >> 5. make L4ARCH=arm menuconfig, >> 6. ordinary l4 build >> 7. put arm-omap3.devs in obj/l4/arm/arm-beagleboard/bin/arm_armv6/l4f >> 8. add: >> entry l4l_1 >> kernel fiasco -serial_esc >> roottask moe rom/l4l_1.cfg >> module l4re >> module ned >> module l4l_1.cfg >> module arm-omap3.devs >> module gumstix-fb-l4l.io >> module io >> module vmlinuz.arm >> module ramdisk-arm.rd >> >> in src/l4/conf/modules.list >> 9. put l4l_1.cfg and gumstix-fb-l4l.io in src/l4/conf/examples >> 10. make uimage and choose l4l_1 >> >> Then you got around 8mb uImage, witch can boot. >> After that you will have BB platform sources in >> arch/l4/kernel/arch-arm, so, if you interesting in USB-host You should >> edit it >> I will try to do it too in nearest future, cos me need a sd/mmc and >> USB-host too. >> Btw, in our configs, all platform resources (mem io, irq) placed in >> single gumstix-fb-l4l.io and arm-omap3.devs cleared, it's important. >> if you have a same resources in both files, most of them will not work >> >> >> >> >> ---------------------------------------------------------- >> >> Hit any key to stop autoboot: 0 >> reading l4img >> >> 8286416 bytes read >> ## Booting kernel from Legacy Image at 80000000 ... >> Image Name: L4 Image #8 >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 8286352 Bytes = 7.9 MiB >> Load Address: 81000000 >> Entry Point: 81000000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> >> L4 Bootstrapper >> Build: #8 Tue Nov 15 10:30:07 CET 2011, 4.4.1 >> Scanning up to 128 MB RAM >> Memory size is 128MB (80000000 - 88000000) >> RAM: 0000000080000000 - 0000000087ffffff: 131072kB >> Total RAM: 128MB >> mod10: 814e7000-817e7000: ramdisk-arm.rd >> mod09: 81204000-814e60a0: vmlinuz.arm >> mod08: 8111e000-81203074: io >> mod07: 8111d000-8111d97f: gumstix-fb-l4l.io >> mod06: 8111c000-8111c103: arm-omap3.devs >> mod05: 8111b000-8111b302: l4l_1.cfg >> mod04: 810c5000-8111a670: ned >> mod03: 810aa000-810c439c: l4re >> mod02: 8106f000-810a9b50: moe >> mod01: 81065000-8106e70c: sigma0 >> mod00: 81015000-81064ef4: fiasco >> Moving 11 modules to 81100000 with offset eb000 >> moving module 11 { 814e7000-817e7000 } -> { 815d2000-818d2000 } >> moving module 10 { 81204000-814e60a0 } -> { 812ef000-815d10a0 } >> moving module 09 { 8111e000-81203074 } -> { 81209000-812ee074 } >> moving module 08 { 8111d000-8111d97f } -> { 81208000-8120897f } >> moving module 07 { 8111c000-8111c103 } -> { 81207000-81207103 } >> moving module 06 { 8111b000-8111b302 } -> { 81206000-81206302 } >> moving module 05 { 810c5000-8111a670 } -> { 811b0000-81205670 } >> moving module 04 { 810aa000-810c439c } -> { 81195000-811af39c } >> moving module 03 { 8106f000-810a9b50 } -> { 8115a000-81194b50 } >> moving module 02 { 81065000-8106e70c } -> { 81150000-8115970c } >> moving module 01 { 81015000-81064ef4 } -> { 81100000-8114fef4 } >> Scanning fiasco -serial_esc >> Scanning sigma0 >> Scanning moe rom/l4l_1.cfg >> Relocated mbi to [0x8100f000-0x8100f186] >> Loading fiasco >> Loading sigma0 >> Loading moe >> find kernel info page... >> found kernel info page at 0x80002000 >> Regions of list regions >> [ 80001000, 800019ff] { a00} Kern fiasco >> [ 80002000, 80061fff] { 60000} Kern fiasco >> [ 80090000, 800969bf] { 69c0} Sigma0 sigma0 >> [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 >> [ 80140000, 80176183] { 36184} Root moe >> [ 80178000, 8018ed0f] { 16d10} Root moe >> [ 81000000, 810143eb] { 143ec} Boot bootstrap >> [ 8100f000, 8100f283] { 284} Root Multiboot info >> [ 81195000, 818d1fff] { 73d000} Root Modules Memory >> API Version: (87) experimental >> Sigma0 config ip:800900e0 sp:81013704 >> Roottask config ip:801401c0 sp:00000000 >> Starting kernel fiasco at 80001000 >> Hello from Startup::stage2 >> Initialize page table >> Vmem_alloc::init() >> Cache config: ON >> ID_PFR0: 00001031 >> ID_PFR1: 00000011 >> ID_DFR0: 00010400 >> ID_AFR0: 00000000 >> ID_MMFR0: 31100003 >> ID_MMFR1: 20000000 >> ID_MMFR2: 01202000 >> ID_MMFR3: 00000011 >> FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 1, v: c, i: 41, t: hard, p: >> dbl/sngl >> SERIAL ESC: allocated IRQ 74 for serial uart >> Not using serial hack in slow timer handler. >> Welcome to Fiasco.OC (arm)! >> L4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden >> Rev: r38 compiled with gcc 4.4.1 for Beagleboard [] >> Build: #2 Tue Nov 15 09:44:12 CET 2011 >> >> Calibrating timer loop... done. >> SIGMA0: Hello! >> KIP @ 80002000 >> allocated 4KB for maintenance structures >> SIGMA0: Dump of all resource maps >> RAM:------------------------ >> [0:80000000;80000fff] >> [0:80062000;8008ffff] >> [0:80097000;80097fff] >> [0:8009f000;8013ffff] >> [4:80140000;80176fff] >> [0:80177000;80177fff] >> [4:80178000;8018efff] >> [0:8018f000;8100efff] >> [4:8100f000;8100ffff] >> [0:81010000;81194fff] >> [4:81195000;818d1fff] >> [0:818d2000;86ffffff] >> IOMEM:---------------------- >> [0:0;7fffffff] >> [0:88000000;ffffffff] >> MOE: Hello world >> MOE: found 106516 KByte free memory >> MOE: found RAM from 80000000 to 87000000 >> MOE: allocated 112 KByte for the page array @0x80062000 >> MOE: virtual user address space [0-bfffffff] >> MOE: rom name space cap -> [C:501000] >> BOOTFS: [81195000-811af39c] [C:503000] l4re >> BOOTFS: [811b0000-81205670] [C:504000] ned >> BOOTFS: [81206000-81206302] [C:505000] l4l_1.cfg >> BOOTFS: [81207000-81207103] [C:506000] arm-omap3.devs >> BOOTFS: [81208000-8120897f] [C:507000] gumstix-fb-l4l.io >> BOOTFS: [81209000-812ee074] [C:508000] io >> BOOTFS: [812ef000-815d10a0] [C:509000] vmlinuz.arm >> BOOTFS: [815d2000-818d2000] [C:50a000] ramdisk-arm.rd >> MOE: cmdline: moe rom/l4l_1.cfg >> MOE: Starting: rom/ned rom/l4l_1.cfg >> MOE: loading 'rom/ned' >> Ned says: Hi World! >> Ned: loading file: 'rom/l4l_1.cfg' >> IO | Io service >> IO | WARNING: device 'plat' already assigned to an other virtual bus. >> IO | WARNING: device 'prcm3' already assigned to an other virtual >> bus. >> IO | WARNING: device 'prcm2' already assigned to an other virtual >> bus. >> IO | WARNING: device 'sys' already assigned to an other virtual bus. >> IO | WARNING: device 'i2c1' already assigned to an other virtual bus. >> IO | WARNING: device 'gpio' already assigned to an other virtual bus. >> IO | Ready. Waiting for request. >> l4linux | PH 0 (t: 1) offs=00008000 vaddr=00100000 vend=004492ec >> l4linux | phys=00100000 ephys=004492ec >> l4linux | f_sz=002c83cc memsz=003492ec flgs=rwx >> l4linux | PH 1 (t: 4) offs=002d03a8 vaddr=003c83a8 vend=003c83cc >> l4linux | phys=003c83a8 ephys=003c83cc >> l4linux | f_sz=00000024 memsz=00000024 flgs=r-x >> l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 >> l4linux | phys=00000000 ephys=00000000 >> l4linux | f_sz=00000000 memsz=00000000 flgs=rwx >> l4linux | Starting binary at 0x11e2f8, argc=9 argv=0x80007f84 >> *argv=0xb1007ff0 argv0=rom/vmlinuz.arm >> l4linux | External resolver is at 0xa80006a0 >> l4linux | ======> L4Linux 2.6 starting...<======== >> l4linux | Linux version 3.0.0-l4-svn23 (jdoe@ubuntu) (gcc version >> 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #2 Tue Nov 15 09:54:29 CET 2011 >> l4linux | Binary name: rom/vmlinuz.arm >> l4linux | This is an AEABI build. >> l4linux | Linux kernel command line (8 args): mem=64M console=ttyLv0 >> l4x_rd=rom/vHSM.rd root=1:0 rw ramdisk_size=20480 init=/linuxrc debug >> l4linux | CPU mapping (l:p)[1]: 0:0 >> l4linux | Image: 00100000 - 00500000 [4096 KiB]. >> l4linux | Areas: Text: 00100000 - 003a8000 [2720kB] (a bit longer) >> l4linux | Data: 003a8000 - 003c38a0 [110kB] >> l4linux | Initdata: 00100000 - 0011d000 [116kB] >> l4linux | BSS: 003c83cc - 004492ec [515kB] >> l4linux | l4lx_thread_create: Created thread 415 (tamer0) (u:b3000400, >> sp:003cc288) >> l4linux | Tamer0 is 415 >> l4linux | Using tamed mode. >> l4linux | Device scan: >> l4linux | Device: System Control >> l4linux | MEM: 48002000 - 480047ff >> l4linux | MEM: 48004800 - 4800ffff >> l4linux | Device: i2c >> l4linux | MEM: 48070000 - 48070fff >> l4linux | Device: prcm2 >> l4linux | MEM: 48060000 - 4806007f >> l4linux | MEM: 48072000 - 4807207f >> l4linux | MEM: 480ab000 - 480acfff >> l4linux | MEM: 48200000 - 4820ffff >> l4linux | MEM: 48306800 - 48309fff >> l4linux | MEM: 4830a000 - 4830ffff >> l4linux | MEM: 6c000000 - 6cffffff >> l4linux | MEM: 6d000000 - 6dffffff >> l4linux | IRQ: 00000038 - 00000038 >> l4linux | IRQ: 0000003d - 0000003d >> l4linux | IRQ: 00000039 - 00000039 >> l4linux | IRQ: 00000007 - 00000007 >> l4linux | IRQ: 0000005c - 0000005c >> l4linux | Device: plat >> l4linux | IRQ: 0000004d - 0000004d >> l4linux | l4lx_thread_create: Created thread 417 (cpu0) (u:b3000600, >> sp:003a9ff0) >> l4linux | main thread will be 417 >> l4linux | l4x_register_pointer_section: addr = 00100000 size = 3448832 >> l4linux | section-with-init: virt: 0x100000 to 0x4492eb [3364 KiB] >> l4linux | section-with-init: Phys: 0x8034d000 to 0x806962ec, Size: >> 3445484 >> l4linux | l4x_linux_startup: thread 417. >> l4linux | Main thread running, waiting... >> l4linux | main thread: received startup message. >> l4linux | l4x_setup_memory: Forcing superpages for main memory >> l4linux | l4re_global_env: 0xb1007ef4 >> l4linux | Main memory size: 64MB >> l4linux | Main memory: virt: 0x500000 to 0x44fffff [65536 KiB] >> l4linux | Main memory: Phys: 0x81900000 to 0x85900000, Size: 67108864 >> l4linux | Filling lower ptabs... >> l4linux | Done (436 entries). >> l4linux | l4x_register_pointer_section: addr = 004ff000 size = 4096 >> l4linux | end: virt: 0x4ff000 to 0x4fffff [4 KiB] >> l4linux | end: Phys: 0x80698000 to 0x80699000, Size: 4096 >> l4linux | l4x_rd_path: rom/vHSM.rd >> l4linux | Loading: rom/vHSM.rd >> l4linux | Failed to query name 'rom/vHSM.rd': No such object found(-2) >> l4linux | Failed to get initrd: No such object found(-2) >> l4linux | Couldn't load ramdisk :( >> l4linux | l4lx_thread_create: Created thread 41c (IRQ CPU0) >> (u:b3000800, sp:003e3ff0) >> Linux version 3.0.0-l4-svn23 (jdoe@ubuntu) (gcc version 4.4.1 >> (Sourcery G++ Lite 2009q3-67) ) #2 Tue Nov 15 09:54:29 CET 2011 >> CPU: Fiasco [860f0001] revision 1 (ARMvundefined/unknown), cr=00000000 >> CPU: unknown data cache, unknown instruction cache >> cpu_v6_proc_init >> Machine: L4 >> Memory policy: ECC disabled, Data cache writeback >> _CACHE_flush_kern_cache_all() >> On node 0 totalpages: 17409 >> free_area_init_node: node 0, pgdat 003c2f44, node_mem_map 00500000 >> DMA zone: 138 pages used for memmap >> DMA zone: 0 pages reserved >> DMA zone: 17271 pages, LIFO batch:3 >> pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 >> pcpu-alloc: [0] 0 >> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17271 >> Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/vHSM.rd >> root=1:0 rw ramdisk_size=20480 init=/linuxrc debug >> PID hash table entries: 512 (order: -1, 2048 bytes) >> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) >> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) >> Memory: 0MB 68MB = 68MB total >> Memory: 64808k/64808k available, 4828k reserved, 0K highmem >> Virtual kernel memory layout: >> vector : 0xbffff000 - 0xc0000000 ( 4 kB) >> fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) >> DMA : 0xffc00000 - 0xffe00000 ( 2 MB) >> vmalloc : 0x04600000 - 0x0c600000 ( 128 MB) >> lowmem : 0x00000000 - 0x04500000 ( 69 MB) >> modules : 0xff100000 - 0x00100000 ( 16 MB) >> .init : 0x00100000 - 0x0011d000 ( 116 kB) >> .text : 0x0011e000 - 0x003a6e5c (2596 kB) >> .data : 0x003a8000 - 0x003c38a0 ( 111 kB) >> .bss : 0x003c83cc - 0x004492ec ( 516 kB) >> NR_IRQS:395 nr_irqs:395 395 >> l4lx_irq_init: creating IRQ thread on cpu 0 >> Console: colour dummy device 80x30 >> console [ttyLv0] enabled >> Calibrating delay loop... irq_thread: Starting IRQ thread on CPU 0 >> 496.43 BogoMIPS (lpj=2482176) >> pid_max: default: 32768 minimum: 301 >> Mount-cache hash table entries: 512 >> CPU: Testing write buffer coherency: ok >> print_constraints: dummy: >> NET: Registered protocol family 16 >> __l4x_ioremap: Mapping physaddr 48002000 [0x1000 Bytes, >> 48002000+001000] to 04500000+000000 >> __l4x_ioremap: Mapping physaddr 48306800 [0x2000 Bytes, >> 48306000+003000] to 04501000+000800 >> __l4x_ioremap: Mapping physaddr 48004800 [0x2000 Bytes, >> 48004000+003000] to 04504000+000800 >> _CACHE_flush_kern_cache_all() >> __l4x_ioremap: Mapping physaddr 48200000 [0x1000 Bytes, >> 48200000+001000] to 04507000+000000 >> IRQ: Found an INTC at 0x04507000 (revision 4.0) with 96 interrupts >> Total of 96 interrupts on 1 active controller >> omap3xxx_powerdomains_init >> recalculate_root_clocks >> Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz >> ERROR: IO-memory (68000000+ffff) not available >> omap_hwmod: l3_main: Could not ioremap >> omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main >> omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_core >> omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per >> omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup >> __l4x_ioremap: Mapping physaddr 48070000 [0x7f Bytes, 48070000+001000] >> to 04508000+000000 >> __l4x_ioremap: Mapping physaddr 48072000 [0x7f Bytes, 48072000+001000] >> to 04509000+000000 >> __l4x_ioremap: Mapping physaddr 48060000 [0x7f Bytes, 48060000+001000] >> to 0450a000+000000 >> __l4x_ioremap: Mapping physaddr 480ab000 [0xfff Bytes, >> 480ab000+001000] to 0450b000+000000 >> omap_hwmod: i2c1: softreset failed (waited 10000 usec) >> omap_hwmod: i2c2: softreset failed (waited 10000 usec) >> omap_hwmod: i2c3: softreset failed (waited 10000 usec) >> omap2_common_pm_init >> Added static device 'System Control' with 2 resources. >> Added static device 'i2c' with 1 resources. >> Added static device 'prcm2' with 13 resources. >> omap_register_i2c_bus bus_id=1 nr_ports=3 >> omap2_i2c_add_bus >> omap_register_i2c_bus bus_id=3 nr_ports=3 >> omap2_i2c_add_bus >> omap_init_opp_table: no hwmod or odev for iva, [9] cannot add OPPs. >> overo_opp_init: opp default init failed >> >> >> >> ============ >> ICLKEN_CORE 7ffffedb >> ICLKEN_CORE 7ffffedb >> FCLKEN_CORE 43fffe01 >> FCLKEN_CORE c3fffe01 >> CTRL i2c 1 11c0118 >> CTRL i2c 2 118011c >> CTRL i2c 3 1c0118 >> bio: create slab<bio-0> at 0 >> Failed to create "l4x" debugfs directory: 1 >> omap_i2c omap_i2c.1: bus 1 rev3.12 at 2600 kHz >> l4linux | cpu0: utcb=0xb3000600 417 >> l4linux | l4lx_thread_create: Created thread 41f (idler0) (u:b3000a00, >> sp:003e5ff4) >> twl4030: PIH (irq 7) chaining IRQs 368..375 >> twl4030: power (irq 373) chaining IRQs 376..383 >> print_constraints: VUSB1V5: 1500 mV normal standby >> print_constraints: VUSB1V8: 1800 mV normal standby >> print_constraints: VUSB3V1: 3100 mV normal standby >> twl4030_usb twl4030_usb: HW_CONDITIONS 0x90/144; link 1 >> twl4030_usb twl4030_usb: Initialized TWL4030 USB module >> omap_i2c omap_i2c.3: bus 3 rev3.12 at 400 kHz >> Switching to clocksource kip >> musb-hdrc: version 6.0, pio, peripheral >> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk >> split, HB-ISO Rx, HB-ISO Tx, SoftConn) >> musb-hdrc: MHDRC RTL version 1.400 >> musb-hdrc: setup fifo_mode 4 >> musb-hdrc: 28/31 max ep, 16384/16384 memory >> musb-hdrc musb-hdrc: USB Peripheral mode controller at 0450b000 using >> PIO, IRQ 92 >> NET: Registered protocol family 2 >> 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 >> UDP hash table entries: 256 (order: 0, 4096 bytes) >> UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) >> NET: Registered protocol family 1 >> NetWinder Floating Point Emulator V0.97 (double precision) >> msgmni has been set to 126 >> io scheduler noop registered >> io scheduler deadline registered >> io scheduler cfq registered (default) >> L4 serial driver >> ttyLv0 at MMIO 0x1 (irq = 385) is a L4 >> L4 shared mem serial driver >> l4cdds: No name given, not starting. >> brd: module loaded >> l4bdds: No name given, not starting. >> g_ether gadget: using random self ethernet address >> g_ether gadget: using random host ethernet address >> usb0: MAC 4a:57:0a:8c:6d:1c >> usb0: HOST MAC 2a:99:fb:8b:c0:d3 >> g_ether gadget: adding config #2 'RNDIS'/003bf038 >> g_ether gadget: adding 'rndis'/0414cd60 to config 'RNDIS'/003bf038 >> rndis_register: configNr = 0 >> rndis_set_param_medium: 0 0 >> g_ether gadget: RNDIS: dual speed IN/ep1in OUT/ep1out NOTIFY/ep2in >> g_ether gadget: cfg 2/003bf038 speeds: high full >> g_ether gadget: interface 0 = rndis/0414cd60 >> g_ether gadget: interface 1 = rndis/0414cd60 >> g_ether gadget: adding config #1 'CDC Ethernet (ECM)'/003bef9c >> g_ether gadget: adding 'cdc_ethernet'/0414cca0 to config 'CDC Ethernet >> (ECM)'/003bef9c >> g_ether gadget: CDC Ethernet: dual speed IN/ep1in OUT/ep1out NOTIFY/ep2in >> g_ether gadget: cfg 1/003bef9c speeds: high full >> g_ether gadget: interface 0 = cdc_ethernet/0414cca0 >> g_ether gadget: interface 1 = cdc_ethernet/0414cca0 >> g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 >> g_ether gadget: g_ether ready >> mousedev: PS/2 mouse device common for all mice >> i2c /dev entries driver >> TCP cubic registered >> NET: Registered protocol family 17 >> omap2_common_pm_late_init >> >> >> 2011/11/2 Giorgio Wicklein<giowckln(a)googlemail.com>: >>> >>> Hi, >>> >>> I spent a lot of time trying to get specific OMAP3/Beagleboard hardware >>> modules working (EHCI USB mainly). >>> So far, without luck. >>> >>> A generic "how-to-integrate-linux-drivers-in-l4linux" example would be >>> very helpful. >>> The procedure is not very clear to me (since I'm really new here). >>> >>> Based on Vasily's work, I changed some sources of linux drivers, to get >>> musb, >>> otg, and usb-ehci compiled without errors. The bootlog compared to >>> Vasily's >>> one [1], is very different; Drivers seems to load, but they don't >>> recognize the >>> hardware (I think). >>> >>> For example the following boot messages doesn't appear on mine: >>> >>> omap_register_i2c_bus bus_id=1 nr_ports=3 >>> omap2_i2c_add_bus >>> omap_register_i2c_bus bus_id=3 nr_ports=3 >>> omap2_i2c_add_bus >>> >>> or >>> >>> __l4x_ioremap: Mapping physaddr 48200000 [0x1000 Bytes, >>> 48200000+001000] to 04507000+000000 >>> IRQ: Found an INTC at 0x04507000 (revision 4.0) with 96 interrupts >>> >>> or >>> >>> twl4030: PIH (irq 7) chaining IRQs 368..375 >>> twl4030: power (irq 373) chaining IRQs 376..383 >>> print_constraints: VUSB1V5: 1500 mV normal standby >>> print_constraints: VUSB1V8: 1800 mV normal standby >>> print_constraints: VUSB3V1: 3100 mV normal standby >>> twl4030_usb twl4030_usb: HW_CONDITIONS 0x90/144; link 1 >>> twl4030_usb twl4030_usb: Initialized TWL4030 USB module >>> omap_i2c omap_i2c.3: bus 3 rev3.12 at 400 kHz >>> Switching to clocksource kip >>> musb-hdrc: version 6.0, pio, peripheral >>> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk >>> split, HB-ISO Rx, HB-ISO Tx, SoftConn) >>> musb-hdrc: MHDRC RTL version 1.400 >>> musb-hdrc: setup fifo_mode 4 >>> musb-hdrc: 28/31 max ep, 16384/16384 memory >>> musb-hdrc musb-hdrc: USB Peripheral mode controller at 0450b000 using >>> >>> and such... >>> >>> Some of these messages are generated by sources from the mach-omap2 >>> directroy, >>> which AFAIK are not necessary, since changes where not mentioned in >>> Vasily's >>> patch. Do I need to include mach-omap? If yes, how? >>> >>> Please take a look at my patch (attached below). I did some work, >>> specific for >>> ehci usb Beagleboard support. >>> >>> What is the correct method for adding those drivers? >>> Any suggestions? Or examples (since Vasily's is not complete for me)... >>> >>> My configs are in the attachment with the main patch. >>> >>> Thanks, >>> Giorgio >>> >>> [1] Vasily's bootlog - >>> http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/005069.html >>> >>> _______________________________________________ >>> l4-hackers mailing list >>> l4-hackers(a)os.inf.tu-dresden.de >>> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers >>> >>> >> >> >> > > -- Sartakov A. Vasily

2 6

Bugs in Semaphore implementation in Fiasco.OC?
by Chen Tian 27 Nov '11

27 Nov '11

Hello, I wonder if the following two problems are bugs. 1. In u_semaphore.cpp, function wakeup_locked, (around line 189): w->state_change_dirty(~Thread_ipc_mask, Thread_ready); If thread w is running on a different core than thread c, assertion in function state_change_dirty will fail. I think it should be w->state_change_dirty(~Thread_ipc_mask, Thread_ready, false); 2. In u_semaphore.cpp, function block_locked, (around line 146): c->state_del_dirty(~Thread_ipc_mask) should be c->state_del_dirty(Thread_ipc_mask). Otherwise, wrong bits will be cleared, which cause the assertion in assert_irq_entry() to fail. Best, Chen

2 1

FOSDEM 2012 - Multiserver, microkernel-based operating systems devroom
by Jakub Jermar 22 Nov '11

22 Nov '11

FOSDEM 2012 - Multiserver, microkernel-based operating systems devroom *CALL FOR PARTICIPATION* http://fosdem.org/2012 (apologies for cross-posting) The developers of several free and open-source multiserver and/or microkernel-based operating systems will meet at FOSDEM 2012 in Brussels, Belgium and will share a developer room. The devroom is currently looking for content in the form of talks related to the area of multiserver and/or microkernel-based operating systems. Possible topics include, but are not limited to: OS introduction to developers of other OS Subsystems and architecture Hardware and device drivers Tools and languages Release engineering and testing Experience and learning from mistakes Technical challenges Community and life with an OS-project Academia and education Please send your talk proposal(s) to: microkernel-devroom(a)lists.fosdem.org no later than by 2011-12-31. Make sure to include the following in your proposal: - title of your talk (will be printed in the FOSDEM booklet) - your full name (will be printed in the FOSDEM booklet) - your short bio giving us some idea of who you are and what is your relation to and qualification for the subject of your talk - number of 15-minute slots that you need for the talk (talks longer than 45 minutes are discouraged) The final devroom schedule (along with accepted talks) will be announced on 2012-01-9 (Jan 9) in: microkernel-devroom(a)lists.fosdem.org and the speakers will be notified via e-mail. The schedule will be also published on the FOSDEM web and in the FOSDEM booklet after 2012-01-21. If you do not want to or cannot give a talk yourself, you may still send suggestions for what else you would like to see/hear/do in the devroom. Please send your suggestions to the above mailing list. The devroom is scheduled for Sunday of February 5, room K.3.201. The seating capacity of the room is 85 seats. Any changes will be announced in the above mailing list. Jakub Jermar

1 0

L4Linux modules PB11MPCORE
by Varun Ganesh 20 Nov '11

20 Nov '11

Hi, I am trying to load L4Linux on PB11MPCORE. I have only the following modules loding up and configured in modules.list mod09: 014b9000-017b9000: ramdisk-arm.rd mod08: 011f7000-014b8488: vmlinuz.arm mod07: 011f6000-011f60bd: arm-rv.io mod06: 01118000-011f5078: io mod05: 01117000-01117189: l4lx.cfg mod04: 010c1000-01116670: ned mod03: 010a6000-010c039c: l4re mod02: 0106b000-010a5b54: moe mod01: 01061000-0106a714: sigma0 mod00: 01014000-010604b0: fiasco The kernel hangs after fetching kernel info at regions.optimize Are these modules sufficient or should I have any others configured

2 2

L4Linux on PB11MPCORE boot hangs at
by Varun Ganesh 17 Nov '11

17 Nov '11

Hi, I have compiled L4, L4re, L4Linux and done a make image using make image E=L4Linux-arm BOOTSTRAP_DO_UIMAGE=y MODULE_SEARCH_PATH=/home/l4/src/kernel/fiasco :/home/l4/src/kernel/fiasco/mybuildir: /home/l4/src/l4/conf/examples: /home/L4Android/l4linux/l4linux_build:/tmp/: /home/l4/src The ramdisk is included in the image as was given in module.list. When i tried booting the image on PB11MPCORE using the U-Boot command, bootm <kernel-address> The kernel starts booting but gets stuck as follows, Booting kernel from Legacy Image at 00008000 ... Image Name: L4 Image #7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 8097792 Bytes = 7.7 MB Load Address: 01000000 Entry Point: 01000000 Loading Kernel Image ... L4 Bootstrapper Build: #7 Wed Nov 16 14:01:12 EST 2011, 4.3.2 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod09: 014b9000-017b9000: ramdisk-arm.rd mod08: 011f7000-014b8488: vmlinuz.arm mod07: 011f6000-011f60bd: arm-rv.io mod06: 01118000-011f5078: io mod05: 01117000-01117189: l4lx.cfg mod04: 010c1000-01116670: ned mod03: 010a6000-010c039c: l4re mod02: 0106b000-010a5b54: moe mod01: 01061000-0106a714: sigma0 mod00: 01014000-010600f0: fiasco Moving 10 modules to 1100000 with offset ec000 moving module 10 { 14b9000-17b9000 } -> { 15a5000-18a5000 } moving module 09 { 11f7000-14b8488 } -> { 12e3000-15a4488 } moving module 08 { 11f6000-11f60bd } -> { 12e2000-12e20bd } moving module 07 { 1118000-11f5078 } -> { 1204000-12e1078 } moving module 06 { 1117000-1117189 } -> { 1203000-1203189 } moving module 05 { 10c1000-1116670 } -> { 11ad000-1202670 } moving module 04 { 10a6000-10c039c } -> { 1192000-11ac39c } moving module 03 { 106b000-10a5b54 } -> { 1157000-1191b54 } moving module 02 { 1061000-106a714 } -> { 114d000-1156714 } moving module 01 { 1014000-10600f0 } -> { 1100000-114c0f0 } Scanning fiasco Scanning sigma0 Scanning moe rom/l4lx.cfg Relocated mbi to [0x100e000-0x100e151] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 What steps should I take to proceed beyond this point. Thanks, Varun Ganesh

2 1

kernel.ld.arm virt_address
by Wesley Miaw 10 Nov '11

10 Nov '11

I'm trying to understand where the value of virt_address inside kernel.ld.arm is coming from. The value is currently 0xf0000000 and the kernel's interrupt vector table is placed at 0xffff0000. On my Cortex-A9 + uATX Versatile Express board this corresponds to the HSB AXI (peripherals communication bus). The memory map for the RealView Emulation Baseboard maps the 0xf0000000 area to logic tile site 2. An objdump of the fiasco image shows that a number of kernel sections are being placed into 0xf0000000 and higher. And things work, but I would think that the correct address should be somewhere in RAM. (RAM which you then have to not withhold from sigma0.) When I try to move the virt_address and .ivt address to somewhere in DRAM like 0x90000000 and 0x9fffffff respectively the kernel fails to load. Maybe because access is restricted although I don't think the MMU would have been turned on yet (but I haven't yet found the place where the MMU is turned on--I would guess by sigma0 or fiasco). Thanks, -- Wesley Miaw wesley(a)wesman.net

2 2

Using different serial port for 2 linux instances
by Julien SIMONE 10 Nov '11

10 Nov '11

Hello, I have 2 linux running on top of Fiasco.OC and I would like them to use a different serial port. I found out there is "bootstrap -comport=<com#>" but I don't know how to use it..Maybe it's not the only solution and not the best one... Can someone share some experiences? Thank you. Best regards, Julien.

2 1

Booting multiple instances of L4 Linux
by Julien SIMONE 08 Nov '11

08 Nov '11

Hello, I'm trying to boot 2 instances of L4 linux on top of Fiasco.OC micro kernel but I get an error during the checksum verification. I tried to boot a L4Linux and a hello, it was ok but not with 2 L4Linux. I would like to boot 2 l4Linux on a Beagleboard emulated by QEMU (The error is not from QEMU) The output is: " Verifying Checksum ... Bad Data CRC ERROR: Can't get kernel image!" Is it an error from my module.list file? My config file?..Any ideas? Thank you, Best regards. Julien.

2 1

Problem booting L4 on Sheevaplug
by Julian Vetter 08 Nov '11

08 Nov '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everybody, its me again =) I have a problem booting L4 on the Sheevaplug. I have built L4re, Fiasco and also L4Linux for arm platform and built an uimage by calling "make image E=L4Linux-arm BOOTSTRAP_DO_UIMAGE=y SUPPORT_CC_armkirkwood=y MODULE_SEARCH_PATH=/opt/arm/fiasco:/opt/src/l4/conf/examples:/opt/arm/l4linux:/tmp" Everything worked fine. Than I copied the image to my usb stick and tried to boot it on the Sheevaplug with UBoot. I got the following output: Marvell>> usb start Marvell>> fatload usb 0:1 0x00800000 /bootstrap_l4linux-arm.uimage Marvell>> bootm 0x00800000 ## Booting image at 00800000 ... Image Name: L4 Image #11 Created: 2011-11-08 10:20:15 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 8028328 Bytes = 7.7 MB Load Address: 01000000 Entry Point: 01000000 Verifying Checksum ... OK OK Starting kernel ... And then nothing happens after that. I also tried the simple 'Hello'-Example without L4Linux, and it also didn't work. Or at least I get nothing to see... I think the problem is the serial console. But how can I tell L4 that the output should be send to this same console? (I'm connected to the Sheevaplug via MiniUsb->Usb 'screen /dev/ttyUSB0 115200'). I hope someone can help me. Thanks in advance. Cheers, Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOuQcTAAoJEOpGAeJlWp7qygMIALNgU5q0PLFJTtqe31jZwWX0 V8SYxtYuaX/SSowRElRhg7fTHF3FzFKdnGzhmZrRQDc0OGTH2LVpiZR2a6OBhfKX pvq4CjOwNXYSYFz2EtwODie0Z37YH7ywWoO5ojUTJz8XyMkD8mgLlqLqUj9kAL7A RHP5yROXKTc7tvcYiGpqpWAtBs6Em/P/KwynVHZCBeHkgH9UlOvK7ycCbYCTLOBA mqts0mY7NOnNAXG5se5+JuNQXE422lQN66r7PX43Pm5WPumrW/9SJuhH9qyea9FF JCtO9F828pmRK3a98kGc+Nf/TzJjr4EkvsDZKKUQ6zYAWgAVDjVc8OCp1D+kRPk= =0Cgd -----END PGP SIGNATURE-----

2 1

L4CON with client
by Peter Hanzel 08 Nov '11

08 Nov '11

Hello. I am trying L4Re with Fiasco.OC. I have successfuly build l4re-snapshot. Now I am trying to run examples. I am always building iso images with make grub2iso. Now I am editing .cfgs and .list files. I am trying to get working L4CON. The L4Con runs okay, saying: con | Running. Video mode is 800x600@16. con | Ready. Waiting for clients Now I suppose I need some client to work with L4CON. I have tried fbterminal, but it doesn't work. (Or i am missing something in .cfgs) I have added fbterminal to run after "con", but in logs it runs earlier ang log says: fbdrv | Starting server loop mmag | mapped frame buffer at 0x400000 fbtermin| Could not bind event IRQ How can I achive to get some console with for example dash running? Attached are .cfg, .list Thanks.

2 4

Disko UI Framework porting
by Ivan Loskutov 05 Nov '11

05 Nov '11

Hi all! I executed porting of Disko (http://www.diskohq.com/ ) to use in L4Re. Archive with dependencies and patches http://dl.dropbox.com/u/8558928/disko.tar.bz2 1. Differences of Disko original source code I changed *.cpp files name extension to *.cc. I didn’t build a library from *.cpp files. I added files enabling working with framebuffer (mmsgui/fb/mmsfbl4re.cc) and L4Re input subsystem (mmsinput/mmsinputl4rehandler.cc). Virtual file system(VFS) added (mmstool/vfswrapper.cc) for implementation of access at application resources (image, xml form files). Libwhefs library was used for it (http://code.google.com/p/whefs/). 2. Known issues The input system link handler has has only the functions I needed. The touchscreen calibration function was added to mmsinputl4rehandler.cc, but it’s not the best solution. The best solution would be a separate server for the input subsystem that routes handled events to other applications. To simplify the touchscreen handler coding I added a patch to input. See input.patch. L4Re video API function bits_per_pixel returned incorrect pixel size because it was calculated as a sum of R, G, B and A fields sizes. I have used RGB32 format with A field length equal to 0 bits. That’s why the returned total length was 24 bits instead of 32 bits. See video.patch The realloc sometimes malfunctions. But I couldn’t recreate conditions to make this malfunctions repeat. Shared library libdisko.so not building. 3. Comments For application compilation the following utilities are required: taff (from disko tools), whefs-mkfs and whefs-cp (from libwhefs). It was used for creating VFS-image (see examples). You must to build this utilities manually and add they to PATH. For example, to build disko/examples/tutorial/01 vfs-image you need to execute cd disko/examples and run ./convert.sh tutorial/01 I use Gumstix Overo platform with lcd 4.3" and ads7846 touchscreen, drivers added to archive. modules.list and configs added to disko/examples For correct work on ARM you must apply patch from Adam for pthread ( http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004992.html ). Some screenshots: http://dl.dropbox.com/u/8558928/disko-04-arm.jpg http://dl.dropbox.com/u/8558928/disko-04-qemu.jpg http://dl.dropbox.com/u/8558928/disko-05-qemu.jpg

2 1

gcc: symbol lookup error: ...libgendep.so: undefined symbol: dlsym
by Wesley Miaw 03 Nov '11

03 Nov '11

Hi, I saw someone ran into this same problem a couple of years ago but I didn't see a solution posted. I just updated my OS to Ubuntu 11 and all of a sudden I am hitting this error when I run make setup and target either x86 or ARM. gcc: symbol lookup error: ...libgendep.so: undefined symbol: dlsym I see -ldl on the gcc line when building libgendep.so, but when I ldd libgendep.so it only prints linux-gate.so.1, libc.so.6, and /lib/ld-linux.so.2. libdl.so.2 exists and is in my ld cache. I am using gcc (Ubuntu/Linaro) 4.6.1. Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

omap3 usb platform and other
by Vasily Sartakov 02 Nov '11

02 Nov '11

Hello. I would like to discuss with you platforms supported in l4linux. l4linux good working on "vanilla" arm platform, but when we try to use a board specific devices - for example USB, we have some problem with full device support in sources. For example, USB gadget need musb, witch need twl4030, which need i2c, which need clock and power domain initialisation, and all of this part placed in arch/arm/omap. In next mail attachment you can find the our kernel, which support usb on Overo Gumstix platform. We copied sources from arch/arm/omap to arch/l4/kernel/arch-arm/ and made it work. Most of them serious changed, but we tried to save structure. I don't thing what its good solution, but it real working and someone who ask USB support on arm can use it. So, what you think about full board/platform supporting? any idea? Can this solution may be pushed to SVN? I understand that this code should be more clear, and I think it would be better if he would be on the Internet. Incidentally, this is the second version, we have previously done this for kernel 2.6.xx, and it is very difficult to keep a local copy and make regular merge. The other thing which i would like discuss is configuration management for l4re build. With a time, count of a package will be increased, and, like now, the compiling of l4re take a long time. Do you plan in this direction some work? For example, you could make small configuration files for compiling only requirements, similar to Control -- Sartakov A. Vasily

3 4

Problem booting L4Linux
by Julian Vetter 22 Oct '11

22 Oct '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everybody, I'm new to L4 and I tried to run L4Linux in Qemu, But I can't get the system to boot, it always stops at: ... l4linux | l4x_rd_path: rom/ramdisk-x86.rd l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0cc00000 to 0cf00000 [3072KiB] l4linux | rtc not found l4linux | L4Re[rm]: mapping for page fault failed with -2004 @b8000 pc=55fdc4 l4linux | Page fault (non-resolved): pfa=b8000 pc=55fdc4 l4linux | Page fault (non-resolved): pfa=0 pc=4780f6 Die message: Trap: 14 l4linux | panic: going to sleep forever, bye And then hanging there. Can somebody help me? I'm using L4Re, Fiasco and L4Linux all from the SVN. I didn't add any additional parameters to the configuration except for the Serial Device in the L4Linux configuration. Thanks it advance. Julian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOodiQAAoJEOpGAeJlWp7qhJIH/1SVCtKVooaM3D+U7CjgD0wo iSd2ph+Ytpews/2yILU3hnx7tLuT9BXKmycDAZ4LNJGDxhizuCgVMqONQr0dmoiF dU5C/9QNp7AgWZjEbdimBr8rbbpSv9fnSWYZlpnQaewdscYRsmpmdn4EzbOd3Skk Qu4i9gN0WEfwRJnz83Bs+9dmh6H7KXI6yNI3WT502iDevVEG1kTAFRzeoQaSUmCK sA777OilXk8HWL0ROMQZZ5OO7gl1997cPUhOpI3I1LAdHeZywltpGLQWCIqM/UqO dUiOg73XfoS0Bk3HdTTsoEEhQ27F4fxvP97YCXwuMxqSDFYc5UwGNKZZIIbc6Mo= =iGsR -----END PGP SIGNATURE-----

2 2

omap3 board config files
by Vasily Sartakov 21 Oct '11

21 Oct '11

In this attachment you can find our config files for start l4linux' usb on omap3 board. We use a Overo Gumstix for examples. Our boot log looks as: OMAP3530-GP ES3.1 Board revision: 1 Reading boot sector Loading u-boot.bin from mmc U-Boot 2010.12 (Aug 15 2011 - 19:34:31) OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 720 mHz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 512 MiB MMC: OMAP SD/MMC: 0 In: serial Out: serial Err: serial Board revision: 1 Direct connection on mmc2 No EEPROM on expansion board Die ID #1aa60004000000000403951c07002013 Net: smc911x: Invalid chip endian 0xa765e321 No ethernet found. Hit any key to stop autoboot: 0 reading l4img 22999248 bytes read ## Booting kernel from Legacy Image at 80000000 ... Image Name: L4 Image #7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 22999184 Bytes = 21.9 MiB Load Address: 81000000 Entry Point: 81000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... L4 Bootstrapper Build: #7 Fri Oct 21 08:21:47 CEST 2011, 4.4.1 Scanning up to 128 MB RAM Memory size is 128MB (80000000 - 88000000) RAM: 0000000080000000 - 0000000087ffffff: 131072kB Total RAM: 128MB mod10: 814ef000-825ef000: vHSM.rd mod09: 8120c000-814ee0a0: vmlinuz.arm mod08: 81126000-8120b0f8: io mod07: 81125000-8112597f: gumstix-fb-l4l.io mod06: 81124000-81124103: arm-omap3.devs mod05: 81123000-81123302: l4l_1.cfg mod04: 810c5000-811220a8: ned mod03: 810aa000-810c439c: l4re mod02: 8106f000-810a9b50: moe mod01: 81065000-8106e70c: sigma0 mod00: 81015000-81064cf4: fiasco Moving 11 modules to 81100000 with offset eb000 moving module 11 { 814ef000-825ef000 } -> { 815da000-826da000 } moving module 10 { 8120c000-814ee0a0 } -> { 812f7000-815d90a0 } moving module 09 { 81126000-8120b0f8 } -> { 81211000-812f60f8 } moving module 08 { 81125000-8112597f } -> { 81210000-8121097f } moving module 07 { 81124000-81124103 } -> { 8120f000-8120f103 } moving module 06 { 81123000-81123302 } -> { 8120e000-8120e302 } moving module 05 { 810c5000-811220a8 } -> { 811b0000-8120d0a8 } moving module 04 { 810aa000-810c439c } -> { 81195000-811af39c } moving module 03 { 8106f000-810a9b50 } -> { 8115a000-81194b50 } moving module 02 { 81065000-8106e70c } -> { 81150000-8115970c } moving module 01 { 81015000-81064cf4 } -> { 81100000-8114fcf4 } Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/l4l_1.cfg Relocated mbi to [0x8100f000-0x8100f17f] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list regions [ 80001000, 800019ff] { a00} Kern fiasco [ 80002000, 80061fff] { 60000} Kern fiasco [ 80090000, 800969bf] { 69c0} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 801761bb] { 361bc} Root moe [ 80178000, 8018ed0f] { 16d10} Root moe [ 81000000, 810143eb] { 143ec} Boot bootstrap [ 8100f000, 8100f27c] { 27d} Root Multiboot info [ 81195000, 826d9fff] { 1545000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:800900e0 sp:81013704 Roottask config ip:801401c0 sp:00000000 Starting kernel fiasco at 80001000 Hello from Startup::stage2 Initialize page table Vmem_alloc::init() Cache config: ON ID_PFR0: 00001031 ID_PFR1: 00000011 ID_DFR0: 00010400 ID_AFR0: 00000000 ID_MMFR0: 31100003 ID_MMFR1: 20000000 ID_MMFR2: 01202000 ID_MMFR3: 00000011 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 1, v: c, i: 41, t: hard, p: dbl/sngl SERIAL ESC: allocated IRQ 74 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden Rev: rUNKNOWN compiled with gcc 4.4.1 for Beagleboard [] Build: #2 Fri Oct 21 07:39:05 CEST 2011 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:80000000;80000fff] [0:80062000;8008ffff] [0:80097000;80097fff] [0:8009f000;8013ffff] [4:80140000;80176fff] [0:80177000;80177fff] [4:80178000;8018efff] [0:8018f000;8100efff] [4:8100f000;8100ffff] [0:81010000;81194fff] [4:81195000;826d9fff] [0:826da000;86ffffff] IOMEM:---------------------- [0:0;7fffffff] [0:88000000;ffffffff] MOE: Hello world MOE: found 92148 KByte free memory MOE: found RAM from 80000000 to 87000000 MOE: allocated 112 KByte for the page array @0x80062000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [81195000-811af39c] [C:503000] l4re BOOTFS: [811b0000-8120d0a8] [C:504000] ned BOOTFS: [8120e000-8120e302] [C:505000] l4l_1.cfg BOOTFS: [8120f000-8120f103] [C:506000] arm-omap3.devs BOOTFS: [81210000-8121097f] [C:507000] gumstix-fb-l4l.io BOOTFS: [81211000-812f60f8] [C:508000] io BOOTFS: [812f7000-815d90a0] [C:509000] vmlinuz.arm BOOTFS: [815da000-826da000] [C:50a000] vHSM.rd MOE: cmdline: moe rom/l4l_1.cfg MOE: Starting: rom/ned rom/l4l_1.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4l_1.cfg' IO | Io service IO | WARNING: device 'plat' already assigned to an other virtual bus. IO | WARNING: device 'prcm3' already assigned to an other virtual bus. IO | WARNING: device 'prcm2' already assigned to an other virtual bus. IO | WARNING: device 'sys' already assigned to an other virtual bus. IO | WARNING: device 'i2c1' already assigned to an other virtual bus. IO | WARNING: device 'gpio' already assigned to an other virtual bus. IO | Ready. Waiting for request. l4linux | PH 0 (t: 1) offs=00008000 vaddr=00100000 vend=004472ec l4linux | phys=00100000 ephys=004472ec l4linux | f_sz=002c63cc memsz=003472ec flgs=rwx l4linux | PH 1 (t: 4) offs=002ce3a8 vaddr=003c63a8 vend=003c63cc l4linux | phys=003c63a8 ephys=003c63cc l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x11e2f8, argc=9 argv=0x80007f84 *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa80006a0 l4linux | ======> L4Linux 2.6 starting... <======== l4linux | Linux version 3.0.0-l4-svn23 (jdoe@ubuntu) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #7 Fri Oct 21 08:21:19 CEST 2011 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (8 args): mem=64M console=ttyLv0 l4x_rd=rom/vHSM.rd root=1:0 rw ramdisk_size=20480 init=/linuxrc debug l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00100000 - 00500000 [4096 KiB]. l4linux | Areas: Text: 00100000 - 003a6000 [2712kB] (a bit longer) l4linux | Data: 003a6000 - 003c18a0 [110kB] l4linux | Initdata: 00100000 - 0011d000 [116kB] l4linux | BSS: 003c63cc - 004472ec [515kB] l4linux | l4lx_thread_create: Created thread 415 (tamer0) (u:b3000400, sp:003ca288) l4linux | Tamer0 is 415 l4linux | Using tamed mode. l4linux | Device scan: l4linux | Device: System Control l4linux | MEM: 48002000 - 480047ff l4linux | MEM: 48004800 - 4800ffff l4linux | Device: i2c l4linux | MEM: 48070000 - 48070fff l4linux | Device: prcm2 l4linux | MEM: 48060000 - 4806007f l4linux | MEM: 48072000 - 4807207f l4linux | MEM: 480ab000 - 480acfff l4linux | MEM: 48200000 - 4820ffff l4linux | MEM: 48306800 - 48309fff l4linux | MEM: 4830a000 - 4830ffff l4linux | MEM: 6c000000 - 6cffffff l4linux | MEM: 6d000000 - 6dffffff l4linux | IRQ: 00000038 - 00000038 l4linux | IRQ: 0000003d - 0000003d l4linux | IRQ: 00000039 - 00000039 l4linux | IRQ: 00000007 - 00000007 l4linux | IRQ: 0000005c - 0000005c l4linux | Device: plat l4linux | IRQ: 0000004d - 0000004d l4linux | l4lx_thread_create: Created thread 417 (cpu0) (u:b3000600, sp:003a7ff0) l4linux | main thread will be 417 l4linux | l4x_register_pointer_section: addr = 00100000 size = 3440640 l4linux | section-with-init: virt: 0x100000 to 0x4472eb [3356 KiB] l4linux | section-with-init: Phys: 0x8034f000 to 0x806962ec, Size: 3437292 l4linux | l4x_linux_startup: thread 417. l4linux | Main thread running, waiting... l4linux | main thread: received startup message. l4linux | l4x_setup_memory: Forcing superpages for main memory l4linux | l4re_global_env: 0xb1007ef4 l4linux | Main memory size: 64MB l4linux | Main memory: virt: 0x500000 to 0x44fffff [65536 KiB] l4linux | Main memory: Phys: 0x82700000 to 0x86700000, Size: 67108864 l4linux | Filling lower ptabs... l4linux | Done (438 entries). l4linux | l4x_register_pointer_section: addr = 004ff000 size = 4096 l4linux | end: virt: 0x4ff000 to 0x4fffff [4 KiB] l4linux | end: Phys: 0x80698000 to 0x80699000, Size: 4096 l4linux | l4x_rd_path: rom/vHSM.rd l4linux | Loading: rom/vHSM.rd l4linux | INITRD: Size of RAMdisk is 17408KiB l4linux | RAMdisk from 0c600000 to 0d700000 [17408KiB] l4linux | l4lx_thread_create: Created thread 41c (IRQ CPU0) (u:b3000800, sp:003e1ff0) Linux version 3.0.0-l4-svn23 (jdoe@ubuntu) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #7 Fri Oct 21 08:21:19 CEST 2011 CPU: Fiasco [860f0001] revision 1 (ARMvundefined/unknown), cr=00000000 CPU: unknown data cache, unknown instruction cache cpu_v6_proc_init Machine: L4 Memory policy: ECC disabled, Data cache writeback _CACHE_flush_kern_cache_all() On node 0 totalpages: 17409 free_area_init_node: node 0, pgdat 003c0f44, node_mem_map 00500000 DMA zone: 138 pages used for memmap DMA zone: 0 pages reserved DMA zone: 17271 pages, LIFO batch:3 INITRD: 0c600000 - 0d700000 pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17271 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/vHSM.rd root=1:0 rw ramdisk_size=20480 init=/linuxrc debug PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 0MB 68MB = 68MB total Memory: 64808k/64808k available, 4828k reserved, 0K highmem Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0x04600000 - 0x0c600000 ( 128 MB) lowmem : 0x00000000 - 0x04500000 ( 69 MB) modules : 0xff100000 - 0x00100000 ( 16 MB) .init : 0x00100000 - 0x0011d000 ( 116 kB) .text : 0x0011e000 - 0x003a5e5c (2592 kB) .data : 0x003a6000 - 0x003c18a0 ( 111 kB) .bss : 0x003c63cc - 0x004472ec ( 516 kB) NR_IRQS:395 nr_irqs:395 395 l4lx_irq_init: creating IRQ thread on cpu 0 Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... irq_thread: Starting IRQ thread on CPU 0 496.43 BogoMIPS (lpj=2482176) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok print_constraints: dummy: NET: Registered protocol family 16 __l4x_ioremap: Mapping physaddr 48002000 [0x1000 Bytes, 48002000+001000] to 04500000+000000 __l4x_ioremap: Mapping physaddr 48306800 [0x2000 Bytes, 48306000+003000] to 04501000+000800 __l4x_ioremap: Mapping physaddr 48004800 [0x2000 Bytes, 48004000+003000] to 04504000+000800 _CACHE_flush_kern_cache_all() __l4x_ioremap: Mapping physaddr 48200000 [0x1000 Bytes, 48200000+001000] to 04507000+000000 IRQ: Found an INTC at 0x04507000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller omap3xxx_powerdomains_init recalculate_root_clocks Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz ERROR: IO-memory (68000000+ffff) not available omap_hwmod: l3_main: Could not ioremap omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_core omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup __l4x_ioremap: Mapping physaddr 48070000 [0x7f Bytes, 48070000+001000] to 04508000+000000 __l4x_ioremap: Mapping physaddr 48072000 [0x7f Bytes, 48072000+001000] to 04509000+000000 __l4x_ioremap: Mapping physaddr 48060000 [0x7f Bytes, 48060000+001000] to 0450a000+000000 __l4x_ioremap: Mapping physaddr 480ab000 [0xfff Bytes, 480ab000+001000] to 0450b000+000000 omap_hwmod: i2c1: softreset failed (waited 10000 usec) omap_hwmod: i2c2: softreset failed (waited 10000 usec) omap_hwmod: i2c3: softreset failed (waited 10000 usec) omap2_common_pm_init Added static device 'System Control' with 2 resources. Added static device 'i2c' with 1 resources. Added static device 'prcm2' with 13 resources. omap_register_i2c_bus bus_id=1 nr_ports=3 omap2_i2c_add_bus omap_register_i2c_bus bus_id=3 nr_ports=3 omap2_i2c_add_bus omap_init_opp_table: no hwmod or odev for iva, [9] cannot add OPPs. overo_opp_init: opp default init failed ============ ICLKEN_CORE 7ffffedb ICLKEN_CORE 7ffffedb FCLKEN_CORE 43fffe01 FCLKEN_CORE c3fffe01 CTRL i2c 1 11c0118 CTRL i2c 2 118011c CTRL i2c 3 1c0118 bio: create slab <bio-0> at 0 Failed to create "l4x" debugfs directory: 1 omap_i2c omap_i2c.1: bus 1 rev3.12 at 2600 kHz l4linux | cpu0: utcb=0xb3000600 417 l4linux | l4lx_thread_create: Created thread 41f (idler0) (u:b3000a00, sp:003e3ff4) twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 print_constraints: VUSB1V5: 1500 mV normal standby print_constraints: VUSB1V8: 1800 mV normal standby print_constraints: VUSB3V1: 3100 mV normal standby twl4030_usb twl4030_usb: HW_CONDITIONS 0x90/144; link 1 twl4030_usb twl4030_usb: Initialized TWL4030 USB module omap_i2c omap_i2c.3: bus 3 rev3.12 at 400 kHz Switching to clocksource kip musb-hdrc: version 6.0, pio, peripheral musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 1.400 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory musb-hdrc musb-hdrc: USB Peripheral mode controller at 0450b000 using PIO, IRQ 92 NET: Registered protocol family 2 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 UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 385) is a L4 L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. g_ether gadget: using random self ethernet address g_ether gadget: using random host ethernet address usb0: MAC be:e4:f9:c0:9d:96 usb0: HOST MAC f6:b1:7f:e8:97:68 g_ether gadget: adding config #2 'RNDIS'/003bd038 g_ether gadget: adding 'rndis'/02e4dd60 to config 'RNDIS'/003bd038 rndis_register: configNr = 0 rndis_set_param_medium: 0 0 g_ether gadget: RNDIS: dual speed IN/ep1in OUT/ep1out NOTIFY/ep2in g_ether gadget: cfg 2/003bd038 speeds: high full g_ether gadget: interface 0 = rndis/02e4dd60 g_ether gadget: interface 1 = rndis/02e4dd60 g_ether gadget: adding config #1 'CDC Ethernet (ECM)'/003bcf9c g_ether gadget: adding 'cdc_ethernet'/02e4dca0 to config 'CDC Ethernet (ECM)'/003bcf9c g_ether gadget: CDC Ethernet: dual speed IN/ep1in OUT/ep1out NOTIFY/ep2in g_ether gadget: cfg 1/003bcf9c speeds: high full g_ether gadget: interface 0 = cdc_ethernet/02e4dca0 g_ether gadget: interface 1 = cdc_ethernet/02e4dca0 g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 g_ether gadget: g_ether ready mousedev: PS/2 mouse device common for all mice i2c /dev entries driver TCP cubic registered NET: Registered protocol family 17 omap2_common_pm_late_init omap_voltage_late_init: Unable to create voltage debugfs main dir vdd_debugfs_init: Unable to create debugfs directory for vdd_mpu vdd_debugfs_init: Unable to create debugfs directory for vdd_core RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 17408KiB [1 disk] into ram disk... done. VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing init memory: 116K Initializing random number generator... done. Configuring network interfaces... done. Setting up IP spoofing protection: rp_filter. OpenEmbedded Linux ##-l4 ttyLv0 ##-micro-eglibc 0.1-20111007 ##-l4 ttyLv0 ##-l4 login:root Password: root@##-l4:~# ifconfig usb0 192.168.0.5 usb0: eth_open usb0: eth_start g_ether gadget: ecm_open g_ether gadget: notify connect true g_ether gadget: notify speed 425984000 root@##-l4:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) usb0 Link encap:Ethernet HWaddr 2E:5B:FA:2A:AC:B8 inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5 errors:0 dropped:5 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:336 (336.0 B) TX bytes:0 (0.0 B) root@##-l4:~# ping 192.168.0.2 PING 192.168.0.2 (192.168.0.2): 56 data bytes 64 bytes from 192.168.0.2: seq=13 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=14 ttl=64 time=3.000 ms 64 bytes from 192.168.0.2: seq=15 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=16 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=17 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=18 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=19 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=20 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=21 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=22 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=23 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=24 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=25 ttl=64 time=2.000 ms 64 bytes from 192.168.0.2: seq=26 ttl=64 time=2.000 ms -- Sartakov A. Vasily

1 0

omap3 platform drivers
by Vasily Sartakov 21 Oct '11

21 Oct '11

In this patch we add some changes to l4linux drivers, especiali to i2c and musb Unfortunately we had to make these changes, because without them, nothing worked. -- Sartakov A. Vasily

1 0

Running L4 linux on Beagle board
by Julien SIMONE 20 Oct '11

20 Oct '11

Hello, I tried to run L4linux on a beagle board. I downloaded the snapshot, did Make setup (I chose config for beagleBoard) Make I compiled quiet well but I can't launch le L4linux on my qemu (Maybe I did something wrong), I'm currently using qemu-linaro (last release) Qemu-system-arm -M beagle -m512 -kernel obj/l4/arm-beagleboard/images/bootstrap_L4Linux_ARM.elf -initrd files/ramdisks-arm.rd And I get this error: Qemu:Hardware error: no boot device found CPU#0 {registers....} Aborted Thank you Best regards, -- Simone Julien Stagiaire Novasys

3 2

Mouse and keyboard on L4Android
by Giorgio Wicklein 19 Oct '11

19 Oct '11

Hi, Short: how to get an USB mouse/keyboard working on L4Re? Long: I'm having some difficulties to get my keyboard and mouse on a beagleboard working. I noticed that the io file of the realview-eb includes the keyboard and mouse hardware addresses, since they are mapped to dedicated registers [1] on this board. The beagleboard doesn't have such registers. Found only USB EHCI register addresses and the related interrupt number. So, I'm trying to connect an USB mouse and USB keyboard over the EHCI USB port. Does L4Re support only PS/2 devices? Or also USB input devices? Is USB working on L4Linux/L4Android? I defined USB in my io file as following (for beagleboard): USB => new Device() { .hid = "usb"; new-res Mmio(0x48064000 .. 0x48064fff); new-res Irq(77); } Can L4Linux access now to the USB interface, or are any further steps required? Thanks, Giorgio [1] http://infocenter.arm.com/help/topic/com.arm.doc.dui0303e/Bbajihec.html

3 3

v_insert() in Mem_space class for ARM architecture
by Jung Hyun Yoo 19 Oct '11

19 Oct '11

Hi, During looking into the source code of v_insert() function in mem_space-arm.cpp file, I found two cases where it returns improper Mem_space::Status. Case #1 When the size parameter of v_insert() is 0x100000 (that is, section mapping is asked), and the entry in the corresponding first-level page table indicates a coarse second-level page table (that is, it’s already valid) and only the entry in the second-level table is invalid: v_insert() function returns Insert_OK status. But it seems proper to return Insert_err_exists because there is already valid entry and inserting a new entry fails. Case #2 When the size parameter of v_insert() is 0x1000 (that is, 4KB small page mapping is asked), and the memory allocation for creating a coarse second-level page table fails in Page_table::walk() function: v_insert() returns Insert_OK status. But it seems proper to return Insert_err_nomem because due to memory shortage inserting a new entry fails. I wonder my understanding is right. Cheers, Junghyun Yoo

2 1

l4sigma0_map_iomem Allowed Addresses
by Wesley Miaw 18 Oct '11

18 Oct '11

I'm having some trouble understanding the acceptable values usable in a call to l4sigma0_map_iomem. It looks like the way for me to request a map from an available physical address block to a virtual memory address that can be used by the program. Perhaps I am lacking a more fundamental understanding of the ARM memory model. But what addresses should be allowed? My Verstaile Express board has 1GB RAM starting at physical address 0x60000000 but I can't use this address. I immediately get an error. I also tried starting at 0x80000000. (The L4 Bootloader seems to be using memory at 0x60000000 for its own purposes anyway.) Error: Cannot map physical memory: (-2147451404) No fpage received If I try to get size 0x04000000 from address 0x08000000 it works fine. I am going off the memory map of the CoreTile A9x4. http://infocenter.arm.com/help/topic/com.arm.doc.dui0448e/CIAGFCHA.html#BBA… The CoreTile A9x4 uses the Versatile Express Motherboard uATX's Legacy memory map. http://infocenter.arm.com/help/topic/com.arm.doc.dui0447e/ch04s02s01.html#C… Thanks, -- Wesley Miaw wesley(a)wesman.net

4 5

how can i download previous versions
by gaober 17 Oct '11

17 Oct '11

hello everyone! i am a student from china. recently i did some research on Fiasco. i wonder how can i download the previous releases of fiasco,l4re and l4linux. i found the latest version of fiasco,l4re and l4linux here at http://os.inf.tu-dresden.de/download/snapshots-oc/.i want to get l4linux with the linux kernel 2.6.32 or 2.6.34 or 2.6.35 and the compatible fiasco microkernel and l4re. i have another question. now the fiasco microkernel becomes fiasco.OC.when did it get this changes? and what does it mean with the name of the version like fiasco-2011081207. i am beginner with so much doubt and waiting for request of teachers. thanks! Wilbert Gao

2 1

Is there a way to build a non-PIC shared library with l4env?
by Valery V. Sedletski 17 Oct '11

17 Oct '11

Hi, I am trying to establish a shared arena for loading DLL's, i.e. a shared memory region, in which DLL's are loaded at the same address in each address space. I also need some ELF shared library loaded at fixed address, so I could call routines in .so from these DLL's (yes, a mixed case: LX format DLL's calling an ELF shared object, this shared object is a client library for some servers, and I want to call their API's from DLL's). So, I intend to load a shared oblect at fixed address to be the same in different address spaces. But the l4env build system seems to produce PIC shared objects only, and no suitable example. Is there any way to compile a non-PIC shared object with l4env build system? I also hope the 'loader' server will load the shared library at pre-compiled address. Maybe, also the PIC ones could be loaded at desired address (I know that, at least, libloader.s.so is loaded at fixed address, but maybe, this is a single hardcoded case) Thanks in advance, valery

2 16

Re: L4Android/L4Linux Beagleboard framebuffer and driver
by Giorgio Wicklein 13 Oct '11

13 Oct '11

On Mon, Oct 03, 2011 at 11:26:25PM +0200, Adam Lackorzynski wrote: > (...) > Ok, but then it's good as it is displaying something. It's just the > driver that needs to learn about that. > > Adam Hi Adam, what steps are required to do that? Do I need to adjust the driver in lcd-omap3.c (l4/src/l4/pkg/drivers/lcd/src)? That file contains the following code: 335 static void configure_dss_beagleboard(l4_addr_t frame_buffer) 336 { 337 // for beagleboard just set the framebuffer address and let it run, 338 // everything else is already configured by U-Boot 339 write_dss_reg(Reg_dispc_gfx_ba0, frame_buffer); 340 write_dss_reg(Reg_dispc_gfx_ba1, frame_buffer); 341 } So it should just work. Maybe a newer version of U-Boot solves this? Sorry for these newbish questions. Thanks Giorgio

2 3

Problem with l4linux on real hardware
by Shashi Sharma 07 Oct '11

07 Oct '11

Hi, I am trying to run l4linux on an AMD based server platform with 2 CPU with 16 cores in total. I built L4 and fiasco with default configuration. And then built l4linux-3.0 with x86-ux_defconfig. I setup the grub.cfg as follows. +++++++++++++++++++++++++++++++++++++++++++++++ set timeout=0 menuentry "l4linux" { echo "/bootstrap /bootstrap -modaddr 0x01100000" multiboot /bootstrap /bootstrap -modaddr 0x01100000 echo "/fiasco fiasco -serial_esc" module /fiasco fiasco -serial_esc echo "/sigma0 sigma0" module /sigma0 sigma0 echo "/moe moe rom/l4linux.cfg" module /moe moe rom/l4linux.cfg echo "/l4linux.cfg l4linux.cfg" module /l4linux.cfg l4linux.cfg echo "/l4re l4re" module /l4re l4re echo "/ned ned" module /ned ned echo "/io io" module /io io echo "/rtc rtc" module /rtc rtc echo "/mag mag" module /mag mag echo "/fb-drv fb-drv" module /fb-drv fb-drv echo "/x86-legacy.devs x86-legacy.devs" module /x86-legacy.devs x86-legacy.devs echo "/l4lx-x86.io l4lx-x86.io" module /l4lx-x86.io l4lx-x86.io echo "/vmlinuz vmlinuz" module /vmlinuz vmlinuz echo "/drops-rd.rd drops-rd.rd" module /drops-rd.rd drops-rd.rd } ++++++++++++++++++++++++++++++++++++++++++++++++++ And here is the kernel command line. ++++++++++++++++++++++++++++++++++++++++++++++++++++ " mem=128M earlyprintk=yes showpfexc=1 console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk_size=20000 init=/bin/sh"); +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I am able to run this under qemu. and it works great. But when I run it on the real Hardware I get following error. Can you please help me with this. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ l4linux | INITRD: Size of RAMdisk is 16384KiB l4linux | RAMdisk from 10800000 to 11800000 [16384KiB] Linux version 3.0.0-l4-svn23 (shashi@shashi-desktop) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #53 Tue Oct 4 17:02:52 PDT 2011 [Firmware Bug]: TSC doesn't count with P0 frequency! BIOS-provided physical RAM map: L4Lx-Memory: 0000000000000000 - 0000000000400000 (reserved) L4Lx-Memory: 0000000000400000 - 0000000000728000 (usable) L4Lx-Memory: 0000000000728000 - 0000000000800000 (unusable) L4Lx-Memory: 0000000000800000 - 0000000008800000 (usable) Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! last_pfn = 0x8800 max_arch_pfn = 0x100000 init_memory_mapping: 0000000000000000-0000000008800000 INITRD: 10800000 - 11800000 136MB LOWMEM available. mapped low ram: 0 - 08800000 low ram: 0 - 08800000 Zone PFN ranges: DMA 0x00000400 -> 0x00000000 Normal 0x00000000 -> 0x00008800 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000400 -> 0x00000728 0: 0x00000800 -> 0x00008800 Allocating PCI resources starting at 8800000 (gap: 8800000:f7800000) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 33312 Kernel command line: mem=128M earlyprintk=yes showpfexc=1 console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk_size=20000 init=/bin/sh console [earlykdb0] enabled PID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Initializing CPU#0 l4linux | Page fault: addr = 00000000 pc = 00476cf6 (ro) l4linux | Page fault (non-resolved): pfa=0 pc=476cf6 l4linux | EX: 0: pc = 00476cf6 sp = 0063fcf0 trapno = 0xe err/pfa = 0x0 r Die message: Trap: 14 Trap: 14: 0004 [#1] Modules linked in: Pid: 0, comm: swapper Not tainted 3.0.0-l4-svn23 #53 EIP: 0000:[<00476cf6>] EFLAGS: 00010206 CPU: 0 EIP is at kmem_cache_alloc+0x26/0x80 EAX: b3000600 EBX: 00000020 ECX: 00000020 EDX: 00000020 ESI: 00000000 EDI: 00000001 EBP: 0063fd00 ESP: 0063fce8 DS: 0000 ES: 0000 FS: 0023 GS: 0043 SS: 0023 Process swapper (pid: 0, ti=0063e000 task=00643000 task.ti=0063e000) Stack: 0063fcf0 00000000 00000000 0000000b 00649d80 00000001 0063fd24 00427835 00000000 0000ffff 0000000b 0063fd38 00643000 0063fd6c 00000000 0063fd44 004281c5 00000001 00643258 0000000b 0000000b 00643000 00000000 0063fd64 Call Trace: [<00427835>] __sigqueue_alloc+0x45/0xc0 [<004281c5>] T.954+0x95/0x210 [<004297cc>] force_sig_info+0x5c/0xb0 [<00403443>] l4x_deliver_signal+0x43/0x70 [<004faa07>] ? number+0x357/0x370 [<004faa07>] ? number+0x357/0x370 [<00400700>] ? l4x_vcpu_handle_kernel_exc+0x50/0x60 [<004046af>] l4x_vcpu_entry_kern+0x54f/0xaa0 [<004fc2aa>] ? vsnprintf+0x2da/0x430 [<0041fffc>] ? timespec_add_safe+0x1c/0x70 [<0041c805>] ? console_unlock+0x165/0x1b0 [<00662c79>] ? xstate_enable_boot_cpu+0x8d/0x210 [<004fc2aa>] ? vsnprintf+0x2da/0x430 [<0041c10f>] ? print_tainted+0x8f/0xc0 [<00404c00>] ? l4x_vcpu_entry_kern+0xaa0/0xaa0 [<0040543b>] l4x_vcpu_entry+0x83b/0x1580 [<0041c805>] ? console_unlock+0x165/0x1b0 [<0041cc13>] ? vprintk+0x143/0x340 [<00668fb0>] ? alloc_large_system_hash+0x1ac/0x1d8 [<00404c00>] ? l4x_vcpu_entry_kern+0xaa0/0xaa0 [<00673601>] ? xsave_init+0x20/0x22 [<00674094>] ? cpu_init+0x71/0x76 [<00660fb9>] ? trap_init+0x224/0x22c [<0065d4d1>] ? start_kernel+0x132/0x294 [<0065d1c9>] ? kernel_init+0x102/0x102 [<00418000>] ? dequeue_task_idle+0x10/0x30 [<00418000>] ? dequeue_task_idle+0x10/0x30 [<0066316f>] ? i386_start_kernel+0x82/0x8a [<00418000>] ? dequeue_task_idle+0x10/0x30 [<006601c3>] ? l4x_linux_startup+0x2d9/0x2e1 [<00411000>] ? x86_pmu_del+0xa0/0xc0 Code: 27 00 00 00 00 55 89 e5 83 ec 10 89 5d f4 8b 1d 30 b6 65 00 89 75 f8 89 c6 89 7d fc 21 d3 e8 62 c8 f8 ff 89 45 f0 e8 2a c8 f8 ff <8b EIP: [<00476cf6>] kmem_cache_alloc+0x26/0x80 SS:ESP 0023:0063fce8 ---[ end trace 4eaa2a86a8e2da22 ]--- Kernel panic - not syncing: Attempted to kill the idle task! Pid: 0, comm: swapper Tainted: G D 3.0.0-l4-svn23 #53 Call Trace: [<005c161a>] panic+0x57/0x143 [<0041f3b7>] do_exit+0x5f7/0x630 [<0041c464>] ? kmsg_dump+0x34/0xc0 [<005c171e>] ? printk+0x18/0x1a [<0040da52>] oops_end+0x62/0x90 [<0040db15>] die+0x45/0x70 [<00476cf6>] ? kmem_cache_alloc+0x26/0x80 [<00427835>] ? __sigqueue_alloc+0x45/0xc0 [<004281c5>] ? T.954+0x95/0x210 [<004297cc>] ? force_sig_info+0x5c/0xb0 [<00403443>] ? l4x_deliver_signal+0x43/0x70 [<004faa07>] ? number+0x357/0x370 [<004faa07>] ? number+0x357/0x370 [<00400700>] ? l4x_vcpu_handle_kernel_exc+0x50/0x60 [<004046af>] ? l4x_vcpu_entry_kern+0x54f/0xaa0 [<004fc2aa>] ? vsnprintf+0x2da/0x430 [<0041fffc>] ? timespec_add_safe+0x1c/0x70 [<0041c805>] ? console_unlock+0x165/0x1b0 [<00662c79>] ? xstate_enable_boot_cpu+0x8d/0x210 [<004fc2aa>] ? vsnprintf+0x2da/0x430 [<0041c10f>] ? print_tainted+0x8f/0xc0 [<00404c00>] ? l4x_vcpu_entry_kern+0xaa0/0xaa0 [<0040543b>] ? l4x_vcpu_entry+0x83b/0x1580 [<0041c805>] ? console_unlock+0x165/0x1b0 [<0041cc13>] ? vprintk+0x143/0x340 [<00668fb0>] ? alloc_large_system_hash+0x1ac/0x1d8 [<00404c00>] ? l4x_vcpu_entry_kern+0xaa0/0xaa0 [<00673601>] ? xsave_init+0x20/0x22 [<00674094>] ? cpu_init+0x71/0x76 [<00660fb9>] ? trap_init+0x224/0x22c [<0065d4d1>] ? start_kernel+0x132/0x294 [<0065d1c9>] ? kernel_init+0x102/0x102 [<00418000>] ? dequeue_task_idle+0x10/0x30 [<00418000>] ? dequeue_task_idle+0x10/0x30 [<0066316f>] ? i386_start_kernel+0x82/0x8a [<00418000>] ? dequeue_task_idle+0x10/0x30 [<006601c3>] ? l4x_linux_startup+0x2d9/0x2e1 [<00411000>] ? x86_pmu_del+0xa0/0xc0 panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Thanks -Shashi

2 5

Ankh examples
by Ivan Loskutov 05 Oct '11

05 Oct '11

Hello, Hackers! How can I start ankh examples? I think I need use src/l4/pkg/ankh/doc/ankh.lua. But what is "require ("Aw");" and what must I write to files ankh.vbus and modules.list for x86 qemu? I use l4re-snapshot-2011081207. Thanks.

2 2

Object-Capabilities and Physical Memory Mapping
by François Goichon 05 Oct '11

05 Oct '11

Hello everyone, I have some questions regarding object-capabilities and physical memory mapping. - First of all, my goal is to manage and develop drivers on top of Fiasco. The documentation mentions the existence of an I/O server that does not seem to be on the repository anymore. Did I miss any announcement or is the I/O server in development? - As I did not find this server, I tried to code drivers from scratch but fail to see how I can map physical addresses in the first place. With other L4 kernels I would expect to find a map system call which would provide such a mapping to a thread with sufficient capabilities. In your model however, it seems that object-capabilities on such operations are transmitted to sigma0 only and that further mapping requests should go through sigma0. I actually lack any example on how to talk to sigma0 in the first place - what OC should I use as the first argument of l4sigma0_map_iomem(). - I also fail to understand the actual meaning of the environment OCs "map region" and "mem alloc" and the actual operations they provide, along with the "classic capabilities" my thread has on physical addresses for instance. Moreover, is there any configuration step where I can modify/list those "classic capabilities" passed to the thread spawned by moe? Any help/clarification would be greatly appreciated, François -- Goichon François PhD - Hardware Security in Operating Systems INSA Lyon, Dpt. Telecommunications - francois.goichon(a)insa-lyon.fr CITI Laboratory, INRIA - francois.goichon(a)inria.fr

3 3

Building L4Re
by BratSinot aka Куршамбай 03 Oct '11

03 Oct '11

Hello there! I want build L4Re. When i enter "make B=path/to/builddir", something happens, make runs a billion the same processes. In the end, make eating up all memory and system crashes. Snapshot 2011081207.

2 1

l4 task map in different factory.
by Chen Tian 02 Oct '11

02 Oct '11

Hello, If I create a new factory and using it to create a new task, can I map capability slots in this new task to some slots in a task that is created by an old (different) factory? Thanks. Chen

3 8

L4 courses
by Slex Sangiuliano 23 Sep '11

23 Sep '11

Morning, i'm searching some university courses that use L4. Searching on the net i found a document that talks of a university with a O.S. course with the target to build a small operating system based on l4 at the end of the course. Unfortunatly i haven't found slides and the university. Do you know some univeristy that uses l4 for the O.S. course? Thanks and sorry for the stupid request. Slex

4 4

VM API for TZ Decl != Impl
by Wesley Miaw 17 Sep '11

17 Sep '11

It looks like the definitions for l4_vm_run and l4_vm_run_u in vm.h are incorrect? The implementation signatures look like what they are supposed to be, as called from L4::Vm::run(...) in the 'vm' file in the same directory. -- Wesley Miaw wesley(a)wesman.net

2 1

clntsrv example capabilities
by Wesley Miaw 17 Sep '11

17 Sep '11

Hi, I'm still trying to fully understand capabilities, and I guess maybe what I need to do is create a new capability of some sort, but I thought asking might help me understand better. Basically, I am trying to build an example like the clntsrv example, and the server.cc attempts to register itself. If that fails, it prints out an error message saying "Readonly namespace?". I guess this is because the namespace is still 'rom'. I tried understanding the contents of the various .cfg files but I'm afraid I'm still confused. Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

pthread issue on ARM
by Ivan Loskutov 16 Sep '11

16 Sep '11

Hello, Hackers! I trying to porting a library from Linux to L4Re and I got a issue with libpthread on ARM device (beagleboard clone). If I create a detached thread use pthread_detach() or pthread attributes then error is occured. Error does not occur on x86, tested in qemu. I wrote a simple programm for test. Is problem in L4Re? Or should I make any steps before use pthread? Thank you! Code: #include <stdio.h> #include <string.h> #include <pthread.h> void *thread(void* arg) { int res; int num = (int)arg; printf("Start thread %d\n", num); res = pthread_detach(pthread_self()); printf("Detach thread %d (%d)\n", num, res); usleep(5000*num); printf("End thread %d\n", num); return 0; } int main(int argc, char* argv[]) { pthread_t t1, t2; printf("Test pthread\n"); while(1) { printf("new loop...\n"); pthread_create(&t1, NULL, thread, (void*)1); pthread_create(&t2, NULL, thread, (void*)2); usleep(100000); } return 0; } Log: Starting kernel ... L4 Bootstrapper Build: #101 Срд Сен 14 16:32:30 MSD 2011, 4.4.1 Scanning up to 128 MB RAM Memory size is 128MB (80000000 - 88000000) RAM: 0000000080000000 - 0000000087ffffff: 131072kB Total RAM: 128MB mod04: 810c5000-810e7ec0: pthread_test mod03: 810aa000-810c439c: l4re mod02: 8106f000-810a9b50: moe mod01: 81065000-8106e70c: sigma0 mod00: 81015000-81064f74: fiasco Moving 5 modules to 81100000 with offset eb000 moving module 05 { 810c5000-810e7ec0 } -> { 811b0000-811d2ec0 } moving module 04 { 810aa000-810c439c } -> { 81195000-811af39c } moving module 03 { 8106f000-810a9b50 } -> { 8115a000-81194b50 } moving module 02 { 81065000-8106e70c } -> { 81150000-8115970c } moving module 01 { 81015000-81064f74 } -> { 81100000-8114ff74 } Scanning fiasco Scanning sigma0 Scanning moe --init=rom/pthread_test Relocated mbi to [0x8100f000-0x8100f0e4] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list regions [ 80001000, 800019ff] { a00} Kern fiasco [ 80002000, 80061fff] { 60000} Kern fiasco [ 80090000, 800969bf] { 69c0} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 8017618b] { 3618c} Root moe [ 80178000, 8018ed0f] { 16d10} Root moe [ 81000000, 810143eb] { 143ec} Boot bootstrap [ 8100f000, 8100f1e1] { 1e2} Root Multiboot info [ 81195000, 811d2ebf] { 3dec0} Root Modules Memory API Version: (87) experimental Sigma0 config ip:800900e0 sp:81013704 Roottask config ip:801401c0 sp:00000000 Starting kernel fiasco at 80001000 Hello from Startup::stage2 Initialize page table Vmem_alloc::init() Cache config: ON ID_PFR0: 00001031 ID_PFR1: 00000011 ID_DFR0: 00010400 ID_AFR0: 00000000 ID_MMFR0: 31100003 ID_MMFR1: 20000000 ID_MMFR2: 01202000 ID_MMFR3: 00000011 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 1, v: c, i: 41, t: hard, p: dbl/sngl Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden Rev: rUNKNOWN compiled with gcc 4.4.1 for Beagleboard [] Build: #1 Чтв Сен 8 11:49:39 MSD 2011 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:80000000;80000fff] [0:80062000;8008ffff] [0:80097000;80097fff] [0:8009f000;8013ffff] [4:80140000;80176fff] [0:80177000;80177fff] [4:80178000;8018efff] [0:8018f000;8100efff] [4:8100f000;8100ffff] [0:81010000;81194fff] [4:81195000;811d2fff] [0:811d3000;86ffffff] IOMEM:---------------------- [0:0;7fffffff] [0:88000000;ffffffff] MOE: Hello world MOE: found 113680 KByte free memory MOE: found RAM from 80000000 to 87000000 MOE: allocated 112 KByte for the page array @0x80062000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [81195000-811af39c] [C:503000] l4re BOOTFS: [811b0000-811d2ec0] [C:504000] pthread_test MOE: cmdline: moe --init=rom/pthread_test MOE: Starting: rom/pthread_test MOE: loading 'rom/pthread_test' Test pthread new loop... Start thread 1 Detach thread 1 (0) Start thread 2 Detach thread 2 (0) End thread 1 L4Re[rm]: unhandled read page fault @300d3c pc=1003b54 L4Re: unhandled exception: pc=0x1003b54 End thread 2 new loop... modules.list: modaddr 0x01100000 entry pthread_test roottask moe --init=rom/pthread_test module l4re module pthread_test

2 4

L4Re/L4Android specify RAM size on Beagleboard
by giowck 15 Sep '11

15 Sep '11

Hi, when running L4Linux/L4Android on the Beagleboard (rev. C4), only 128MB of 256MB RAM are detected by the bootstrap process. Here [1] you write that the older Beagleboard has only 128MB, so this is default setting. As described in that thread, I tried to create the Makeconf.boot file, and it works so far (image is build with 256MB RAM), but still only 128MB are actualy detected (limited by scan): L4 Bootstrapper Build: #30 Di 6. Sep 14:38:47 CEST 2011, 4.5.1 Scanning up to 256 MB RAM Memory size is 128MB (Limited by Scan) (80000000 - 88000000) RAM: 0000000080000000 - 0000000087ffffff: 131072kB Total RAM: 128MB Please see [2] for the full bootstrap log. I already tried to adjust manually the support.h and startup.cc file in the src/l4/pkg/bootstrap/server/src directory, resulting exactly the same issue. By the way, I think this is causing L4Android to fail during boot, since memory is not correctly allocated: android | l4x_setup_memory: Can't get main memory of 256MB! MOE: mem_alloc: quota: limit=-1 Byte, used=11572080 Byte MOE: mem_alloc: global: avail=57008128 Byte android | Terminating L4Linux. mag | GC: step this=0x108d220 _life = 0x13228 mag | GC: object=0x13228 Thank you for your help so far! Regards Giorgio [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2011/004773.html [2] http://pastebin.com/nHQYGz6s

2 3

Re: Sigma0 raised exception on boot
by Wesley Miaw 14 Sep '11

14 Sep '11

On Wed, 2011-08-03 at 20:51 +0000, Adam Lackorzynski wrote: > On Wed Aug 03, 2011 at 12:58:08 +0100, Anna Fischer wrote: > > I'm running Fiasco on the PandaBoard. On platform boot I'm getting an > > error that Sigma0 raised an exception and then Fiasco panics and the > > boot process stops. > > > > Any idea what the problem could be? I can't find any more information to > > debug this properly. I have compile Fiasco.OC and L4Re for the > > PandaBoard platform. The board has 1GB memory. > > > > KERNEL: Warning: Sigma0 raised an exception --> HALT > > Panic: ... > > Return reboots, "k" enters L4 kernel debugger... > > In src/kern/thread-ipc.cpp, before the message "Sigma0 raised an > exception", please add an 'ts->dump();' and retry. This should show more > info on what's going on. This is something that should definitely not > happen. I'm wondering if a solution was ever found to this problem? I am hitting the same error on my Versatile Express rev. D board. My dump output looks similar to Anna's, but with a different RAM base address: EXCEPTION: swi pfa=6009e00c, error=00200000 R[0]: 6009e00c 60096510 0000000f 60096710 6009e018 60002000 0000000f 00000001 R[8]: 60096510 00000000 00000000 00000000 00000000 61013704 27102178 ffffff04 Here's Anna's dump for comparison: EXCEPTION: swi pfa=8009e00c, error=00200000 R[0]: 8009e00c 80096b50 0000000f 80094dd4 8009e018 80002000 0000000f 00000001 R[8]: 80096b50 00000000 00000000 00000000 80096d48 81013044 45559145 ffffff04 This is happening as a result of the call to sigma0_thread->activate() inside kernel_thread-std.cpp. I haven't been able yet to track it down farther. Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

Re: build error: No rule to make target crtendS.o
by Wesley Miaw 13 Sep '11

13 Sep '11

On Mon, September 12, 2011 09:45, Adam Lackorzynski wrote: > Hi, > On Mon Sep 12, 2011 at 08:38:56 -0700, Wesley Miaw wrote: >> Do you have any clues as to why I only get garbage printed out when I try to run one of the bootstrap programs? > Hmm, the baud-rate in bootstrap is set to 115200, so that's what you're using? IIRC the boot monitor is using 38400. Thanks, Adam. That was exactly the problem for why I was getting garbage. I didn't think to guess the bootstrap might be changing the console baud rate. I've tried changing the code to use 38400 instead of 115200 (because I can't find a way to change the board's startup to use 115200, only post-startup, which makes things inconvenient) but all of my attempts to change the values of 115200 to 38400 in the code don't seem to have any effect. I had to switch the RAM_BASE to 0x60000000 but after doing that, it looks like things should be working. I also changed the Fiasco globalconfig settings to change it to VEXPRESS and use 0x60000000 as the RAM location. I noticed there are two builds of Fiasco being created also. One of which is multi-core and has a TrustZone option. The other does not: arm-mp-rv-pb11mp and arm-up-rv-9. I'm not sure which one is getting used right now. Anyway, doing this got everything to load until the point where it says there is an invalid System ID. I'm guessing I still need to tweak the kernel configuration but at least I've made some good progress today! Starting kernel fiasco at 60001000 Realview System ID: Rev=3 HBI=190 Build=f Arch=5 FPGA=05 Invalid System ID for this kernel config Expected (3190f505 & ffffff00) == 1190f500 Stopping. Thanks for your help. :) -- Wesley Miaw wesley(a)wesman.net

2 1

Re: build error: No rule to make target crtendS.o
by Wesley Miaw 12 Sep '11

12 Sep '11

Hi Adam, Do you have any clues as to why I only get garbage printed out when I try to run one of the bootstrap programs? I thought it might be because I need to use the generic-hosted.ld linker script packaged with arm-none-eabi, but since you said you think everything should work with arm-none-linux-gnueabi, I'm questioning my conclusion now. (I haven't gotten around to testing a build with arm-none-eabi and generic-hosted.ld yet.) Thanks, -- Wesley Miaw wesley(a)wesman.net On Sep 12, 2011, at 3:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > > On Sun Sep 11, 2011 at 10:48:57 -0700, Wesley Miaw wrote: >> On Sep 11, 2011, at 3:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: >>> >>> On Sat Sep 10, 2011 at 12:26:05 -0700, Wesley Miaw wrote: >>>> I'm not getting any errors printed out on the console when I run the >>>> ELF or RAW bootstrap binaries. It just prints out a line of garbage >>>> (e.g. ? or other random characters). Then I have to hit the reset >>>> button. This is >>> >>> You were mentioning a 'too many headers error' when compiling/linking >>> with arm-none-linux-gnueabi which you seemed to not get with >>> arm-none-eabi. I would like to understand what makes the difference in >>> your setup and then see further. >> >> Ah, I see. I don't know why I got that error originally when compiling >> L4, but I am no longer getting that error. Maybe I did something wrong >> (or remembering things incorrectly)--I see in the bootstrap linker >> script that it purposefully combines the data and bss sections with a >> comment that sounds like it is explicitly working around the problem >> of a regular linker script creating too many headers. >> >> If I compile some other program I write myself to ELF, like a single >> file Hello World, using arm-none-linux-gnueabi then I get the too many >> headers error when the ARM Boot Manager tries to flash the ELF binary. >> Switching to arm-none-eabi and using the generic-hosted.ld linker >> script fixes this problem. > > That's also the reason why bootstrap is generated into a single header, > because there are loaders that can only do one unfortunately, like the > one on this platform.

2 1

Re: build error: No rule to make target crtendS.o
by Wesley Miaw 12 Sep '11

12 Sep '11

On Sep 11, 2011, at 3:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > > On Sat Sep 10, 2011 at 12:26:05 -0700, Wesley Miaw wrote: >> I'm not getting any errors printed out on the console when I run the >> ELF or RAW bootstrap binaries. It just prints out a line of garbage >> (e.g. ? or other random characters). Then I have to hit the reset >> button. This is > > You were mentioning a 'too many headers error' when compiling/linking > with arm-none-linux-gnueabi which you seemed to not get with > arm-none-eabi. I would like to understand what makes the difference in > your setup and then see further. Ah, I see. I don't know why I got that error originally when compiling L4, but I am no longer getting that error. Maybe I did something wrong (or remembering things incorrectly)--I see in the bootstrap linker script that it purposefully combines the data and bss sections with a comment that sounds like it is explicitly working around the problem of a regular linker script creating too many headers. If I compile some other program I write myself to ELF, like a single file Hello World, using arm-none-linux-gnueabi then I get the too many headers error when the ARM Boot Manager tries to flash the ELF binary. Switching to arm-none-eabi and using the generic-hosted.ld linker script fixes this problem. Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

Re: build error: No rule to make target crtendS.o
by Wesley Miaw 11 Sep '11

11 Sep '11

I'm not getting any errors printed out on the console when I run the ELF or RAW bootstrap binaries. It just prints out a line of garbage (e.g. ? or other random characters). Then I have to hit the reset button. This is I tried modifying the load and run memory addresses but that didn't make any difference. There weren't any build errors as far as I could see. Is there some other error you would like me to try capturing? Thanks, -- Wesley Miaw wesley(a)wesman.net On Sep 10, 2011, at 3:00 AM, l4-hackers-request(a)os.inf.tu-dresden.de wrote: > Hi, > > On Fri Sep 09, 2011 at 13:09:09 -0700, Wesley Miaw wrote: >>>> % arm-none-eabi-gcc --version >>>> arm-none-eabi-gcc (Linaro GCC 4.5-2011.02-0) 4.5.2 >>>> make[8]: *** No rule to make target >> `/opt/armgcc/lib/gcc/arm-none-eabi/4.5.2//crtendS.o', needed by >> `libl4sys.so'. Stop. >>> >>> Please use the arm-none-linux-gnueabi version of gcc. Looks like we >>> might not need to link crtendS.o at least with 4.5 but I'm not sure >>> currently for other versions. >> >> I'm having trouble understanding how the bootstrap images are supposed to >> be run on an ARM board if they are compiled with arm-none-linux-gnueabi >> instead of arm-none-eabi. Reading the Sourcery G++ Lite documentation, and >> talking to ARM support, bare metal should be compiled using arm-none-eabi. >> >> I am able to compile a hello world application for execution off the >> Versatile Express Boot Monitor using arm-none-eabi but not when using >> arm-none-linux-gnueabi (too many headers error). I saw in the bootstrap >> linker script that the data and bss sections are combined to fix this >> problem. But when I try to run one of the E=hello bootstrap images (ELF or >> RAW) I get garbage printed out. With arm-none-eabi I have to specify a >> 'hosted' linker script to get it to output text. >> >> Fiasco.OC's Features web page states it supports the Versatile Express >> board. I'm unable to find any documentation on it though. >> >> At this point, would I need to modify the build to use arm-none-eabi and >> the Makeconf.local to use the correct arm-none-eabi linker script and >> build option (e.g. -mcpu=cortex-a9)? > > I would like to see the errors you are getting with a non-modified > setup. For basic things like bootstrap it does not matter whether it is > the arm-none-eabi or arm-none-linux-gnueabi as it does not make use of > any of those specifics. I for example use the arm-none-linux-gnueabi > variant just fine. Also, this does not have to do anything with the > specific board such as Versatile Express or others, or with the specific > CPU variant the compiler is targeting for. This is 'just' a compile/link > issue.

2 1

Re: build error: No rule to make target crtendS.o
by Wesley Miaw 10 Sep '11

10 Sep '11

Hi Adam, >> % arm-none-eabi-gcc --version >> arm-none-eabi-gcc (Linaro GCC 4.5-2011.02-0) 4.5.2 >> make[8]: *** No rule to make target `/opt/armgcc/lib/gcc/arm-none-eabi/4.5.2//crtendS.o', needed by `libl4sys.so'. Stop. > > Please use the arm-none-linux-gnueabi version of gcc. Looks like we > might not need to link crtendS.o at least with 4.5 but I'm not sure > currently for other versions. I'm having trouble understanding how the bootstrap images are supposed to be run on an ARM board if they are compiled with arm-none-linux-gnueabi instead of arm-none-eabi. Reading the Sourcery G++ Lite documentation, and talking to ARM support, bare metal should be compiled using arm-none-eabi. I am able to compile a hello world application for execution off the Versatile Express Boot Monitor using arm-none-eabi but not when using arm-none-linux-gnueabi (too many headers error). I saw in the bootstrap linker script that the data and bss sections are combined to fix this problem. But when I try to run one of the E=hello bootstrap images (ELF or RAW) I get garbage printed out. With arm-none-eabi I have to specify a 'hosted' linker script to get it to output text. Fiasco.OC's Features web page states it supports the Versatile Express board. I'm unable to find any documentation on it though. At this point, would I need to modify the build to use arm-none-eabi and the Makeconf.local to use the correct arm-none-eabi linker script and build option (e.g. -mcpu=cortex-a9)? Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

loading boot task
by Chen Tian 09 Sep '11

09 Sep '11

Hi, When Fiasco.OC loads the boot task, how are physical pages allocated for different elf sections? I am experiencing a page fault when accessing the second page that contains .bss section data. Is this normal? It will be great if someone can tell me where the boot task loading is implemented in the kernel. Thanks a lot. Chen

2 2

L4Android bootstrap errors
by giowck 07 Sep '11

07 Sep '11

Hi, I'm trying to get L4Android working on a BeagleBoard (rev. C4). After some minor issues, I finally managed to build L4Re, Fiasco.OC, L4Linux and L4Android successfully. Everything works great on my board, including L4Linux. But L4Android gives me some errors during the bootstrap: io | Io service io | L4Re[rm]: unhandled read page fault @40000c pc=102b4c8 io | L4Re: unhandled exception: pc=0x102b4c8 Please see [1] for the full bootstrap (target: ARM beagleboard). To exclude some hardware related issues, I rebuilt L4Android with realview board (ARM) as target, in order to test it using qemu. This time, I get the following error: android | L4Re: unhandled exception: pc=0xa80001c8 Please see [2] for the full bootstrap (target: ARM realview board). Would be nice if someone could build L4Android for realview-b and tell me if it works in qemu. Maybe those errors are related to my newbieness :D Just another thing. On the L4Android Website, in the 'build diskimage' instructions, you write: "Next we need to modify the init.rc script. Mount the newly created image and locate the section where the system and data partition are to be mounted and replace the commands with the lines following the mount:" mount cramfs /l4bdds0 /system mount cramfs /l4bdds0 /system ro remount mount tmpfs tmpfs /data size=32M Then I saw that on your prebuilt root/system images for x86, the "on fs" section of the init.rc file is empty: on fs # mount mtd partitions So, i could not compare the section with mine, which looks the following: on fs # mount mtd partitions # Mount /system rw first to give the filesystem a chance to save a checkpoint # mount yaffs2 mtd@system /system # mount yaffs2 mtd@system /system ro remount # mount yaffs2 mtd@userdata /data nosuid nodev mount cramfs /l4bdds0 /system mount cramfs /l4bdds0 /system ro remount mount tmpfs tmpfs /data size=32M mount yaffs2 mtd@cache /cache nosuid nodev #unchanged Anyway, I tried to empty the "on fs" section like on the prebuilt images, but the above errors still persist. So any idea about those errors? Thank you! Giorgio Build environment in use ======================== - L4Re/L4Linux/Fiasco.OC: l4re-snapshot-2011062216 (not the last revision, since l4android needs to be updated) - L4Android: latest available revision (19 Jul 2011) - Compiler: CodeSourcery (arm-2010.09-50-arm-none-linux-gnueabi) - OS: Ubuntu 11.04 x86 [1] http://pastebin.com/95M7iiPv [2] http://pastebin.com/eYvM65ij

3 3

L4Android servicemanager segfault
by LeMay, Michael D 01 Sep '11

01 Sep '11

Hello, I'm trying to configure L4Android for the RealView PBX A9 emulated by QEMU, but I'm experiencing the segfault indicated near the end of this bootstrap log: L4 Bootstrapper Build: #25 Mon Aug 29 22:02:55 CDT 2011, 4.5.2 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod13: 0174b000-03a96000: system-arm-ginger.img mod12: 0164b000-0174b000: root-arm-ginger.img mod11: 012a9000-0164a448: vmlinuz.android mod10: 012a8000-012a810a: l4_android-arm.vbus mod09: 012a7000-012a74c1: arm-rv-eb.devs mod08: 012a6000-012a665f: l4_gingerbread-arm.cfg mod07: 0127c000-012a55b8: fb-drv mod06: 011ee000-0127b46c: mag mod05: 01113000-011edb58: io mod04: 010bf000-011121b8: ned mod03: 010a5000-010be510: l4re mod02: 0106b000-010a45f0: moe mod01: 01061000-0106a33c: sigma0 mod00: 01015000-0106036c: fiasco Moving 14 modules to 1100000 with offset eb000 moving module 14 { 174b000-3a96000 } -> { 1836000-3b81000 } moving module 13 { 164b000-174b000 } -> { 1736000-1836000 } moving module 12 { 12a9000-164a448 } -> { 1394000-1735448 } moving module 11 { 12a8000-12a810a } -> { 1393000-139310a } moving module 10 { 12a7000-12a74c1 } -> { 1392000-13924c1 } moving module 09 { 12a6000-12a665f } -> { 1391000-139165f } moving module 08 { 127c000-12a55b8 } -> { 1367000-13905b8 } moving module 07 { 11ee000-127b46c } -> { 12d9000-136646c } moving module 06 { 1113000-11edb58 } -> { 11fe000-12d8b58 } moving module 05 { 10bf000-11121b8 } -> { 11aa000-11fd1b8 } moving module 04 { 10a5000-10be510 } -> { 1190000-11a9510 } moving module 03 { 106b000-10a45f0 } -> { 1156000-118f5f0 } moving module 02 { 1061000-106a33c } -> { 114c000-115533c } moving module 01 { 1015000-106036c } -> { 1100000-114b36c } Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/l4_gingerbread-arm.cfg Relocated mbi to [0x100f000-0x100f1fc] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 19ff] { a00} Kern fiasco [ 2000, 5cfff] { 5b000} Kern fiasco [ 90000, 9e17b] { e17c} Sigma0 sigma0 [ 140000, 17160b] { 3160c} Root moe [ 178000, 18eec7] { 16ec8} Root moe [ 1000000, 10143eb] { 143ec} Boot bootstrap [ 100f000, 100f2f9] { 2fa} Root Multiboot info [ 1190000, 3b80fff] { 29f1000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:000900e0 sp:01013044 Roottask config ip:00140178 sp:00000000 Starting kernel fiasco at 00001000 Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 L2: ID=00000000 Type=00000000 L2 cache enabled Hello from Startup::stage2 Initialize page table Number of IRQs available at this GIC: 96 Vmem_alloc::init() Cache config: ON ID_PFR0: 00001031 ID_PFR1: 00000011 ID_DFR0: 00000000 ID_AFR0: 00000000 ID_MMFR0: 00100103 ID_MMFR1: 20000000 ID_MMFR2: 01230000 ID_MMFR3: 00002111 SERIAL ESC: allocated IRQ 44 for serial uart Not using serial hack in slow timer handler. [1;32mWelcome to Fiasco.OC (arm)! [0;32mL4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden Rev: r36 compiled with gcc 4.5.2 for Realview [] Build: #1 Mon Aug 29 13:29:34 CDT 2011 [0m Calibrating timer loop... done. SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:5d000;8ffff] [0:9f000;13ffff] [4:140000;171fff] [0:172000;177fff] [4:178000;18efff] [0:18f000;100efff] [4:100f000;100ffff] [0:1010000;118ffff] [4:1190000;3b80fff] [0:3b81000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 202084 KByte free memory MOE: found RAM from 5d000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [1190000-11a9510] [C:503000] l4re BOOTFS: [11aa000-11fd1b8] [C:504000] ned BOOTFS: [11fe000-12d8b58] [C:505000] io BOOTFS: [12d9000-136646c] [C:506000] mag BOOTFS: [1367000-13905b8] [C:507000] fb-drv BOOTFS: [1391000-139165f] [C:508000] l4_gingerbread-arm.cfg BOOTFS: [1392000-13924c1] [C:509000] arm-rv-eb.devs BOOTFS: [1393000-139310a] [C:50a000] l4_android-arm.vbus BOOTFS: [1394000-1735448] [C:50b000] vmlinuz.android BOOTFS: [1736000-1836000] [C:50c000] root-arm-ginger.img BOOTFS: [1836000-3b81000] [C:50d000] system-arm-ginger.img MOE: cmdline: moe rom/l4_gingerbread-arm.cfg MOE: Starting: rom/ned rom/l4_gingerbread-arm.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4_gingerbread-arm.cfg' [31mio | Io service[0m [31mio | Ready. Waiting for request.[0m [36mfb | libio: Warning: Finding 'icu' in system bus failed with 'No such object found'[0m [36mfb | Using LCD driver: ARM AMBA PrimeCell 11x[0m [32mmag | Hello from MAG[0m [36mfb | Running on QEmu (assuming PL111).[0m [36mfb | Video memory is at virtual 0x4000 (size: 0x180000 Bytes)[0m [36mfb | Physical video memory is at 0x48c000[0m [36mfb | Color mode: 11:5:0 5:6:5[0m [36mfb | Detected a 'ARM AMBA PrimeCell PL111' device.[0m [36mfb | Configure 8.4 CLCD[0m [36mfb | Starting server loop[0m [32mmag | mapped frame buffer at 0x200000[0m [32mmag | View::Info:[0m [32mmag | flags: 0[0m [32mmag | size: 1024x768 pos: 0, 0[0m [32mmag | bytes_per_line: 2048[0m [32mmag | buffer_offset: 0[0m [32mmag | RGBA(2): 5(11):6(5):5(0):0(0)[0m [32mmag | memory 200000-380000[0m [32mmag | Plugin: Mag_client service started[0m [32mmag | Plugin: Frame-buffer service started[0m [32mmag | L4INPUT native mode activated[0m [32mmag | L4INPUT: !!! W A R N I N G !!![0m [32mmag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT.[0m [32mmag | L4INPUT: !!! W A R N I N G !!![0m[32m[0m [32mmag | pl050: got memory 10006000, virtual base at 0x102000, IRQ 52[0m [32mmag | input: AT Raw Set 2 keyboard on AMBA KMI Kbd[0m [32mmag | pl050: got memory 10007000, virtual base at 0x103000, IRQ 53[0m [32mmag | input: ImExPS/2 Generic Explorer Mouse on AMBA KMI mou[0m [32mmag | l4drv: Could not find driver for OMAP_TSC.[0m [32mmag | l4drv: Could not find driver for OMAP_KP.[0m [32mmag | connect "AT Raw Set 2 keyboard", AMBA KMI Kbd/input0[0m [32mmag | connect "ImExPS/2 Generic Explorer Mouse", AMBA KMI mou/input0[0m [33mandroid | libio: Warning: Finding 'icu' in system bus failed with 'No such device'[0m [33mandroid | PH 0 (t: 1) offs=00008000 vaddr=00100000 vend=0050efe4[0m [33mandroid | f_sz=[0m[33m00388538 memsz=0040efe4 flgs=rwx[0m [33mandroid | PH 1 (t: 4) offs=00390514 vaddr=00488514 vend=00488538[0m [33mandroid | f_sz=[0m[33m00000024 memsz=00000024 flgs=r-x[0m [33mandroid | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000[0m [33mandroid | f_sz=[0m[33m00000000 memsz=00000000 flgs=rwx[0m [33mandroid | Starting binary at 0x129498, argc=15 argv=0x80007f6c *argv=0xb1007fec argv0=rom/vmlinuz.android[0m [33mandroid | External resolver is at 0xa8000670[0m [33mandroid | [34;1m======> L4Linux 2.6 starting... <========[0m[0m [33mandroid | Linux version 2.6.39-l4+ (mdlemay2@...) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #3 SMP Mon Aug 29 21:01:42 CDT 2011[0m [33mandroid | Binary name: rom/vmlinuz.android[0m [33mandroid | This is an AEABI build.[0m [33mandroid | Linux kernel command line (14 args): [0m[33mconsole=ttyLv0 androidboot.console=ttyLv0 mem=128M l4bdds.add=rom/system-arm-ginger.img,rw boot=local android.ril=ttyLv1 ip=dhcp l4x_rd=rom/root-arm-ginger.img rw root=1:0 ramdisk_size=1500 init=/init --debug l4fb.touchscreen=1[0m[33m[0m [33mandroid | CPU mapping (l:p)[1]: 0:0[0m [33mandroid | Image: 00100000 - 00600000 [5120 KiB].[0m [33mandroid | Areas: Text: 00100000 - 00466000 [3480kB] (a bit longer)[0m [33mandroid | Data: 00466000 - 00483dc0 [119kB][0m [33mandroid | Initdata: 00100000 - 00128000 [160kB][0m [33mandroid | BSS: 00488538 - 0050efe4 [538kB][0m [33mandroid | Device scan:[0m [33mandroid | l4lx_thread_create: Created thread 415 (cpu0) (u:b3000400, v:b3000600, sp:00467ff0)[0m [33mandroid | main thread will be 415[0m [33mandroid | l4x_register_pointer_section: addr = 00100000 size = 4255744[0m [33mandroid | section-with-init: virt: 0x100000 to 0x50efe3 [4155 KiB][0m [33mandroid | section-with-init: Phys: 0x00722000 to 0x00b30fe4, Size: 4255716[0m [33mandroid | l4x_linux_startup: thread 415.[0m [33mandroid | Main thread running, waiting...[0m [33mandroid | main thread: received startup message.[0m [33mandroid | utcb 0xb3000400[0m [33mandroid | l4x_setup_memory: Forcing superpages for main memory[0m [33mandroid | l4re_global_env: 0xb1007e54[0m [33mandroid | Main memory size: 128MB[0m [33mandroid | Main memory: virt: 0x600000 to 0x85fffff [131072 KiB][0m [33mandroid | Main memory: Phys: 0x03c00000 to 0x0bc00000, Size: 134217728[0m [33mandroid | Filling lower ptabs...[0m [33mandroid | Done (495 entries).[0m [33mandroid | l4x_register_pointer_section: addr = 005ff000 size = 4096[0m [33mandroid | end: virt: 0x5ff000 to 0x5fffff [4 KiB][0m [33mandroid | end: Phys: 0x00bc8000 to 0x00bc9000, Size: 4096[0m [33mandroid | l4x_rd_path: rom/root-arm-ginger.img[0m [33mandroid | Loading: rom/root-arm-ginger.img[0m [33mandroid | INITRD: Size of RAMdisk is 1024KiB[0m [33mandroid | RAMdisk from 10600000 to 10700000 [1024KiB][0m [33mandroid | l4lx_thread_create: Created thread 41c (timer.i0) (u:b3000800, v:00000000, sp:004a5ff4)[0m [33mandroid | timer_irq_thread: Starting timer IRQ thread.[0m Linux version 2.6.39-l4+ (mdlemay2@...) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #3 SMP Mon Aug 29 21:01:42 CDT 2011 CPU: Fiasco [860f0001] revision 1 (ARMvundefined/unknown), cr=00000000 CPU: unknown data cache, unknown instruction cache cpu_v7_proc_init Machine: L4 Memory policy: ECC disabled, Data cache writealloc arm926_flush_kern_cache_all() INITRD: 10600000 - 10700000 PERCPU: Embedded 5 pages/cpu @00713000 s6208 r0 d14272 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 33781 Kernel command line: console=ttyLv0 androidboot.console=ttyLv0 mem=128M l4bdds.add=rom/system-arm-ginger.img,rw boot=local android.ril=ttyLv1 ip=dhcp l4x_rd=rom/root-arm-ginger.img rw root=1:0 ramdisk_size=1500 init=/init --debug l4fb.touchscreKernePID hash table entries: 1024 (order: 0, 4096 bytes) Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 0MB 133MB = 133MB total Memory: 129740k/129740k available, 6456k reserved, 0K highmem Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0x08600000 - 0x10600000 ( 128 MB) lowmem : 0x00000000 - 0x08600000 ( 134 MB) modules : 0xff100000 - 0x00100000 ( 16 MB) .init : 0x00100000 - 0x00128000 ( 160 kB) .text : 0x00129000 - 0x00464744 (3310 kB) .data : 0x00466000 - 0x00483dc0 ( 120 kB) Hierarchical RCU implementation. NR_IRQS:220 l4lx_irq_init: l4lx_irq_max = 220 l4lx_irq_dev_startup_timer(0) Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 269.10 BogoMIPS (lpj=1345536) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok Brought up 1 CPUs SMP: Total of 1 processors activated (269.10 BogoMIPS). NET: Registered protocol family 16 bio: create slab <bio-0> at 0 Switching to clocksource kip NET: Registered protocol family 2 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: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered UDP hash table entries: 128 (order: 0, 4096 bytes) UDP-Lite hash table entries: 128 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. Hi from the sample module [33mandroid | sample module: Also a warm welcome to the console[0m msgmni has been set to 253 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) l4fb l4fb.0: look for capability 'fb' as goos session l4fb l4fb.0: 640x480@16 2bypp, size: 614400 @ 10600000 l4fb l4fb.0: 5:6:5 11:5:0 linelen=1280 visual=2 Console: switching to colour frame buffer device 80x30 l4fb l4fb.0: l4fb L4 frame buffer device (refresh: 10jiffies) input: L4keyb '0' as /devices/virtual/input/input0 input: L4mouse '0' as /devices/virtual/input/input1 L4 serial driver ttyLv0 at MMIO 0x1 (irq = 210) is a L4 L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: Disk 'rom/system-arm-ginger.img' size = 36140 KB (35 MB) flags=101 addr=10697000 ------------[ cut here ]------------ WARNING: at /home/mdlemay2/tmp/l4android/kernel/softirq.c:159 local_bh_enable_ip+0xa0/0xac() [<001360ac>] (unwind_backtrace+0x0/0xf8) from [<00147b7c>] (warn_slowpath_common+0x50/0x60) [<00147b7c>] (warn_slowpath_common+0x50/0x60) from [<00147c40>] (warn_slowpath_null+0x1c/0x24) [<00147c40>] (warn_slowpath_null+0x1c/0x24) from [<0014de44>] (local_bh_enable_ip+0xa0/0xac) [<0014de44>] (local_bh_enable_ip+0xa0/0xac) from [<0019594c>] (bdi_register+0xec/0x150) [<0019594c>] (bdi_register+0xec/0x150) from [<001959dc>] (bdi_register_dev+0x2c/0x34) [<001959dc>] (bdi_register_dev+0x2c/0x34) from [<002ad8b8>] (add_disk+0x9c/0x27c) [<002ad8b8>] (add_disk+0x9c/0x27c) from [<001138fc>] (l4bdds_init+0x234/0x28c) [<001138fc>] (l4bdds_init+0x234/0x28c) from [<00100780>] (do_one_initcall+0xa0/0x16c) [<00100780>] (do_one_initcall+0xa0/0x16c) from [<00100918>] (kernel_init+0xcc/0x15c) [<00100918>] (kernel_init+0xcc/0x15c) from [<0012e5d0>] (kernel_thread_exit+0x0/0x8) ---[ end trace 9feec23bbcf28fc1 ]--- l4bdds0: detected capacity change from 0 to 37007360 l4bdds0: unknown partition table mousedev: PS/2 mouse device common for all mice TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type [32mmag | Input: new keyboard device (src='userdata: 0x1e2e8' stream='userdata: 0x13560')[0m [32mmag | bus='i8042' vendor=0x1 product=0x2 version=43907[0m[32m[0m RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 1024KiB [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\done. EXT2-fs (ram0): warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing init memory: 160K init: cannot open '/initlogo.rle' init: Unable to open persistent property directory /data/property errno: 2 init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead. init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' [33mandroid | cpu0: segfault for servicemanager(24) [T:a5] at 00000000, ip=00008ca2, pferror = 4[0m [33mandroid | 00008000 - 0000a000 r-xp 00000 /system/bin/servicemanager <====[0m [33mandroid | 0000a000 - 0000b000 rwxp 00002 /system/bin/servicemanager[0m [33mandroid | 0000b000 - 0000c000 rwxp[0m [33mandroid | 400ed000 - 400f5000 r-xs 00000 /dev/__properties__ (deleted)[0m [33mandroid | 40118000 - 40119000 r-xp[0m [33mandroid | afa00000 - afa03000 r-xp 00000 /system/lib/liblog.so[0m [33mandroid | afa03000 - afa04000 rwxp 00003 /system/lib/liblog.so[0m [33mandroid | afb00000 - afb20000 r-xp 00000 /system/lib/libm.so[0m [33mandroid | afb20000 - afb21000 rwxp 00020 /system/lib/libm.so[0m [33mandroid | afc00000 - afc01000 r-xp 00000 /system/lib/libstdc++.so[0m [33mandroid | afc01000 - afc02000 rwxp 00001 /system/lib/libstdc++.so[0m [33mandroid | afd00000 - afd40000 r-xp 00000 /system/lib/libc.so[0m [33mandroid | afd40000 - afd43000 rwxp 00040 /system/lib/libc.so[0m [33mandroid | afd43000 - afd4e000 rwxp[0m [33mandroid | b0001000 - b0009000 r-xp 00001 /system/bin/linker[0m [33mandroid | b0009000 - b000a000 rwxp 00009 /system/bin/linker[0m [33mandroid | b000a000 - b0013000 rwxp[0m [33mandroid | bf96f000 - bf991000 rw-p[0m [33mandroid | ffff0000 - ffff1000 r-xp[0m [33mandroid | 0: 00000000 00000000 afd46608 00000001 4: 0000a170 00000000 afd41504 bf990ccc[0m [33mandroid | 8: 00000000 00000000 00000000 00000000 12: 0000a1ac [01;34mbf990c88[0m 00008795 [01;34m00008ca2[0m[0m [33mandroid | CPSR: 40000030 Err: 00000004[0m [1;25r[25;1H [32m ---------------------------------------------------------------------[m CPU 0 [f0012190]: segfault [25;1H[32m[ l4lx.cpu0] jdb: [m[K I built the Android userspace from source using the generic-user configuration. Here is my L4Re configuration file: BUILD_SYSTEMS=arm_armv7a arm_armv7a-l4f COLOR_TERMINAL=y CONFIG_ARM_PLATFORM_TYPE="rv" CONFIG_BUILD_ABI="l4f" CONFIG_BUILD_ABI_l4f=y CONFIG_BUILD_ARCH="arm" CONFIG_BUILD_ARCH_arm=y CONFIG_CPU_ARM_ARMV7A=y CONFIG_CPU_ARMV6KPLUS=y CONFIG_CPU_ARMV6PLUS=y CONFIG_CPU="armv7a" CONFIG_CTAGS="ctags" CONFIG_DROPS_INSTDIR="/path/to/l4re" CONFIG_DROPS_STDDIR="/path/to/l4re" CONFIG_ETAGS="etags" CONFIG_LABEL="" CONFIG_LEX="flex" CONFIG_PLATFORM_ARM_rv=y CONFIG_RAM_BASE=0x0 CONFIG_RAM_SIZE_MB=256 CONFIG_YACC="yacc" GCCDIR=/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2 GCCLIBDIR=/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2/ GCCLIB_EH=/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2/libgcc_eh.a GCCLIB=/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2/libgcc.a GCCMAJORVERSION=4 GCCMINORVERSION=5 GCCNOSTACKPROTOPT=-fno-stack-protector GCCSUBVERSION=2 GCCSYSLIBDIRS=-L=/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2/ -L/opt/armgcc/bin/../lib/gcc/ -L/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2/../../../../arm-none-linux-gnueabi/lib/arm-none-linux-gnueabi/4.5.2/ -L/opt/armgcc/bin/../lib/gcc/arm-none-linux-gnueabi/4.5.2/../../../../arm-none-linux-gnueabi/lib/ -L/opt/armgcc/bin/../arm-none-linux-gnueabi/libc/lib/arm-none-linux-gnueabi/4.5.2/ -L/opt/armgcc/bin/../arm-none-linux-gnueabi/libc/lib/ -L/opt/armgcc/bin/../arm-none-linux-gnueabi/libc/usr/lib/arm-none-linux-gnueabi/4.5.2/ -L/opt/armgcc/bin/../arm-none-linux-gnueabi/libc/usr/lib/ GCCVERSION=4.5 HOST_SYSTEM=linux INT_CPP_NAME=cc1 INT_CXX_NAME=cc1plus INT_LD_NAME=arm-none-linux-gnueabi-ld LD_EMULATION=armelf_linux_eabi LD_GENDEP_PREFIX=LD_PRELOAD=libgendep.so LD_LIBRARY_PATH=/home/mdlemay2/tmp/l4re/l4/build/tool/gendep/64:/home/mdlemay2/tmp/l4re/l4/build/tool/gendep/32 LD_HAS_HASH_STYLE_OPTION=y LDVERSION=220 include /home/mdlemay2/tmp/l4re/l4/build/.config.indep Here is my Fiasco (r36) configuration file: # # Automatically generated make config: don't edit # Fiasco configuration # Mon Aug 29 13:29:25 2011 # # # Target configuration # # CONFIG_IA32 is not set # CONFIG_AMD64 is not set CONFIG_ARM=y CONFIG_PF_REALVIEW=y # CONFIG_PF_IMX is not set # CONFIG_PF_S3C2410 is not set # CONFIG_PF_TEGRA2 is not set # CONFIG_PF_OMAP is not set # CONFIG_PF_XSCALE is not set # CONFIG_PF_SA1100 is not set # CONFIG_PF_KIRKWOOD is not set # CONFIG_PF_INTEGRATOR is not set CONFIG_BSP_NAME="realview" # CONFIG_PF_REALVIEW_EB is not set # CONFIG_PF_REALVIEW_PB11MP is not set CONFIG_PF_REALVIEW_PBX=y # CONFIG_PF_REALVIEW_VEXPRESS is not set CONFIG_PF_REALVIEW_RAM_PHYS_BASE_0x0=y # CONFIG_PF_REALVIEW_RAM_PHYS_BASE_0x2 is not set # CONFIG_PF_REALVIEW_RAM_PHYS_BASE_0x7 is not set CONFIG_PF_REALVIEW_RAM_PHYS_BASE=0x0 CONFIG_PF_REALVIEW_L2CACHE=y CONFIG_ABI_VF=y CONFIG_PF_ARM_MP_CAPABLE=y CONFIG_CAN_ARM_CPU_CORTEX_A9=y CONFIG_ARM_CORTEX_A9=y # CONFIG_ARM_ALIGNMENT_CHECK is not set # CONFIG_ARM_CA9_ENABLE_SWP is not set # CONFIG_FPU is not set # # Kernel options # CONFIG_CONTEXT_4K=y # CONFIG_FINE_GRAINED_CPUTIME is not set CONFIG_SCHED_FIXED_PRIO=y # # Debugging # CONFIG_INLINE=y # CONFIG_NDEBUG is not set CONFIG_NO_FRAME_PTR=y # CONFIG_STACK_DEPTH is not set # CONFIG_LIST_ALLOC_SANITY is not set CONFIG_SERIAL=y CONFIG_JDB=y # CONFIG_JDB_LOGGING is not set # CONFIG_JDB_DISASM is not set # CONFIG_JDB_GZIP is not set # CONFIG_VMEM_ALLOC_TEST is not set # CONFIG_DEBUG_KERNEL_PAGE_FAULTS is not set # CONFIG_WARN_NONE is not set CONFIG_WARN_WARNING=y # CONFIG_WARN_ANY is not set # # Compiling # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_HOST_CC="gcc" CONFIG_HOST_CXX="g++" # CONFIG_VERBOSE is not set # CONFIG_MAINTAINER_MODE is not set CONFIG_LABEL="" # CONFIG_EXPERIMENTAL is not set CONFIG_PERF_CNT=y CONFIG_BIT32=y CONFIG_ARM_V7=y CONFIG_ARM_V6PLUS=y CONFIG_WARN_LEVEL=1 CONFIG_XARCH="arm" CONFIG_ABI="vf" I built an ELF image for QEMU and executed it with this command: qemu-system-arm -kernel build/images/bootstrap_lx_ginger-arm.elf -M realview-pbx-a9 -serial stdio -m 256 Any ideas on what's going wrong or next steps I can take to diagnose the issue? Thanks! Best regards, Michael LeMay http://m.lemays.org

2 3

How can I destroy a kernel object
by Chen Tian 30 Aug '11

30 Aug '11

Hello, Is there any L4RE API that allows me to destroy a kernel object that is created via l4_factory_create_xxx? Thanks. Chen

2 1

L4Android minor issue report
by giowck 29 Aug '11

29 Aug '11

Hi, I found a small issue during the build process of L4Android for x86 target (arm target build works as expected). When using the make command to generate images (e.g make grub2iso lx_gingerbread-x86), the following error appears: Processing entry 'l4_gingerbread' Could not find 'l4_gingerbread.cfg' with path '...' make[1]: *** [grub2iso] Error 2 make[1]: Exiting Directory '/home/giowck/tests/target_x86/l4re-snapshot-2011062216/src/l4' make: *** [grub2iso] Error 2 This is caused by an outdated module entry in the 'modules-x86.list' file in the 'configs' git repository (and L4Android Website in the 'Create ISO Image' instructions). Here are some 'x86' suffixes missing. Patch file ========== --- modules-x86.list 2011-08-28 13:43:09.669688003 +0200 +++ modules-x86_fixed.list 2011-08-28 13:44:02.546068212 +0200 @@ -1,6 +1,6 @@ modaddr 0x01100000 entry l4_gingerbread -roottask moe rom/l4_gingerbread.cfg +roottask moe rom/l4_gingerbread-x86.cfg kernel fiasco -serial_esc module l4re module ned @@ -8,9 +8,9 @@ module rtc module mag module fb-drv -module l4_gingerbread.cfg +module l4_gingerbread-x86.cfg module x86-legacy.devs -module l4_android.vbus +module l4_android-x86.vbus module vmlinuz.android module root-x86-ginger.img module system-x86-ginger.img With the above patch, the images are built successfully. It would be nice if you update the L4Android Website ("Create ISO Image") and the configs repository. Regards Giorgio

2 1

Broken links in L4Re documentation
by Michal Sojka 24 Aug '11

24 Aug '11

Hi, I've just browsed through L4Re documentation and found that links to examples in http://os.inf.tu-dresden.de/L4Re/doc/classL4Re_1_1Dataspace.html are broken. For example, one link poinst to http://os.inf.tu-dresden.de/L4Re/doc/examples_2libs_2l4re_2c_09_09_2shared_… and the correct URL seems to be http://os.inf.tu-dresden.de/L4Re/doc/examples_2libs_2l4re_2c_09_09_2shared_… -Michal

2 1

l4re-snapshot-2011081207 and l4android for arm: build error after update
by giowck 24 Aug '11

24 Aug '11

Hi, I downloaded the latest l4re snapshot (l4re-snapshot-2011081207), in order to compile it along with l4android for arm. Finally it compiles with the CodeSourcery cross compiler (as noted in the README file), where the previous snapshot failed and worked only for me with the 4.2-arm-softfloat compiler (without EABI support). But, with the latest snapshot I get a new error: # make L4ARCH=arm CROSS_COMPILE=arm-linux- -j4 make -C /home/wicklein/tests/l4android/kernel O=/home/wicklein/tests/l4android/l4android_builddir/. Package l4re-main was not found in the pkg-config search path. Perhaps you should add the directory containing `l4re-main.pc' to the PKG_CONFIG_PATH environment variable No package 'l4re-main' found Getting required compilation flags failed. L4OBJ: /home/wicklein/tests/l4re-snapshot-latest/obj/l4/arm-beagleboard L4_REQUIRED_MODS: l4re-main libc_be_minimal_log_io libc_minimal libsupc++_minimal log l4re_c-util libio libvcpu shmc /home/wicklein/tests/l4android/kernel/arch/l4/Makefile:315: *** Aborting.. Schluss. make[1]: *** [sub-make] Fehler 2 make: *** [all] Fehler 2 Just wanted to report that. Now I'll try to copy just the l4re-main.pc file from the old snapshot to the new pc directory. Regards Giorgio

2 1

Little fixup around pthreads
by Marc CHALAND 22 Aug '11

22 Aug '11

Hi guys, Symptoms are: sem_timedwait behaves quite like sem_wait after 0x80000000 usec system has been started. Regards Marc diff --git a/src/l4/pkg/uclibc/lib/libpthread/src/restart.h b/src/l4/pkg/uclibc/lib/libpthread/src/restart index 26ae5ea..92b71d3 100644 --- a/src/l4/pkg/uclibc/lib/libpthread/src/restart.h +++ b/src/l4/pkg/uclibc/lib/libpthread/src/restart.h @@ -37,7 +37,7 @@ static __inline__ int timedsuspend(pthread_descr self, { #if 1 extern uint64_t __attribute__((weak)) __libc_l4_kclock_offset; - uint64_t clock = abstime->tv_sec * 1000000 + abstime->tv_nsec / 1000; + uint64_t clock = ((uint64_t) abstime->tv_sec) * 1000000 + ((uint64_t) abstime->tv_nsec) / 1000; if (&__libc_l4_kclock_offset) clock -= __libc_l4_kclock_offset; l4_msgtag_t res = l4_usem_down_to(self->p_thsem_cap, &self->p_thsem,

3 3

[Fix] Small build fix for old Fiasco/L4Env version
by Sebastian Sumpf 16 Aug '11

16 Aug '11

Hi there, I attached a small build correction I encountered while building L4Env with Perl 5.12. This is necessary since Perl 5.11's and above 'split' does not automatically assign '@_' anymore. Greetings, Sebastian

2 1

Building L4Re, make errors
by giowck 12 Aug '11

12 Aug '11

Hi l4-hackers, I'm trying to compile the L4 Runtime for the x86 arch, using the latest snapshot (l4re-snapshot-2011062216). After "make setup" and "make", the following error interrupts the build process: "/home/giowck/tests/l4re-snapshot-2011062216/src/l4/pkg/uclibc-minimal/libc/Make.rules:22: *** unkwon source file: libc/signal/sigsetops.h. Abort." The full output of the make command is available on a pastebin [1]. I'm using: gcc-Version 4.6.1 (GCC), see [2] for the full "gcc -v" output. My system is Arch Linux i686. Maybe anyone can give me a hint? Thank you, Giorgio [1] http://pastebin.com/r4K4SFef [2] http://pastebin.com/1zLnLy9w

2 2

Test suite for Fiasco
by Bryce CR 11 Aug '11

11 Aug '11

Hello Hackers, I've been tinkering with the internals of Fiasco a bit, and I'm at the point where the kernel boots & runs hello as well as hello-shared without issue. The thing is, though, these tests seem to use only a fraction of my code (and I know there are some pretty sketchy lurkers in my code...), so I'm looking for a more thorough test of kernel capabilities to verify my changes are relatively operational in many/most cases. I'm aware of some options here, but I didn't want to use a hammer if all I need is a screwdriver. So, to you: what is the most straightforward way to test Fiasco with existing software? I'm aware of L4Linux and ORe as possibilities -- are these good options, or is there a simpler tool for the job? Thank you! --Bryce

2 5

question about read clock API in ARM
by 박찬주 07 Aug '11

07 Aug '11

Hello, I'm newbie in L4 and now i'm trying to find out how to get system clock info. My test environment is QEMU, ARM realview EB. In fiasco kernel, there is a function to read system's clock Clock::read_count(){ return Io::read<Mword>(SYS_24MHZ); } then how can I use this in l4re application? Is there any related API in l4re? Thanks in advance, david

2 1

Sigma0 raised exception on boot
by Anna Fischer 04 Aug '11

04 Aug '11

I'm running Fiasco on the PandaBoard. On platform boot I'm getting an error that Sigma0 raised an exception and then Fiasco panics and the boot process stops. Any idea what the problem could be? I can't find any more information to debug this properly. I have compile Fiasco.OC and L4Re for the PandaBoard platform. The board has 1GB memory. L4 Bootstrapper Build: #162 Wed Aug 3 12:52:02 BST 2011, 4.5.2 Scanning up to 1024 MB RAM Memory size is 1024MB (80000000 - c0000000) RAM: 0000000080000000 - 00000000bfffffff: 1048576kB Total RAM: 1024MB [...] Relocated mbi to [0x8100f000-0x8100f1b1] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list regions [ 80001000, 800019ff] { a00} Kern fiasco [ 80002000, 8005cfff] { 5b000} Kern fiasco [ 80090000, 8009e17b] { e17c} Sigma0 sigma0 [ 80140000, 8017160b] { 3160c} Root moe [ 80178000, 8018eec7] { 16ec8} Root moe [ 81000000, 810143eb] { 143ec} Boot bootstrap [ 8100f000, 8100f2ae] { 2af} Root Multiboot info [ 81190000, 8194dfff] { 7be000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:800900e0 sp:81013044 Roottask config ip:80140178 sp:00000000 Starting kernel fiasco at 80001000 Hello from Startup::stage2 Initialize page table Number of IRQs available at this GIC: 160 Vmem_alloc::init() Cache config: ON ID_PFR0: 00001231 ID_PFR1: 00000011 ID_DFR0: 00010444 ID_AFR0: 00000000 ID_MMFR0: 00100103 ID_MMFR1: 20000000 ID_MMFR2: 01230000 ID_MMFR3: 00102111 SERIAL ESC: allocated IRQ 106 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden Rev: r36 compiled with gcc 4.5.2 for Pandaboard [] Build: #4 Wed Aug 3 12:46:10 BST 2011 Calibrating timer loop... done. KERNEL: Warning: Sigma0 raised an exception --> HALT Panic: ... Return reboots, "k" enters L4 kernel debugger...

2 2

Dependencies
by Bryce CR 03 Aug '11

03 Aug '11

Hi Hackers, I'm attempting to build the Fiasco.OC kernel including several additional files. When I attempt to make, I get endless complaints about multiple definitions of functions. The catch is, every single file I have added has a unique include guard... A few things I want to check: > My files are written in standard c++ format, not Preprocess compatible format. E.g. I make use of namespaces. I haven't added the files to any modules lists / Makerules files, so my thinking is that I'm just trying to link with these files but not use any of their features (for testing purposes). My impression was that namespace usage would be tolerated for files used thus: Preprocess doesn't complain. > The c++ preprocessor is still run, correct? I don't see include guards in kernel source files: are these generated by Preprocess, or simply not needed? > Specifically, the errors start appearing at "==> Archiving into jdb_compound.o," and they complain about finding a definition of a function in my source file which was already defined in an object file, e.g.: jdb-ia32-amd64.o: In function `prio_queue_rel::query_iterator_priority__element::next()': /home/bryce/parsnip/fiasco_modified_src/recovery/src/kernel/fiasco/src/kern/R_test11impl.cpp:499: multiple definition of `prio_queue_rel::query_iterator_priority__element::next()' jdb.o:/home/bryce/parsnip/fiasco_modified_src/recovery/src/kernel/fiasco/src/kern/R_test11impl.cpp:499: first defined here I know that's not a lot to go on, but I'm not sure what else would be useful. Please let me know what I do to help you help me... Thank you! --Bryce

2 2

L4Linux and mmap
by Vasily Sartakov 03 Aug '11

03 Aug '11

Hallo. I try to use a mmap for communicate userspace application and other servers via kernel character driver. and its doesn't work. but, of course its work in native linux. my mmap call return no error, but when i try acces to memmory via returned pointer, i got seg fault Here is driver source and example program, based on mmap example: any of vmalloc or kalloc got seg fault: mmap ok, vaddr = 40034000 Segmentation fault //#include <linux/config.h> #include <linux/version.h> #include <linux/init.h> #include <linux/module.h> #include <linux/fs.h> #include <linux/cdev.h> #include <linux/slab.h> #include <linux/vmalloc.h> #include <linux/mm.h> #ifdef MODVERSIONS # include <linux/modversions.h> #endif #include <asm/io.h> /* character device structures */ static dev_t vhsm_dev; static struct cdev vhsm_cdev; /* methods of the character device */ static int vhsm_open(struct inode *inode, struct file *filp); static int vhsm_release(struct inode *inode, struct file *filp); static int vhsm_mmap(struct file *filp, struct vm_area_struct *vma); /* the file operations, i.e. all character device methods */ static struct file_operations vhsm_fops = { .open = vhsm_open, .release = vhsm_release, .mmap = vhsm_mmap, .owner = THIS_MODULE, }; // internal data // length of the two memory areas #define NPAGES 16 // pointer to the vmalloc'd area - alway page aligned static int *vmalloc_area; // pointer to the kmalloc'd area, rounded up to a page boundary static int *kmalloc_area; // original pointer for kmalloc'd area as returned by kmalloc static void *kmalloc_ptr; /* character device open method */ static int vhsm_open(struct inode *inode, struct file *filp) { return 0; } /* character device last close method */ static int vhsm_release(struct inode *inode, struct file *filp) { return 0; } // helper function, mmap's the kmalloc'd area which is physically contiguous int vhsm_kmem(struct file *filp, struct vm_area_struct *vma) { int ret; long length = vma->vm_end - vma->vm_start; /* check length - do not allow larger mappings than the number of pages allocated */ if (length > NPAGES * PAGE_SIZE) return -EIO; /* map the whole physically contiguous area in one piece */ if ((ret = remap_pfn_range(vma, vma->vm_start, virt_to_phys((void *)kmalloc_area) >> PAGE_SHIFT, length, vma->vm_page_prot)) < 0) { return ret; } return 0; } /* character device mmap method */ static int vhsm_mmap(struct file *filp, struct vm_area_struct *vma) { /* at offset 0 we map the vmalloc'd area */ if (vma->vm_pgoff == 0) { return vhsm_vmem(filp, vma); } /* at offset NPAGES we map the kmalloc'd area */ if (vma->vm_pgoff == NPAGES) { return vhsm_kmem(filp, vma); } /* at any other offset we return an error */ return -EIO; } /* module initialization - called at module load time */ static int __init vhsm_init(void) { int ret = 0; int i; /* allocate a memory area with kmalloc. Will be rounded up to a page boundary */ if ((kmalloc_ptr = kmalloc((NPAGES + 2) * PAGE_SIZE, GFP_KERNEL)) == NULL) { ret = -ENOMEM; goto out; } /* round it up to the page bondary */ kmalloc_area = (int *)((((unsigned long)kmalloc_ptr) + PAGE_SIZE - 1) & PAGE_MASK); /* allocate a memory area with vmalloc. */ if ((vmalloc_area = (int *)vmalloc(NPAGES * PAGE_SIZE)) == NULL) { ret = -ENOMEM; goto out_kfree; } /* get the major number of the character device */ if ((ret = alloc_chrdev_region(&vhsm_dev, 0, 1, "mmap")) < 0) { printk(KERN_ERR "could not allocate major number for mmap\n"); goto out_vfree; } /* initialize the device structure and register the device with the kernel */ cdev_init(&vhsm_cdev, &vhsm_fops); if ((ret = cdev_add(&vhsm_cdev, vhsm_dev, 1)) < 0) { printk(KERN_ERR "could not allocate chrdev for mmap\n"); goto out_unalloc_region; } /* mark the pages reserved */ for (i = 0; i < NPAGES * PAGE_SIZE; i+= PAGE_SIZE) { SetPageReserved(vmalloc_to_page((void *)(((unsigned long)vmalloc_area) + i))); SetPageReserved(virt_to_page(((unsigned long)kmalloc_area) + i)); } /* store a pattern in the memory - the test application will check for it */ for (i = 0; i < (NPAGES * PAGE_SIZE / sizeof(int)); i += 2) { vmalloc_area[i] = (0xaffe << 16) + i; vmalloc_area[i + 1] = (0xbeef << 16) + i; kmalloc_area[i] = (0xdead << 16) + i; kmalloc_area[i + 1] = (0xbeef << 16) + i; } return ret; out_unalloc_region: unregister_chrdev_region(vhsm_dev, 1); out_vfree: vfree(vmalloc_area); out_kfree: kfree(kmalloc_ptr); out: return ret; } /* module unload */ static void __exit vhsm_exit(void) { int i; /* remove the character deivce */ cdev_del(&vhsm_cdev); unregister_chrdev_region(vhsm_dev, 1); /* unreserve the pages */ for (i = 0; i < NPAGES * PAGE_SIZE; i+= PAGE_SIZE) { SetPageReserved(vmalloc_to_page((void *)(((unsigned long)vmalloc_area) + i))); SetPageReserved(virt_to_page(((unsigned long)kmalloc_area) + i)); } /* free the memory areas */ vfree(vmalloc_area); kfree(kmalloc_ptr); } module_init(vhsm_init); module_exit(vhsm_exit); test program: #include <stdio.h> #include <unistd.h> #include <sys/mman.h> #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> #include <stdlib.h> #define NPAGES 16 /* this is a test program that opens the mmap_drv. It reads out values of the kmalloc() and vmalloc() allocated areas and checks for correctness. You need a device special file to access the driver. The device special file is called 'node' and searched in the current directory. To create it - load the driver 'insmod mmap_mod.o' - find the major number assigned to the driver 'grep mmapdrv /proc/devices' - and create the special file (assuming major number 254) 'mknod node c 254 0' */ int main(void) { int fd; unsigned int *vadr; unsigned int *kadr; int len = NPAGES * getpagesize(); if ((fd=open("node", O_RDWR|O_SYNC))<0) { perror("open"); exit(-1); } vadr = mmap(0, len, PROT_READ, MAP_SHARED, fd, 0); if (vadr == MAP_FAILED) { perror("mmap"); exit(-1); } if ((vadr[0]!=0xaffe0000) || (vadr[1]!=0xbeef0000) || (vadr[len/sizeof(int)-2]!=(0xaffe0000+len/sizeof(int)-2)) || (vadr[len/sizeof(int)-1]!=(0xbeef0000+len/sizeof(int)-2))) { printf("0x%x 0x%x\n", vadr[0], vadr[1]); printf("0x%x 0x%x\n", vadr[len/sizeof(int)-2], vadr[len/sizeof(int)-1]); } kadr = mmap(0, len, PROT_READ|PROT_WRITE, MAP_SHARED| MAP_LOCKED, fd, len); if (kadr == MAP_FAILED) { perror("mmap"); exit(-1); } if ((kadr[0]!=0xdead0000) || (kadr[1]!=0xbeef0000) || (kadr[len / sizeof(int) - 2] != (0xdead0000 + len / sizeof(int) - 2)) || (kadr[len / sizeof(int) - 1] != (0xbeef0000 + len / sizeof(int) - 2))) { printf("0x%x 0x%x\n", kadr[0], kadr[1]); printf("0x%x 0x%x\n", kadr[len / sizeof(int) - 2], kadr[len / sizeof(int) - 1]); } close(fd); return(0); } -- Sartakov A. Vasily

2 1

CfP: Workshop on Isolation and Integration in Embedded Systems (IIES)
by Michael Engel 01 Aug '11

01 Aug '11

Dear colleagues, the fourth Workshop on Isolation and Integration in Embedded Systems, organized by Olaf Spinczyk (TU Dortmund), Jörg Nolte (BTU Cottbus) and myself (TU Dortmund), takes place on October 9th, 2011 at ESweek in Taipei, Taiwan. Embedded systems developers today are confronted with a large variety of challenges in the design and implementation of a system. Issues such as co-location of different applications, platform integration of different embedded operating environments as well as safety and protection of embedded software systems require novel approaches to embedded systems development as well as the adaptation of technologies from mainframe and desktop computing, like virtualization and emulation. This, in turn, will change traditional embedded design processes to include hardware and software of growing complexity. The IIES workshop is a platform to discuss recent developments and novel concepts in these areas. We would be happy if you submitted a research or position paper. Submissions may be up to six pages long (ACM SIGOPS Format). Submission deadline: August 15th, 2011 Notification of acceptance: September 12th, 2011 Workshop: October 9th, 2011 Best regards, Michael Engel (michael.engel(a)tu-dortmund.de) -- Dr. Michael Engel michael.engel(a)tu-dortmund.de - engel(a)multicores.org TU Dortmund Phone: +49 231 755 6141 Faculty of Computer Science XII Fax: +49 231 755 6116 Embedded Systems Group - Otto-Hahn-Str. 16 - D-44221 Dortmund, Germany

1 0

L4Re Library Usage
by Wesley Miaw 30 Jul '11

30 Jul '11

I have been able to get my module to compile as an ext-pkg. However I'm a little confused by the description of L4Re listed at http://os.inf.tu-dresden.de/L4Re/overview.html What exactly do I need to replace in my code to use the L4Re C or C++ libraries, or libstdc++ etc.? I didn't get any compilation errors with code that directly calls malloc() and I saw some other modules call malloc() too. But I would have thought all memory allocation/deallocation needs to be changed to use an L4 function. When I looked inside packages like cxx or libstdc++ it doesn't actually look like these are replacements for the GNU headers or libraries. Is the only code I need to have use L4Re functions and types the code that is going to handle message receiving and sending? Everything else could be as if it was not part of L4? Thanks, Wes

2 1

[ANNOUNCE] NOVA Microhypervisor 0.4 prerelease
by Udo A. Steinberg 28 Jul '11

28 Jul '11

Hi, The NOVA project is happy to announce that there is a new prerelease of the NOVA microhypervisor available for download at http://www.hypervisor.org/ under the terms of the GNU General Public License version 2. NOVA is based on a modern microhypervisor written in C++ and assembler. The current implementation runs on multi-core x86 machines that support ACPI, under QEMU (including VM support), and as a microkernel in a virtual machine on top of itself. NOVA makes use of hardware virtualization features such as Intel VT-x/VT-d or AMD-V, and facilitates running unmodified guest operating systems in virtual machines with near-native performance. Among other things, the new prerelease improves the security of device- and interrupt assignment by using capabilities for these operations. There is also a new hypercall for interacting with the scheduler. At the same time, we've released a new version of the NOVA Userland (NUL). While there are few user-visible changes, a lot has changed under the hood. We have integrated a central admission server that is going to implement global policies for CPU time distribution in a future release. Another notable development is rudimentary libvirt support, which will eventually replace the old configuration syntax. Cheers, - Udo

1 0

Re: l4-hackers Digest, Vol 99, Issue 18
by Wesley Miaw 28 Jul '11

28 Jul '11

> On Mon Jul 25, 2011 at 16:43:09 -0700, Wesley Miaw wrote: >> I'm trying to add a new lib/server module to L4 but I'm having some >> trouble. I followed the snapshot top-level README suggestion to >> place the new code in an external directory, so I placed it into >> src/mymodule/ next to src/l4re and src/l4linux. Then I created a >> Makefile under src/mymodule/src/ based on the example with include >> $(L4DIR)/mk/lib.mk. >> >> However, this doesn't appear to be working. $(L4DIR)/mk/Makeconf is >> complaining that files existing inside the obj/l4/... directory are >> not to be found in the obj/mymodule/... directory. (I tried to copy >> the obj/... logic found in the top-level Makefile.) >> >> Is the README's suggestion accurate? > > I think so. Could you show me some of the failed output + surroundings > to better judge what's going on? My bad. I didn't realize the build directory (O=) had to be the l4 obj directory for my own packages. (Missed that part of the README.) It's working for me now. Thanks! -- Wesley Miaw wesley(a)wesman.net

1 0

No configuration file found in build directory
by Wesley Miaw 26 Jul '11

26 Jul '11

I'm trying to add a new lib/server module to L4 but I'm having some trouble. I followed the snapshot top-level README suggestion to place the new code in an external directory, so I placed it into src/ mymodule/ next to src/l4re and src/l4linux. Then I created a Makefile under src/mymodule/src/ based on the example with include $(L4DIR)/mk/ lib.mk. However, this doesn't appear to be working. $(L4DIR)/mk/Makeconf is complaining that files existing inside the obj/l4/... directory are not to be found in the obj/mymodule/... directory. (I tried to copy the obj/... logic found in the top-level Makefile.) Is the README's suggestion accurate? Thanks, -- Wesley Miaw wesley(a)wesman.net

2 1

transfer_msg_items
by Chen Tian 21 Jul '11

21 Jul '11

Hello, Why was a sender's send item (e.g. mr[0] and mr[1] ) merged and stored into the receiver's mr[0]? Basically I have trouble understanding the following code. *rcv_words=(item->b.raw() & ~0x0ff7) | (sfp.raw())&0x0ff0); rcv_word +=2 ; Why didn't we use receiver's mr[1] as well? In the case of page fault handling IPC, the pf address stored in sender's mr[1] is not used ? Thanks. Chen

1 1

what is the difference between the 2 methods of booting hello demo
by cheng guanghui 19 Jul '11

19 Jul '11

Hello: In the modules.list there are 2 entires to boot hello demo as following: entry hello roottask moe --init=rom/hello module l4re module hello entry hello-cfg roottask moe rom/hello.cfg module l4re module ned module hello.cfg module hello The booting logs are following separately : hello MOE: Hello world MOE: found 117648 KByte free memory MOE: found RAM from 1000 to 75c7000 MOE: allocated 117 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136d000-1470e6d] [C:503000] l4re BOOTFS: [1471000-153030b] [C:504000] hello MOE: cmdline: /home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86/bin/x86_586/l4f/moe --init=rom/hello MOE: Starting: rom/hello MOE: loading 'rom/hello' Hello World! Hello World! Hello World! hello-cfg MOE: Hello world MOE: found 115604 KByte free memory MOE: found RAM from 1000 to 75c7000 MOE: allocated 117 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136d000-1470e6d] [C:503000] l4re BOOTFS: [1471000-166e572] [C:504000] ned BOOTFS: [166f000-166f066] [C:505000] hello.cfg BOOTFS: [1670000-172f30b] [C:506000] hello MOE: cmdline: /home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86/bin/x86_586/l4f/moe rom/hello.cfg MOE: Starting: rom/ned rom/hello.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/hello.cfg' hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! hello | Hello World! So hello demo could be booted whatever from Ned or Moe directly. In the document Ned is described as this "The main thing to do here is to coordinate the startup of services and applications as well as to provide the communication channels for them". Does it mean "We use Ned just because we need to dynamically create IPC gate (channel) between different applications". If there is no need to use IPC gate we can use Moe directly to boot application. is it correct? Thanks. Warm regards. Cheng Guanghui

2 2

how can i understand this description in the l4re-source document?
by cheng guanghui 19 Jul '11

19 Jul '11

Hello: In the page 19 of the l4re-source document there is a description about caps as following: Caps The table with application-specific named capabilities (default is an empty table). If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table. How can i understand "If the table does not contain a capability with the name ’rom’, the ’rom’ capability from Ned’s initial caps is inserted into the table." Thanks. Warm regards. Cheng Guanghui

2 2

writing my own filesystem for L4
by Michal Schulz 19 Jul '11

19 Jul '11

Hello. I'm going to write a filesystem for L4, using the tmpfs (l4/pkg/tmpfs) as a starting point. However, I would like to know whether there are any tools I could use to test the filesystem. The tool I would love to have should display all registered filesystem and should allow me to walk through filesystem's directory trees. Is there such a tool or example application? Are there any packages in L4 which use VFS layer at all? regards, Michal. -- Michal Schulz

2 1

Re: l4-hackers Digest, Vol 99, Issue 11
by Chen Tian 18 Jul '11

18 Jul '11

Hi Adam, I don't have a separate PHDR for ctors. I got this problem when I put ctors into the text section. Now I have moved ctors into the data section and the problem disappeared. Any ideas? Another questions is why ktext=0x90909090 in the ld file of fiasco.oc? Is this value randomly chosen? Thanks. On Sat, Jul 16, 2011 at 3:00 AM, <l4-hackers-request(a)os.inf.tu-dresden.de> wrote: > 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: write my own root task. (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 15 Jul 2011 23:20:50 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: write my own root task. > Message-ID: <20110715212050.GB5040(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > > On Thu Jul 14, 2011 at 15:15:25 -0700, Chen Tian wrote: >> I am trying to use C++ to write my own root task. I found that if I >> declare a static or global object, bootstrap complains that two >> regions belonging to my root task overlapped and thus cannot proceed. >> Why does my root task have two conflicting regions? According to the >> bootstrap report, they both have the correct starting address, but one >> ends just at the global object's ctor in .ctors section, while the >> other region covers the entire program. >> If the .ctors section is empty then everything is fine. Any ideas? > > I wonder why you have an own PHDR for ctors? How many do you have? > > > 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 99, Issue 11 > ****************************************** >

2 1

write my own root task.
by Chen Tian 15 Jul '11

15 Jul '11

Hello, I am trying to use C++ to write my own root task. I found that if I declare a static or global object, bootstrap complains that two regions belonging to my root task overlapped and thus cannot proceed. Why does my root task have two conflicting regions? According to the bootstrap report, they both have the correct starting address, but one ends just at the global object's ctor in .ctors section, while the other region covers the entire program. If the .ctors section is empty then everything is fine. Any ideas? Thanks. Chen

2 1

TLS on amd64
by Daniel Müller 15 Jul '11

15 Jul '11

Hello, I want to use the __thread keyword gcc provides. I was told this was recently adjusted to work (at least in the private repository which I am using). It appears to be working when building for IA32 but when I compile the same program for amd64 I get a page fault when running it (it is a simple program just incrementing a __thread declared int). It faults at 10010f4 (the first access of the variable). 00000000010010f0 <main>: 10010f0: 48 83 ec 08 sub rsp,0x8 10010f4: 64 c7 04 25 fc ff ff mov DWORD PTR fs:0xfffffffffffffffc,0x0 10010fb: ff 00 00 00 00 1001100: bf 60 48 01 01 mov edi,0x1014860 1001105: e8 36 88 00 00 call 1009940 <puts> 100110a: 64 83 04 25 fc ff ff add DWORD PTR fs:0xfffffffffffffffc,0x1 1001111: ff 01 1001113: bf 01 00 00 00 mov edi,0x1 1001118: e8 d3 71 00 00 call 10082f0 <sleep> 100111d: eb e1 jmp 1001100 <main+0x10> 100111f: 90 nop Is TLS for amd64 supposed to work? Any idea on the problem? Greetings, Daniel

2 3

Running the IO server
by Anna Fischer 12 Jul '11

12 Jul '11

I'm trying to run the ARM-based frame buffer configuration from conf/examples/arm-rv-lcd.cfg with pkg/io/config/arm-rv-eb-mc.devs and QEMU (-M realview-pbx-a9). I can boot the L4 Linux kernel on this (without GUI but just serial I/O) configuration, but I get an error when trying to set up the LCD (see below). Perhaps the LCD device configuration from the .devs file does not match what hardware QEMU emulates? How can I actually enumerate in the IO server what hardware it actually runs on? Is there a way to do that? Thanks, Anna L4 Bootstrapper Build: #34 Mon Jul 11 16:17:10 BST 2011, 4.5.2 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod11: 012a9000-012cac7c: ex_fb_spectrum mod10: 0121b000-012a846c: mag mod09: 011f1000-0121a5b8: fb-drv mod08: 0119d000-011f01b8: ned mod07: 010c2000-0119cb58: io mod06: 010a8000-010c1510: l4re mod05: 010a7000-010a70e4: arm-rv-lcd.io mod04: 010a6000-010a659d: arm-rv-eb-mc.devs mod03: 010a5000-010a56bb: arm-rv-lcd.cfg mod02: 0106b000-010a45f0: moe mod01: 01061000-0106a33c: sigma0 mod00: 01015000-0106014c: fiasco Moving 12 modules to 1100000 with offset eb000 moving module 12 { 12a9000-12cac7c } -> { 1394000-13b5c7c } moving module 11 { 121b000-12a846c } -> { 1306000-139346c } moving module 10 { 11f1000-121a5b8 } -> { 12dc000-13055b8 } moving module 09 { 119d000-11f01b8 } -> { 1288000-12db1b8 } moving module 08 { 10c2000-119cb58 } -> { 11ad000-1287b58 } moving module 07 { 10a8000-10c1510 } -> { 1193000-11ac510 } moving module 06 { 10a7000-10a70e4 } -> { 1192000-11920e4 } moving module 05 { 10a6000-10a659d } -> { 1191000-119159d } moving module 04 { 10a5000-10a56bb } -> { 1190000-11906bb } moving module 03 { 106b000-10a45f0 } -> { 1156000-118f5f0 } moving module 02 { 1061000-106a33c } -> { 114c000-115533c } moving module 01 { 1015000-106014c } -> { 1100000-114b14c } Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/arm-rv-lcd.cfg Relocated mbi to [0x100f000-0x100f19e] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 19ff] { a00} Kern fiasco [ 2000, 5cfff] { 5b000} Kern fiasco [ 90000, 9e17b] { e17c} Sigma0 sigma0 [ 140000, 17160b] { 3160c} Root moe [ 178000, 18eec7] { 16ec8} Root moe [ 1000000, 10143eb] { 143ec} Boot bootstrap [ 100f000, 100f29b] { 29c} Root Multiboot info [ 1190000, 13b5c7b] { 225c7c} Root Modules Memory API Version: (87) experimental Sigma0 config ip:000900e0 sp:01013044 Roottask config ip:00140178 sp:00000000 Starting kernel fiasco at 00001000 Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 L2: ID=00000000 Type=00000000 L2 cache enabled Hello from Startup::stage2 Initialize page table Number of IRQs available at this GIC: 96 Vmem_alloc::init() Cache config: ON ID_PFR0: 00001031 ID_PFR1: 00000011 ID_DFR0: 00000000 ID_AFR0: 00000000 ID_MMFR0: 00100103 ID_MMFR1: 20000000 ID_MMFR2: 01230000 ID_MMFR3: 00002111 SERIAL ESC: allocated IRQ 44 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2011 TU Dresden Rev: r33 compiled with gcc 4.5.2 for Realview [] Build: #1 Tue Jun 21 12:57:15 BST 2011 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:5d000;8ffff] [0:9f000;13ffff] [4:140000;171fff] [0:172000;177fff] [4:178000;18efff] [0:18f000;100efff] [4:100f000;100ffff] [0:1010000;118ffff] [4:1190000;13b5fff] [0:13b6000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 242832 KByte free memory MOE: found RAM from 5d000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [1190000-11906bb] [C:503000] arm-rv-lcd.cfg BOOTFS: [1191000-119159d] [C:504000] arm-rv-eb-mc.devs BOOTFS: [1192000-11920e4] [C:505000] arm-rv-lcd.io BOOTFS: [1193000-11ac510] [C:506000] l4re BOOTFS: [11ad000-1287b58] [C:507000] io BOOTFS: [1288000-12db1b8] [C:508000] ned BOOTFS: [12dc000-13055b8] [C:509000] fb-drv BOOTFS: [1306000-139346c] [C:50a000] mag BOOTFS: [1394000-13b5c7c] [C:50b000] ex_fb_spectrum MOE: cmdline: moe rom/arm-rv-lcd.cfg MOE: Starting: rom/ned rom/arm-rv-lcd.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/arm-rv-lcd.cfg' IO | Io service mag | libio: Warning: Finding 'icu' in system bus failed with 'Void capability invoked' mag | Hello from MAG fbdrv | libio: Warning: Finding 'icu' in system bus failed with 'Void capability invoked' fbdrv | Could not find LCD. fbdrv | Failed to setup Framebuffer mag | Error: Exception: Void capability invoked: requesting goos info: backtrace ... mag | mag | MAG: destroy FB svc Ned[lua]: Hm, cpapbility 42d000 does not support the meta protocol: -2004 Ned: ERROR: rom/arm-rv-lcd.cfg:62: attempt to call method 'create' (a nil value)

2 2

Fix IO-APIC/IRQ-Routing Bug (affects GSIs 24, 48, 72, ...)
by Christian Ehrhardt 08 Jul '11

08 Jul '11

Hi, there seems to by an off-by-one error in Io_apic::find_apic() that kills IRQ-routing for GSIs that are a multiple of 24. Please consider the patch below (tested on real hardware with 3 IO-APICS). regards Christian diff --git a/src/kernel/fiasco/src/kern/io_apic.cpp b/src/kernel/fiasco/src/kern/io_apic.cpp index 88ffe68..897a1a0 100644 --- a/src/kernel/fiasco/src/kern/io_apic.cpp +++ b/src/kernel/fiasco/src/kern/io_apic.cpp @@ -331,7 +331,7 @@ Io_apic::find_apic(unsigned irqnum) { for (unsigned i = Max_ioapics; i > 0; --i) { - if (_apics[i-1]._apic && _apics[i-1]._offset < irqnum) + if (_apics[i-1]._apic && _apics[i-1]._offset <= irqnum) return i - 1; } return 0;

1 0

Newbie question: L4Linux as a patch
by Pablo Chacin 07 Jul '11

07 Jul '11

Hi all I'm doing a review of options for virtualization in Linux. From the documentation, it seems that L4Linux is a complete port of the Linux Kernel. I'm wondering if there is a patch (or series of patches) that could be used to modify an standard Linux kernel and make it compatible with the L4 virtualization? The question comes from my scenario: I need to deploy a customized linux kernel and want to do so over L4. This kernel is build from the standard kernel applying some patches. I would like to do the same with L4Linux, so the resulting kernel has my patches plus L4. Is this feasible? has been tested? thanks in advance and please consider I'm new to L4Linux. Regards -- ======================================================================== 0 0 0 Pablo Chacin | Dept. d'Arquitectura de Computadors 0 0 0 e-mail: pchacin(a)ac.upc.edu | UPC-Campus Nord. Modul D6-212 0 0 0 phone: +34 +93 405 4059 | Jordi Girona, 1-3 U P C fax: +34 +93 401 7055 | 08034 Barcelona - SPAIN www: http://personals.ac.upc.es/pchacin ========================================================================

2 3

Fiasco.OC Kernel symbolic debugger
by Daniel Waddington 06 Jul '11

06 Jul '11

Hello, Adam, are you likely to get the source-level symbolic debugging working in jdb in the near future? Using objdump is a bit drastic! ;-) Thanks Daniel

2 1

L4 for amd64
by Daniel Müller 05 Jul '11

05 Jul '11

Hi, I have some problems with running L4 for amd64 (i586 is just fine). I am trying to run (qemu-14.1.) the hello world binary and get: --------- L4 Bootstrapper Build: #1 Mi 29. Jun 17:41:45 CEST 2011, x86-64, 4.4.5 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 0000000007ffcfff: 130036kB Total RAM: 127MB Moving 7 modules to 2000000 with offset fa8000 moving module 07 { 1679000-1739a52 } -> { 2621000-26e1a52 } moving module 06 { 1678000-1678039 } -> { 2620000-2620039 } moving module 05 { 1566000-167779e } -> { 250e000-261f79e } moving module 04 { 132d000-1565b9e } -> { 22d5000-250db9e } moving module 03 { 110c000-132cb58 } -> { 20b4000-22d4b58 } moving module 02 { 10be000-110b397 } -> { 2066000-20b3397 } moving module 01 { 1058000-10bdb00 } -> { 2000000-2065b00 } Scanning /fiasco -serial_esc -comspeed 115200 -comport 1 -nokdb This is an invalid binary, fix it (wrong ELF architecture). Key press reboots... Rebooting. --------- This is done with a clean checkout URL: http://svn.tudos.org/repos/oc/tudos/trunk Repository Root: http://svn.tudos.org/repos/oc/tudos Repository UUID: d050ee49-bd90-4346-b210-929a50b99cfc Revision: 33 configured for K8-type CPU. /usr/bin/file tells me: build/obj/bin/amd64_K8/l4f/sigma0: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/moe: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/ned: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/l4re: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/loader: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/l4f/hello: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped build/obj/bin/amd64_K8/bootstrap: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped ./../kernel/fiasco/build/fiasco: symbolic link to `main' So why is bootstrap not built as 64 bit binary? Daniel

2 3

libc environment for l4linux
by Vasily Sartakov 04 Jul '11

04 Jul '11

Hello Does l4re snapshot has a libc environment for build a applications for l4linux? what toolchains did you use for build busybox? -- Sartakov A. Vasily

2 1

Fiasco.OC
by Daniel Waddington 03 Jul '11

03 Jul '11

Hi, I want to use 32bit x86 Fiasco.OC with lots of SMP CPUs (48+). Can you tell me where the current 32 (for 32bit) and 64 (for 64bit) limitations exist in the code - and suggest whether this could be changed? Thanks Daniel Waddington

2 1

the booting error of l4linux
by cheng guanghui 02 Jul '11

02 Jul '11

Hello: I downloaded the latest l4re-snapshot-2011062216. All the compilation is ok. The hello demo could boot successfully. But when i try to boot L4Linux with this command : make qemu E=L4Linux-mag-x86 O=/home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86 There are some errors as following: Allocate cpu_mem @ 0xfc54c000 Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the PIT (i8254) on IRQ 2 for scheduling Absolute KIP Syscalls using: Sysenter CPU[0:0]: GenuineIntel (6:3:3:0)[00000633] Model: Pentium II (Klamath) at 2395 MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 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: 28672 bytes (7 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:1000;9efff] [0:10b000;13ffff] [4:140000;18bfff] [0:18c000;2dcfff] [4:2dd000;2ddfff] [0:2de000;3fffff] [0:465000;136cfff] [4:136d000;166ffff] [0:1670000;1614bfff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:17ffd000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 357544 KByte free memory MOE: found RAM from 1000 to 1614c000 MOE: allocated 353 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [136d000-1470e6d] [C:503000] l4re BOOTFS: [1471000-166e572] [C:504000] ned BOOTFS: [166f000-166f578] [C:505000] l4lx-gfx.cfg MOE: cmdline: /home/cheng/TUDOS/Src/l4re-snapshot-2011062216/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | L4Re: FATAL: Exception No such object found: 'rom/io' io | Exception: No such object found: rom/io: backtrace ... fb-drv | L4Re: FATAL: Exception No such object found: 'rom/fb-drv' fb-drv | Exception: No such object found: rom/fb-drv: backtrace ... mag | L4Re: FATAL: Exception No such object found: 'rom/mag' mag | Exception: No such object found: rom/mag: backtrace ... Ned[lua]: Hm, cpapbility 430000 does not support the meta protocol: -2004 Ned: ERROR: rom/l4lx-gfx.cfg:54: attempt to call method 'create' (a nil value) Do i miss something else? Thanks a lot. Warm regards. Cheng Guanghui

2 6

pthread_exit in L4re
by Chen Tian 30 Jun '11

30 Jun '11

Hello, I want a thread to exit after it finishes its job. The function pthread_exit seems not working. I still can see all threads I created through kernel debugger. Any idea? Best, Chen

2 1

Nokia N900 and Fiasco.OC/l4re
by Valery V. Sedletski 29 Jun '11

29 Jun '11

Hi all Is there a possibility to use Fiasco.OC and L4Re with L4Linux on Nokia N900 internet tablet/phone? Which ARM platform it is compatible with, if so? -- It is based on ARM Cortex A8 600 MHz processor, 256 Mb RAM and 784 Mb swap, Maemo (Debian GNU/Linux based) platform (see http://www.gsmarena.com/nokia_n900-2917.php, for example). Or, if not so, is it possible to use it with Genode or OKL4? WBR, valery

3 6

bbclone fbdrv lcd problem
by Vasily Sartakov 24 Jun '11

24 Jun '11

Hello. I try to start ex_fb_spectrum example on beagleboard clone with 7" 480x800 LCD and have error in fbdrv//lcd-omap3.c: when a i call any l4vbus_i2c* and l4vbus_gpio function i have return -38 --- ENOSYS error whats may be wrong? my configs: -------------------------------------- arm-rv-lcd-io: gui => new System_bus() { # KBD => wrap(hw-root.KBD); # MOUSE => wrap(hw-root.MOUSE); } fbdrv => new System_bus() { sys => wrap(hw-root.sys); lcd => wrap(hw-root.lcd); i2c1 => wrap(hw-root.i2c1); gpio => wrap(hw-root.gpio); } ------------------------------------- arm-rv-lcd-cfg require("L4"); local l = L4.default_loader; local io_buses = { gui = l:new_channel(); fbdrv = l:new_channel(); }; l:start({ caps = { gui = io_buses.gui:svr(), fbdrv = io_buses.fbdrv:svr(), icu = L4.Env.icu, sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0), }, log = { "IO", "y" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/arm-omap3-full.devs rom/arm-rv-lcd.io"); local fbdrv_fb = l:new_channel(); l:startv({ caps = { vbus = io_buses.fbdrv, fb = fbdrv_fb:svr(), }, log = { "fbdrv", "r" }, l4re_dbg = L4.Dbg.Warn, }, "rom/fb-drv", "-c", "init"); local mag_caps = { mag = l:new_channel(), svc = l:new_channel(), }; l:start({ caps = { vbus = io_buses.gui, fb = fbdrv_fb, mag = mag_caps.mag:svr(), svc = mag_caps.svc:svr(), }, log = { "mag", "g" }, l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0xa0, 0x80), }, "rom/mag"); e = l:start({ caps = { fb = mag_caps.svc:create(L4.Proto.Goos, "g=480x480"), }, log = { "spectrum", "b" }, l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8), }, "rom/ex_fb_spectrum"); print("ex_fb_spectrum exited with: " .. e:wait()); ------------------------------------ arm-omap3-full.devs: hw-root { sys => new Device() { .hid = "System Control"; new-res Mmio(0x48002000 .. 0x48002fff); new-res Mmio(0x48004000 .. 0x48004fff); } prcm => new Device() { .hid = "OMAP PRCM qq"; new-res Mmio(0x48000000 .. 0x48000fff); new-res Mmio(0x48001000 .. 0x48001fff); new-res Mmio(0x48002000 .. 0x48002fff); new-res Mmio(0x48003000 .. 0x48003fff); new-res Mmio(0x48004000 .. 0x48004fff); new-res Mmio(0x48005000 .. 0x48005fff); } gpio => new Device() { .hid = "gpio"; new-res Mmio(0x48004000 .. 0x48004fff); new-res Mmio(0x48310000 .. 0x48310fff); new-res Mmio(0x49050000 .. 0x49050fff); new-res Mmio(0x49052000 .. 0x49052fff); new-res Mmio(0x49054000 .. 0x49054fff); new-res Mmio(0x49056000 .. 0x49056fff); new-res Mmio(0x49058000 .. 0x49058fff); } lcd => new Device() { .hid = "OMAP_LCD"; new-res Mmio(0x48050000 .. 0x48050fff); } i2c1 => new Device() { .hid = "i2c"; new-res Mmio(0x48070000 .. 0x48070fff); } } -- Sartakov A. Vasily

2 4

RE: L4Re build error
by Slex Sangiuliano 19 Jun '11

19 Jun '11

I have linked in this way (in /usr/bin): ln -s g++-4.5 g++ ln -s cpp-4.5 cpp ln -s gcc-4.5 gcc (i have previously removed the links to gcc-45, g++-4.5 and cpp-4.5) but the error is the same: In file included from /home/alex/l4env/include/contrib/libstdc++-v3/bits/stl_algobase.h:71:0, from /home/alex/l4env/include/contrib/libstdc++-v3/memory:53, from /home/alex/src/l4/pkg/libstdc++-v3/contrib/libstdc++-v3-4.1.0/src/allocator-inst.cc:34: /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:358:12: error: expected identifier before ‘__is_pod’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:358:12: error: expected unqualified-id before ‘__is_pod’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:371:12: error: expected identifier before ‘__is_empty’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:371:12: error: expected unqualified-id before ‘__is_empty’ make[4]: Entering directory `/home/alex/src/l4/pkg/drivers-frst/nand/src' In file included from /home/alex/l4env/include/contrib/libstdc++-v3/memory:60:0, from /home/alex/src/l4/pkg/libstdc++-v3/contrib/libstdc++-v3-4.1.0/src/allocator-inst.cc:34: /home/alex/l4env/include/contrib/libstdc++-v3/limits:1067:9: error: a cast to a type other than an integral or enumeration type cannot appear in a constant-expression /home/alex/l4env/include/contrib/libstdc++-v3/limits:1080:51: error: ‘std::numeric_limits<double>::is_iec559’ cannot be initialized by a non-constant expression when being declared make[5]: *** [allocator-inst.o] Error 1 now gcc -v says 4.5.3 > Date: Sun, 19 Jun 2011 17:15:09 +0200 > From: adam(a)os.inf.tu-dresden.de > To: alex22_7(a)hotmail.com > Subject: Re: L4Re build error > > > On Sun Jun 19, 2011 at 14:52:43 +0000, Slex Sangiuliano wrote: > > > > more information: > > Platform x86 (pentium D, but in config i choose i686) > > I'm building on 32 bit enviroment (Debian Wheezy, > > the error occurs also on Fedora 15, in FreeBSD 8.2 i get another kind > > of error during gmake O=/home/alex/build config). > > On Debian the > > version of gcc is 4.6.1. (On FreeBSD 4.2.1). I prefer to build on > > Debian, so it, for now, is the reference system. > > Thank you again > > > > P.S: I sent this message after my first message, but for network problem, now solved, it never comes > > So after that i read your response i add another question: I need a specific compiler? if yes what is the best Operating System that has that compiler? > > Ah, 4.6 explains it. 4.6 will be support on the next release. For now > 4.5 will do, which is also available on wheezy. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/

2 2

L4Re build error
by Slex Sangiuliano 19 Jun '11

19 Jun '11

Hi, I have a build problem: In file included from /home/alex/l4env/include/contrib/libstdc++-v3/bits/stl_algobase.h:71:0, from /home/alex/l4env/include/contrib/libstdc++-v3/memory:53, from /home/alex/src/l4/pkg/libstdc++-v3/contrib/libstdc++-v3-4.1.0/src/allocator-inst.cc:34: /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:358:12: error: expected identifier before ‘__is_pod’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:358:12: error: expected unqualified-id before ‘__is_pod’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:371:12: error: expected identifier before ‘__is_empty’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:371:12: error: expected unqualified-id before ‘__is_empty’ In file included from /home/alex/l4env/include/contrib/libstdc++-v3/memory:60:0, from /home/alex/src/l4/pkg/libstdc++-v3/contrib/libstdc++-v3-4.1.0/src/allocator-inst.cc:34: /home/alex/l4env/include/contrib/libstdc++-v3/limits:1067:9: error: a call to a constructor cannot appear in a constant-expression So i can't build, hot to solve this? Thank you, Slex P.S Probably, I sent this email 2 times for a mistake. I'm very sorry

2 1

(no subject)
by Slex Sangiuliano 19 Jun '11

19 Jun '11

Hi, I have a build problem: In file included from /home/alex/l4env/include/contrib/libstdc++-v3/bits/stl_algobase.h:71:0, from /home/alex/l4env/include/contrib/libstdc++-v3/memory:53, from /home/alex/src/l4/pkg/libstdc++-v3/contrib/libstdc++-v3-4.1.0/src/allocator-inst.cc:34: /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:358:12: error: expected identifier before ‘__is_pod’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:358:12: error: expected unqualified-id before ‘__is_pod’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:371:12: error: expected identifier before ‘__is_empty’ /home/alex/l4env/include/contrib/libstdc++-v3/bits/cpp_type_traits.h:371:12: error: expected unqualified-id before ‘__is_empty’ In file included from /home/alex/l4env/include/contrib/libstdc++-v3/memory:60:0, from /home/alex/src/l4/pkg/libstdc++-v3/contrib/libstdc++-v3-4.1.0/src/allocator-inst.cc:34: /home/alex/l4env/include/contrib/libstdc++-v3/limits:1067:9: error: a call to a constructor cannot appear in a constant-expression So i can't build, hot to solve this? Thank you, Slex

1 0

crash: l4linux with virtual PCI bus enabled
by Arno Toell 16 Jun '11

16 Jun '11

Hi list, (please CC me, as I'm not subscribed) I was trying to run l4linux supposed to boot from a NFS root file system. I enabled PCI support and the virtual PCI bus. I was successfully able to establish a network connection to my NFS server, however shortly after I get: l4linux | Page fault (non-resolved): pfa=6 pc=61fff9 Die message: Trap: 14 Trap: 14: 0006 [#1] ... Kernel panic - not syncing: Fatal exception in interrupt I am mostly running a setup with the supplied example configurations. This is my setup: * l4re: http://svn.tudos.org/repos/oc/tudos r33 * l4linux: http://svn.tudos.org/repos/oc/l4linux/trunk, r19 * run time environment: Debian Squeeze x86, gcc version 4.4.5, qemu (0.12.5) * I'm starting l4re with: "qemu -m 768 -vnc :1 -cdrom images/l4linux-mag-x86.iso -serial stdio -net nic,model=e1000 -net user" where l4linux-mag-x86.iso was generated by: * "make grub2iso E=L4Linux-mag-x86 MODULES_LIST=~/ssl/modules.list MODULE_SEARCH_PATH=~/kernel-build/:~/l4linux/:~/bootstrap/" Moreover (hopefully) I attached all configuration files below. all remaining files are untouched from the example configurations. This is the full output: arno@l4:~/l4re-build$ qemu -m 768 -vnc :1 -cdrom images/l4linux-mag-x86.iso -serial stdio -net nic,model=e1000 -net user L4 Bootstrapper Build: #5 Di 14. Jun 13:22:36 EDT 2011, x86-32, 4.4.5 RAM: 0000000000000000 - 000000000009f3ff: 637kB RAM: 0000000000100000 - 000000002fffcfff: 785396kB Total RAM: 767MB Moving 12 modules to 2000000 with offset ddfc2000 moving module 01 { 2403e000-240a4340 } -> { 2000000-2066340 } moving module 02 { 240a5000-240e5879 } -> { 2067000-20a7879 } moving module 03 { 240e6000-242b0883 } -> { 20a8000-2272883 } moving module 04 { 242b1000-2439c771 } -> { 2273000-235e771 } moving module 05 { 2439d000-245821c6 } -> { 235f000-25441c6 } moving module 06 { 2fe95000-2fe9560c } -> { de57000-de5760c } moving module 07 { 24583000-24e0f118 } -> { 2545000-2dd1118 } moving module 08 { 24e10000-24f5dcf3 } -> { 2dd2000-2f1fcf3 } moving module 09 { 24f5e000-252672d2 } -> { 2f20000-32292d2 } moving module 10 { 2ff51000-2ff513b7 } -> { df13000-df133b7 } moving module 11 { 25268000-2526821f } -> { 322a000-322a21f } moving module 12 { 25269000-256a375b } -> { 322b000-366575b } Scanning fiasco Scanning sigma0 Scanning moe rom/l4lx-gfx.cfg Bootloader MMAP: [ 0, 9f400) RAM (1) [ 9f400, a0000) reserved (2) [ f0000, 100000) reserved (2) [ 100000, 2fffd000) RAM (1) [ 2fffd000, 30000000) reserved (2) [ fffc0000, 100000000) reserved (2) Relocated mbi to [0x2dc000-0x2dc183] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x400000 Regions of list regions [ 0, fff] { 1000} Arch BIOS [ 9f400, 9ffff] { c00} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10a1ab] { a1ac} Sigma0 sigma0 [ 140000, 18c5b3] { 4c5b4} Root moe [ 2d0000, 2e03e7] { 103e8} Boot bootstrap [ 2dc000, 2dc280] { 281} Root Multiboot info [ 300000, 38ffff] { 90000} Kern fiasco [ 400000, 46bfff] { 6c000} Kern fiasco [ 2273000, 366575a] { 13f275b} Root Modules Memory [ 2fffd000, 2fffffff] { 3000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001000fc sp:002dba38 Roottask config ip:001400e4 sp:00000000 Starting kernel fiasco at 00300824 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2011 TU Dresden Rev: r33 compiled with gcc 4.4.5 for Pentium M [] Build: #1 Mo 13. Jun 11:13:40 EDT 2011 Performance-critical config option(s) detected: CONFIG_NDEBUG is off Superpages: yes Kmem:: cpu page at 2fbe2000 (4096Bytes) ACPI-Init ACPI: RSDP[0xf8850] r00 OEM:BOCHS. ACPI: RSDT[0x203fde30] r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ffe70] r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203fdf90] r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203fdeb0] r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203fde70] r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203fdeb0 IO-APIC[ 0]: struct: 0x203fdee4 adr=fec00000 IO-APIC[ 0]: pins 23 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 IO-APIC: ovr[ 1] 05 -> 5 IO-APIC: ovr[ 2] 09 -> 9 IO-APIC: ovr[ 3] 0a -> a IO-APIC: ovr[ 4] 0b -> b Allocate cpu_mem @ 0xfffe6000 Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the PIT (i8254) on IRQ 2 for scheduling Absolute KIP Syscalls using: Sysenter CPU[0:0]: GenuineIntel (6:3:3:0)[00000633] Model: Pentium II (Klamath) at 2386 MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 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: 28672 bytes (7 pages) Calibrating timer loop... done. SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:1000;9efff] [0:10b000;13ffff] [4:140000;18cfff] [0:18d000;2dbfff] [4:2dc000;2dcfff] [0:2dd000;3fffff] [0:465000;2272fff] [4:2273000;3665fff] [0:3666000;2bffffff] [0:2fc00000;2fffcfff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:2fffd000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 703400 KByte free memory MOE: found RAM from 1000 to 2fffd000 MOE: allocated 767 KByte for the page array @0x18d000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [2273000-235e771] [C:503000] l4re BOOTFS: [235f000-25441c6] [C:504000] ned BOOTFS: [de57000-de5760c] [C:505000] l4lx-gfx.cfg BOOTFS: [2545000-2dd1118] [C:506000] io BOOTFS: [2dd2000-2f1fcf3] [C:507000] fb-drv BOOTFS: [2f20000-32292d2] [C:508000] mag BOOTFS: [df13000-df133b7] [C:509000] x86-legacy.devs BOOTFS: [322a000-322a21f] [C:50a000] l4lx-x86.io BOOTFS: [322b000-366575b] [C:50b000] vmlinuz MOE: cmdline: moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f8850 io | ACPI: RSDP 0xf8850 00014 (v00 BOCHS ) io | ACPI: RSDT 0x2fffde30 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0x2ffffe70 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0x2fffdfd0 01E22 (v01 BXPC BXDSDT 00000001 INTL 20090521) io | ACPI: FACS 0x2ffffe00 00040 io | ACPI: SSDT 0x2fffdf90 00037 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0x2fffdeb0 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0x2fffde70 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 247 Objects with 47 Devices 79 Methods 5 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 1 Objects with 0 Devices 0 Methods 0 Regions io | tbxface-0601 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0184 [02] Enable : Transition to ACPI mode successful io | evgpeblk-1129 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | /home/arno/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:57:AcpiOsInstallInterruptHandler: UNINPLEMENTED io | Completing Region/Field/Buffer/Package initialization:................ io | Initialized 5/5 Regions 0/0 Fields 7/7 Buffers 4/4 Packages (257 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 0 _STA executions (examined 50 objects) io | evgpeblk-1234 [03] EvInitializeGpeBlock : Found 0 Wake, Enabled 16 Runtime GPEs in this block io | ACPICA-Version:20091214, System in ACPI MODE, 32bit timer io | WARNING: device 'S2__' already assigned to an other virtual bus. io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 2.0 fb-drv | OEM VGABIOS Cirrus extension fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: e0000000 - e0400000 fb-drv | virt: 400000 - 800000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 pos: 0, 0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 400000-800000 mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 mag | Plugin: Frame-buffer service started mag | Plugin: Mag_client service started l4linux | PH 0 (t: 1) offs=00001000 vaddr=00400000 vend=006df000 l4linux | f_sz=002df000 memsz=002df000 flgs=r-x l4linux | PH 1 (t: 1) offs=002e0000 vaddr=006df000 vend=007e0000 l4linux | f_sz=00055168 memsz=00101000 flgs=rw- l4linux | PH 2 (t: 4) offs=00242e1c vaddr=00641e1c vend=00641e40 l4linux | f_sz=00000024 memsz=00000024 flgs=--- l4linux | Starting binary at 0x400000, argc=8 argv=0x80007f98 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa80005b0 l4linux | ======> L4Linux 2.6 starting... <======== l4linux | Linux version 2.6.38-l4-svn19 (arno@l4) (gcc version 4.4.5 (Debian 4.4.5-8) ) #5 Wed Jun 15 08:25:35 EDT 2011 l4linux | Binary name: rom/vmlinuz l4linux | Linux kernel command line (7 args): mem=512M console=ttyLv0 console=tty0 root=/dev/nfs nfsroot=192.168.2.25:/home/arno/bootstrap ip=dhcp nfsrootdebug l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00400000 - 007e0000 [3968 KiB]. l4linux | Areas: Text: 00400000 - 006df000 [2940kB] (a bit longer) l4linux | Data: 006df000 - 00703a20 [146kB] l4linux | Initdata: 00705000 - 00736000 [196kB] l4linux | BSS: 00736000 - 007d0000 [616kB] l4linux | gs=43 fs=43 l4linux | l4lx_thread_create: Created thread 417 (tamer0) (u:b3000400, sp:0074e954) l4linux | Tamer0 is 417 l4linux | Using tamed mode. l4linux | Device scan: l4linux | Device: l4linux | PORT: 000001f0 - 000001f7 l4linux | PORT: 000003f6 - 000003f6 l4linux | IRQ: 0000000e - 0000000e l4linux | PORT: 00000170 - 00000177 l4linux | PORT: 00000376 - 00000376 l4linux | IRQ: 0000000f - 0000000f l4linux | PORT: 0000c000 - 0000c00f l4linux | Device: l4linux | IRQ: 0000000b - 0000000b l4linux | MEM: e2020000 - e203ffff l4linux | PORT: 0000c040 - 0000c07f l4linux | l4x_fiasco_gdt_entry_offset = 9 l4linux | rtc not found l4linux | WARNING: RTC server does not seem there! l4linux | l4lx_thread_create: Created thread 419 (cpu0) (u:b3000600, sp:006e1ff4) l4linux | main thread will be 419 l4linux | l4x_register_pointer_section: addr = 006df000 size = 1052672 l4linux | section-with-init: virt: 0x6df000 to 0x7dffff [1028 KiB] l4linux | section-with-init: Phys: 0x009e8000 to 0x00ae9000, Size: 1052672 l4linux | l4x_linux_startup: thread 419. l4linux | Main thread running, waiting... l4linux | main thread: received startup message. l4linux | utcb 0xb3000600 l4linux | l4x_setup_memory: Forcing superpages for main memory l4linux | l4re_global_env: 0xb1007ea0 l4linux | Main memory size: 512MB l4linux | Main memory: virt: 0x800000 to 0x207fffff [524288 KiB] l4linux | Main memory: Phys: 0x03800000 to 0x23800000, Size: 536870912 l4linux | Filling lower ptabs... l4linux | blah l4linux | blah l4linux | Done (1028 entries). l4linux | l4x_register_pointer_section: addr = 006df000 size = 1052672 l4linux | end: virt: 0x6df000 to 0x7dffff [1028 KiB] l4linux | end: Phys: 0x009e8000 to 0x00ae9000, Size: 1052672 l4linux | l4lx_thread_create: Created thread 41e (IRQ CPU0) (u:b3000800, sp:00765ff4) l4linux | rtc not found Linux version 2.6.38-l4-svn19 (arno@l4) (gcc version 4.4.5 (Debian 4.4.5-8) ) #5 Wed Jun 15 08:25:35 EDT 2011 BIOS-provided physical RAM map: L4Lx-Memory: 0000000000000000 - 0000000000001000 (usable) L4Lx-Memory: 0000000000400000 - 00000000007e0000 (usable) L4Lx-Memory: 00000000007e0000 - 0000000000800000 (unusable) L4Lx-Memory: 0000000000800000 - 0000000020800000 (usable) Notice: NX (Execute Disable) protection missing in CPU! last_pfn = 0x20800 max_arch_pfn = 0x100000 init_memory_mapping: 0000000000000000-0000000020800000 520MB LOWMEM available. mapped low ram: 0 - 20800000 low ram: 0 - 20800000 Zone PFN ranges: DMA 0x00000400 -> 0x00000000 Normal 0x00000000 -> 0x00020800 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x00000400 -> 0x000007e0 0: 0x00000800 -> 0x00020800 Allocating PCI resources starting at 20800000 (gap: 20800000:df800000) Built 1 zonelists in Zone order, mobility grouping on. Total pages: 131032 Kernel command line: mem=512M console=ttyLv0 console=tty0 root=/dev/nfs nfsroot=192.168.2.25:/home/arno/bootstrap ip=dhcp nfsrootdebug PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Initializing CPU#0 Memory: 519772k/532480k available (2310k kernel code, 8484k reserved, 776k data, 196k init, 0k highmem) virtual kernel memory layout: fixmap : 0x00100000 - 0x0011a000 ( 104 kB) vmalloc : 0x20800000 - 0x28800000 ( 128 MB) lowmem : 0x00000000 - 0x20800000 ( 520 MB) .init : 0x00705000 - 0x00736000 ( 196 kB) .data : 0x0064185a - 0x00703a20 ( 776 kB) .text : 0x00400000 - 0x0064185a (2310 kB) NR_IRQS:192 l4lx_irq_init: creating IRQ thread on cpu 0 Console: colour dummy device 80x25 console [tty0] enabled irq_thread: Starting IRQ thread on CPU 0 console [ttyLv0] enabled Detected 2386.687 MHz processor. Calibrating delay loop (skipped), value calculated using timer frequency.. 4773.37 BogoMIPS (lpj=23866870) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 512 CPU: Intel Pentium II (Klamath) stepping 03 Performance Events: l4linux | WARNING: Unknown rdmsr: 00000186 at 0x70c14d l4linux | WARNING: Unknown rdmsr: 00000187 at 0x70c14d l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x70c1db l4linux | WARNING: Unknown rdmsr: 000000c1 at 0x70c1e9 Broken PMU hardware detected, using software events only. NET: Registered protocol family 16 bio: create slab <bio-0> at 0 vgaarb: loaded PCI: L4 root bridge is device 176e0 PCI: Using L4-IO for IRQ routing pci 0000:00:00.0: No interrupt pin configured for device 0000:00:00.0 L4IRQ: set irq type of 11 to 4 pci 0000:00:01.0: PCI INT A -> GSI 11 (level, high) -> IRQ 11 Switching to clocksource l4kipclk NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. platform rtc_cmos: registered platform RTC device (no PNP device found) nfs4filelayout_init: NFSv4 File Layout Driver Registering... msgmni has been set to 1015 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) l4fb l4fb.0: look for capability 'fb' as goos sesseion l4fb l4fb.0: 640x480@16 2bypp, size: 614400 @ 28800000 l4fb l4fb.0: 5:6:5 11:5:0 linelen=1280 visual=2 Console: switching to colour frame buffer device 80x30 l4fb l4fb.0: l4fb L4 frame buffer device (refresh: 10jiffies) input: L4keyb '0' as /devices/virtual/input/input0 input: L4mouse '0' as /devices/virtual/input/input1 L4 serial driver ttyLv0 at MMIO 0x1 (irq = 64) is a L4 L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI e1000: Copyright (c) 1999-2006 Intel Corporation. L4IRQ: set irq type of 11 to 4 e1000 0000:00:01.0: PCI INT A -> GSI 11 (level, high) -> IRQ 11 __l4x_ioremap: Mapping physaddr e2020000 [0x20000 Bytes, e2020000+020000] to 28897000+000000 l4linux | cpu0: utcb=0xb3000600 419 l4linux | l4lx_thread_create: Created thread 423 (idler0) (u:b3000a00, sp:00767ff8) Switching to clocksource tsc e1000 0000:00:01.0: eth0: (PCI:33MHz:32-bit) 52:54:00:12:34:56 e1000 0000:00:01.0: eth0: Intel(R) PRO/1000 Network Connection e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 e1000e: Copyright(c) 1999 - 2011 Intel Corporation. mousedev: PS/2 mouse device common for all mice TCP cubic registered NET: Registered protocol family 17 Registering the dns_resolver key type e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sending DHCP requests ., OK IP-Config: Got DHCP answer from 10.0.2.2, my address is 10.0.2.15 IP-Config: Complete: device=eth0, addr=10.0.2.15, mask=255.255.255.0, gw=10.0.2.2, host=10.0.2.15, domain=, nis-domain=(none), bootserver=10.0.2.2, rootserver=192.168.2.25, rootpath= Root-NFS: nfsroot=/home/arno/bootstrap NFS: nfs mount opts='udp,nolock,addr=192.168.2.25' NFS: parsing nfs mount option 'udp' NFS: parsing nfs mount option 'nolock' NFS: parsing nfs mount option 'addr=192.168.2.25' NFS: MNTPATH: '/home/arno/bootstrap' NFS: sending MNT request for 192.168.2.25:/home/arno/bootstrap NFS: received 1 auth flavors NFS: auth flavor[0]: 1 NFS: MNT request succeeded NFS: using auth flavor 1 VFS: Mounted root (nfs filesystem) on device 0:11. Freeing unused kernel memory: 196k freed Clocksource tsc unstable (delta = 85885513 ns) Switching to clocksource l4kipclk l4linux | Page fault (non-resolved): pfa=6 pc=61fff9 Die message: Trap: 14 Trap: 14: 0006 [#1] last sysfs file: /sys/kernel/uevent_seqnum Modules linked in: Pid: 824, comm: mv Not tainted 2.6.38-l4-svn19 #5 EIP: 0000:[<0061fff9>] EFLAGS: 00003246 CPU: 0 EIP is at rpc_wake_up_task_queue_locked+0x69/0x1f0 EAX: 00000000 EBX: 1fe181ac ECX: 00000000 EDX: 1fc92420 ESI: 1fe181ac EDI: 1fe18000 EBP: 1fc0bcb8 ESP: 1fc0bc7c DS: 0000 ES: 0000 FS: 0043 GS: 0043 SS: 0023 Process mv (pid: 824, ti=1fc0a000 task=1fcadba0 task.ti=1fc98000) Stack: 1fc0bc84 00000000 1fded94c 00000078 00403866 1fc0bcbc 00000000 1fe18000 1fc0bcb4 0041fc64 1fc0bca8 000f4240 1fe181ac 1fc92420 1fe18000 1fc0bcc8 006203ff 1fe1e3d0 1fc92420 1fc0bd14 0061c4d8 1fc0bcfc 00000078 00000000 Call Trace: [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<0041fc64>] ? ns_to_timespec+0x44/0x70 [<006203ff>] rpc_wake_up_queued_task+0x1f/0x30 [<0061c4d8>] xprt_complete_rqst+0x118/0x180 [<0061f05a>] xs_udp_data_ready+0x14a/0x1b0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<005b1e43>] sock_queue_rcv_skb+0xe3/0x130 [<005db2fb>] ip_queue_rcv_skb+0x2b/0x50 [<005f5e86>] __udp_queue_rcv_skb+0x16/0x70 [<005f74d9>] udp_queue_rcv_skb+0x1b9/0x280 [<005f8876>] __udp4_lib_rcv+0x166/0x5c0 [<005d69ee>] ? ip_defrag+0x41e/0xa60 [<00419000>] ? __sched_setscheduler+0x1a0/0x390 [<005f8ce2>] udp_rcv+0x12/0x20 [<005d615c>] ip_local_deliver+0x6c/0x180 [<005d5eca>] ip_rcv+0x2da/0x500 [<005bac0c>] __netif_receive_skb+0x26c/0x2d0 [<00406bf9>] ? nommu_map_page+0x29/0xd0 [<005b4e46>] ? __alloc_skb+0x56/0x100 [<005badca>] netif_receive_skb+0x2a/0x60 [<005bae37>] napi_skb_finish+0x37/0x50 [<005bb9cb>] napi_gro_receive+0xdb/0xf0 [<005b4e46>] ? __alloc_skb+0x56/0x100 [<0057843d>] e1000_receive_skb+0x3d/0x60 [<00578b69>] e1000_clean_rx_irq+0x1d9/0x370 [<0057b798>] e1000_clean+0x1b8/0x510 [<004039ad>] ? l4x_global_restore_flags+0x3d/0x50 [<00418858>] ? try_to_wake_up+0x58/0xa0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<005bb037>] net_rx_action+0x77/0x100 [<00420722>] __do_softirq+0x72/0x100 [<004206b0>] ? __do_softirq+0x0/0x100 <IRQ> [<0042011d>] ? irq_exit+0x2d/0x40 [<0040d73b>] ? do_IRQ+0x3b/0x90 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<004038f7>] ? l4x_global_cli+0x57/0xd0 [<00528bc5>] ? irq_thread+0x175/0x380 Code: 42 38 a8 04 0f 84 10 01 00 00 8b 4a 34 85 c9 74 49 f6 05 c8 ea 7c 00 40 0f 85 73 01 00 00 8b 42 58 8b 4a 54 c7 42 34 00 00 00 00 <89> 41 04 89 08 8d 43 48 c7 42 54 00 01 10 00 c7 42 58 00 02 20 EIP: [<0061fff9>] rpc_wake_up_task_queue_locked+0x69/0x1f0 SS:ESP 0023:1fc0bc7c ---[ end trace 63f9d268df476d30 ]--- Kernel panic - not syncing: Fatal exception in interrupt Pid: 824, comm: mv Tainted: G D 2.6.38-l4-svn19 #5 Call Trace: [<0063fced>] ? panic+0x57/0x143 [<0040de5a>] ? oops_end+0x8a/0x90 [<0040dfd5>] ? die+0x45/0x70 [<0061fff9>] ? rpc_wake_up_task_queue_locked+0x69/0x1f0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<0041fc64>] ? ns_to_timespec+0x44/0x70 [<006203ff>] ? rpc_wake_up_queued_task+0x1f/0x30 [<0061c4d8>] ? xprt_complete_rqst+0x118/0x180 [<0061f05a>] ? xs_udp_data_ready+0x14a/0x1b0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<005b1e43>] ? sock_queue_rcv_skb+0xe3/0x130 [<005db2fb>] ? ip_queue_rcv_skb+0x2b/0x50 [<005f5e86>] ? __udp_queue_rcv_skb+0x16/0x70 [<005f74d9>] ? udp_queue_rcv_skb+0x1b9/0x280 [<005f8876>] ? __udp4_lib_rcv+0x166/0x5c0 [<005d69ee>] ? ip_defrag+0x41e/0xa60 [<00419000>] ? __sched_setscheduler+0x1a0/0x390 [<005f8ce2>] ? udp_rcv+0x12/0x20 [<005d615c>] ? ip_local_deliver+0x6c/0x180 [<005d5eca>] ? ip_rcv+0x2da/0x500 [<005bac0c>] ? __netif_receive_skb+0x26c/0x2d0 [<00406bf9>] ? nommu_map_page+0x29/0xd0 [<005b4e46>] ? __alloc_skb+0x56/0x100 [<005badca>] ? netif_receive_skb+0x2a/0x60 [<005bae37>] ? napi_skb_finish+0x37/0x50 [<005bb9cb>] ? napi_gro_receive+0xdb/0xf0 [<005b4e46>] ? __alloc_skb+0x56/0x100 [<0057843d>] ? e1000_receive_skb+0x3d/0x60 [<00578b69>] ? e1000_clean_rx_irq+0x1d9/0x370 [<0057b798>] ? e1000_clean+0x1b8/0x510 [<004039ad>] ? l4x_global_restore_flags+0x3d/0x50 [<00418858>] ? try_to_wake_up+0x58/0xa0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<005bb037>] ? net_rx_action+0x77/0x100 [<00420722>] ? __do_softirq+0x72/0x100 [<004206b0>] ? __do_softirq+0x0/0x100 <IRQ> [<0042011d>] ? irq_exit+0x2d/0x40 [<0040d73b>] ? do_IRQ+0x3b/0x90 [<00403866>] ? l4x_global_sti+0xa6/0xe0 [<004038f7>] ? l4x_global_cli+0x57/0xd0 [<00528bc5>] ? irq_thread+0x175/0x380 panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye FWIW: The ram disk example works with the same kernel. -- Arno Töll GnuPG Key-ID: 0x9D80F36D

2 4

Properly detect muliple PCI root brings in L4Re's io process
by Christian Ehrhardt 16 Jun '11

16 Jun '11

Hi, I tried to run fiasco and L4Linux on an SMP machine that features two idenpendent PCI root bridges. Currently, the io process fails to scan the bus connected to the second bridge. It properly detects that two PCI root bridges are present and creates two seperate Pci_port_root_bridge objects. However, it fails to initialize the Pci_bridge::num field properly. As a result, the io process scans the first bus twice. This causes major havoc as PCI devices on the second bus don't show up in L4Linux at all and devices on the first bus are detected twice. According to http://www.acpi.info/acpi_faq.htm the ACPI structures should contain a _BBN method to detect the bus number of both root busses. The following patch uses this method to detect and set the Pci_bridge::num field properly. A patch to fix this is provided below. With this patch NICs on both PCI busses are detected and work properly on the hardware in question. As always comments are appreciated. regards Christian The contributions made by this patch are licensed under the MIT license (http://www.opensource.org/licenses/mit-license.php). diff --git a/src/l4/pkg/io/server/src/acpi.cc b/src/l4/pkg/io/server/src/acpi.cc index f76c768..4179c4e 100644 --- a/src/l4/pkg/io/server/src/acpi.cc +++ b/src/l4/pkg/io/server/src/acpi.cc @@ -572,9 +572,25 @@ discover_pre_cb(ACPI_HANDLE obj, UINT32 nl, void *ctxt, void **) //AcpiUtReleaseMutex(ACPI_MTX_NAMESPACE); // hm, this seems very specific for PCI + /* + * Systems with multiple PCI root bridges must provide the PCI bus + * number of each bus via the _BBN method. + */ if (pci_rb) { - d_printf(DBG_DEBUG, "Found PCI root bridge...\n"); + ACPI_INTEGER pci_int; + bool have_bbn = false; + + if (ACPI_SUCCESS(AcpiUtEvaluateNumericObject((char*)METHOD_NAME__BBN, + node, &pci_int))) + { + d_printf(DBG_DEBUG, "PCI root bridge with BBN=%llx...\n", pci_int); + have_bbn = true; + } + else + { + d_printf(DBG_DEBUG, "Found PCI root bridge without BBN...\n"); + } if (Pci_root_bridge *rb = pci_root_bridge(0)) { if (rb->host()) @@ -582,9 +598,13 @@ discover_pre_cb(ACPI_HANDLE obj, UINT32 nl, void *ctxt, void **) // we found a second root bridge // create a new root pridge instance rb = new Pci_port_root_bridge(nd); + if (!have_bbn) + d_printf(DBG_ERR, "ERROR: Multiple root bridges without BBN\n"); } else rb->set_host(nd); + if (have_bbn) + rb->num = pci_int; nd->set_discover_bus_if(rb); }

4 4

Pager in Fiasco.OC
by Chen Tian 15 Jun '11

15 Jun '11

Hello, In Fiasco.OC, can we register a distinct pager for each thread? I wonder if l4_thread_control_pager is for this purpose. Thanks, Chen

2 1

Building L4Linux for ARM
by Anna Fischer 15 Jun '11

15 Jun '11

Hi, I am trying to compile/build L4Linux for an ARM-based platform. When I execute make then I get an error saying Makeconf.l4conf cannot be found. These are the steps I have followed to build L4Linux. # cd /root/l4linux # svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux # cd l4linux/ # mkdir build # cp arch/l4/configs/arm-mp_defconfig build/.config # make O=build/ oldconfig # make O=build/ menuconfig (set L4 tree build directory to '/root/l4linux/l4linux/build') (de-configure PCI etc) # make O=build/ L4 source directory: /root/l4linux/l4linux PWD=/root/l4linux/l4linux make -C /root/l4linux/l4linux -f /root/l4linux/l4linux/arch/l4/Makefile.l4conf O=/root/l4linux/l4linux/build L4X_LOOP_CHECK=1 OUTPUT=/root/l4linux/l4linux/build/Makeconf.l4conf make[3]: *** No rule to make target `/.config.all', needed by `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. make[2]: *** [/root/l4linux/l4linux/build/Makeconf.l4conf] Error 2 GEN /root/l4linux/l4linux/build/Makefile scripts/kconfig/conf --silentoldconfig Kconfig make[2]: *** No rule to make target `/.config.all', needed by `/root/l4linux/l4linux/build/Makeconf.l4conf'. Stop. Creating asm-l4/api-l4env -> asm/api symlink Creating asm-l4/l4lxapi/impl symlink Creating asm-l4/l4x-arm -> asm/l4x symlink Creating asm-l4/l4-arch/asm symlink Creating asm-l4/arm-arch/mach symlink Creating asm-l4/orig-arch symlink make[1]: *** No rule to make target `/root/l4linux/l4linux/build/Makeconf.l4conf', needed by `archprepare'. Stop. make: *** [sub-make] Error 2 My cross-compiler is arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2011.03-41) 4.5.2. I have successfully used it to also build fiasco + L4Re. Thanks for your help. Anna

2 4

Twl4030 over I2C at BB clone with Fiasco.
by Vasily Sartakov 10 Jun '11

10 Jun '11

Hello. I would like a use twl4030 usb on my BB clone board - devkit8000 and i have some question about it. For do it, shell i add platform initialisation from linux arm/mach-omap2/board-devkit8000 to l4l/arch/l4/kernel/arch-arm ? then change .config to use omap devices, like omap-i2c, twl4030 etc? Thanks -- Sartakov A. Vasily

2 2

Re: L4 on Qualcomm snapdragon chipset?
by joel nider 09 Jun '11

09 Jun '11

Hi Anna, I can confirm that it is possible. The Scorpion processor is fully ARM v7 compliant, and as you said the instruction set is compatible with the Cortex-A8. Of course you will have to write the BSP (in kern/arm/bsp) - I suggest using the realview directory as a template, and modify the files as needed. If you change the Kconfig file, then you can get Snapdragon to show up as a new target. # PF: Snapdragon # PFDESCR: 7x30, 7x27, etc # PFCAN: CAN_ARM_CPU_CORTEX_A8 # PFDEPENDS: ARM Joel On Mon Jun 06, 2011 at 13:55:37 +0100, Anna Fischer wrote: > I was wondering if anyone can confirm that Fiasco will run on a Qualcomm > Snapdragon chipset? > > http://www.arm.com/markets/mobile/qualcomm-snapdragon-chipset.php > > It is based on ARM v7 and similar to the Cortex-8. > > On the Fiasco build (make config) it only shows ARM CPUs. > Thanks, > Anna

1 0

L4 on Qualcomm snapdragon chipset?
by Anna Fischer 07 Jun '11

07 Jun '11

Hi, I was wondering if anyone can confirm that Fiasco will run on a Qualcomm Snapdragon chipset? http://www.arm.com/markets/mobile/qualcomm-snapdragon-chipset.php It is based on ARM v7 and similar to the Cortex-8. On the Fiasco build (make config) it only shows ARM CPUs. Thanks, Anna

3 5

Re: building L4 x86 on cygwin (Adam Lackorzynski)
by joel nider 01 Jun '11

01 Jun '11

Hi Adam, Sorry - I had not installed my GCC correctly. I just wanted to report that by using the following command line: make SYSTEM_TARGET=arm-elf- L4STD_INCDIR=/usr/local/lib/gcc/arm-elf/4.4.3/include/ CONFIG_KERNEL_LOAD_ADDR=0x80000000 I was able to build successfully on Cygwin, and load the kernel image to my device. I am now in the process of debugging the boot sequence. It seems the memory I am loading to is not zero-initialized, and this is causing some issues with non-initialized variables. Also, I don't have a serial port so printf() was crashing while trying to write to the Console. I will write back when I have completed, or get really stuck. Thanks for the support, Joel > Hi, > > On Sun May 22, 2011 at 12:09:56 +0300, joel nider wrote: > > I'm trying to build l4 on cygwin (windows) for x86. I have > built binutils 2.21 and gcc 4.5.2 as cross-compilers (-- > target=i386-elf). When I try to build l4, I pass > SYSTEM_TARGET=i386-elf- as a parameter to 'make'. > > > > Preprocessing seems to complete successfully, but compilation > fails on the first file (kip.cpp). The error message is: > > > > src/kernel/fiasco/src/types/types.h:4:20: fatal error: stddef.h: > No such file or directory > > > > My question is - what is missing? Do I need to build glibc? Or > did I miss something while installing my gcc? > > stddef.h comes with gcc, is it there in your installation? If, in > whichpath is it? > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/

1 0

utcb's address in Fiasco.OC
by Chen Tian 01 Jun '11

01 Jun '11

Hi, Where is the utcb's address of a thread is stored? If I implement a user level thread context switch (i.e., change the contents in registers EIP/ESP and general purpose registers), will a thread lose its utcb pointer? Thanks. Best, Chen

2 1

kmem_alloc: out of kernel memory
by David Silcott 30 May '11

30 May '11

Hi, I've synced my local copy of Pistachio against the latest available and now all of my builds are reporting an out of memory error when I try to run any application, even pingpong or memtest KickStart 0.13.06 Detected multiboot compliant loader kernel (0x00824000-0x0090ad41) => 0x001ef4d0 (0x00824000-0x0083f388) -> 0x00100000-0x0011b388 (0x00840000-0x00840028) -> 0x0011c000-0x0011c028 (0x00841000-0x0084a376) -> 0x0011d000-0x00126376 (0x0084b000-0x008ef0c0) -> 0x00127000-0x001cb0c0 (0x008f0000-0x008f4338) -> 0x001ec000-0x001f0338 sigma0 (0x0090b000-0x0092eb24) => 0x00020000 (0x0090c000-0x00915524) -> 0x00020000-0x00029524 roottask (0x0092f000-0x0093d424) => 0x00400000 (0x00930000-0x00935044) -> 0x00400000-0x00405044 Launching kernel ... L4Ka::Pistachio - built on May 28 2011 21:39:10 by david@andesite using gcc version 3.3.6 --- "KD# kmem_alloc: out of kernel memory" --- --------------------------------- (eip=f010909c, esp=00000000) --- A query of the memory statistics reveals the following: /stats> kmem Kernel memory statistics: Chunk size = 1024 bytes Free chunks = 2 (2KB) Consecutive Number of chunks matches 1 2 2 1 4 0 8 0 16 0 32 0 64 0 128 0 256 0 512 0 1024+ 0 Max consecutive chunks: 2 I get the same results even if I explicitly pass memory values to kickstart: maxmem=1G kmem=128M I have tried several versions of GCC with 3.3.6 being the last but all have reported some form of 'out of memory' error and the error occurs both on qemu and on a physical machine. The processor and memory spcecs of my machine are: CPU: Intel Core 2 duo Memory: 4G Can anyone see what I am doing wrong? I didn't have this problem before updated pistachio I have attached a copy of my config.out file. Regards David

1 1

Genode OS Framework 11.05 released
by Stefan Kalkowski 26 May '11

26 May '11

Dear L4 hackers, we are pleased to announce the release of version 11.05 of the Genode OS Framework. Genode is an OS architecture that promises to align high security and robustness with dynamic application workloads. It is laid out to run on a number of different microkernels and Linux. After bringing Genode on top of Fiasco.OC with the last release, the new version comprises a lot of new features, and refinements with respect to Fiasco.OC, in particular: * Shared libraries * Signalling framework * ARM RealView PBX-A9 support * x86 64-bit support Moreover, we enabled L4Linux to run on top of Genode. Beside these functionality improvements, we discovered a way to seamlessly integrate Fiasco.OC's and L4Linux build process into Genode's build system. Thereby we drastically simplified the process of developing for Genode/Fiasco.OC. Alongside the improved support of the Fiasco.OC kernel, the new release implies a bunch of new features, and improvements, like: * New API for type-safe inter-process communication * New experimental GDB support * Device-I/O support for MicroBlaze platform * ARM RealView PBX device drivers for input, display, network, and sdcard * New ready-to-use scripts for easy test-driving of various Genode features such as Qt4, lwIP, Noux, L4Linux, GDB Please find a more elaborative description of the changes accompanied with a lot of background information in the release notes of version 11.05: http://genode.org/documentation/release-notes/11.05 The new version is ready for download at our download page at Sourceforge and our public SVN repository: http://genode.org/download Regards -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Questions about Pistachio
by Gregory 26 May '11

26 May '11

I am experimenting with l4 pistachio and i seem to be running into some rather weird problems. 1) when i attempt to create a thread, my thread creation code does seem to work if it is in "main()" however if i move the code into another function an call that function from main, the code works. What happens is that if I attempt to create a thread from "main" when i call "L4_ThreadControl()" the function returns an error value (which is found to be '6'), which indicates that the the UTCB location is invalid. However, the latter does not happen when the exact same thread creation code is in a different function. Now this does not bother me that much, as long as i can still successfully create threads, but, i am a bit curious as to why this happens. 2) the piece of code that i use to create threads (derived from the l4test app), obtains the utcb location of new thread looks like this: L4_Word_t root_utcb = *(*L4_Word_t)&root_local_id; root_utcb &= ~(L4_UtcbAreaSize(kip) - 1); L4_Word_t new_utcb = root_utcb + (L4_UtcbSize(kip) * (L4_ThreadNo(new_tid) - L4_ThreadNo(root_tid))); Now this piece of code works, but, i do not understand why the second line is needed if the local thread id is already equal to the utcb location. Why is this needed? 3) I cannot seem to receive interrupt IPCs. I have seen no code built on pistachio that handle interrupts thus far, so my code looks like this: L4_Thread_t irq; //simple handler function that simply acknowledges the interrupt ipc void handler_func(void) { printf("the handler has been called\n"); L4_Msg_t msg; L4_MsgTag_t tag; L4_Clear(&msg); L4_Load(&msg); tag = L4_Send(irq, L4_TimePeriod(1000000)); if(L4_IpcFailed(tag)) /*prints out the error. ">>1" is used to remove propagation bit printf("the ipc failed with error [%d]", (int)L4_ErrorCode()>>1); } int main() { ... //initialization, etc irq = L4_GlobalId(1,1); //in hopes of getting the keyboard interrupt L4_AssociateInterrupt(irq, handler); //the handler thread is setup ealier L4_Sleep(L4_Never); //so that the code doesn't exit } this piece of code prints out: the handler has been called the ipc failed with error [1] Which base on the v4 reference manual mean "timeout, from is defined in this case". Also if i "sleep" for less than L4_Never the kernel crashes and reports that there is an invalid opcode. Where am i going wrong?

1 1

Pager in the Fiasco.OC.
by Chen Tian 25 May '11

25 May '11

Hello, After a pager resolves a page fault in user space, I assume the reply message, which contains the mapping, should be processed in the kernel (e.g., update page table etc.). Am I right? If so, where can I find the corresponding implementation? Thanks. Best, Chen

2 1

building L4 x86 on cygwin
by joel nider 23 May '11

23 May '11

Hi, I'm trying to build l4 on cygwin (windows) for x86. I have built binutils 2.21 and gcc 4.5.2 as cross-compilers (--target=i386-elf). When I try to build l4, I pass SYSTEM_TARGET=i386-elf- as a parameter to 'make'. Preprocessing seems to complete successfully, but compilation fails on the first file (kip.cpp). The error message is: src/kernel/fiasco/src/types/types.h:4:20: fatal error: stddef.h: No such file or directory My question is - what is missing? Do I need to build glibc? Or did I miss something while installing my gcc? Thanks in advance, Joel

2 1

information on interrupt thread convention
by Jason Phillips 21 May '11

21 May '11

hi all, does the interrupt number of interrupt thread correspond to IRQ number? So thread-id for IRQ2 is 0x00008001?

2 9

Freeze L4-thread of Fiasco.OC
by Ivan Bludov 20 May '11

20 May '11

Hello, I intend to freeze some l4-thread from another thread on Fiasco.OC. What have I use for doing this? By investigation I discover that it could be done by l4_thread_schedule on L4Env of Fiasco in past. But this function is obsolete in L4Re. I suggest that process can be frozen by other way. Could you make some advice how to do it? Regards, Ivan Bludov

2 1

JVM port for Fiasco.OC/L4Re
by Nuno Santos 17 May '11

17 May '11

Hello I'd like to ask if you are aware of a JVM port to run natively on Fiasco.OC/L4Re. Apparently, there is a port of Kaffe to DROPS, but its last version is from 2008 and it seems to be stale at the moment. Thank you very much, --Nuno Santos

2 1

build error: No rule to make target crtendS.o
by Guillaume Salagnac 17 May '11

17 May '11

Hi all, I'm trying to compile Fiasco/L4Re for beagleboard from a 64bit macosx host. "make setup" is quite happy, even though it yields a few warnings, but "make" itself chokes on the "No rule to make target ...crtendS.o, needed by libl4sys.so". (full transcript below, the error is at the very bottom) I do know it's the first item in the FAQ, but I can't seem to understand the fix: the ARM target is 32-bit anyway, so why am I getting bitten by these 32-bits/64-bits issues ? I installed pretty much all packages I could think of (several variants of arm-gcc, of gcc, including multilib) but obviously I'm missing something important. Any advice would be greatly appreciated, -Guillaume Salagnac % arm-none-eabi-gcc --version arm-none-eabi-gcc (Linaro GCC 4.5-2011.02-0) 4.5.2 Copyright (C) 2010 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. % make =============== Building all Fiasco configurations ============ ============ Building in obj/fiasco/arm-beagleboard ========= make -C /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/../tool/kconfig O=/Users/gsalagnac/prog/L4/fiasco/obj/fiasco/arm-beagleboard Kconfig=Kconfig KCONFIG_AUTOHEADER=globalconfig.h KCONFIG_TRISTATE=config/tristate.conf KCONFIG_CONFIG=globalconfig.out KCONFIG_AUTOCONFIG=config/auto.conf KERNELVERSION=SVN MENUCONFIG_COLOR=blackbg INCLUDE_PPC32= fiasco_srcdir=/Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/.. oldconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/lex.zconf.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o In file included from scripts/kconfig/zconf.tab.c:2500:0: /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/tool/kconfig/scripts/kconfig/util.c: In function 'file_lookup': /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/tool/kconfig/scripts/kconfig/util.c:26:13: warning: assignment discards 'const' qualifier from pointer target type [enabled by default] HOSTLD scripts/kconfig/conf scripts/kconfig/conf --oldconfig Kconfig # # configuration written to globalconfig.out # make -C /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/../tool/kconfig O=/Users/gsalagnac/prog/L4/fiasco/obj/fiasco/arm-beagleboard Kconfig=Kconfig KCONFIG_AUTOHEADER=globalconfig.h KCONFIG_TRISTATE=config/tristate.conf KCONFIG_CONFIG=globalconfig.out KCONFIG_AUTOCONFIG=config/auto.conf KERNELVERSION=SVN MENUCONFIG_COLOR=blackbg INCLUDE_PPC32= fiasco_srcdir=/Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/.. silentoldconfig scripts/kconfig/conf --silentoldconfig Kconfig Creating .Modules.deps make srcdir=/Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src objbase=/Users/gsalagnac/prog/L4/fiasco/obj/fiasco/arm-beagleboard -f /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/Makefile.sub1 rm -f \ touch .Clean-auto -n Checking compiler config... CHANGED. Recompiling. ... Preprocessing kip ... Preprocessing l4_types ... Preprocessing l4_fpage ... Preprocessing l4_msg_item ... Preprocessing l4_buf_desc ... Preprocessing l4_error ... Preprocessing cpu_mask ... Preprocessing rcupdate ... Preprocessing pages ... Preprocessing kobject_mapdb ... Preprocessing mem_region ... Preprocessing per_cpu_data ... Preprocessing startup ... Preprocessing boot_info ... Preprocessing cmdline ... Preprocessing queue ... Preprocessing queue_item ... Preprocessing l4_buf_iter ... Preprocessing irq_pin ... Preprocessing bitmap ... Preprocessing mapping ... Preprocessing spin_lock ... Preprocessing mapping_tree ... Preprocessing mappable ... Preprocessing dbg_page_info ... Preprocessing mapdb ... Preprocessing pic ... Preprocessing kobject_dbg ... Preprocessing kobject_iface ... Preprocessing kobject ... Preprocessing ready_queue_wfq ... Preprocessing ready_queue_fp ... Preprocessing obj_space ... Preprocessing ptab_base ... Preprocessing ram_quota ... Preprocessing ref_ptr ... Preprocessing ref_obj ... Preprocessing mem_space ... Preprocessing mem_space_sigma0 ... Preprocessing space ... Preprocessing vlog ... Preprocessing kmem ... Preprocessing kmem_alloc ... Preprocessing slab_cache_anon ... Preprocessing mem_layout ... Preprocessing kmem_slab_simple ... Preprocessing kmem_slab ... Preprocessing switch_lock ... Preprocessing kip_init ... Preprocessing thread_lock ... Preprocessing helping_lock ... Preprocessing cpu_lock ... Preprocessing timer ... Preprocessing timeout ... Preprocessing ipc_timeout ... Preprocessing timeslice_timeout ... Preprocessing per_cpu_data_alloc ... Preprocessing vcpu ... Preprocessing kobject_helper ... Preprocessing icu_helper ... Preprocessing thread_state ... Preprocessing context ... Preprocessing mp_lock ... Preprocessing sender ... Preprocessing receiver ... Preprocessing mem_unit ... Preprocessing factory ... Preprocessing lock ... Preprocessing ipc_sender ... Preprocessing thread ... Preprocessing thread_object ... Preprocessing syscalls ... Preprocessing kernel_thread ... Preprocessing map_util ... Preprocessing irq ... Preprocessing banner ... Preprocessing warn ... Preprocessing app_cpu_thread ... Preprocessing dirq ... Preprocessing globals ... Preprocessing watchdog ... Preprocessing kernel_uart ... Preprocessing main ... Preprocessing config ... Preprocessing mapped_alloc ... Preprocessing vmem_alloc ... Preprocessing paging ... Preprocessing fpu ... Preprocessing fpu_state ... Preprocessing fpu_alloc ... Preprocessing cpu ... Preprocessing entry_frame ... Preprocessing kernel_console ... Preprocessing ipc_gate ... Preprocessing task ... Preprocessing kernel_task ... Preprocessing irq_controller ... Preprocessing irq_chip ... Preprocessing terminate ... Preprocessing continuation ... Preprocessing sched_context ... Preprocessing utcb_init ... Preprocessing perf_cnt ... Preprocessing trap_state ... Preprocessing buddy_alloc ... Preprocessing vkey ... Preprocessing kdb_ke ... Preprocessing prio_list ... Preprocessing ipi ... Preprocessing scheduler ... Preprocessing clock ... Preprocessing vm_factory ... Preprocessing sys_call_page ... Preprocessing __main ... Preprocessing mem_op ... Preprocessing pagetable ... Preprocessing kmem_space ... Preprocessing boot_uart_init ... Preprocessing irq_chip_generic ... Preprocessing bootstrap ... Preprocessing kern_lib_page ... Preprocessing jdb_extensions ... Preprocessing outer_cache ... Preprocessing utcb_support ... Preprocessing u_semaphore ... Preprocessing uart_console ... Preprocessing jdb_tbuf ... Preprocessing jdb_tbuf_init ... Preprocessing tb_entry ... Preprocessing jdb_trace ... Preprocessing std_macros ... Preprocessing atomic ... Preprocessing lock_guard ... Preprocessing auto_ptr ... Preprocessing dlist ... Preprocessing sa1100 ... Preprocessing mux_console ... Preprocessing console ... Preprocessing uart ... Preprocessing filter_console ... Preprocessing h3xxx ... Preprocessing io ... Preprocessing mem ... Preprocessing mmu ... Preprocessing reset ... Preprocessing processor ... Preprocessing delayloop ... Preprocessing paranoia ... Preprocessing s_cruft ... Preprocessing jdb_ktrace ... Preprocessing jdb_handler_queue ... Preprocessing jdb_module ... Preprocessing jdb_pic ... Preprocessing jdb ... Preprocessing jdb_core ... Preprocessing jdb_prompt_ext ... Preprocessing jdb_list ... Preprocessing jdb_prompt_module ... Preprocessing jdb_exit_module ... Preprocessing jdb_kern_info ... Preprocessing jdb_tcb ... Preprocessing jdb_screen ... Preprocessing jdb_thread_list ... Preprocessing jdb_input ... Preprocessing jdb_symbol ... Preprocessing jdb_lines ... Preprocessing push_console ... Preprocessing jdb_timeout ... Preprocessing jdb_dump ... Preprocessing jdb_ptab ... Preprocessing jdb_attach_irq ... Preprocessing jdb_table ... Preprocessing jdb_kern_info_kmem_alloc ... Preprocessing jdb_kern_info_kip ... Preprocessing jdb_mapdb ... Preprocessing kern_cnt ... Preprocessing jdb_trace_set ... Preprocessing jdb_entry_frame ... Preprocessing jdb_kobject ... Preprocessing jdb_kobject_names ... Preprocessing jdb_util ... Preprocessing jdb_space ... Preprocessing jdb_utcb ... Preprocessing jdb_trap_state ... Preprocessing jdb_ipi ... Preprocessing jdb_rcupdate ... Preprocessing jdb_ipc_gate ... Preprocessing jdb_obj_space ... Preprocessing jdb_log ... Preprocessing jdb_factory ... Preprocessing jdb_semaphore ... Preprocessing jdb_thread ... Preprocessing jdb_scheduler ... Preprocessing jdb_sender_list ... Preprocessing jdb_perf ... Preprocessing jdb_vm ... Preprocessing jdb_regex ... Preprocessing jdb_disasm ... Preprocessing jdb_bp ... Preprocessing jdb_tbuf_output ... Preprocessing jdb_tbuf_show ... Preprocessing tb_entry_output make srcdir=/Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src objbase=/Users/gsalagnac/prog/L4/fiasco/obj/fiasco/arm-beagleboard -f /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/Makefile.sub2 all ... Generating version information ... Making kip.o ... Making kip-debug.o ... Making kip-arm.o ... Making l4_types.o ... Making l4_types-debug.o ... Making l4_fpage.o ... Making l4_msg_item.o ... Making l4_buf_desc.o ... Making l4_error.o ==> Archiving into libabi.a ... Making kernel.arm.lds ... Making crt0.o ... Making kernel_panic.o ... Making libc_backend_lock.o ... Making cpu_mask.o ... Making rcupdate.o ... Making pages.o ... Making kobject_mapdb.o ... Making mem_region.o ... Making per_cpu_data.o ... Making startup.o ... Making startup-arm.o ... Making boot_info.o ... Making boot_info-arch.o ... Making cmdline.o ... Making queue.o ... Making queue_item.o ... Making l4_buf_iter.o ... Making irq_pin.o ... Making bitmap.o ... Making mapping-arm.o ... Making mapping.o ... Making spin_lock.o ... Making spin_lock-arm.o ... Making mapping_tree.o ... Making mappable.o ... Making dbg_page_info.o ... Making mapdb.o ... Making pic.o ... Making pic-arm.o ... Making pic-arm-omap3.o ... Making kobject_dbg.o ... Making kobject_iface.o ... Making kobject.o ... Making ready_queue_wfq.o ... Making ready_queue_fp.o ... Making obj_space.o ... Making obj_space-virt.o ... Making ptab_base.o ... Making ram_quota.o ... Making ref_ptr.o ... Making ref_obj.o ... Making mem_space.o ... Making mem_space-arm.o ... Making mem_space-user.o ... Making mem_space_sigma0.o ... Making space.o ... Making space-arm.o ... Making vlog.o ... Making kmem.o ... Making kmem_alloc.o ... Making kmem_alloc-arm.o /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/arm/kmem_alloc-arm.cpp: In constructor 'Kmem_alloc::Kmem_alloc()': /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/arm/kmem_alloc-arm.cpp:59:1: warning: the frame size of 536 bytes is larger than 512 bytes [-Wframe-larger-than=] ... Making slab_cache_anon.o ... Making mem_layout.o ... Making mem_layout-arm.o ... Making mem_layout-noncont.o ... Making mem_layout-arm-omap3.o ... Making kmem_slab_simple.o ... Making kmem_slab.o ... Making switch_lock.o ... Making kip_init.o ... Making thread_lock.o ... Making helping_lock.o ... Making cpu_lock.o ... Making cpu_lock-generic.o ... Making timer.o ... Making timer-arm.o ... Making timer-arm-omap3.o ... Making timeout.o ... Making ipc_timeout.o ... Making timeslice_timeout.o ... Making per_cpu_data_alloc.o ... Making vcpu.o ... Making kobject_helper.o ... Making icu_helper.o ... Making thread_state.o ... Making context.o ... Making context-arm.o ... Making context-vcpu.o ... Making mp_lock.o ... Making sender.o ... Making receiver.o ... Making mem_unit.o ... Making factory.o ... Making lock.o ... Making ipc_sender.o ... Making thread.o ... Making thread-arm.o ... Making thread-jdb.o ... Making thread-ipc.o /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/thread-ipc.cpp: In member function 'void Thread::do_ipc(const L4_msg_tag&, bool, Thread*, bool, Sender*, L4_timeout_pair, Syscall_frame*, unsigned char)': /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/thread-ipc.cpp:744:55: warning: ignoring return value of 'bool Context::switch_exec_locked(Context*, Context::Helping_mode)', declared with attribute warn_unused_result [-Wunused-result] ... Making thread-pagefault.o ... Making thread-log.o ... Making thread-ulock.o ... Making thread-vcpu.o ... Making thread-debug.o ... Making thread_object.o ... Making syscalls.o ... Making syscalls-log.o ... Making kernel_thread.o ... Making kernel_thread-std.o ... Making kernel_thread-arm.o ... Making map_util.o ... Making map_util-mem.o ... Making map_util-objs.o In file included from auto/map_util-objs.cc:3:0: /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/map_util.cpp: In function 'L4_error map(MAPDB*, SPACE*, Space*, Page_number, Page_count, SPACE*, Space*, Page_number, bool, unsigned int, unsigned int, typename SPACE::Reap_list**) [with SPACE = Generic_obj_space<Space>, MAPDB = Kobject_mapdb, Page_number = Page_addr<0>, Page_count = Page_addr<0>, typename SPACE::Reap_list = Kobject*]': /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/map_util.cpp:515:13: warning: 'mapdb_frame.Kobject_mapdb::Frame::frame' may be used uninitialized in this function [-Wuninitialized] ... Making irq.o ... Making banner.o ... Making warn.o ... Making app_cpu_thread.o ... Making dirq.o ... Making dirq-arm.o ... Making globals.o ... Making watchdog.o ... Making kernel_uart.o ... Making kernel_uart-arm-omap3.o ... Making main.o ... Making config.o ... Making config-arm.o ... Making config-arm-omap3.o ... Making mapped_alloc.o ... Making vmem_alloc.o ... Making vmem_alloc-arch.o ... Making paging-arm.o ... Making paging.o ... Making fpu.o ... Making fpu-arm.o ... Making fpu_state.o ... Making fpu_alloc.o ... Making cpu.o ... Making cpu-arm.o ... Making entry_frame.o ... Making entry_frame-arm.o ... Making entry_frame-abs-timeout-hack.o ... Making kernel_console.o ... Making ipc_gate.o ... Making task.o /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/task.cpp: In member function 'virtual void Task::invoke(L4_obj_ref, Mword, Syscall_frame*, Utcb*)': /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/kern/task.cpp:408:22: warning: 'guard.Lock_guard_2<Helping_lock>::_state2' may be used uninitialized in this function [-Wuninitialized] ... Making task-arm.o ... Making kernel_task.o ... Making kernel_task-arm.o ... Making irq_controller.o ... Making irq_chip.o ... Making terminate.o ... Making continuation-arm.o ... Making sched_context-wfq.o ... Making sched_context-fixed_prio.o ... Making sched_context-fp_wfq.o ... Making sched_context.o ... Making utcb_init.o ... Making perf_cnt.o ... Making perf_cnt-arm.o ... Making trap_state.o ... Making buddy_alloc.o ... Making vkey.o ... Making kdb_ke.o ... Making kdb_ke-arm.o ... Making prio_list.o ... Making ipi.o ... Making ipi-arm.o ... Making scheduler.o ... Making clock.o ... Making clock-generic.o ... Making vm_factory.o ... Making sys_call_page.o ... Making sys_call_page-arm.o ... Making __main.o ... Making mem_op.o ... Making pagetable.o ... Making pagetable-arch.o ... Making kmem_space.o ... Making boot_uart_init.o ... Making irq_chip_generic.o ... Making bootstrap.o ... Making bootstrap-arm-omap3.o ... Making kern_lib_page.o ... Making jdb_extensions.o ... Making outer_cache.o ... Making utcb_support.o ... Making utcb_support-arm.o ... Making u_semaphore.o ... Making uart_console.o ... Making jdb_tbuf.o ... Making jdb_tbuf_init.o ... Making tb_entry.o ... Making tb_entry-arm.o ... Making jdb_trace.o ... Making dump_tcboffsets ... Making tcboffset.o ==> Linking tcboffset.bin ./dump_tcboffsets tcboffset.bin > tcboffset.h.new mv tcboffset.h.new tcboffset.h ... Making ivt.o ... Making jdb_handler_queue.o ... Making jdb_module.o ... Making jdb_pic.o ... Making jdb.o ... Making jdb-arm.o ... Making jdb-ansi.o ... Making jdb-thread.o ... Making jdb_core.o ... Making jdb_prompt_ext.o ... Making jdb_list.o ... Making jdb_prompt_module.o ... Making jdb_exit_module.o ... Making jdb_kern_info.o ... Making jdb_kern_info-arm.o ... Making jdb_kern_info-bench.o ... Making jdb_kern_info-bench-arm.o ... Making jdb_kern_info-cpu-arm.o /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/jdb/arm/jdb_kern_info-cpu-arm.cpp: In member function 'Mword Jdb_kern_info_cpu::mrc(Mword)': /Users/gsalagnac/prog/L4/fiasco/src/kernel/fiasco/src/jdb/arm/jdb_kern_info-cpu-arm.cpp:36:13: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ... Making jdb_tcb.o ... Making jdb_tcb-arm.o ... Making jdb_screen.o ... Making jdb_thread_list.o ... Making jdb_input.o ... Making jdb_symbol.o ... Making jdb_lines.o ... Making push_console.o ... Making jdb_timeout.o ... Making jdb_dump.o ... Making jdb_ptab.o ... Making jdb_ptab-ia32-ux-arm.o ... Making jdb_ptab-arm.o ... Making jdb_attach_irq.o ... Making jdb_table.o ... Making jdb_kern_info_kmem_alloc.o ... Making jdb_kern_info_kip.o ... Making jdb_mapdb.o ... Making kern_cnt.o ... Making jdb_trace_set.o ... Making jdb_trace_set-arm.o ... Making jdb_entry_frame-arm.o ... Making jdb_kobject.o ... Making jdb_kobject_names.o ... Making jdb_util.o ... Making jdb_space.o ... Making jdb_utcb.o ... Making jdb_trap_state.o ... Making jdb_ipi.o ... Making jdb_rcupdate.o ... Making jdb_ipc_gate.o ... Making jdb_obj_space.o ... Making jdb_log.o ... Making jdb_factory.o ... Making jdb_semaphore.o ... Making jdb_thread.o ... Making jdb_scheduler.o ... Making jdb_sender_list.o ... Making jdb_perf.o ... Making jdb_vm.o ... Making jdb_regex.o ... Making jdb_disasm.o ... Making jdb_bp.o ... Making jdb_tbuf_output.o ... Making jdb_tbuf_show.o ... Making tb_entry_output.o ==> Archiving into jdb_compound.o ... Making std_macros.o ... Making atomic.o ... Making atomic-arm-up.o ... Making lock_guard.o ... Making auto_ptr.o ... Making dlist.o ==> Archiving into libk.a ... Making sa1100.o ... Making mux_console.o ... Making console.o ... Making uart.o ... Making uart-arm-omap3.o ... Making filter_console.o ... Making h3xxx.o ... Making io.o ... Making io-arm.o ... Making mem.o ... Making mem-arm.o ... Making mmu.o ... Making mmu-arm.o ... Making reset-arm-omap3.o ... Making processor.o ... Making processor-arm.o ... Making delayloop.o ==> Archiving into libdrivers.a ... Making uart_omap35x.o ==> Archiving into libuart.a ... Making paranoia.o ... Making s_cruft.o ==> Archiving into libcxx.a ... Making atexit.o ... Making memccpy.o ... Making memcmp.o ... Making memmove.o ... Making memset.o ... Making memcpy.o ... Making memchr.o ... Making panic.o ... Making strchr.o ... Making strcmp.o ... Making strcpy.o ... Making strlen.o ... Making strncmp.o ... Making strncpy.o ... Making strstr.o ... Making __assert_fail.o ... Making printf.o ... Making __v_printf.o ... Making vprintf.o ... Making strtol.o ... Making strtoul.o ... Making __lltostr.o ... Making __ltostr.o ... Making putchar.o ... Making puts.o ... Making getchar.o ... Making gets.o ... Making construction.o ... Making sprintf.o ... Making snprintf.o ... Making vsnprintf.o ... Making vsprintf.o ... Making longjmp.o ... Making isalnum.o ... Making isalpha.o ... Making isascii.o ... Making isblank.o ... Making iscntrl.o ... Making isdigit.o ... Making isgraph.o ... Making islower.o ... Making isprint.o ... Making ispunct.o ... Making isspace.o ... Making isupper.o ... Making isxdigit.o ... Making strspn.o ... Making strcspn.o ... Making tolower.o ... Making raise.o ... Making aeabi.o ... Making setjmp.o ==> Archiving into libc.a ... Making glue_libc.o ==> Archiving into libgluedriverslibc.a ==> Linking fiasco.image ==> Linking fiasco chmod 755 fiasco arm-linux-nm fiasco.image | c++filt | sort > Symbols.new mv Symbols.new Symbols chmod 755 Symbols ... Making jdb_ktrace.o ==> Archiving into libjabi.a --> Build-Nr: 1 =============== Building all L4Re configurations ============ ============ Building in obj/l4/arm-beagleboard ========= make[5]: Nothing to be done for `all'. ... Compiling /Users/gsalagnac/prog/L4/fiasco/obj/l4/arm-beagleboard/tool/elf-patcher/elf-patcher Makefile:97: /Users/gsalagnac/prog/L4/fiasco/obj/l4/arm-beagleboard/pkg/.Package.deps: No such file or directory make[4]: Circular ldscripts <- ldscripts dependency dropped. === Building package "ldscripts" === ... Building /Users/gsalagnac/prog/L4/fiasco/obj/l4/arm-beagleboard/pkg/ldscripts/.general.d ... Building .general.d ... Building Makefile.inc ... Generating main_stat.ld ==> Installing main_stat.ld to local build-tree ... Generating main_rel.ld ==> Installing main_rel.ld to local build-tree ... Generating main_dyn.ld ==> Installing main_dyn.ld to local build-tree ... Compiling crti.o ==> Installing crti.o to local build-tree ... Compiling crtn.o ==> Installing crtn.o to local build-tree ... Compiling crt1.o ==> Installing crt1.o to local build-tree ... Compiling crti.s.o ==> Installing crti.s.o to local build-tree ... Compiling crtn.s.o ==> Installing crtn.s.o to local build-tree ... Compiling crt1.s.o ==> Installing crt1.s.o to local build-tree === Building package "l4sys" === ... Building /Users/gsalagnac/prog/L4/fiasco/obj/l4/arm-beagleboard/pkg/l4sys/include/.general.d ... Updating symlinks ... Building /Users/gsalagnac/prog/L4/fiasco/obj/l4/arm-beagleboard/pkg/l4sys/lib/src/.general.d ... Building .general.d ... Building Makefile.inc ... Compiling utcb.o ... Compiling errtostr.o ... Compiling ARCH-arm/atomic_ops_s.o ==> Archiving into libl4sys.a ==> "libl4sys.a" built make[8]: *** No rule to make target `/opt/armgcc/lib/gcc/arm-none-eabi/4.5.2//crtendS.o', needed by `libl4sys.so'. Stop. make[7]: *** [/Users/gsalagnac/prog/L4/fiasco/obj/l4/arm-beagleboard/pkg/l4sys/lib/src/OBJ-arm_armv6-l4f] Error 2 make[6]: *** [src] Error 2 make[5]: *** [lib] Error 2 make[4]: *** [l4sys] Error 2 make[3]: *** [pkg] Error 2 make[2]: *** [x] Error 2 Error building the L4Re 'obj/l4/arm-beagleboard' variant. Press RETURN to continue with other variants.

2 1

CFP: SSV 2011 - Workshop on Systems Software Verification [deadline extended]
by Hendrik Tews 17 May '11

17 May '11

[The deadline for abstract submissions has just been extended to May 29th. My apologies if you receive multiple copies of this CfP -- Hendrik Tews] ============================================================================= 6th International Workshop on Systems Software Verification (SSV 2011) Real Software, Real Problems, Real Solutions August 26-27 2011, Nijmegen, The Netherlands https://es.fbk.eu/events/ssv2011 Industrial-strength software analysis and verification has advanced in recent years through the introduction of model checking, automated and interactive theorem proving, and static analysis techniques as well as correctness by design, correctness by contract, and model-driven development. However, many techniques are working under restrictive assumptions which are invalidated by complex (embedded) system software such as operating system kernels, low-level device drivers or microcontroller code. The aim of this workshop is to bring together researchers and developers from both academia and industry, who are facing real software and real problems to find real, applicable solutions. By "real" we mean problems such as time-to-market or reliability that the industry is facing and is trying to fix in software that is deployed in the market place. A real solution is one that is applicable to the problem in industry and not one that only applies to an abstract, academic toy version of it. This forum will discuss software analysis/development techniques and tools; it will also serve as a platform to discuss open problems and future challenges in dealing with existing and upcoming systems level code. Topics include (but are not limited to): * model checking * automated and interactive theorem proving * static analysis * model-driven development * embedded systems development * automated testing * programming languages * verifying compilers * software certification * software tools * experience reports Submissions must be made electronically through the EasyChair system [1] until May 29 2011, 23:59h Samoan time. Papers should be up to 15 pages in pdf format and formatted in LNCS style [2]. Additional details may be included in a clearly marked appendix, which will be read at the discretion of the program committee. All will be subject to peer review under normal conference standards. Experience reports and papers on work in progress are welcome as long as there is a clear contribution. Submissions which are based or discuss a non-trivial piece of software are required to make all those non-standard software parts available, which a referee may need, in order to check the claims of the submission. Submitted papers must not have previously appeared in a journal or conference with published proceedings and must not be concurrently submitted to any other peer-reviewed workshop, symposium, conference or archival journal. Any partial overlap with any such published or concurrently submitted paper must be clearly indicated. The workshop proceedings are planned to be published in the form of post-proceedings in the Springer series Lecture Notes in Computer Science (LNCS). Important dates May 29 2011 Abstract Registration Deadline June 03 2011 Paper submission deadline June 30 2011 Notification of accepted papers July 15 2011 Final version August 26-27 2011 Workshop The workshop is organized as a two-day workshop (August 26-27 2011). Location The workshop will be held in Nijmegen, The Netherlands in conjunction with the 2nd International Conference on Interactive Theorem Proving (ITP 2011). Program Chair Jörg Brauer (RWTH Aachen University, Germany) Marco Roveri (FBK-irst, Italy) Hendrik Tews (TU Dresden, Germany) Steering Committee Ralf Huuck (NICTA, Australia) Gerwin Klein (NICTA, Australia) Bastian Schlich (ABB Corporate Research, Germany) Program Committee Dirk Beyer (University of Passau, Germany) Jörg Brauer (RWTH Aachen University, Germany) Adam Chlipala (Harvard, USA) Ansgar Fehnker (NICTA, Australia) Alexey Gotsman (IMDEA, Spain) Chris Hawblitzel (Microsoft Research, USA) Andy King (University of Kent, UK) Stefan Kowalewski (RWTH Aachen University, Germany) Thomas Kropf (Bosch, Germany) Kim G. Larsen (Aalborg University, Denmark) Wolfgang Reif (University of Augsburg, Germany) Marco Roveri (FBK-irst, Italy) Axel Simon (TU Munich, Germany) Nishant Sinha (NEC Labs, USA) Hendrik Tews (TU Dresden, Germany) Michael Whalen (UMSEC -- University of Minnesota, USA) Kwangkeun Yi (Seoul National University, Korea) Invited Speakers Following a tradition established over the past iterations of SSV, this years workshop will feature at least two keynote talks. The invited speakers will be announced soon. [1] http://www.easychair.org/conferences/?conf=ssv2011 [2] http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0

1 0

L4 on ARM: cache coherency and virtual address space
by Michal Schulz 11 May '11

11 May '11

Hello, I am implementing an USB stack for ARM machine maintained by the L4 microkernel. It works quite well at the moment - USB hubs and HID devices are working properly. However, there are few open issues there: 1. Since ARM machine I use does not provide cache snooping, i.e. I have to flush/invalidate the caches manually, I've attempted to use the l4_cache_dma_coherent function. It did worked to some degree, but it flushed/invalidated only *some* lines of cache within requested region, instead of *all* lines of cache. Since I've failed to trace the bug, I've extended sigma0 with new functionality - ability to map uncached memory. I still don't like my hack though and I would like to find an official way to either change the attributes (from cached to uncached) of given page, or have fully working l4_cache_dma_coherent. 2. The USB stack is a multithreaded app where I would like to have different servers (e.g. server for HID input events, server for mass storage devices). Unfortunately a server seemed to work only when started from the main thread. Why is it so? Was that my fault? 3. When the mass storage server receives either read or write call, it needs to map caller's memory in uncached manner. Moreover, USB stack needs *physical* address of the caller's buffer. How can I find that out? with best regards, Michal. -- Michal Schulz

2 3

Rename compund to compound
by Christian Ehrhardt 04 May '11

04 May '11

Hi, in the past weeks I've been reading through the fiasco kernel code. This is the start of a series of patches that clean up stuff or fix bugs that I think I found. Comments appreciated. The first patch renames a method called compund to compound, more important patches follow :-) regards Christian diff --git a/src/kernel/fiasco/src/abi/l4_msg_item.cpp b/src/kernel/fiasco/src/abi/l4_msg_item.cpp index bbb92ef..1155a5f 100644 --- a/src/kernel/fiasco/src/abi/l4_msg_item.cpp +++ b/src/kernel/fiasco/src/abi/l4_msg_item.cpp @@ -16,7 +16,7 @@ public: }; explicit L4_msg_item(Mword raw) : _raw(raw) {} - Mword compund() const { return _raw & 1; } + Mword compound() const { return _raw & 1; } Type type() const { return Type(_raw & 8); } bool is_void() const { return _raw == 0; } bool is_small_obj() const { return _raw & 2; } diff --git a/src/kernel/fiasco/src/kern/thread-ipc.cpp b/src/kernel/fiasco/src/kern/thread-ipc.cpp index f8e1995..3288b2a 100644 --- a/src/kernel/fiasco/src/kern/thread-ipc.cpp +++ b/src/kernel/fiasco/src/kern/thread-ipc.cpp @@ -948,7 +948,7 @@ Thread::transfer_msg_items(L4_msg_tag const &tag, Thread* snd, Utcb *snd_utcb, --items; - if (!item->b.compund()) + if (!item->b.compound()) buf_iter->next(); }

2 9

I have a problem when I built the L4Re environment
by 王彬彬 04 May '11

04 May '11

> ==> Installing crti.o to local build-tree > ... Compiling crtn.o > initfini.c: Assembler messages: > initfini.c:29: Error: .size expression for _init does not evaluate to a > constant > initfini.c:29: Error: .size expression for _fini does not evaluate to a > constant > make[3]: *** [crtn.o] Error 1 > make[3]: Leaving directory > `/home/wegrzyn/Fiasco/L4re-build/pkg/ldscripts/OBJ-x86_core2' > make[2]: *** > [/home/wegrzyn/Fiasco/L4re-build/pkg/ldscripts/OBJ-x86_core2] Error 2 > make[2]: Leaving directory `/home/wegrzyn/Fiasco/src/l4/pkg/ldscripts' > make[1]: *** [ldscripts] Error 2 > make[1]: Leaving directory `/home/wegrzyn/Fiasco/src/l4/pkg' > make: *** [pkg] Error 2 Can anyone venture a guess what I need to correct? TYXL HFUT,China

2 1

64 bit support in L4Linux
by Stefan Kalkowski 03 May '11

03 May '11

Hi, I've a short question related to L4Linux for 'x86_64'. When looking at the L4-specific architecture-files, I got the impression that the 64-bit support from the x86 port got retained. But my attempts to enable 64-bit in L4Linux failed. (Setting environment variables, tweaking configuration, hacking Kconfig a bit...) Does that mean 64-bit isn't supported by now, or if it is, what is the recommended way to enable it? Any advice on approach is welcome. Thanks, Stefan

2 2

how i can determine utcb loaction in order to make thread
by Jason Philip 01 May '11

01 May '11

I am very puzzled, I can't seem to find utcb location in L4Ka::pistachio. One example do this: L4_ThreadId_t mylocalid = L4_MyLocalId (); utcb_base = *(L4_Word_t *) &mylocalid; utcb_base &= ~(L4_UtcbAreaSize (kip) - 1); where the current thread is initial thread (main), but i try this it do not work. Can someone suggest proper way to determine the utcb location so that I can create a new thread? Please

3 13

Ethernet on Beagleboard xM with Ankh+L4Linux ?
by Julien Heyman 23 Apr '11

23 Apr '11

Hello, I am trying to understand what it would take to have access to (physical) ethernet from L4Linux running on a Beagleboard xM. As far as I understood/read, I can either try to integrate the native ethernet driver in L4Linux, or rely on Ankh networking server. Since I am running two instances of L4Linux, I'd rather use the Ankh solution. >From what I see Ankh does not currently include an appropriate driver for the BB xM's ethernet chip. Is it doable to pick an existing ethernet driver for the BB xM from, say, the Angström linux distribution for Beagleboard, and integrate it to Ankh ? Assuming this is possible, do I understand correctly that I would then only have to enable the Ankh driver option in the L4Linux configuration, to get an ethernet access in L4Linux ? Regards, Julien

2 2

Assertion failed: 'prev_next' [ret=0xf000e9c8] (arm qemu realview pbx system)
by Siegfried Podesser 19 Apr '11

19 Apr '11

hello together, If I try to run the L4Linux or the hello example via a patched QEMU (with trustzone support) I get the following error message: ------------ ./qemu-system-arm -M vexpress-a9 -kernel /home/beresford/Work-Repositories/sepia/desastro/l4/build/images/bootstrap_hello.elf -initrd /home/beresford/Downloads/ramdisk-arm.rd -append "console=ttyAMA0 console=tty0 dhcp=on" -m 1024 -s -gdb tcp::5022 erster teilerfolg: Fiasco + L4 hüpfen zumindest mal an... ./qemu-system-arm -M vexpress-a9 -kernel /home/beresford/Work-Repositories/sepia/desastro/l4/build/images/bootstrap_L4linux_ARM.elf -initrd /home/beresford/Downloads/ramdisk-arm.rd -append "console=ttyAMA0 console=tty0 dhcp=off" -m 512 -smp 1 -gdb tcp::1234 -serial stdio bp147: attached 100e6000..100e6fff to TZDECPROT0[6] bp147: attached 100e4000..100e4fff to TZDECPROT0[4] L4 Bootstrapper Build: #3 Tue Apr 19 09:46:31 CEST 2011, 4.5.1 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod09: 01500000-01800000: ramdisk-arm.rd mod08: 0124e000-014ff488: vmlinuz.arm mod07: 0124d000-0124d0bd: arm-rv.io mod06: 01162000-0124c7d4: io mod05: 01161000-01161189: l4lx.cfg mod04: 01105000-011601ac: ned mod03: 010e3000-01104488: l4re mod02: 010a5000-010e266c: moe mod01: 01093000-010a4304: sigma0 mod00: 01015000-01092a2c: fiasco Moving 10 modules to 1100000 with offset eb000 moving module 10 { 1500000-1800000 } -> { 15eb000-18eb000 } moving module 09 { 124e000-14ff488 } -> { 1339000-15ea488 } moving module 08 { 124d000-124d0bd } -> { 1338000-13380bd } moving module 07 { 1162000-124c7d4 } -> { 124d000-13377d4 } moving module 06 { 1161000-1161189 } -> { 124c000-124c189 } moving module 05 { 1105000-11601ac } -> { 11f0000-124b1ac } moving module 04 { 10e3000-1104488 } -> { 11ce000-11ef488 } moving module 03 { 10a5000-10e266c } -> { 1190000-11cd66c } moving module 02 { 1093000-10a4304 } -> { 117e000-118f304 } moving module 01 { 1015000-1092a2c } -> { 1100000-117da2c } Scanning fiasco Scanning sigma0 Scanning moe rom/l4lx.cfg Relocated mbi to [0x100f000-0x100f151] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 19ff] { a00} Kern fiasco [ 2000, 8cfff] { 8b000} Kern fiasco [ 90000, 9e193] { e194} Sigma0 sigma0 [ 140000, 18b48b] { 4b48c} Root moe [ 1000000, 10143eb] { 143ec} Boot bootstrap [ 100f000, 100f24e] { 24f} Root Multiboot info [ 11ce000, 18eafff] { 71d000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:00090000 sp:01013044 Roottask config ip:00140088 sp:00000000 Starting kernel fiasco at 00001000 Realview System ID: Rev=1 HBI=190 Build=f Arch=5 FPGA=00 L2: ID=00000000 Type=00000000 L2 cache enabled Hello from Startup::stage2 Assertion failed: 'prev_next' [ret=0xf000e9c8] /home/beresford/Work-Repositories/sepia/desastro/kernel/fiasco/src/kern/buddy_alloc.cpp:23 at f000e834 --------------------------------- If I remove the assertion check it executes a little bit more and I get the following error: --------------------------------- ... Starting kernel fiasco at 00001000 Realview System ID: Rev=1 HBI=190 Build=f Arch=5 FPGA=00 L2: ID=00000000 Type=00000000 L2 cache enabled Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf007a628-0xf007b030) Initialize page table Number of IRQs available at this GIC: 32 Number of IRQs available at this GIC: 32 Vmem_alloc::init() Cache config: ON ID_PFR0: 00001031 ID_PFR1: 00000011 ID_DFR0: 00000000 ID_AFR0: 00000000 ID_MMFR0: 00100103 ID_MMFR1: 20000000 ID_MMFR2: 01230000 ID_MMFR3: 00002111 Panic: UTCB pointer page allocation failure Press any key to reboot. ---------------------------------- Through the mailing list i found your posting from Thu, 25 Sep 2008 10:57:29 where you have suggested to check the RAM_SIZE_MB in the l4 config file. I've checked it and it is set to 256MB as my qemu is set as well. I tried it further with 512MB and 1GB but it changes nothing. Do you have any further ideas ? kind regards, siegfried

2 1

L4Linux (arm) - change CPU speed
by Siegfried Podesser 12 Apr '11

12 Apr '11

Hello, is there a way or an example source code to change the CPU speed? I'm using the original Fiasco kernal together with the given L4Linux for arm platforms. Thank you for your help! kind regards, siegfried

2 1

How to add more NIC drivers for ankh?
by Alexey Aizatullin 10 Apr '11

10 Apr '11

Hello, Could you please explain what steps should I do to add drivers for other ethernet adapters for ankh? -- --------------------------------------- Alexey Aizatullin

2 1

Increase L4linux ramdisk size ?
by Julien Heyman 07 Apr '11

07 Apr '11

Hello, I am using Fiasco.OC/L4Re/L4Linux on a Beagleboard. After having successfully used/customized the L4Linux ramdisk provided as part of the snapshot, I created a larger ramdisk (8Mb instead of ~3Mb) from scratch and adjusted the "ramdisk_size" option on the linux boot args line in my LUA script, and rebuilt my u-boot image. I then get plenty of errors during linux boot, starting with: RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 8000KiB [1 disk] into ram disk... l4linux1| Non-resolvable page fault at e0d1619, ip 170384. l4linux1| Page fault (non-resolved): pfa=e0d1619 pc=170384 l4linux1| Non-resolvable page fault at e0d161a, ip 170384. Internal error: Boom!: 410005 [#1] etc... My questions: - is there a specific way to create a ramdisk file for l4linux, and/or specific constraints on the ramdisk size ? - am I missing other configuration parameters than ramdisk_size that should be adjusted to reflect the larger ramdisk size ? Thanks, Julien

3 5

How to block an API call without blocking server message loop?
by Valery V. Sedletski 05 Apr '11

05 Apr '11

Hi all. When an L4 server is started, its main thread goes into the server loop and blocks until a message from a client is received. When a message is received, a server loop calls a dispatch function, which calls functions, specific to RPC opcodes. The problem is that if one of these functions is blocked, the whole server loop is blocked. In my case, I am implementing an API, which is called by a client program. This API starts a child process, and has an option to block the calling program, until the child is terminated. This API is called DosExecPgm(). So, the client program calls this API, then the API call blocks, and then the child must be executed, and finally, call another API, which is called DosExit(). But when DosExecPgm is called, the server loop is blocked, and it cannot receive a message for calling the next API, DosExit. I tried to implement API call blocking using a semaphore. DosExecPgm from a parent process is waiting on the semaphore, and DosExit from a child process reset the semaphore. So, the problem is with server loop blocking. So, I thought to make for DosExecPgm a dedicated server loop. which is blocked, but the main server loop continues to execute. But how to correctly make these server loops? There are many API's which can block, so, what can I do if not to dedicate a separate loop for each function? And, if there are many server loops, then there will be many threads executing them, so I must to register each thread on the name server. -- Then how can the calling program determine, which server thread to call for each API? I feel that these problems have common solutions, but i'm in trouble -- maybe, someone will help with finding these common solutions? Thanks in advance, WBR, valery

2 5

Build errors in building L4re for ARM
by Rahul Ramasubramanian 04 Apr '11

04 Apr '11

Hi I was trying to build l4re and ran into rather strange compilation errors. The code where the error is trowing up is in ../src/l4/pkg/bootstrap/server/src/startup.cc The relevant part of the error log looks like make[5]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/l4rebuild/pkg/libvbus/lib/src/OBJ-arm_armv6zk-l4f' ==> "libcxx_libc_io_e.a" built ==> Installing libcxx_libc_io.a to local build-tree ==> Installing libcxx_libc_io_e.a to local build-tree make[5]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/l4rebuild/pkg/cxx_libc_io/lib/src/OBJ-arm_armv6zk-l4f' make[4]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/cxx_libc_io/lib/src' make[3]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/cxx_libc_io/lib' make[2]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/cxx_libc_io' ... Compiling ios_failure.o make[5]: Entering directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/l4rebuild/pkg/libvbus/lib/src/OBJ-arm_armv6zk-l4f' ... Compiling vbus.o ... Compiling module.o ... Compiling ARCH-arm/crt0.o ... Compiling vbus_pci.o ... Compiling region.o ... Compiling ios_init.o ... Compiling vbus_gpio.o === Building package "libkproxy" === ... Compiling startup.o make[2]: Entering directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/libkproxy' arm-none-linux-gnueabi-g++: Mar: No such file or directory arm-none-linux-gnueabi-g++: 31: No such file or directory arm-none-linux-gnueabi-g++: 18:28:52: No such file or directory arm-none-linux-gnueabi-g++: EDT: No such file or directory arm-none-linux-gnueabi-g++: 2011": No such file or directory <command-line>: warning: missing terminating " character /home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/bootstrap/server/src/startup.cc:1054: error: missing terminating " character ... Compiling vbus_i2c.o make[5]: *** [startup.o] Error 1 make[5]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/l4rebuild/pkg/bootstrap/server/src/OBJ-arm_armv6zk' make[4]: *** [/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/l4rebuild/pkg/bootstrap/server/src/OBJ-arm_armv6zk] Error 2 make[4]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/bootstrap/server/src' make[3]: *** [src] Error 2 make[3]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/bootstrap/server' make[2]: *** [server] Error 2 make[2]: Leaving directory `/home/rahul/newbuild_17_3_11/x86droid/l4Build/src/l4/pkg/bootstrap' make[1]: *** [bootstrap] Error 2 make[1]: *** Waiting for unfinished jobs.... ... Compiling ios-inst.o The toolcahin I am using is arm-linux-gcc-4.3.2.tgz, which I downloaded from some embedded system user group (www.friendlyarm.net) I think that this maybe has something to the toolchain. Can anyone point out why this error is and what i should do to fix this error . Thanks and Regards Rahul Ramasubramanian

2 3

Question about Mapping DB Recursion Depth on Fiasco.OC
by Christoph Szeppek 24 Mar '11

24 Mar '11

Hello, as far as I understand, the mapping database consists of a treemap with an entry for each superpage. Each entry points to an array describing the page's mappings (mapping tree). Each element of this mapping tree either represents a mapping or stores the address of a treemap, if the superpage has been splitted into pieces with a size of the next smaller valid page size. Is it correct that an element of a mapping tree references another treemap only in case the page has been spllitted and therefor the maximum recursion depth is limited by the amount of valid page sizes? Christoph

3 2

Customizing L4Linux, on ARM/Beagleboard
by Julien Heyman 24 Mar '11

24 Mar '11

Hello everyone, I would appreciate getting some advice as to the proper way to customize and rebuild an L4Linux kernel. I am testing Fiasco.OC/L4Re/L4Linux on a Beagleboard (ARM), I installed everything from the latest snapshot package, full build is fine, and launching the provided L4Linux "arm-up" kernel on my Beagleboard is ok. Now, to customize the configuration of the L4Linux kernel, I did "*make O=../../obj/l4linux/arm-up menuconfig*" from *\src\l4linux* directory, adjusted a few options, saved & exited, so far so good. Then I try to rebuild the L4Linux kernel using "*make O=../../obj/l4linux/arm-up*", and I get: *"<path...>/src/l4linux is not clean, please run 'make mrproper' in the '<path...>/src/l4linux' directory."* So I do just that, * <path..>/src/l4linux$ make O=../../obj/l4linux/arm-up mrproper* but : - it ends with an error *"rm: cannot remove `arch/l4/include/asm/orig-arch': Is a directory"* - as expected, it wipes out a lot of things in the target build directory, including... the *.config* corresponding to my customized kernel....back to square one. I must be missing something trivial, so if someone could point it out to me... ;) Regards, Julien

3 4

Help on write first client-server on Fiasco
by Wenhao Xu 23 Mar '11

23 Mar '11

Hi guys, I am new to both microkernel and fiasco. All I read were some microkenel paper in the operating system course. After reading introduction to FIasco, I am very insterested in it. I have just compiled and run the hello demo in the Fiasco web page. Now I cannot wait to write my own client-server. I have never written an operating system before. Can you help me or give me some guide on how to write my first client-server in Fiasco? And are there window manager implementation or file system implementation for Fiasco? If not, I am also very interested in write one for Fiasco. Thanks very much for the help. Regards, Wenhao -- ~_~

2 1

Fiasco.OC on amd64 Opteron 6000
by Daniel Waddington 16 Mar '11

16 Mar '11

Hi, I'm trying to run Fiasco.OC amd64 build on an Opteron 6100 magny-cours series (4-way-SMP, 12-cores-per-chip). When it boots it is as if the scheduling interrupt on the local APIC is not getting set up correctly. It also warns about some errata. It does boot with MP disabled, and RTC for the scheduling - not much use on a 48-core machine though ;-) Any clues??? Thanks, Daniel --- Per_cpu_data_alloc: (orig: 0xfffffffff0080840-0xfffffffff0081498) Allocate 3160 bytes (3KB) for CPU[43] local storage (offset=fc887c0) OSVW_MSR1 = 0x000000000000000c #Errata known 4, affected by at least one Allocate cpu_mem @ 0xffffffffffd0b000 Local APIC[19]: version=10 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) for scheduling CPU[43:25]: AuthenticAMD (10:9:1:0)[00100f91] Model: Unknown CPU at 2200 MHz 32/512 Entry I TLB (4K pages) 16 Entry I TLB (4M pages) 48/512 Entry D TLB (4K pages) 48/128 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) 512 KB L2 U Cache (8-way associative, 64 bytes per line) 10240 KB L3 U Cache (13-way associative, 64 bytes per line) CPU[43]: goes to idle loop

3 2

L4Re + Bytecode Translation
by Michael Brooks 16 Mar '11

16 Mar '11

I think it would be very interesting if the L4 Runtime Environment adopted a bytecode translator like the one implemented in Parrot VM<http://parrot.org/> or Nested VM <http://nestedvm.ibex.org/>. This feature would mean that L4 could support MANY LANGUAGES <http://trac.parrot.org/parrot/wiki/Languages> natively. So L4 would not only the ability to boot up a wide selection of operating systems, but also support for a wide selection of runtime environments. --Michael Brooks

1 0

L4Linux - Freescale i.MX51 Bebbage Board - vmlinuz.arm wanted
by Siegfried Podesser 15 Mar '11

15 Mar '11

Hello everyone, I'm just trying since nearly a week to compile L4Linux. But neither the SVN-copy nor the snapshot (l4re-snapshot-2011022209) compiles at all. Before I will explain what I've already tried, my main question, can someone here send me a correct build vmlinuz.arm file ? What have I already tried: _'_'_'_'_'_L4 Linux from SVN _'_'_'_'_'_'_'_' 1. checked it out :) -> svn co http://svn.tudos.org/repos/oc/l4linux/trunk l4linux 2. kernel configuration and building -> make ARCH=arm mx51_defconfig O=build (or make ARCH=l4 mx51_defconfig O=build with recopying mx51_defconfig) -> make ARCH=arm all CROSS_COMPILE=arm-none-linux-gnueabi- O=build produces in any case a missing .config.all error where I have no idea how to produce/get it -->... make[3]: *** No rule to make target `/.config.all', needed by `/home/beresford/Work-Repositories/sepia/l4linux/build/Makeconf.l4conf'. Stop. make[2]: *** [/home/beresford/Work-Repositories/sepia/l4linux/build/Makeconf.l4conf] Error 2 GEN /home/beresford/Work-Repositories/sepia/l4linux/build/Makefile scripts/kconfig/conf --silentoldconfig Kconfig make[2]: *** No rule to make target `/.config.all', needed by `/home/beresford/Work-Repositories/sepia/l4linux/build/Makeconf.l4conf'. Stop. make[1]: *** [check_linux_config] Error 1 make: *** [sub-make] Error 2 _'_'_'_'_'_L4 Linux from snapshot file _'_'_'_'_'_'_'_' or with the snapshot in general (means for the existing realview platform and not for the mx51, just to see if it builds at least) 1. checked it out -> wget http://os.inf.tu-dresden.de/download/snapshots-oc/l4re-snapshot-2011022209.… 2. -> wget http://os.inf.tu-dresden.de/download/ramdisk-arm.rd für die ramdisk.arm 3. then unzipped 4. then I've tried it exactly as Wesley Miaw posted on Jan 4.1.11 with GCC_PATH_PREFIX=/opt/sourcery-g++-lite/bin/arm-none-linux-gnueabi- L4ARCH=arm make setup -> selected ARM realview make cd obj/l4linux/arm-up make arm_defconfig make menuconfig -> set L4 build path obj/l4/arm-rv -> set cross compile prefix arm-none-linux-gnueabi- -> turned on ARM EABI + old EABI binaries options make the last step does not build at all: ... /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/include/linux/math64.h:51:15: note: each undeclared identifier is reported only once for each function it appears in In file included from /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/include/linux/mm_types.h:11:0, from /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/include/linux/sched.h:63, from /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/arch/l4/kernel/../../arm/kernel/asm-offsets.c:13, from /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/arch/l4/kernel/asm-offsets.c:5: /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/include/linux/rwsem.h: At top level: /home/beresford/Work-Repositories/sepia/l4re-snapshot-2011022209/src/l4linux/include/linux/rwsem.h:22:65: fatal error: asm/rwsem.h: No such file or directory compilation terminated. make[3]: *** [arch/l4/kernel/asm-offsets.s] Error 1 make[2]: *** [prepare0] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 Maybe someone has an idea. My development platform: Gentoo Linux 64bit, 2.6.37-rc1, GCC 4.5.2, arm-none-linux-gnueabi-... version (Sourcery G++ Lite 2010.09-50) 4.5.1 Thank you :) siegfried

3 4

IPC performance comparison of Fiasco.OC and Pistachio
by Jaeyeon Kang 11 Mar '11

11 Mar '11

Hello, I have a question about IPC performance of Fiasco.OC and Pistachio. When I compared the performance for a pingpong benchmark, Pistachio provides better performance than Fiasco.OC (about 1.5 times faster). Is there anyone who can explain the reasons that Fiasco.OC's IPC is slower compared to Pistachio? Thanks, Jaeyeon

2 1

Samsung R&D - Full-time OS Researcher Position
by Daniel Waddington 10 Mar '11

10 Mar '11

Samsung R&D, San Jose - CA, is recruiting full-time researchers in the area of Operating Systems (OS) for future cyber-physical systems. We are looking for individuals with a passion for systems research and the desire to follow through from concept to pre-transition prototype. Position: Full-time Researcher for the Systems Research Group Summary: The Systems Research Group is developing new OS and software platform designs that can meet the needs of future computing platforms based on multicore, manycore and cloud technologies. We are currently developing a solution based on L4 microkernel technology that will readily scale from sensors-to-servers, whilst providing advanced support for transparent distributed processing, Quality-of-Service (QoS) guarantees for co-located real-time and best-effort applications, and the "first-class" integration of parallel programming technologies. We are looking for highly motivated and creative individuals to join the San Jose research team and to augment existing system research expertise. This is an excellent opportunity to join a new team advancing state-of-the-art software technologies for Samsung's current and future business. Duties and Responsibilities: . Research and develop micro-kernel based solutions for next generation products. . Research and develop innovative technologies to directly address scalability limitations of existing solutions. . Research and develop ideas around the single-system image concept. . Research and develop new ideas in OS-level and language-level support for heterogeneous processor platforms. . Develop ideas around the support of fine-grained resource management and QoS monitoring, policing and adaptation in the context of real-time cyber-physical applications. . Build proof-of-concept prototypes. . Write research papers and technical articles publishing work and results in top-tier conferences and journals. Necessary Skills/Attributes: . Ph.D. in Computer Science or related area with 0-5 years of practical experience. . A track record in OS research pertaining to the above areas of interest with high-quality publications in the field. . Hands-on experience with low-level systems prototyping and development - a true hacker at heart. . Proficiency with C/C++ and Linux-based development including multi-threaded programming. . Excellent communication and team working skills are required with a willingness to work with an international team to deliver an integrated solution. . A willingness to learn new things and take on new challenges. Desirable Skills/Attributes: . Experience with L4 or other similar microkernel technology (e.g., QNX, Integrity) . Experience with embedded systems development. . Experience building OS sub-systems such as memory managers, and task schedulers. . Experience with the use of machine-learning to drive system optimization. . Experience with distributed and parallel computing. . Experience developing on TILE processors and programming with TILE assembly. . Experience developing on ARM processors and programming with ARM assembly. Contact: Please send resumes and enquiries to Dr. Daniel Waddington (d.waddington(a)samsung.com)

1 0

Re: Genode OS framework and kernel-specific features
by Valery V. Sedletski 09 Mar '11

09 Mar '11

On Sun, 06 Mar 2011 09:29:52 +1200 (MSK), Valery V. Sedletski wrote: > >PS: maybe, offtopic, but I'm in trouble a bit. > Already googled the Linux Framebuffer HOWTO and several articles. It seems that vesafb will not work for me (I have Matrox G400 card, on which I get a message "Cannot set vga mode, press Enter..." when booting Linux. Also, it supports VESA 2.0, but GRUB sees only modes not higher than 800x600). I also found some drivers in ./kernel/drivers/video/matrox, will check them.

3 6

Can L4 modules be accessed as files from L4Linux?
by Dan Haim 07 Mar '11

07 Mar '11

Hi, I'm trying to find a solution to the following scenario - I want to have an L4Linux instance running (from a CD) where the root filesystem is several hundred MB's big, so it is not feasible to run it from a ramdisk (the filesystem is larger than the amount of RAM available) - I need to run it directly from the CD. A possible solution I'm thinkning about is to give the L4Linux instance access to the CD-ROM drive, then store a SquashFS image as a file on the drive and UnionFS it with a tmpfs when the system starts. Now here's the catch - While this solution may technically work, it is still not 'good enough' because I can't give the L4Linux instance direct access to the CD-ROM drive - I need to have it completely isolated so a user working on the L4Linux instance will not have access to any files stored on the CD (other than the SquashFS image) even if he/she has root access over the L4Linux instance. I was thinking - is it possible to specify the SquashFS image as an L4 module and then somehow mount it from within L4Linux in-place (i.e. without completely loading it to RAM)? Is there any other way to accomplish what's needed in this scenario? Thank you all, Dan.

2 2

Genode OS framework and kernel-specific features
by Valery V. Sedletski 05 Mar '11

05 Mar '11

Hi all. I am now giving a try to the Genode OS framework. I like it's concepts and ideas and its elegant design, and maybe, will migrate to it eventually. -- I was developing an OS/2 clone based on Fiasco microkernel and l4env. Now they're discontinued. So, I must probably, migrate to something else. The most probable candidates are L4Re or Genode. I like Genode because of its kernel-neutrality (It can work on any L4 flavour, it is very attractive feature) and has interesting ideas regarding the scalability and capability to build a hierarchy of subsystems, minimising the application-specific Trusted Computing Bases. So, as I understood, it abstracts the kernel specifics from a developer. But in some cases, it can be desirable to make some kernel-specific implementations. For example, Fiasco kernel based on l4v2 API has 'segments' feature which, for example, is actively used by L4Linux. We use this feature too. One of our objectives is a binary compatibility with existing OS/2 applications. And OS/2 application ABI includes a convention that FS register for Ring3 application, holds a selector of a structure named Thread Info Block. Though the application can obtain this structure by calling an DosGetInfoBlocks() API, the C startup code generated by many compilers, relies on the convention that FS must contain the TIB selector. So, if we try to implement this feature on L4, we must have the means to allocate GDT selectors and get the allocated selector. On Fiasco, this can be done by filling the registers in a special way and issuing a 'LLDT' instruction, or, by calling a fiasco_gdt_set() function, and get the allocated selector by fiasco_gdt_get_entry_offset() (which is the same, but through a 'l4sys' package). On Fiasco.OC, this can be done similar way (not through LLDT instruction, though). My question is: Can be the underlying kernel determined under Genode, and then try doing kernel-specific things? Or, maybe, there is a more elegant way to do kernel-specific things? Thanks in advance, valery. PS: On Pistachio, as I heard, the application also can operate on GDT selectors, but this possibility has even more limitations. (It seems, only LDT selectors can be altered, but not GDT ones, or something)

2 2

Compiling l4re for BeagleBoard
by Ivan Bludov 04 Mar '11

04 Mar '11

Hello, I'm trying to compile l4re for ARM (beagleboard). I used the cross-toolchain for AMR (from CodeSourcery and toolchain downloaded from your site), but I got errors during making configuration of l4 : =========================================================== set -e; X="tmp.$$$RANDOM.c" ; echo 'int main(void){}'>$X ; \ rm -f $X.out ; LD_PRELOAD=libgendep.so LD_LIBRARY_PATH=/home/ibludov/Downloads/l4re-snapshot-2011022209.0/src/l4/build/tool/gendep/64: GENDEP_SOURCE=$X \ GENDEP_OUTPUT=$X.out arm-linux-gcc -c $X -o $X.o; \ test -e $X.out; echo INT_CPP_NAME=`cat $X.out` \ >>/home/ibludov/Downloads/l4re-snapshot-2011022209.0/src/l4/build/.config.all; \ rm -f $X $X.{o,out}; ERROR: ld.so: object 'libgendep.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libgendep.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libgendep.so' from LD_PRELOAD cannot be preloaded: ignored. ============================================================ These errors appear only when I use the arm-linux compiler and do not appear when I use host compiler. Is it a problem of toolchan or some other system libraries? Can you make some advise to fix it? Ivan Bludov

2 1

thread creation help
by Jason Philip 27 Feb '11

27 Feb '11

Can someone tell me how to create a thread (in the same address space as the creating thread)? This very confusing to me, I need help.

3 5

Announcement: Genode 11.02 with support for both NOVA v0.3 and Fiasco.OC
by Norman Feske 24 Feb '11

24 Feb '11

Dear L4 hackers, I am pleased to announce the release of the version 11.02 of the Genode OS Framework. Genode is an OS architecture that promises to align high security and robustness with dynamic application workloads. The Genode OS Framework as the reference implementation of this architecture. With the new version 11.02, we enabled the framework to be used with the Fiasco.OC kernel developed at TU Dresden in addition to the already supported base platforms L4/Fiasco, L4ka::Pistachio, Linux, OKL4v2, Codezero, and NOVA. Furthermore, we upgraded the NOVA support to version 0.3, which was published earlier this month. So now, both current kernel developments at TU Dresden are fully embraced by the framework. We are grateful for the excellent support we got from Alexander Warg and Udo Steinberg. Alongside the expanded platform support, the new release features many improvements, the most prominent being - Fiasco.OC as new base platform - Running Genode natively on MicroBlaze CPUs - Support for version 0.3 of the NOVA hypervisor - Noux execution environment for GNU userland software - Base framework - Core resource accounting using guarded allocators - Protocol enhancements for upgrading session quotas - Qt4 updated to version 4.7.1 - New tooling support for automated integration and testing Please find a more elaborative description of the changes accompanied with a lot of background information in the release notes of version 11.02: http://genode.org/documentation/release-notes/11.02 The new version is ready for download at our download page at Sourceforge and our public SVN repository: http://genode.org/download Best Regards -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

L4Re: C++ or DICE for IPC
by Valery V. Sedletski 24 Feb '11

24 Feb '11

Hi, all. I checked out a new L4Re userland and a new Fiasco.OC microkernel. I noticed that it seems, no IDL compiler is used for IPC anymore, but found that, like in l4\pkg\examples\clntsrv\ example, IPC is encapsulated in C++ classes. That's nice, C++ is a feature-rich object oriented language. But what can I do if I want to write a program on other languages, like plain C, Ada etc.? I think, such possibility must exist too, and IDL is a means of implementing such a language neutrality. Is DICE discontinued? And how can I do something with communication code if not using IDL? Thanks in advance, WBR, valery

4 6

Boot into video mode with grub2
by Dan Haim 23 Feb '11

23 Feb '11

Hi, I'm trying to boot L4Linux under MAG. I used to use the "vbeset 0x117" GRUB command to set the screen into the correct video mode but now I'm using GRUB2 and I can't find any equivalent command(s). Has anyone successfully booted MAG under GRUB2?

2 2

[L4 on realview Cortex A9] Failing on board check during fiasco bootup
by Naveen Chandrakar 23 Feb '11

23 Feb '11

Hello Guys, I was attempting to run fiasco built for CortexA9/realview-pbx board on qemu. "qemu-system-arm" version used for this experimentation is "QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5)" L4 Code used "l4re-core-2011020417" with hello world example. Below are the messages which i got when i tried to run fiasco on qemu - 1st set of logs I tried to comment the check inside Board_check::check_board() in the hope that it might boot up, but later i got crash for qemu (hw mismatch ?) - 2nd set of logs *1st set of logs* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L4 msgs specifying invalid sys id~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ novino@naveen-linux:~/L4/l4re-core-2011020417/src/l4/mybuild-realview-pbx-a9/images$ qemu-system-arm -M realview-pbx-a9 -cpu cortex-a9 -kernel bootstrap_hello.elf -m 256 -nographic -net nic -net user L4 Bootstrapper Build: #2 Thu Feb 10 18:21:42 MVT 2011, 4.5.1 Scanning up to 256 MB RAM ........some messages ..... Starting kernel fiasco at 00001000 Cache config: ON Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 Invalid System ID for this kernel config Expected (01780500 & ffffff00) == 1182f500 Stopping. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ end of msgs ~~~~~~~~~~~~~~~~~~~~~ *2nd Set of logs* ~~~~~~~~~~~~~~~~~~~ L4 msgs after modifying Board_check::check_board() ~~~~~~~~~~~~~~~~~~~~~~~~ novino@naveen-linux:~/L4/l4re-core-2011020417/src/l4/mybuild-realview-pbx-a9/images$ qemu-system-arm -M realview-pbx-a9 -cpu cortex-a9 -kernel bootstrap_hello.elf -m 256 -nographic -net nic -net user L4 Bootstrapper Build: #3 Thu Feb 10 19:06:41 MVT 2011, 4.5.1 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod04: 010d3000-010f4450: hello mod03: 010b1000-010d2488: l4re mod02: 01073000-010b066c: moe mod01: 01061000-01072304: sigma0 mod00: 01015000-010608f8: fiasco Moving 5 modules to 1100000 with offset eb000 moving module 05 { 10d3000-10f4450 } -> { 11be000-11df450 } moving module 04 { 10b1000-10d2488 } -> { 119c000-11bd488 } moving module 03 { 1073000-10b066c } -> { 115e000-119b66c } moving module 02 { 1061000-1072304 } -> { 114c000-115d304 } moving module 01 { 1015000-10608f8 } -> { 1100000-114b8f8 } Scanning fiasco Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x100f000-0x100f0d6] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 19ff] { a00} Kern fiasco [ 2000, 5cfff] { 5b000} Kern fiasco [ 90000, 9e193] { e194} Sigma0 sigma0 [ 140000, 18b48b] { 4b48c} Root moe [ 1000000, 10143eb] { 143ec} Boot bootstrap [ 100f000, 100f1d3] { 1d4} Root Multiboot info [ 119c000, 11df44f] { 43450} Root Modules Memory API Version: (87) experimental Sigma0 config ip:00090000 sp:01013044 Roottask config ip:00140088 sp:00000000 Starting kernel fiasco at 00001000 Cache config: ON Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 <<Commented>> Invalid System ID for this kernel config Expected (01780500 & ffffff00) == 1182f500 Stopping. Hello from Startup::stage2 Initialize page table Number of IRQs available at this GIC: 96 Number of IRQs available at this GIC: 32 Vmem_alloc::init() qemu: fatal: Unimplemented cp15 register write (c9, c14, {0, 0}) R00=00000000 R01=00000000 R02=80000000 R03=00000001 R04=f00487b0 R05=00054004 R06=00215406 R07=00115406 R08=00015406 R09=00002000 R10=00000000 R11=0100f058 R12=ffffffff R13=f0048670 R14=f005bd3c R15=f005bd28 PSR=a00001d3 N-C- A svc32 Aborted ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~end of msgs ~~~~~~~~~~~~~~~~~~~~~~~~ Warm Regards, Naveen

2 9

13th Real Time Linux Workshop - 1st Call for Papers
by Nicholas Mc Guire 23 Feb '11

23 Feb '11

Hi ! would be nice if we could get an update of the current L4 activities for at the next RTLWS - CfP bellow. thx! hofrat 13th Real-Time Linux Workshop October 20-22, 2011 Faculty of Electrical Engineering Czech Technical University in Prague Prague, Czech Republic Following the meetings of academics, developers and users of real-time and embedded Linux at the previous 12 real-time Linux workshops held world-wide (Vienna, Orlando, Milano, Boston, Valencia, Singapore, Lille, Lanzhou, Linz, Guadalajara, Dresden and Nairobi), the Real-Time Linux Workshop for 2011 will come to the Czech Technical University in Prague, Faculty of Electrical Engineering, Dept. of Control Engineering - academic OSADL member since 2008. The workshop will be held from October 20 to 22. Rationale Embedded and real-time Linux are gaining traction in consumer electronics and in industrial computing in breath-taking speed. Linux runs a wide range of industrial applications including real-time and safety-related systems. And the best is that everyone on earth has access to this unparalleled pool of Open Source software as long as he or she has access to the Internet. Nevertheless, this access is by no means one-way - the return paths are from providing bug reports, additions and ideas for enhancements and, finally, the very important mechanism of peer review that makes Linux, and particularly real-time Linux, as stable and innovative as it is. In addition to sending patches and providing feedback via Internet, direct mutual exchange between field engineers, system integrators, and project managers, and hardware, driver, board support package and kernel developers is needed. The Real Time Linux Workshop is successfully serving this purpose since more than 10 years. We are looking forward to meeting each other at another great Real Time Linux Workshop - this time in Prague, Czech Republic. Call for papers Authors from academics, industry as well as the user community are invited to submit papers on original work related to Open Source real-time systems. Such work may deal with general topics related to Open Source based real-time systems but also with research, experiments and case studies, as well as with issues of integration of Open Source real-time and embedded systems. A special focus will be on industrial case studies and safety-related systems. Topics of interest include, but are not limited to: - Modifications and variants of the GNU/Linux operating systems extending its 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 - Safety-related FLOSS systems - 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 - RT-safe interaction of RT and non RT components - IPC mechanisms in RTOS - Analysis and benchmarking methods and results of real-time GNU/Linux variants - Real-time networking with COTS - Medical applications using COTS and FLOSS - Debugging techniques and tools, both for code and temporal debugging of core RTOS components, drivers and real-time applications - Real-time related extensions to development environments Abstract submission If you wish to present a paper at the workshop, please submit an abstract using the submission page at https://www.osadl.org/RTLWS13-Abstract.submission-form.0.html. Final paper to be included into the RTLWS13 Proceedings Upon acceptance of an abstract by the RTLWS13 Program Committee, the author will be invited to submit a full paper in a form defined by https://www.osadl.org/paper.tgz. A detailed description of the editing and formatting process will be provided along with the notification email. Important dates - Release of this Call for Papers on February 22, 2011 - Second Call for Papers on May 3, 2011 - Third Call for Papers on May 31, 2011 - Deadline for abstract submission on June 13, 2011 - Notification upon acceptance by July 8, 2011 - Paper submission deadline on September 5, 2011 - RTLWS13 from October 20 to 22, 2011 - LinuxCon Europe in Prague from October 26 to 28, 2011 - Embedded Linux Conference (ELC) Europe in Prague from October 26 to 28, 2011 For more information about the Czech Technical University in Prague, the organizers and the members of the program committee, please refer to the RTLWS13 Homepage at osadl.org/RTLWS. The Organization committee Local staff at the Czech Technical University Prague - Michal Sojka (Faculty of Electrical Engineering, Department of Control Engineering) - Pavel Pisa (Faculty of Electrical Engineering, Department of Control Engineering) - Petr Hodac (SUT - Stredisko un*xovych technologii, UN*X Technologies Center) Real-Time Linux Foundation Working Group and OSADL - Nicholas Mc Guire (Distributed and Embedded Systems Lab, Lanzhou University, China) - Qingguo Zhou (Distributed and Embedded Systems Lab, Lanzhou University, China) - Andreas Platschek (Opentech, Austria) - Carsten Emde (OSADL, Germany)

1 0

A few general questions about L4
by Maciej Katafiasz 22 Feb '11

22 Feb '11

Hello, I'm currently investigating L4 as the platform on which to base an OS I'm considering writing, and for this reason I have several more or less specific questions to help me get oriented in the whole L4 ecosystem. As a matter of introduction, the OS I have in mind is a modern incarnation of a Lisp Machine (http://en.wikipedia.org/wiki/Lisp_machine), attempting to marry the good parts of LispM's such as hackability and the ability to inspect and touch the OS on any level, without their problems (such as the great ease of _crashing_ the OS by mistake, and their inherent lack of security and compartmentalisation). The OS is intended to be practical, and I'm greatly interested in preserving compatibility with existing software, and the ability to mix Lisp apps with C libraries and vice-versa. The practicality requirement also means that I want to avoid writing everything I can avoid writing, in particular drivers. With this being said, here are my initial questions: * Which implementations are currently considered active and sufficient for basing new efforts on? I know Fiasco.OC, seL4, OKL4 and L4Ka. Out of these, seL4 and OKL4 are closed-source and proprietary, thus not really suitable for my needs. Fiasco.OC seems active, L4Ka somewhat less so, with last full release from 2004 (although the last commit to Hg seems to be from 2 months ago). * Furthermore, Fiasco.OC includes, from what I understand, a capability security model, which'd probably be handy for my purposes. However, I can find no documentation on this model. Are there any docs I'm missing? That actually holds for L4 in general as well as Fiasco, the only thing I could find is the X.2 API reference manual, and the very incomplete user manual. Are there any more complete versions of the user manual or other documents explaining the whys of L4, not just hows? * On the other hand, L4Ka has existing projects such as driver virtualisation, which are of great interest to me, as mentioned in the introduction. Thus I'd like to know how compatible in practice the different L4 implementations are. If I took the code from L4Ka's Afterburner, is it at all possible to run it on top of Fiasco, or would I have to rewrite it? Similarly, would it be possible to port NICTA's L4/Darwin IOKit compatibility layer to another L4, or is it tied to the specific implementation of L4 from NICTA? * Since I want to preserve the compatibility with existing environments such as POSIX and/or Win32, I'd like to know if anybody has done any practical research into running multiple OS personalities on top of a microkernel such as L4. I'd be extremely grateful for any links and/or advice regarding running personalities, as well as mixing code operating within the different subsystems. * Lastly, I'd like to know if there's any reasonably-populated IRC channel dedicated to L4. Since I'm still very much exploring the problem space more than the solution space, I appreciate the interactive nature of IRC, which helps me formulate questions I might not even know I have yet. I've found one old mail asking about IRC previously, with Adam's reply pointing to his personal homepage, but I still wasn't able to find any L4 channels that way. Cheers, Maciej Katafiasz

2 1

Fiasco-oc l4linux
by David Leimbach 18 Feb '11

18 Feb '11

Hi Using the latest snapshot, and kind of lost on how to get l4linux to actually build. I did get python running with mag in vmware however, so I've got a little experience. Just not sure what the right way to do this is. My obj/l4linux directory is empty. Any thoughts what I should try? I used "make setup". Then "make" which died for some reason. So i went into obj/l4.../pkg and did "make all". The top level make now completes. Sent from my iPhone

2 3

which is faster an ipc or a function call
by Jason Philip 17 Feb '11

17 Feb '11

I suspect that function call will faster but is this really so? And how faster will it be, it noticeable?

3 3

[ANNOUNCE] NOVA Microhypervisor 0.3 prerelease
by Udo A. Steinberg 17 Feb '11

17 Feb '11

Hi, The NOVA project is happy to announce that there is a new prerelease of the NOVA microhypervisor available for download at http://www.hypervisor.org/ or http://os.inf.tu-dresden.de/~us15/nova/ under the terms of the GNU General Public License version 2. NOVA is based on a modern microhypervisor written in C++ and assembler. The current implementation runs on multi-core x86 machines that support ACPI, under QEMU (including VM support), and as a microkernel in a virtual machine on top of itself. NOVA makes use of hardware virtualization features such as Intel VT-x/VT-d or AMD-V, and facilitates running unmodified guest operating systems in virtual machines with near-native performance. The new release brings virtual-machine support to QEMU and older AMD CPUs, both of which lack nested paging. Furthermore, the microhypervisor can now translate related capabilities during message passing. Cheers, - Udo

2 1

MP Fiasco.UX
by Daniel Waddington - SISA 15 Feb '11

15 Feb '11

Hi, This may be a silly question, but can Fiasco.UX support multi-processing (i.e. SMP)? When I use JDB in Fiasco.UX I can only get one CPU even with MP configured in the kernel build. Thanks Daniel

2 1

build errors in fiasco kernel contained in l4re-core-2011021416 with JDB disabled
by Christoph Szeppek 15 Feb '11

15 Feb '11

Hi, when trying to build the kernel contained in l4re-core-2011021416 (from download page) with JDB disabled, I receive the following error messages: /prefix/l4re-core-2011021416/src/kernel/fiasco/src/kern/space.cpp: In static member function ‘static void* Space::Ku_mem::operator new(size_t, Ram_quota*)’: /prefix/l4re-core-2011021416/src/kernel/fiasco/src/kern/space.cpp:83: error: invalid use of undefined type ‘struct slab_cache_anon’ /prefix/l4re-core-2011021416/src/kernel/fiasco/src/kern/ram_quota.cpp:5: error: forward declaration of ‘struct slab_cache_anon’ /prefix/l4re-core-2011021416/src/kernel/fiasco/src/kern/space.cpp: In member function ‘void Space::Ku_mem::free(Ram_quota*)’: /prefix/l4re-core-2011021416/src/kernel/fiasco/src/kern/space.cpp:86: error: invalid use of undefined type ‘struct slab_cache_anon’ /prefix/l4re-core-2011021416/src/kernel/fiasco/src/kern/ram_quota.cpp:5: error: forward declaration of ‘struct slab_cache_anon’ This happens for ia32 pentium pro and arm integrator platform. With JDB enabled, both builds succeed. Christoph

2 1

None
by sasamy 14 Feb '11

14 Feb '11

Hello. I can not run fiasco kernel, version l4re-core-2011020417 # qemu-system-arm -kernel /home/sasa/fiasco/l4re-core-2011020417/src/l4/build/images/bootstrap.elf -serial stdio -m 256 L4 Bootstrapper Build: #2 Sun Feb 13 15:58:18 MSK 2011, 4.3.3 Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 10000000) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod04: 010d4000-010f5ad8: hello mod03: 010b2000-010d3ba0: l4re mod02: 01071000-010b16a4: moe mod01: 0105f000-01070538: sigma0 mod00: 01013000-0105e8e4: fiasco Moving 5 modules to 1100000 with offset ed000 moving module 05 { 10d4000-10f5ad8 } -> { 11c1000-11e2ad8 } moving module 04 { 10b2000-10d3ba0 } -> { 119f000-11c0ba0 } moving module 03 { 1071000-10b16a4 } -> { 115e000-119e6a4 } moving module 02 { 105f000-1070538 } -> { 114c000-115d538 } moving module 01 { 1013000-105e8e4 } -> { 1100000-114b8e4 } Scanning fiasco Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x100e000-0x100e0d6] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list regions [ 1000, 19bf] { 9c0} Kern fiasco [ 2000, 5cfff] { 5b000} Kern fiasco [ 90000, 9d193] { d194} Sigma0 sigma0 [ 140000, 18e2db] { 4e2dc} Root moe [ 1000000, 10123eb] { 123ec} Boot bootstrap [ 100e000, 100e1d3] { 1d4} Root Multiboot info [ 119f000, 11e2ad7] { 43ad8} Root Modules Memory API Version: (87) experimental Sigma0 config ip:00090000 sp:0100d744 Roottask config ip:00140120 sp:00000000 Starting kernel fiasco at 00001000 Cache config: ON Hello from Startup::stage2 Initialize page table Vmem_alloc::init() Vmem_alloc::TEST allocate zero-filled page... [0xefc01000] done free zero-filled page... done allocate no-zero-filled page... [0xefc02000] done free no-zero-filled page... done SERIAL ESC: allocated IRQ 1 for serial uart Not using serial hack in slow timer handler. Panic: __div0 Press any key to reboot. I have no experience, I'm not sure that everything is done correctly. #make qemu E=hello O=`pwd`/build MODULE_SEARCH_PATH=/tmp:/home/sasa/fiasco/l4re-core-2011020417/src/kernel/fiasco/build MODULES_LIST=/home/sasa/fiasco/l4re-core-2011020417/src/l4/conf/modules.list I tried to run on a real processor at91sam9m10 and got the same result (I think I wrote all the minimum necessary modules for it) Start SD card AT91Bootstrap... Image size: 0xf6000, load_addr: 0x71000000, ep: 0x71000000 relocating image to proper address, dst: 0x71000000, src: 0x72000040, len: 0xf6000 L4 Bootstrapper Build: #3 Sun Feb 13 14:10:12 MSK 2011, 4.3.3 Scanning up to 64 MB RAM Memory size is 64MB (70000000 - 74000000) RAM: 0000000070000000 - 0000000073ffffff: 65536kB Total RAM: 64MB mod04: 710d4000-710f5ad8: hello mod03: 710b2000-710d3ba0: l4re mod02: 71071000-710b16a4: moe mod01: 7105f000-71070538: sigma0 mod00: 71013000-7105e724: fiasco Moving 5 modules to 71100000 with offset ed000 moving module 05 { 710d4000-710f5ad8 } -> { 711c1000-711e2ad8 } moving module 04 { 710b2000-710d3ba0 } -> { 7119f000-711c0ba0 } moving module 03 { 71071000-710b16a4 } -> { 7115e000-7119e6a4 } moving module 02 { 7105f000-71070538 } -> { 7114c000-7115d538 } moving module 01 { 71013000-7105e724 } -> { 71100000-7114b724 } Scanning fiasco Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x7100e000-0x7100e0d6] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x70002000 Regions of list regions [ 70001000, 7000193f] { 940} Kern fiasco [ 70002000, 7005cfff] { 5b000} Kern fiasco [ 70090000, 7009d193] { d194} Sigma0 sigma0 [ 70140000, 7018e2db] { 4e2dc} Root moe [ 71000000, 710123eb] { 123ec} Boot bootstrap [ 7100e000, 7100e1d3] { 1d4} Root Multiboot info [ 7119f000, 711e2ad7] { 43ad8} Root Modules Memory API Version: (87) experimental Sigma0 config ip:70090000 sp:7100d744 Roottask config ip:70140120 sp:00000000 Starting kernel fiasco at 70001000 Cache config: ON Hello from Startup::stage2 Initialize page table Vmem_alloc::init() SERIAL ESC: allocated IRQ 1 for serial uart Not using serial hack in slow timer handler. Panic: __div0 Press any key to reboot.

2 5

can't interface I/O address Space
by Jason Philip 06 Feb '11

06 Feb '11

I writing small program to run on top the microkernel, but, I not sure how to interface the I/O space. I acquire I/O space using "L4_IoFpage()" call, but when I attempt interface it do not work. I try use pointer to I/O locations, but I not sure if this is a correct method. Can somebody tell me what is a correct method?

2 2

Fiasco.OC IPC performance
by Chen Tian 06 Feb '11

06 Feb '11

Hello, I am trying to compare the IPC performance between Pistachio and Fiasco.OC. I found the performances are almost the same for the Pingpong benchmark (I modified the one in Pistachio so that it can run with Fiasco.OC as well). I notice that if I turn off "tracebuffer" and "perfmon counter" switches when compiling Pistachio kernel, the IPC of Pistachio is much faster -- about 150x speedup for Pingpong! I tried to do the same thing for Fiasco.OC by turning off debugging related switches. However, I was not able to observe any performance improvement. I wonder if what config options that can dramatically affect the IPC performance for Fiasco.OC. Also, I will appreciate it if anyone could explain to me the major IPC implementation differences. Thanks, Chen

5 8

Can't access memory region
by Jason Philip 03 Feb '11

03 Feb '11

I need to have access to the VGA port and register. The register I need access in the range of 0x300 to 0x400 so I try getting a 1KB page from 300 onward, but it do not work. I suspect it do not work because it is I/O FPage and they have to align to (in this case 1kB) address. Could anyone help me access these port?

2 5

Questions on implementation details of capabilities
by Christoph Szeppek 03 Feb '11

03 Feb '11

Hello! I try to understand how capabilities are enforced by the Fiasco.OC kernel. From what I think I understood, capabilities are created in the kernel space area of an address space (which is the same in every address space) at Config::Caps_start. Each cap is identified by an index in this area and holds a reference to an object of type kobject_iface in its _obj attribute. This is the object this cap is controlling access to. Now I've got a few questions about further details. Where does the translation from address space local to kernel global cap id happen? How does the kernel know threads of which space are allowed to access which cap (mapdb?)? When a thread sends IPC, in which place of the kernel code do these caps get enforced / checked? BR, Christoph

2 1

Fiasco.OC internals
by Amadeo Cuadrado 03 Feb '11

03 Feb '11

Hello, My apologies if this question has been asked before in this list. What would be the most accurate doc that explains in detail the design and implementation of Fiasco.OC internals? Thanks in advance. Amadeo

2 1

Public release of seL4
by Gernot Heiser 02 Feb '11

02 Feb '11

NICTA and Open Kernel Labs have jointly released seL4. For those not aware of seL4, it is an L4 microkernel which is formally verified (meaning that the implementation is mathematically proven to conform to the specification). It is the world's first (and only) OS kernel that is formally verified in this strict sense. The public release includes the formal specification of the kernel (ARM version), kernel binaries for x86 and ARM, and a para-virtualized Linux running on top of seL4/x86. More about seL4: http://ertos.nicta.com.au/research/sel4/ NICTA download site: http://ertos.nicta.com.au/software/seL4/home.pyl Gernot

1 0

Fiasco Kernel extended V2 API vs. Pistachio X2 API
by Daniel Waddington - SISA 27 Jan '11

27 Jan '11

Hi, Can someone briefly explain the basic differences between the current Fiasco kernel API and the Pistachio X2 API? Thanks Daniel Waddington

3 2

I cannot for the life of me compile l4linux
by Daniel F. Haaland 27 Jan '11

27 Jan '11

l4re and fiasco seem to be working just fine (tested by running the hello world in qemu), but trying to add l4linux on top of l4re has caused me a lot of grief and the following error message: Getting required compilation flags failed. L4OBJ: /home/drxl/l4stuff/builddirs/L4Re-R27MP L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc /home/drxl/l4stuff/src/l4linux/arch/l4/Makefile:301: *** Aborting.. Stop. make: *** [sub-make] Error 2 zsh: exit 2 make O=$MY_L4LINUX_OBJDIR I've detailed how I got to that point in painstaking detail here: http://blog.fairchild.dk/notes/2011/01/25/getting-l4linux-up-and-running/ In short I've begged, bargained and even resorted to shell-foo like: find . -type f -name 'Makefile' -exec grep -Hn REQUIRE {} \; |\ sed -e 's,$.*$\\$,\1,g' -e 's,^.*=$.*$$,\1,g' | sed -n 'H;${g;s/\n//gp}'| \ sed -e 's,[ ]*$[^ ]*$,\1\n,g' | sort -u | uniq | xargs -I ® svn update ® in the l4/pkg dir, to try and fix any unmet dependencies, but to no avail. So I guess I wouldn't mind a little help at this point. best regards Daniel

2 3

Processor compatibility
by Jason Philip 26 Jan '11

26 Jan '11

Is Pistachio compatible with Intel Celeron processor?

3 3

PCI Bus access
by Jason Philip 25 Jan '11

25 Jan '11

I am planning to interfacing the PCI bus using L4, however, I do not quite know how PCI interface works. I know that there is three memory region: configuration space, I/O space and Memory space, and that configuration space is use to detect and configure the device, but I do not know where any of this space are located and the protocol for interfacing them. Please help.

2 1

Privilege threads
by Jason Philip 24 Jan '11

24 Jan '11

how do you create privileged threads?

2 1

PingPong not working
by Jason Philip 23 Jan '11

23 Jan '11

I tried to build kernel and user level applications, but them don't work. When I boot the kernel using QEMU it tell me "loading kernel" but never go further. I try use user level application from earlier version and they work but I can't get my own build to work, why this happening?

3 5

Issue with building L4RE:multiple definition error
by WangKevis 21 Jan '11

21 Jan '11

Hi, when I was doing the building of L4RE as the building instructions, the follwing problems hit me: make[4]: Entering directory `/home/kaikai/embedded/obj/tuduos/pkg/lua/interpr/OBJ-x86_586-l4f' ... Compiling interpr.o ==> Linking lua /home/kaikai/embedded/obj/tuduos/lib/x86_586/l4f/libl4re-vfs.o.a: In function `__L4_STACK_ADDR__': (*ABS*+0xb0000000): multiple definition of `__L4_STACK_ADDR__' /home/kaikai/embedded/obj/tuduos/lib/x86_586/l4f/libl4re-vfs.o.a: In function `__L4_KIP_ADDR__': (*ABS*+0xaffff000): multiple definition of `__L4_KIP_ADDR__' make[4]: *** [lua] Error 1 make[4]: Leaving directory `/home/kaikai/embedded/obj/tuduos/pkg/lua/interpr/OBJ-x86_586-l4f' make[3]: *** [/home/kaikai/embedded/obj/tuduos/pkg/lua/interpr/OBJ-x86_586-l4f] Error 2 make[3]: Leaving directory `/home/kaikai/embedded/mybuild/src/l4/pkg/lua/interpr' make[2]: *** [interpr] Error 2 王凯凯

2 1

problem building L4Linux, comments welcome
by eric van tassell 19 Jan '11

19 Jan '11

I was endeavoring to follow http://wiki.tudos.org/Quickstart. Below's the tail of the build log. Thanks for any suggestions. L4 source directory: /home/evt/wrk/L4/TUD/forest1/src/l4 PWD=/home/evt/wrk/L4/TUD/forest1/src/l4 make -C /home/evt/wrk/L4/TUD/forest1/src/l4 -f /home/evt/wrk/L4/TUD/forest1/src/l4linux/arch/l4/Makefile.l4conf O=/home/evt/wrk/L4/TUD/forest1/src/l4/out L4X_LOOP_CHECK=1 OUTPUT=/home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf GEN /home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf GEN /home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makefile scripts/kconfig/conf --silentoldconfig arch/l4/Kconfig Getting required compilation flags failed. L4OBJ: /home/evt/wrk/L4/TUD/forest1/src/l4/out L4_REQUIRED_MODS: stdlibs log l4re_c-util libio shmc rtc /home/evt/wrk/L4/TUD/forest1/src/l4linux/arch/l4/Makefile:301: *** Aborting.. -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl

2 4

demo cd question
by eric van tassell 17 Jan '11

17 Jan '11

Should the demo CD iso image from http://os.inf.tu-dresden.de/L4/LinuxOnL4/download.shtml boot in VirtualBox? It definitely does not on my alienware m17x hardware. I do have an older machine I can try. -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl

2 1

Fiasco.OC for PowerPC
by Wes 16 Jan '11

16 Jan '11

I keep seeing mention of there being a PowerPC WiP but can't seem to find it anywhere and the version in the snapshots and svn repos don't seem to have PowerPC as a target option. Where can I find this work? Cheers, Wes

2 2

Cannot determine L4 source directory
by eric van tassell 16 Jan '11

16 Jan '11

I've built L4Re and Fiasco without error but get the message below trying to build L4Linux. Does this indicate that CONFIG_L4_OBJ_TREE is set improperly? What should it point to? My directory structure looks like $ROOT /kernel /out #build dir /l4 /l4/out /l4linux /l4linux/out ERROR: Cannot determine L4 source directory Please properly set the path to your L4 build directory in the configuration menu. make[2]: *** [/home/evt/wrk/L4/TUD/forest1/src/l4linux/out/Makeconf.l4conf] Error 1 -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl

2 1

L4 fpages
by jason philip 16 Jan '11

16 Jan '11

I new to the L4 microkernel and do not understand how fpages works. What are the functions of fpages? Can them be used to extend the address space? Are they just for copy a region from one address space to other address space?

4 6

neophyte startup question
by eric van tassell 16 Jan '11

16 Jan '11

I'm intending to target an arm board in a few weeks but just to build and run the code does anyone have a suggestion as to the easiest way to get started? Do people usually use qemu to experiment with an x86 build? My goal is just to build the code and prove it boots, then move toward arm. Thanks. -- - evt (Eric van Tassell) twitter: evt_texelsoft linked-in: linkedin.com/in/evttxl

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