- l4-hackers - example.com Site

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