l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

Problem when booting L4 Fiasco/Re
by Sören Jonsson 11 Mar '14

11 Mar '14

Hello, I have now successfully compiled the L4 Fiasco.OC and your runtime environment. I made the hello.iso bootable image as well, and made an attempt to run it under VMWare workstation. My problem is that it don't work. It stops during boot, with the following information: I had to provide two images, in order to capture all information. The information above "Total RAM: 255MB" disapers very fast otherwise. Is this enough information to explain what is happening, or can I provide more information using other methods? With my best regards, Sören Jonsson Sweden

2 1

seL4 what exactly is in the kernel
by Taylor Bioniks 08 Mar '14

08 Mar '14

What does the seL4 kernel actually provide in the kernel itself? I've read through documentation and it seems they just stop before they state exactly what the seL4 kernel does. So what I'd like to know is what features and components are in the kernel and what is outside of it? Does the kernel have a single kernel stack or multiple kernel stacks and is/are it/they in kernel mode or user mode? Are there any good diagrams that show how seL4 works with its user space components? Thanks in advance

2 1

Panic with l4Linux
by Ismael BARAKAT 07 Mar '14

07 Mar '14

Hello, I'm working on Fiasco, l4Re and l4Linux. I build the uImage for an arm architecture. When I boot it, I have a "panic: going to sleep forever, bye". Can someone help I don't know what caused the problem. This is the information I have on my console when I boot: L4 Bootstrapper Build: #10 Thu Mar 6 11:11:19 CET 2014, 4.7.3 Scanning up to 128 MB RAM Memory size is 128MB (80000000 - 87ffffff) RAM: 0000000080000000 - 0000000087ffffff: 131072kB Total RAM: 128MB mod07: 813f7000-816f7000: ramdisk-arm.rd mod06: 81125000-813f6480: vmlinuz.arm mod05: 81124000-81124189: l4Linux.cfg mod04: 810d1000-81123bc0: ned mod03: 810b7000-810d0458: l4re mod02: 81085000-810b6624: moe mod01: 8107b000-8108433c: sigma0 mod00: 81015000-8107a3a8: fiasco Moving up to 8 modules behind 81100000 moving module 00 { 81015000-8107a3a7 } -> { 817e2000-818473a7 } [414632] moving module 01 { 8107b000-8108433b } -> { 81848000-8185133b } [37692] moving module 02 { 81085000-810b6623 } -> { 81852000-81883623 } [202276] moving module 03 { 810b7000-810d0457 } -> { 816f7000-81710457 } [103512] moving module 04 { 810d1000-81123bbf } -> { 81711000-81763bbf } [338880] moving module 05 { 81124000-81124188 } -> { 81100000-81100188 } [393] moving module 06 { 81125000-813f647f } -> { 81101000-813d247f } [2954368] moving module 07 { 813f7000-816f6fff } -> { 813d3000-816d2fff } [3145728] moving module 03 { 816f7000-81710457 } -> { 816d3000-816ec457 } [103512] moving module 04 { 81711000-81763bbf } -> { 816ed000-8173fbbf } [338880] Scanning fiasco Scanning sigma0 Scanning moe rom/l4Linux.cfg Relocated mbi to [0x8100e000-0x8100e12a] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x80002000 Regions of list 'regions' [ 80001000, 80001b3f] { b40} Kern fiasco [ 80002000, 80072fff] { 71000} Kern fiasco [ 80090000, 800965fb] { 65fc} Sigma0 sigma0 [ 80098000, 8009e17b] { 617c} Sigma0 sigma0 [ 80140000, 8016cacb] { 2cacc} Root moe [ 80170000, 80186f0f] { 16f10} Root moe [ 81000000, 810143f3] { 143f4} Boot bootstrap [ 8100e000, 8100e227] { 228} Root Multiboot info [ 81100000, 8173fbbf] { 63fbc0} Root Module API Version: (87) experimental Sigma0 config ip:80090100 sp:81013de4 Roottask config ip:80140260 sp:00000000 Starting kernel fiasco at 80001300 Hello from Startup::stage2 Cache config: ON ID_PFR[01]: 00001131 00000011 ID_[DA]FR0: 00010400 00000000 ID_MMFR[04]: 01100003 20000000 01202000 00000211 Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned director compiled with gcc 4.7.3 for Beagleboard [] Build: #1 Wed Mar 5 17:15:13 CET 2014 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 80002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:80000000;80000fff] [0:80073000;8008ffff] [0:80097000;80097fff] [0:8009f000;8013ffff] [4:80140000;8016cfff] [0:8016d000;8016ffff] [4:80170000;80186fff] [0:80187000;8100dfff] [4:8100e000;8100efff] [0:8100f000;810fffff] [4:81100000;8173ffff] [0:81740000;86ffffff] IOMEM:---------------------- [0:0;7fffffff] [0:88000000;ffffffff] MOE: Hello world MOE: found 107500 KByte free memory MOE: found RAM from 80000000 to 87000000 MOE: allocated 112 KByte for the page array @0x80073000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [816d3000-816ec458] [C:503000] l4re BOOTFS: [816ed000-8173fbc0] [C:504000] ned BOOTFS: [81100000-81100189] [C:505000] l4Linux.cfg BOOTFS: [81101000-813d2480] [C:506000] vmlinuz.arm BOOTFS: [813d3000-816d3000] [C:507000] ramdisk-arm.rd MOE: cmdline: moe rom/l4Linux.cfg MOE: Starting: rom/ned rom/l4Linux.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4Linux.cfg' l4Linux | libio: Warning: Query of 'vbus' failed! l4Linux | PH 0 (t: 1) offs=00008000 vaddr=01000000 vend=01331b1c l4Linux | phys=01000000 ephys=01331b1c l4Linux | f_sz=002b33d4 memsz=00331b1c flgs=rwx l4Linux | PH 1 (t: 4) offs=002bb3b0 vaddr=012b33b0 vend=012b33d4 l4Linux | phys=012b33b0 ephys=012b33d4 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 0x10002a0, argc=7 argv=0x80007f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4Linux | External resolver is at 0xa8000794 l4Linux | ======> L4Linux starting... <======== l4Linux | Linux version 3.7.0-l4-svn30 (juliens@ubuntu) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-64) ) #1 Wed May 29 10:25:09 CEST 2013 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: 01000000 - 01400000 [4096 KiB]. l4Linux | Areas: Text: 01000000 - 01290000 [2624kB] (a bit longer) l4Linux | Data: 01290000 - 012aeee0 [123kB] l4Linux | Initdata: 01273000 - 0128ed7c [111kB] l4Linux | BSS: 012b33d4 - 01331b1c [505kB] l4Linux | Device scan: l4Linux | Device scan done. l4Linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:01291fa4) l4Linux | main thread will be 413 l4Linux | l4x_register_pointer_section: addr = 01000000 size = 3350528 l4Linux | section-with-init: virt: 0x1000000 to 0x1331b1b [3270 KiB] l4Linux | section-with-init: Phys: 0x80241000 to 0x80572b1c, Size: 3349276 l4Linux | Main thread running, waiting... l4Linux | L4x: Setting superpages for main memory l4Linux | Main memory size: 64MB l4Linux | Main memory: virt: 0x1400000 to 0x53fffff [65536 KiB] l4Linux | Main memory: Phys: 0x81800000 to 0x85800000, Size: 67108864 l4Linux | Filling lower ptabs... l4Linux | Done (220 entries). l4Linux | l4x_register_pointer_section: addr = 01000000 size = 3350528 l4Linux | text: virt: 0x1000000 to 0x1331b1b [3270 KiB] l4Linux | text: Phys: 0x80241000 to 0x80572b1c, Size: 3349276 l4Linux | l4x_rd_path: rom/ramdisk-arm.rd l4Linux | Loading: rom/ramdisk-arm.rd l4Linux | INITRD: Size of RAMdisk is 3072KiB l4Linux | RAMdisk from 0d400000 to 0d700000 [3072KiB] l4Linux | panic: going to sleep forever, bye Kinds regards and thanks for the help, Ismaël Barakat

2 1

Seting Library search path
by Sören Jonsson 06 Mar '14

06 Mar '14

Hello, I am interested in L4 Fiasco as a virtualization environment. I am currently attempting to compile the L4 runtime environment, and I am getting the following error message: === Building package "bootstrap" === ==> Linking bootstrap32.elf /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: error: ld returned 1 exit status make[5]: *** [bootstrap32.elf] Error 1 make[4]: *** [/home/osj/l4re/build/pkg/bootstrap/server/src/OBJ-amd64_amdfam10] Error 2 make[3]: *** [src] Error 2 make[2]: *** [server] Error 2 make[1]: *** bootstrap] Error 2 make: *** [pkg] Error 2 I have examined the problem, and can see that I have a library /usr/lib/gcc/x86_64-linux-gnu/4.7.2, as well as the /usr/lib/gcc/x86_64-linux-gnu/4.7. Can the problem be that the linker is attempting to link to a dated version of the library, and what is the best way to resolve this problem? Best regards, Sören Jonsson Sweden

2 1

Running application can't create a file
by Irvanda Kurniadi 03 Mar '14

03 Mar '14

Hi, Recently I'm using libtiff library on L4/Fiasco. I can use some function from that library. But when I'm trying to create an image by using libtiff function, I got this error message: TIFFOpen: output.tif: Cannot open. Could not open output.tif for writing MOE: task 1561539 exited with 42 Here is my configuration in module.list entry tiff_test2 roottask moe --init=rom/tiff_test2 module l4re module tiff_test2 I compile and run it over linux and it works properly. This application is supposed to create the output file and then open it by TIFFOpen function. So, I think there is a trick to launch this tiff application over L4/fiasco, so the kernel can permit the application to create a file. But, it's only my assumption and I'm not really sure about this. If by any chance you know something about it, please let me know. Thanks regards, Irvanda

2 3

Framebuffer in L4Re for Raspberry PI
by Peter Hanzel 03 Mar '14

03 Mar '14

Hello. I have compiled Fiasco.OC and L4Re for Raspberry PI. It boots ok with UART output. Now I want to add framebuffer device and output to monitor. Is this a work in progress or is it already implemented? or to be implemented? Thanks.

4 4

Genode 14.02 enables VirtualBox on NOVA
by Christian Helmuth 28 Feb '14

28 Feb '14

Today we released a new version of Genode, which, beside many other improvements, adds support for VirtualBox as VMM on NOVA. For years, we addressed virtualization in Genode beginning with OKLinux on the OKL4 kernel. Later, we added support for L4Linux on Fiasco.OC and the Vancouver/Seoul VMM on NOVA. All these solutions had strong points in distinct usage scenarios but we always missed support for a wide range of guest OSes, guest-host integration features, ease of use, active development, and, finally, support for MS Windows guests. Therefore, we are happy to have enabled VirtualBox on the NOVA microhypervisor now, which brings all these features and (due to NOVA's virtualization support) integrates perfectly with the architecture of Genode. Besides VirtualBox, the main features and improvements of the current release are: - Base framework - Improved stack management - Storage - NetBSD file systems ported via rump kernels - Revised block-driver framework - New block cache - New FUSE-based NTFS-3g support - Ported e2fsprogs to the Noux runtime - Low-level OS infrastructure - New pseudo file system as tracing front end - Unified interfaces for graphics - New status-reporting mechanism - Nitpicker support for dynamic screen resizing - Libraries and applications - Extended Noux runtime with POSIX signals - Dynamic ROM service - Platforms - Basic support ODROID XU More details about version 14.02 can be found in the release documentation here http://genode.org/documentation/release-notes/14.02 Best regards -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

L4 Performance
by Gernot Heiser 24 Feb '14

24 Feb '14

Given the recent discussions re IPC performance, I thought it’d be helpful to summarise the state of the art. I’ve put up a performance page on http://l4hq.org (linked from the home page) showing IPC latencies of various L4 kernels across 20 years of architectures. It’s an expanded version of what’s in [Elphinstone & Heiser, SOSP’13]. Each entry in there is, AFAIK, the fastest ever-reported IPC performance of any full-semantics microkernel (i.e. not jsut L4, it’s just that no non-L4 kernel ever broke any records in the last 20 years). If you have any data to contribute please let me know. Gernot

1 0

Fortran Compiler Missing
by Irvanda Kurniadi 22 Feb '14

22 Feb '14

Hi, I have some problem in building some package. It is a little bit weird because the packages just compiled fine in my office, but when I tried to build the same package on the same system in my laptop using VMware, I got this debug message: Fortran compiler (gcc-4.6 or later) missing, skipping directory '/home/..' Since the other package requires the library which is supposed to be built by fortran compiler, then I got this error message: Library dependencies missing: libmpich_f77sup in directory '/home/..'; aborting. I don't know why this problem occur when it worked just fine in another PC. regards, Irvanda

2 2

Library dependencies missing: stdlibs in directory
by Emanuel Berg 21 Feb '14

21 Feb '14

I tried to do exactly as your 'hello' application to see if I could compile and link. Among some other output, I got this message on 'make O=obj_path': Library dependencies missing: stdlibs in directory '/home/incal/core/l4re-snapshot-2013123021/src/l4/pkg/hi/server/src'; aborting. Cflags dependencies missing: stdlibs in directory '/home/incal/core/l4re-snapshot-2013123021/src/l4/pkg/hi/server/src'; aborting. Stop. Before I did that, it told me to 'make O=obj_path config' from src/l4, which I did, though I didn't setup anything explicitly. I had to fetch 'pkg-config' from the repos, but that worked great, only it wouldn't work less the terminal had at least 80 columns - turns out, in the Linux VT, I have 73 columns (i.e., char width), and in X, in urxvt 78. But xterm was configurable in .Xresources like this: xterm*geometry: 80x28 Just sayin'. What is "stdlibs"? It sounds like the C standard library except for the trailing "s". I tried to remove the "include" stuff from the C source, as well as the 'puts' and 'sleep' (to just make it return 0) - this, I thought, would make it independent of any library routines, however, I got the same error message. -- underground experts united: http://user.it.uu.se/~embe8573

4 16

Jump to page:

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