- l4-hackers - example.com Site

Unexpected trap while booting Fiasco
by Stefan Fritsch 01 Aug '13

01 Aug '13

Hi, sometimes I get 'Unexpected trap while booting Fiasco' when booting L4Re with grub 0.97. How often this happens seems to depend on the loaded modules, but I haven't been able to determine some rule when it will happen. It does not depend on the number or total size of the modules reaching a certain size. However, since we upgraded to l4re-snapshot-2013060718 from -2013021819, it always happen for me in the below module configuration (it only happened rarely before the upgrade). It looks like parts of fiasco are not mapped at the correct address. Do you have any idea what could cause this? Cheers, Stefan L4 Bootstrapper Build: #1 Mon Jul 29 19:27:21 CEST 2013, x86-32, 4.4.5 Limiting 'RAM' region [ 40005000, c4eb9fff] { 84eb5000} to [ 40005000, bcffffff] { 7cffb000} due to 3024 MB address limit Dropping 'RAM' region [ c50bc000, d82eefff] { 13233000} due to 3024 MB address limit Dropping 'RAM' region [ dafff000, daffffff] { 1000} due to 3024 MB address limit Dropping 'RAM' region [100000000, 11e5fffff] { 1e600000} due to 3024 MB address limit RAM: 0000000000000000 - 000000000009d7ff: 630kB RAM: 0000000000100000 - 000000001fffffff: 523264kB RAM: 0000000020200000 - 0000000040003fff: 522256kB RAM: 0000000040005000 - 00000000bcffffff: 2047980kB Total RAM: 3021MB Moving up to 22 modules behind 1100000 moving module 00 { 319000-3adc23 } -> { a669000-a6fdc23 } [609316] moving module 01 { 3ae000-3f0a71 } -> { a6fe000-a740a71 } [273010] moving module 02 { 3f1000-5be834 } -> { a741000-a90e834 } [1890357] moving module 03 { 5bf000-6ae6e5 } -> { 9882000-99716e5 } [980710] moving module 04 { 6af000-792266 } -> { 9972000-9a55266 } [930407] moving module 05 { 793000-996b94 } -> { 9a56000-9c59b94 } [2112405] moving module 06 { 997000-99802b } -> { 9c5a000-9c5b02b } [4140] moving module 07 { 999000-12e9408 } -> { 9c5c000-a5ac408 } [9765897] moving module 08 { 12ea000-12eab20 } -> { 1100000-1100b20 } [2849] moving module 09 { 12eb000-12eb547 } -> { 1101000-1101547 } [1352] moving module 10 { 12ec000-13da7a1 } -> { 1102000-11f07a1 } [976802] moving module 11 { 13db000-1a39b4e } -> { 11f1000-184fb4e } [6679375] moving module 12 { 1a3a000-7839fff } -> { 1850000-764ffff } [98566144] moving module 13 { 783a000-7c6b5ee } -> { 7650000-7a815ee } [4396527] moving module 14 { 7c6c000-8eebfff } -> { 7a82000-8d01fff } [19398656] moving module 15 { 8eec000-8eec025 } -> { 8d02000-8d02025 } [38] moving module 16 { 8eed000-8ef0f17 } -> { 8d03000-8d06f17 } [16152] moving module 17 { 8ef1000-8f5d42b } -> { 8d07000-8d7342b } [443436] moving module 18 { 8f5e000-942ca58 } -> { 8d74000-9242a58 } [5040729] moving module 19 { 942d000-9610fff } -> { 9243000-9426fff } [1982464] moving module 20 { 9611000-9880749 } -> { 9427000-9696749 } [2553674] moving module 21 { 9881000-988119e } -> { 9697000-969719e } [415] moving module 03 { 9882000-99716e5 } -> { 9698000-97876e5 } [980710] moving module 04 { 9972000-9a55266 } -> { 9788000-986b266 } [930407] moving module 05 { 9a56000-9c59b94 } -> { 986c000-9a6fb94 } [2112405] moving module 06 { 9c5a000-9c5b02b } -> { 9a70000-9a7102b } [4140] moving module 07 { 9c5c000-a5ac408 } -> { 9a72000-a3c2408 } [9765897] Scanning /l4/fiasco -serial_esc -esc -noscreen Scanning /l4/sigma0 Scanning /l4/moe rom/vs-top.cfg Bootloader MMAP: [ 0, 9d800) RAM (1) [ 9d800, a0000) reserved (2) [ e0000, 100000) reserved (2) [ 100000, 20000000) RAM (1) [ 20000000, 20200000) reserved (2) [ 20200000, 40004000) RAM (1) [ 40004000, 40005000) reserved (2) [ 40005000, c4eba000) RAM (1) [ c4eba000, c50bc000) reserved (2) [ c50bc000, d82ef000) RAM (1) [ d82ef000, daeef000) reserved (2) [ daeef000, daf9f000) ACPI NVS (4) [ daf9f000, dafff000) ACPI (3) [ dafff000, db000000) RAM (1) [ db000000, dfa00000) reserved (2) [ f8000000, fc000000) reserved (2) [ fec00000, fec01000) reserved (2) [ fed08000, fed09000) reserved (2) [ fed10000, fed18000) reserved (2) [ fed18000, fed19000) reserved (2) [ fed19000, fed1a000) reserved (2) [ fed1c000, fed20000) reserved (2) [ fee00000, fee01000) reserved (2) [ ffca0000, 100000000) reserved (2) [100000000, 11e600000) RAM (1) Relocated mbi to [0x2e0000-0x2e0304] Loading /l4/fiasco Loading /l4/sigma0 Loading /l4/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /l4/fiasco [ 9d800, 9ffff] { 2800} Arch BIOS [ e0000, fffff] { 20000} Arch BIOS [ 100000, 10a1b3] { a1b4} Sigma0 /l4/sigma0 [ 140000, 18c25f] { 4c260} Root /l4/moe [ 2d0000, 2e4427] { 14428} Boot bootstrap [ 2e0000, 2e0401] { 402} Root Multiboot info [ 300000, 38ffff] { 90000} Kern /l4/fiasco [ 400000, 49dfff] { 9e000} Kern /l4/fiasco [ 1100000, a3c2408] { 92c2409} Root Module [ 20000000, 201fffff] { 200000} Arch BIOS [ 40004000, 40004fff] { 1000} Arch BIOS [ c4eba000, c50bbfff] { 202000} Arch BIOS [ d82ef000, daeeefff] { 2c00000} Arch BIOS [ daeef000, daf9efff] { b0000} Arch BIOS [ daf9f000, daffefff] { 60000} Arch BIOS [ db000000, df9fffff] { 4a00000} Arch BIOS [ f8000000, fbffffff] { 4000000} Arch BIOS [ fec00000, fec00fff] { 1000} Arch BIOS [ fed08000, fed08fff] { 1000} Arch BIOS [ fed10000, fed19fff] { a000} Arch BIOS [ fed1c000, fed1ffff] { 4000} Arch BIOS [ fee00000, fee00fff] { 1000} Arch BIOS [ ffca0000, ffffffff] { 360000} Arch BIOS API Version: (87) experimental Sigma0 config ip:001001dc sp:002df150 Roottask config ip:001401c4 sp:00000000 Starting kernel /l4/fiasco at 00300834 EAX f0000000 EBX 2BADB002 ECX 00303000 EDX 00400000 ESI 00035dac EDI 002d81cf EBP 0038fd28 ESP 0038fd20 EIP f00653f0 EFLAGS 00013046 CS 0010 SS 0018 DS 0018 ES 0018 FS 0000 GS 0000 trapno 14, error 00000000, from kernel mode page fault linear address f00653f0 00300055 002dce5c 002dcfe8 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Unexpected trap while booting Fiasco! objdump shows that EIP/pagefault address is the start of init_global_kip(): f00653f0 g F .text 00000014 _ZN3Kip15init_global_kipEPS_ -- genua Gesellschaft fuer Netzwerk- und Unix-Administration mbH Domagkstrasse 7, 85551 Kirchheim bei Muenchen tel +49 89 991950-0, fax -999, www.genua.de Geschaeftsfuehrer: Dr. Magnus Harlander, Dr. Michaela Harlander, Bernhard Schneck. Amtsgericht Muenchen HRB 98238

2 2

Build errors with L4
by Bob Stewart 29 Jul '13

29 Jul '13

I pulled down revisions 56 of l4re per the l4re download instructions on an x86 platform running Ubuntu 13.04. I'm cross compiling for an ARM 8 Beaglebone platform. I created a set of tool links pointing to gcc, g++, ar, ld, etc. from the current Genode toolchain. I then followed the l4 build instructions. The build proceeded normally until is started to link in libc static libraries at which point the following errors killed the build: ... make[5]: Entering directory `/home/bob/fiasco/builds/l4/pkg/loader/server/src/OBJ-arm_armv7a-l4f' ... Compiling main.o ... Compiling slab_alloc.o ... Compiling region.o ... Compiling app_task.o ... Compiling name_space.o ... Compiling log.o ... Compiling global.o ... Compiling sched_proxy.o ... Compiling alloc.o ==> Linking loader /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__exit_handler.o): In function `__new_exitfn': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/_atexit.c:259: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(malloc.o): In function `malloc': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdlib/malloc-standard/malloc.c:1018: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(fwrite.__DO_UNLOCKED.o): In function `fwrite_unlocked': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdio/fwrite.c:36: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(__errno_location.o): In function `__errno_location': /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/misc/internals/__errno_location.c:16: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/misc/internals/__errno_location.c:16: undefined reference to `__emutls_v.__libc_errno' /home/bob/fiasco/builds/l4/lib/arm_armv7a/l4f/libuc_c.a(_trans2w.o):/home/bob/fiasco/builds/l4/pkg/uclibc/lib/uclibc/src/libc/stdio/_trans2w.c:67: more undefined references to `__emutls_v.__libc_errno' follow make[5]: *** [loader] Error 1 Is there some undocumented compiler flag related to TLS I should be setting somewhere to fix these library references? Thanks you Bob Stewart

5 7

Launch of L4Linux
by Maximin Coste 29 Jul '13

29 Jul '13

Hi all, I trying to launch L4Linux over Fiasco.OC+L4RE but here is my serial output: INITRD: Freeing memory. l4x: Checks passed. 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 = 211) is a L4 l4ser_shm: 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: 112K /bin/sh: can't access tty; job control turned off # io | Dev_factory: register factory for N2Hw6DeviceE io | GTF: register factory for 7Pci_dev io | GTF: register factory for N2Hw12Msi_resourceE io | Dev_factory: register factory for N2Hw11Gpio_deviceE io | Io service io | Ready. Waiting for request. [ ...Launching µC/OS-II part... ] So all I got from L4Linux is "/bin/sh: can't access tty; job control turned off" What does that mean ? I also have to say that I use the ramdisk.rd from the official website (http://os.inf.tu-dresden.de/L4/LinuxOnL4/download/drops-rd.rd) is this correct ? This is the content of my modules.list file: modaddr 0x1100000 entry l4LinuxUcos kernel fiasco -serial_esc roottask moe rom/l4lx_ucos.cfg module l4re module ned module io module l4lx_ucos.cfg module vmlinuz.arm module ramdisk-arm.rd module l4ucos module beagle.devs module beagle.io And here is my l4lx configuration file: loader:start( { caps = { log = L4.Env.log:m("rws"), calc_server = calc_server, }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, mem = L4.Env.mem_alloc:create(L4.Proto.Factory, 100*1024*1024):m("rws"), scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x80, 0x70) }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-" .. L4.Info.arch() .. ".rd root=1:0 ramdisk_size=17000 init=/bin/sh earlyprintk=1"); Thanks in advance, -- Maximin COSTE-LEENHARDT

2 9

Getting fiasco-ux to exit after moe's init process terminates
by John Millikin 27 Jul '13

27 Jul '13

I'm just getting started with L4 and Fiasco, and wanted to try a Hello World. The goal is to have a program which will run in fiasco-ux, print some text to the screen, and then exit back to the terminal. $ cat helloworld.c #include <stdio.h> int main(int argc, char **argv) { printf("Hello world from L4!\n"); return 1; } I'm encountering a problem where after the program runs, moe detects that it's terminated but doesn't itself exit. $ ./fiasco -R './moe --init=rom/helloworld' -l ./l4re -l ./helloworld [...] MOE: cmdline: ./moe --init=rom/helloworld MOE: Starting: rom/helloworld MOE: loading 'rom/helloworld' Hello world from L4! MOE: task 1557475 exited with 1 Looking through src/l4/pkg/moe/server/src, I can't find any obvious way to make moe exit when its init process terminates. Being able to exit seems like fairly important functionality, so I assume it's present somewhere, but I can't figure out how to enable it. moe has no flags related to exiting, and its main() appears to end in the infinite-loop server.loop_noexc() procedure. Is exiting supported? If yes, how do I enable it? If no, why, and would patches be accepted to do this?

2 1

Problem with setting up namespaces
by Johannes Schlatow 19 Jul '13

19 Jul '13

Hi, I was just trying to set up a simple application that uses L4Re namespaces. I therefore took the clntsrv example and modified it as shown in the diff below with the result that the server blocks on the bind_thread() call. Am I missing something? Cheers Johannes diff --git a/src/l4/pkg/examples/clntsrv/clntsrv.cfg b/src/l4/pkg/examples/clntsrv/clntsrv.cfg index bb2ae50..dd7dfa5 100644 --- a/src/l4/pkg/examples/clntsrv/clntsrv.cfg +++ b/src/l4/pkg/examples/clntsrv/clntsrv.cfg @@ -9,13 +9,16 @@ local ld = L4.default_loader; -- Channel for the two programs to talk to each other. local calc_server = ld:new_channel(); +local server_ns = ld:create_namespace({ calc_server = calc_server:svr()}); +local client_ns = ld:create_namespace({ calc_server = calc_server}); + -- The server program, getting the channel in server mode. -ld:start({ caps = { calc_server = calc_server:svr() }, +ld:start({ caps = { namespace = server_ns }, log = { "server", "blue" } }, "rom/ex_clntsrv-server"); -- The client program, getting the 'calc_server' channel to be able to talk -- to the server. The client will be started with a green log output. -ld:start({ caps = { calc_server = calc_server }, +ld:start({ caps = { namespace = client_ns }, log = { "client", "green" } }, "rom/ex_clntsrv-client"); diff --git a/src/l4/pkg/examples/clntsrv/server.cc b/src/l4/pkg/examples/clntsrv/server.cc index 2f2e3fc..9c4c0b9 100644 --- a/src/l4/pkg/examples/clntsrv/server.cc +++ b/src/l4/pkg/examples/clntsrv/server.cc @@ -12,6 +12,7 @@ #include <l4/re/util/cap_alloc> #include <l4/re/util/object_registry> #include <l4/cxx/ipc_server> +#include <l4/re/namespace> #include "shared.h" @@ -60,12 +61,34 @@ main() { static Calculation_server calc; - // Register calculation server - if (!server.registry()->register_obj(&calc, "calc_server").is_valid()) - { - printf("Could not register my service, is there a 'calc_server' in the caps table?\n"); - return 1; - } + L4::Cap<L4Re::Namespace> ns = L4Re::Env::env()->get_cap<L4Re::Namespace>("namespace"); + if (!ns.is_valid()) { + printf("Could not get namespace cap from cap table.\n"); + return 1; + } + L4::Cap<L4::Ipc_gate> calc_server = L4Re::Util::cap_alloc.alloc<L4::Ipc_gate>(); + + if (ns->query("calc_server", calc_server) != 0) { + printf("Could not get 'calc_server' cap from namespace\n"); + return 1; + } + + if (!calc_server.is_valid()) { + printf("calc_server cap is invalid\n"); + return 1; + } + + l4_umword_t id = l4_umword_t(0xcaffee); + L4::Cap<L4::Thread> tcap = L4Re::Env::env()->main_thread(); + + printf("bind_thread()...\n"); + int err = l4_error(calc_server->bind_thread(tcap, id)); + if (err < 0) { + printf("failed\n"); + return 1; + } + + printf("OK\n"); printf("Welcome to the calculation server!\n" "I can do substractions and negations.\n");

4 6

Fiasco.OC Kernel memory running out (I think)
by Daniel Waddington 18 Jul '13

18 Jul '13

Hi, I'm using Fiasco.OC r56 on x86_64 (with Genode). After doing quite a lot of memory mapping, mem_map finally fails. It seems that the _allocators[0]->alloc(...) fails during the Mapping_tree::new operator creation of a Mapping_tree object in the Treemap::tree method. How can I increase the available kernel memory attached to this allocator? Thanks Daniel

2 1

Error during the "ned" package build (svn revision 42)
by ggasnier31＠free.fr 16 Jul '13

16 Jul '13

Hello, I got the following error building the "ned" package for ARM architecture (Cortex-A9, Pandaboard). I use the last Linaro toolchain "gcc-linaro-arm-linux-gnueabihf-4.7-2012.12-20121214_linux". === Building package "ned" === make[1]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make[2]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[3]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' ... Building /home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/.general.d make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[3]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[4]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' ... Building .general.d ... Building Makefile.inc make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[4]: Entering directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[4]: *** No rule to make target `ned.lua.bin.o', needed by `ned'. Stop. make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[3]: *** [/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f] Error 2 make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[2]: *** [src] Error 2 make[2]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make: *** [ned] Error 2 Commenting the line "OBJS += ned.lua.bin.o" in the file l4/pkg/ned/server/src/Makefile gives this error. ==> Linking ned lua.o: In function `lua(int, char const* const*)': /home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src/lua.cc:97: undefined reference to `_binary_ned_lua_start' /home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src/lua.cc:97: undefined reference to `_binary_ned_lua_end' make[4]: *** [ned] Error 1 make[4]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f' make[3]: *** [/home/repository/L4.kernel/fiasco/src/l4/ArmBuild/pkg/ned/server/src/OBJ-arm_armv7a-l4f] Error 2 make[3]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server/src' make[2]: *** [src] Error 2 make[2]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned/server' make[1]: *** [server] Error 2 make[1]: Leaving directory `/home/repository/L4.kernel/fiasco/src/l4/pkg/ned' make: *** [ned] Error 2 Regards, Guillaume GASNIER

3 3

x86_fb-example
by Rudolf Weber 15 Jul '13

15 Jul '13

Hello, I want to try out the x86-fb-example in the l4re-snapshot-2013060718. I found the following patch necessary: --- src/l4/conf/examples/x86-fb.list.vorrudi 2013-06-07 18:36:35.000000000 +0200 +++ src/l4/conf/examples/x86-fb.list 2013-07-12 18:23:39.688816451 +0200 @@ -1,5 +1,5 @@ -modaddr 0x1100000 +modaddr 0x2000000 entry x86-fb-example bootstrap bootstrap -serial @@ -13,4 +13,4 @@ module ned module fb-drv module mag -module ex_fb_spectrum +module ex_fb_spectrum_cc --- src/l4/conf/examples/x86-fb.cfg.vorrudi 2013-06-07 18:36:35.000000000 +0200 +++ src/l4/conf/examples/x86-fb.cfg 2013-07-12 18:12:30.837274646 +0200 @@ -64,5 +64,5 @@ l4re_dbg = L4.Dbg.Warn, -- scheduler = L4.Env.user_factory:create(L4.Proto.Scheduler, 0x18, 0x8), }, - "rom/ex_fb_spectrum"); + "rom/ex_fb_spectrum_cc"); print("ex_fb_spectrum exited with: " .. e:wait()); I generated a iso-Image with make grub2iso E=x86-fb-example MODULES_LIST=/home/rw/l4exp/l4re-snapshot-2013060718/src/l4/conf/examples/x86-fb.list and started with qemu-system-i386 -cdrom images/x86-fb-example.iso -serial stdio It's great to have examples ! Greetings Rudolf Weber http://www.infnet.verein.de/home/rw/index.html Computer Science and Network Club Ravensburg

2 1

Help needed
by vijay kumar godavarthy 06 Jul '13

06 Jul '13

Dear all, I am a newbie to l4re and fiasco. I would like to execute the client-server example given in the example directory. Please let me know the steps to be followed. In case I write a new server how to compile and execute it in QEMU. Best regards and many thanks -- vijay kumar

2 1

A interprocess communication system for two l4linux instances
by Wajidali Whowe 05 Jul '13

05 Jul '13

Dear all, I am trying to implement an IPC method between two l4linux instances (lets call them as vmlinuz1 and vmlinuz2) using l4ser driver. Nevertheless both l4linux instances stuck during boot up printing, the following last sentence: "vmlinuz.| L4 serial driver" Going over the driver/tty/serial/l4ser.c file, I have seen that the stuck position line is in the function "l4ser_init_port"; "t = L4XV_FN(l4_msgtag_t, l4_icu_bind(l4ser_port[num].vcon_cap, 0, l4ser_port[num].vcon_irq_cap));" The following is my lua script: local ttyChannel = l:new_channel(); local hid = l:new_channel(); local linux_caps = { log = L4.Env.log:m("rws"); vbus = io_caps.linux_bus, rtc = rtc_caps.rtc, ev = hid:svr(), rom = L4.Env.rom, ttyMv0 = ttyChannel, }; l:start( { caps = linux_caps, }, "rom/vmlinuz1 mem=512M l4ser.add=ttyMv0 l4-input-srv.enable=1 console=ttyLv0 ramdisk=rom/myRamdisk root=1:0 ramdisk_size=190000 l4x_rd=rom/myRamdisk init=/sbin/init"); local linux_caps2 = { vbus = io_caps.linux_bus2, rtc = rtc_caps.rtc, rom = L4.Env.rom, ttyMv0 = ttyChannel, }; l:start( { caps = linux_caps2, }, "rom/vmlinuz.android mem=512M l4ser.add=ttyMv0 console=ttyLv0 ramdisk=rom/ramdisk root=1:0 ramdisk_size=190000 l4x_rd=rom/ramdisk init=/sbin/init"); How do you think that might cause the problem? Best regards and many thanks.

1 0