- l4-hackers - example.com Site

Task creation in ned or moe
by Stark, Josef 31 Jul '14

31 Jul '14

Hello, could maybe someone kindly explain to me (roughly), how task creation/startup is done in ned or moe? I assumed that the Factory methods create_task() and create_thread() would be used, but instead it seems that Elf_Loader is used for this. I skimmed through this class but I don't fully understand it. Basically, it seems that moe's call "elf_loader.start(_init_prog, cxx::String(""));" (in file main.cc) leads in the end to this call: "Ldr::Elf_loader<Moe_x_app_model, Dbg>::launch(&am, "rom/l4re", ldr);" (loader_elf.cc). So, to me it seems that just l4re gets started, not the desired binary (ned), but clearly I am missing something (a lot) here (because it actually works the way it should). Could someone enlighten me here? And why aren't create_task() and create_thread() used here? (In this text I am referring to moe, but in ned I couldn't find these two methods either.) Thanks in advance! Josef

2 1

LUA bindings / kill task
by Stark, Josef 31 Jul '14

31 Jul '14

Dear all, is there maybe a list somewhere containing all the LUA bindings that are exported by L4(Re)? I found a few functions in the file src/l4/pkg/lua/lib/l4/ll4lib.c ("ipc_call", "ipc_reply_and_wait" etc.) and also in src/l4/pkg/ned/server/src/ned.lua (mainly "start" and "startv") but specifically I am looking for a command to kill a task. It seems that the file src/l4/pkg/ned/server/src/ned.lua prepares to offer such a function (in the array "_task_ops[]" the function "__task_kill" corresponds to the name "kill"), however I didn't succeed in calling this kill function. What could I be doing wrong? If it is not yet implemented, what needs to be changed? I tried it in interactive ned mode as well as in the mode which interprets a config file (using the latest snapshot). Thanks in advance! Cheers, Josef Stark

2 2

Problems with python to compile seL4
by Jorge Ventura 29 Jul '14

29 Jul '14

I am still using Debian 6. I installed python 2.7.8 but I am having problems to compile the seL4. arduino@squeeze64:~/ARM/src/seL4$ TOOLPREFIX=arm-none-eabi- ARCH=arm PLAT=am335x ARMV=armv7-a CPU=cortex-a8 make Traceback (most recent call last): File "./tools/invocation_header_gen.py", line 18, in <module> import tempita ImportError: No module named tempita make: *** [arch/api/invocation.h] Error 1 What is this module "tempita"? What package is that?

3 3

seL4 is free!
by Gernot Heiser 29 Jul '14

29 Jul '14

A few hours ago we open-sourced seL4. The release covers the kernel source and proofs (under GPL v2) as well as tools and libraries (mostly BSD). http://sel4.systems contains details, including download and mailing list links. Enjoy, Gernot

1 0

Question about IPI
by Yuxin Ren 28 Jul '14

28 Jul '14

Hi All, Now I want to how many IPIs are sent during an IPC. So I add a counter for IPI in the kernel, and in the user level, there is a client sending IPC to a server on another core. But I found some behavior are very strange. 1. The total number of IPI are not multiple times of the number of IPC. It seems that there are some "extra IPIs", and with the number of IPC increases, the number of "extra IPIs" are also increasing. So my question is if there are some background program in the kernel or L4Re to send IPIs? 2. If I add printf statement in the kernel, the number of IPIs are also increasing. Does printf in the kernel cause sending IPI? If it does, is there any methods to avoid this. Like in Linux, it has printk function in the kernel. Thanks a lot!! Yuxin

2 5

Start a process with a specified pager
by Noah Zentzis 24 Jul '14

24 Jul '14

Hi, I'm trying to launch a new task and run it under a custom pager, but I can't seem to figure out how to go about it. I've looked through the Moe and libloader source code, but I'm not sure how the task actually ends up getting created, only where the ELF image is loaded into memory. Can anyone point me towards the documentation for task creation or explain how Moe actually ends up turning the executable image into a running task? Thanks! - Noah Zentzis

2 1

Question about irq
by Maria Soler 24 Jul '14

24 Jul '14

Hello, I have a question about how the irqs work in L4re. I am running FIASCO.OC + L4re on qemu for arm. I want to be able to raise an interruption from qemu and handle it from my VM. I am basing my work on the example at examples/libs/libirq (I am coding in C, so it is more convenient than other examples in C++). I have a qemu device that has the interrupt number #N in qemu. I rise the interrupt but the l4irq_wait function doesn't return. I have tried both with qemu_irq_pulse(state->irq); and with qemu_set_irq(state->irq, 1), also I have tried attaching the irq and requesting it; but there is no difference. My basic doubts are: - Is the number of the interruption the same within L4re as in qemu? and if not, how can I calculate/check what the number is in L4re? - If the number is OK, what can be the problem I am facing? The mentioned example doesn't work for me either (l4irq_request returns 0 in this case), so I don't know how to solve this exactly. - Is there a better example for this that I can use as a baseline? In case this is relevant, this is part of a more complex project, so I have a .devs file where I have a line like: Io.Res.irq(#N); I am also using this file in the present step to keep things as similar as possible to the real scenario. Thanks! Regards, María.

2 1

Why need a lock in memory/capability map
by Yuxin Ren 24 Jul '14

24 Jul '14

Hi All, I note that when a thread does memory or capability mapping, both over system call and IPC, it needs take a lock, which is the existence_lock of target task. I cannot understand it needs take a per task, as cap/page table are per thread. What data does this lock to protect? Thank you. Yuixn

2 3

Segmentation fault while running arm image on top of qemu
by cem akpolat 24 Jul '14

24 Jul '14

Hi, While running "ARM with Android 2.3.4", the segmentation fault occured. The parameters that I typed on the console as follows: *$qemu-system-arm -M realview-pbx-a9 -m 512 -kernel l4_gingerbread-arm.elf -serial stdio* And the console outputs: L4 Bootstrapper Build: #14 Wed Jul 20 06:44:48 CEST 2011, 4.5.1 Scanning up to 512 MB RAM Memory size is 512MB (70000000 - 90000000) RAM: 0000000070000000 - 000000008fffffff: 524288kB Total RAM: 512MB mod13: 716c9000-73e2f000: system-arm-ginger.img mod12: 715c9000-716c9000: root-arm-ginger.img mod11: 712bf000-715c8448: vmlinuz.android mod10: 712be000-712be10a: arm_android.io mod09: 712bd000-712bd4c1: arm-rv-eb.devs mod08: 712bc000-712bc698: lx_ginger-arm.cfg mod07: 71292000-712bb5e0: fb-drv mod06: 71204000-7129146c: mag mod05: 71129000-71203b58: io mod04: 710d5000-711281b8: ned mod03: 710bb000-710d4510: l4re mod02: 71081000-710ba5f0: moe mod01: 71077000-7108033c: sigma0 mod00: 71015000-7107655c: fiasco Moving 14 modules to 71100000 with offset eb000 moving module 14 { 716c9000-73e2f000 } -> { 717b4000-73f1a000 } moving module 13 { 715c9000-716c9000 } -> { 716b4000-717b4000 } moving module 12 { 712bf000-715c8448 } -> { 713aa000-716b3448 } moving module 11 { 712be000-712be10a } -> { 713a9000-713a910a } moving module 10 { 712bd000-712bd4c1 } -> { 713a8000-713a84c1 } moving module 09 { 712bc000-712bc698 } -> { 713a7000-713a7698 } moving module 08 { 71292000-712bb5e0 } -> { 7137d000-713a65e0 } moving module 07 { 71204000-7129146c } -> { 712ef000-7137c46c } moving module 06 { 71129000-71203b58 } -> { 71214000-712eeb58 } moving module 05 { 710d5000-711281b8 } -> { 711c0000-712131b8 } moving module 04 { 710bb000-710d4510 } -> { 711a6000-711bf510 } moving module 03 { 71081000-710ba5f0 } -> { 7116c000-711a55f0 } moving module 02 { 71077000-7108033c } -> { 71162000-7116b33c } moving module 01 { 71015000-7107655c } -> { 71100000-7116155c } Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/lx_ginger-arm.cfg Relocated mbi to [0x7100f000-0x7100f1ed] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x70002000 Regions of list regions [ 70001000, 700019ff] { a00} Kern fiasco [ 70002000, 70070fff] { 6f000} Kern fiasco [ 70090000, 7009e17b] { e17c} Sigma0 sigma0 [ 70140000, 701717f3] { 317f4} Root moe [ 70178000, 7018eec7] { 16ec8} Root moe [ 71000000, 710143eb] { 143ec} Boot bootstrap [ 7100f000, 7100f2ea] { 2eb} Root Multiboot info [ 711a6000, 73f19fff] { 2d74000} Root Modules Memory API Version: (87) experimental Sigma0 config ip:700900e0 sp:71013044 Roottask config ip:70140178 sp:00000000 Starting kernel fiasco at 70001000 Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 L2: ID=410000c8 Type=1c100100 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 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 0, v: 9, i: 41, t: hard, p: dbl/sngl 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.1 for Realview [] Build: #5 Tue Jul 19 19:26:41 CEST 2011 [0m Calibrating timer loop... done. SIGMA0: Hello! KIP @ 70002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:70000000;70000fff] [0:70071000;7008ffff] [0:7009f000;7013ffff] [4:70140000;70171fff] [0:70172000;70177fff] [4:70178000;7018efff] [0:7018f000;7100efff] [4:7100f000;7100ffff] [0:71010000;711a5fff] [4:711a6000;73f19fff] [0:73f1a000;8effffff] IOMEM:---------------------- [0:0;6fffffff] [0:90000000;ffffffff] MOE: Hello world MOE: found 460556 KByte free memory MOE: found RAM from 70000000 to 8f000000 MOE: allocated 496 KByte for the page array @0x7009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [711a6000-711bf510] [C:503000] l4re BOOTFS: [711c0000-712131b8] [C:504000] ned BOOTFS: [71214000-712eeb58] [C:505000] io BOOTFS: [712ef000-7137c46c] [C:506000] mag BOOTFS: [7137d000-713a65e0] [C:507000] fb-drv BOOTFS: [713a7000-713a7698] [C:508000] lx_ginger-arm.cfg BOOTFS: [713a8000-713a84c1] [C:509000] arm-rv-eb.devs BOOTFS: [713a9000-713a910a] [C:50a000] arm_android.io BOOTFS: [713aa000-716b3448] [C:50b000] vmlinuz.android BOOTFS: [716b4000-717b4000] [C:50c000] root-arm-ginger.img BOOTFS: [717b4000-73f1a000] [C:50d000] system-arm-ginger.img MOE: cmdline: moe rom/lx_ginger-arm.cfg MOE: Starting: rom/ned rom/lx_ginger-arm.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/lx_ginger-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 | Video memory is at virtual 0x4000 (size: 0x96000 Bytes)[0m [36mfb | Physical video memory is at 0x704df000[0m [36mfb | Color mode: 10:5:0 5:5:5[0m [36mfb | Detected a 'Unknown' 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: 640x480 pos: 0, 0[0m [32mmag | bytes_per_line: 1280[0m [32mmag | buffer_offset: 0[0m [32mmag | RGBA(2): 5(10):5(5):5(0):0(0)[0m [32mmag | memory 200000-296000[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=004dc140[0m [33mandroid | f_sz=[0m[33m002eb484 memsz=003dc140 flgs=rwx[0m [33mandroid | PH 1 (t: 4) offs=002f3460 vaddr=003eb460 vend=003eb484[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 0x11f330, 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-g8b7f1ac-dirty (mlange@rhea) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) #20 Tue Jul 19 20:21:49 CEST 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=256M 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 - 00500000 [4096 KiB].[0m [33mandroid | Areas: Text: 00100000 - 003cc000 [2864kB] (a bit longer)[0m [33mandroid | Data: 003cc000 - 003e67c0 [105kB][0m [33mandroid | Initdata: 00100000 - 0011e000 [120kB][0m [33mandroid | BSS: 003eb484 - 004dc140 [963kB][0m [33mandroid | Device scan:[0m [33mandroid | l4lx_thread_create: Created thread 415 (cpu0) (u:b3000400, v:b3000600, sp:003cdff0)[0m [33mandroid | main thread will be 415[0m [33mandroid | l4x_register_pointer_section: addr = 00100000 size = 4050944[0m [33mandroid | section-with-init: virt: 0x100000 to 0x4dc13f [3952 KiB][0m [33mandroid | section-with-init: Phys: 0x7070d000 to 0x70ae9140, Size: 4047168[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: 256MB[0m [33mandroid | Main memory: virt: 0x500000 to 0x104fffff [262144 KiB][0m [33mandroid | Main memory: Phys: 0x74000000 to 0x84000000, Size: 268435456[0m [33mandroid | Filling lower ptabs...[0m [33mandroid | Done (289 entries).[0m [33mandroid | l4x_register_pointer_section: addr = 004ff000 size = 4096[0m [33mandroid | end: virt: 0x4ff000 to 0x4fffff [4 KiB][0m [33mandroid | end: Phys: 0x70aeb000 to 0x70aec000, 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 10500000 to 10600000 [1024KiB][0m [33mandroid | l4lx_thread_create: Created thread 41b (timer.i0) (u:b3000800, v:00000000, sp:00405ff4)[0m [33mandroid | timer_irq_thread: Starting timer IRQ thread.[0m Linux version 2.6.39-l4-g8b7f1ac-dirty (mlange@rhea) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) #20 Tue Jul 19 20:21:49 CEST 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 writeback arm926_flush_kern_cache_all() INITRD: 10500000 - 10600000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 66039 Kernel command line: console=ttyLv0 androidboot.console=ttyLv0 mem=256M 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: 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) Memory: 0MB 260MB = 260MB total Memory: 259580k/259580k available, 6664k reserved, 0K highmem Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0x10600000 - 0x18600000 ( 128 MB) lowmem : 0x00000000 - 0x10500000 ( 261 MB) modules : 0xff100000 - 0x00100000 ( 16 MB) .init : 0x00100000 - 0x0011e000 ( 120 kB) .text : 0x0011f000 - 0x003ca298 (2733 kB) .data : 0x003cc000 - 0x003e67c0 ( 106 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... 53.04 BogoMIPS (lpj=265216) 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 Advanced Linux Sound Architecture Driver Version 1.0.24. Switching to clocksource kip 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 Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. ashmem: initialized msgmni has been set to 506 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 @ 10500000 l4fb l4fb.0: 5:5:5 10: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 brd: module loaded l4bdds: Disk 'rom/system-arm-ginger.img' size = 40344 KB (39 MB) flags=101 addr=18600000 ------------[ cut here ]------------ WARNING: at /home/mlange/projects/l4android/kernel/kernel/softirq.c:159 local_bh_enable+0x9c/0xa8() Modules linked in: [<0012bc80>] (unwind_backtrace+0x0/0xf8) from [<0013c638>] (warn_slowpath_common+0x54/0x64) [<0013c638>] (warn_slowpath_common+0x54/0x64) from [<0013c664>] (warn_slowpath_null+0x1c/0x24) [<0013c664>] (warn_slowpath_null+0x1c/0x24) from [<001420a0>] (local_bh_enable+0x9c/0xa8) [<001420a0>] (local_bh_enable+0x9c/0xa8) from [<0018f408>] (bdi_register+0x100/0x164) [<0018f408>] (bdi_register+0x100/0x164) from [<0018f498>] (bdi_register_dev+0x2c/0x34) [<0018f498>] (bdi_register_dev+0x2c/0x34) from [<00214ce8>] (add_disk+0x74/0x250) [<00214ce8>] (add_disk+0x74/0x250) from [<0011088c>] (l4bdds_init+0x238/0x294) [<0011088c>] (l4bdds_init+0x238/0x294) from [<0011f488>] (do_one_initcall+0x34/0x17c) [<0011f488>] (do_one_initcall+0x34/0x17c) from [<00100774>] (kernel_init+0xb4/0x144) [<00100774>] (kernel_init+0xb4/0x144) from [<00123770>] (kernel_thread_exit+0x0/0x8) ---[ end trace ff4e3c975709dc7d ]--- l4bdds0: detected capacity change from 0 to 41312256 l4bdds0: unknown partition table mousedev: PS/2 mouse device common for all mice logger: created 64K log 'log_main' logger: created 256K log 'log_events' logger: created 64K log 'log_radio' logger: created 64K log 'log_system' ALSA device list: #0: Dummy 1 TCP cubic registered NET: Registered protocol family 17 VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 0 /home/mlange/projects/l4android/kernel/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [32mmag | Input: new pointer device (src='userdata: 0x1e510' stream='userdata: 0x1dd0c')[0m [32mmag | bus='i8042' vendor=0x2 product=0x6 version=0[0m[32m[0m RAMDISK: ext2 filesystem found at block 0 RAMDISK: Loading 1024KiB [1 disk] into ram disk... |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\done. VFS: Mounted root (ext2 filesystem) on device 1:0. Freeing init memory: 120K init: Timed out waiting for /dev/.coldboot_done init: cannot open '/initlogo.rle' 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' init: service 'console' requires console [32mmag | Input: new keyboard device (src='userdata: 0x1e510' stream='userdata: 0x13788')[0m [32mmag | bus='i8042' vendor=0x1 product=0x2 version=43907[0m[32m[0m [33mandroid | cpu0: segfault for servicemanager(22) [T:9d] at 00000000, ip=00008cfa, 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 | 40037000 - 4003f000 r-xs 00000 /dev/__properties__ (deleted)[0m [33mandroid | 40051000 - 40052000 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 - afb16000 r-xp 00000 /system/lib/libm.so[0m [33mandroid | afb16000 - afb17000 rwxp 00016 /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 | bf445000 - bf467000 rw-p[0m [33mandroid | ffff0000 - ffff1000 r-xp[0m [33mandroid | 0: 00000000 40046207 00000000 bf466ccc 4: 000086e4 0000a170 00000000 bf466ccc[0m [33mandroid | 8: 00000000 00000000 00000000 00000000 12: 00000000 [01;34mbf466c90[0m 000087d1 [01;34m00008cfa[0m[0m [33mandroid | CPSR: 60000030 Err: 00000004[0m [1;25r[25;1H [32m ---------------------------------------------------------------------[m CPU 0 [f001337c]: segfault [25;1H[32m[ l4lx.cpu0] jdb: [m[K =============== Cheers, Cem Cem Akpolat

1 1

l4android compilation issue
by cem akpolat 24 Jul '14

24 Jul '14

Dear all, I compiled l4android in the light of the explanation under l4android.org, however, I encountered the failure or another state that I don't know what it exactly means. It doesn't seem as an error, however, it stays here. By the way, the build.pl file provided in l4android.org doesn't work, therefore I have compiled everything manually. n/x86_586/l4f/system-x86-ginger.img " -serial stdio -m 3000 L4 Bootstrapper Build: #1 Mo 21. Jul 16:33:27 CEST 2014, x86-32, 4.8.2 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 00000000bb7fdfff: 3070968kB Total RAM: 2999MB Moving up to 15 modules behind 1100000 moving module 00 { 2e5000-350c3f } -> { 845a000-84c5c3f } [441408] moving module 01 { 351000-3a4c48 } -> { 84c6000-8519c48 } [343113] moving module 02 { 3a5000-5e6a68 } -> { 851a000-875ba68 } [2366057] moving module 03 { 5e7000-716a82 } -> { 763f000-776ea82 } [1243779] moving module 04 { 717000-96517b } -> { 776f000-79bd17b } [2417020] moving module 05 { 966000-147138f } -> { 875c000-926738f } [11580304] moving module 06 { 1472000-15778b8 } -> { 1100000-12058b8 } [1071289] moving module 07 { 1578000-199efcd } -> { 1206000-162cfcd } [4353998] moving module 08 { 199f000-1b18ebd } -> { 162d000-17a6ebd } [1547966] moving module 09 { 1b19000-1b19839 } -> { 17a7000-17a7839 } [2106] moving module 10 { 1b1a000-1b1a36b } -> { 17a8000-17a836b } [876] moving module 11 { 1b1b000-1b1b86e } -> { 17a9000-17a986e } [2159] moving module 12 { 1b1c000-1ecae4e } -> { 17aa000-1b58e4e } [3862095] moving module 13 { 1ecb000-1fcafff } -> { 1b59000-1c58fff } [1048576] moving module 14 { 1fcb000-763efff } -> { 1c59000-72ccfff } [90652672] moving module 03 { 763f000-776ea82 } -> { 72cd000-73fca82 } [1243779] moving module 04 { 776f000-79bd17b } -> { 73fd000-764b17b } [2417020] moving module 05 { 875c000-926738f } -> { 764c000-815738f } [11580304] Scanning /home/akpolat/mysvn/l4android/l4android/src/src/kernel/fiasco/build//fiasco -serial_esc Scanning /home/akpolat/mysvn/l4android/l4android/src/src/l4/build/bin/x86_586/l4f/sigma0 Scanning /home/akpolat/mysvn/l4android/l4android/src/src/l4/build/bin/x86_586/l4f/moe rom/lx_ginger.cfg Bootloader MMAP: [ 0, 9fc00) RAM (1) [ 9fc00, a0000) reserved (2) [ f0000, 100000) reserved (2) [ 100000, bb7fe000) RAM (1) [ bb7fe000, bb800000) reserved (2) [ fffc0000, 100000000) reserved (2) Relocated mbi to [0x2dd000-0x2dd606] Loading /l4android/l4android/src/src/kernel/fiasco/build//fiasco Loading ndroid/l4android/src/src/l4/build/bin/x86_586/l4f/sigma0 Loading l4android/l4android/src/src/l4/build/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10b197] { b198} Sigma0 ndroid/l4android/src/src/l4/build/bin/x86_586/l4f/sigma0 [ 140000, 18e21f] { 4e220} Root l4android/l4android/src/src/l4/build/bin/x86_586/l4f/moe [ 2d0000, 2e34a7] { 134a8} Boot bootstrap [ 2dd000, 2dd703] { 704} Root Multiboot info [ 300000, 38ffff] { 90000} Kern /l4android/l4android/src/src/kernel/fiasco/build//fiasco [ 400000, 471fff] { 72000} Kern /l4android/l4android/src/src/kernel/fiasco/build//fiasco [ 1100000, 815738f] { 7057390} Root Module [ bb7fe000, bb7fffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:00100218 sp:002e1040 Roottask config ip:001401f6 sp:00000000 Starting kernel /l4android/l4android/src/src/kernel/fiasco/build//fiasco at 003007b0 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2012 TU Dresden Rev: UNKNOWN compiled with gcc 4.8.2 for Intel Pentium [] Build: #1 Mo 21. Jul 16:36:47 CEST 2014 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at bb3e2000 (4096Bytes) ACPI-Init ACPI: RSDP[0xf09e0] r00 OEM:BOCHS. Boot_alloc: size=0x10 Boot_alloc: allocated extra memory block @0xfffe5000 (size=400) Boot_alloc: @ 0xfffe5000 Boot_alloc: remaining free block @ 0xfffe5010 (size=3f0) ACPI: RSDT[0x203ffbc1] r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ff1c0] r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203ff234] r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203ffb11] r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203ffb89] r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203ffb11 IO-APIC[ 0]: struct: 0x203ffb45 adr=fec00000 Boot_alloc: size=0x1c Boot_alloc: @ 0xfffe5010 Boot_alloc: remaining free block @ 0xfffe5030 (size=3d0) Boot_alloc: size=0x120 Boot_alloc: @ 0xfffe5030 Boot_alloc: remaining free block @ 0xfffe5150 (size=2b0) 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 Boot_alloc: size=0x4 Boot_alloc: @ 0xfffe5150 Boot_alloc: remaining free block @ 0xfffe5158 (size=2a8) Allocate cpu_mem @ 0xfffe5400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) for scheduling SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Boot_alloc: size=0x14 Boot_alloc: @ 0xfffe5158 Boot_alloc: remaining free block @ 0xfffe5170 (size=290) Boot_alloc: size=0x300 Boot_alloc: allocated extra memory block @0xfffe5800 (size=400) Boot_alloc: @ 0xfffe5800 Boot_alloc: remaining free block @ 0xfffe5b00 (size=100) Enable MSI support: chained IRQ mgr @ 0xfffe5150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 2694MHz 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:10c000;13ffff] [4:140000;18efff] [0:18f000;2dcfff] [4:2dd000;2ddfff] [0:2de000;3fffff] [0:46b000;10fffff] [4:1100000;8157fff] [0:8158000;b77fffff] [0:bb400000;bb7fdfff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:bb7fe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 2894324 KByte free memory MOE: found RAM from 1000 to bb7fe000 MOE: allocated 2999 KByte for the page array @0x46b000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [72cd000-73fca83] [C:503000] l4re BOOTFS: [73fd000-764b17c] [C:504000] ned BOOTFS: [764c000-8157390] [C:505000] io BOOTFS: [1100000-12058b9] [C:506000] rtc BOOTFS: [1206000-162cfce] [C:507000] mag BOOTFS: [162d000-17a6ebe] [C:508000] fb-drv BOOTFS: [17a7000-17a783a] [C:509000] lx_ginger.cfg BOOTFS: [17a8000-17a836c] [C:50a000] x86-legacy.devs BOOTFS: [17a9000-17a986f] [C:50b000] x86_android.vbus BOOTFS: [17aa000-1b58e4f] [C:50c000] vmlinuz.android BOOTFS: [1b59000-1c59000] [C:50d000] root-x86-ginger.img BOOTFS: [1c59000-72cd000] [C:50e000] system-x86-ginger.img MOE: cmdline: /home/akpolat/mysvn/l4android/l4android/src/src/l4/build/bin/x86_586/l4f/moe rom/lx_ginger.cfg MOE: Starting: rom/ned rom/lx_ginger.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/lx_ginger.cfg' 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 | Find root Pointer io | Find root Pointer: f09e0 io | ACPI: RSDP 0xf09e0 00014 (v00 BOCHS ) io | ACPI: RSDT 0xbb7ffbc1 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbff1c0, 0x80007d08, 0x80007d0c): UNINPLEMENTED io | ACPI: FACP 0xbb7ff1c0 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfe040, 0x80007ce8, 0x80007cec): UNINPLEMENTED io | ACPI: DSDT 0xbb7fe040 01180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbfe000, 0x80007ce8, 0x80007cec): UNINPLEMENTED io | ACPI: FACS 0xbb7fe000 00040 io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbff234, 0x80007d08, 0x80007d0c): UNINPLEMENTED io | ACPI: SSDT 0xbb7ff234 008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbffb11, 0x80007d08, 0x80007d0c): UNINPLEMENTED io | ACPI: APIC 0xbb7ffb11 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbffb89, 0x80007d08, 0x80007d0c): UNINPLEMENTED io | ACPI: HPET 0xbb7ffb89 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 144 Objects with 18 Devices 52 Methods 8 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 155 Objects with 32 Devices 42 Methods 1 Regions io | tbxfload-0274 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0175 [02] Enable : Transition to ACPI mode successful io | evgpeblk-0523 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:60:AcpiOsInstallInterruptHandler(9, 0x107d6c0, 0x3aa8): UNINPLEMENTED io | Completing Region/Field/Buffer/Package initialization:..................................... io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer io | <0xb120>IRQ [00000000000000-00000000000000 1] rising edge (32bit) (align=0 flags=44201) io | <0x16b38>IRQ [00000000000000-00000000000000 1] rising edge (32bit) (align=0 flags=44201) io | Ready. Waiting for request. mag | Hello from MAG fb | Trying execution of ``set VBE mode'' using x86emu fb | Found VESA BIOS version 3.0 fb | OEM SeaBIOS VBE(C) 2011 rtc | Date:21.07.2014 Time:15:05:38 Best Regards, Cem Akpolat

2 9

booting lx_ginger.iso
by cem akpolat 21 Jul '14

21 Jul '14

Hi, There is also issues while booting lx_ginger.iso (from l4android.org) it stems from the lx_ginger.cfg file. akpolat@akpolatX240:~/Desktop$ qemu-system-x86_64 -cdrom lx_ginger.iso -m 512 -serial stdio Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2011 TU Dresden Rev: r30 compiled with gcc 4.4.3 for Intel Pentium [.up] Build: #32 Tue Feb 15 10:07:33 CET 2011 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at 1fff8000 (4096Bytes) Enabling SVM support NASID: 0x10 ACPI-Init ACPI: RSDP = 0xf09e0 pRSDT = 1ffffbc1 pXSDT = 0 ACPI: OEM: BOCHS MADT = 0x203ffb11 IO-APIC[ 0]: struct: 0x203ffb45 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 @ 0xfeff6000 Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) 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. Absolute KIP Syscalls using: Sysenter CPU[0:0]: AuthenticAMD (6:6:3:0)[00000663] Model: Athlon (Palomino) at 2694 MHz 255/512 Entry I TLB (4K pages) 255 Entry I TLB (4M pages) 255/512 Entry D TLB (4K pages) 255 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) Freeing init code/data: 28672 bytes (7 pages) VMX: Not supported 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:10c000;13ffff] [4:140000;18ffff] [0:190000;2dbfff] [4:2dc000;2dcfff] [0:2dd000;3fffff] [0:469000;137dfff] [4:137e000;7883fff] [0:7884000;1d70ffff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:1fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 377736 KByte free memory MOE: found RAM from 1000 to 1d710000 MOE: allocated 471 KByte for the page array @0x1000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [137e000-146d25c] [C:503000] l4re BOOTFS: [146e000-165555b] [C:504000] ned BOOTFS: [1656000-1ea917f] [C:505000] io BOOTFS: [1eaa000-1f82d39] [C:506000] rtc BOOTFS: [1f83000-22812f8] [C:507000] mag BOOTFS: [2282000-23d7cf5] [C:508000] fb-drv BOOTFS: [908a000-908a83b] [C:509000] lx_ginger.cfg BOOTFS: [9064000-90643b7] [C:50a000] x86-legacy.devs BOOTFS: [9080000-908086f] [C:50b000] x86_android.vbus BOOTFS: [23d8000-28179f3] [C:50c000] vmlinuz.android BOOTFS: [2818000-2912000] [C:50d000] root-x86-ginger.img BOOTFS: [2913000-7884000] [C:50e000] system-x86-ginger.img MOE: cmdline: moe rom/lx_ginger.cfg MOE: Starting: rom/ned rom/lx_ginger.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/lx_ginger.cfg' io | Io service io | Hello from L4-ACPICA io | Find root Pointer io | AcpiOsMapMemory(40e, 2) = 40040e io | AcpiOsMapMemory(9fc00, 400) = 49fc00 io | AcpiOsMapMemory(e0000, 20000) = 4e0000 io | Find root Pointer: f09e0 io | AcpiOsMapMemory(f09e0, 24) = 4f09e0 io | ACPI: RSDP 0xf09e0 00014 (v00 BOCHS ) io | AcpiOsMapMemory(1ffffbc1, 24) = bffbc1 io | ACPI: RSDT 0x1ffffbc1 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | AcpiOsMapMemory(1ffffbc1, 34) = bffbc1 io | AcpiOsMapMemory(1ffff1c0, 24) = bff1c0 io | ACPI: FACP 0x1ffff1c0 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | AcpiOsMapMemory(1ffff1c0, 74) = bff1c0 io | AcpiOsMapMemory(1fffe040, 24) = bfe040 io | ACPI: DSDT 0x1fffe040 01180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | AcpiOsMapMemory(1fffe000, 24) = bfe000 io | ACPI: FACS 0x1fffe000 00040 io | AcpiOsMapMemory(1ffff234, 24) = bff234 io | ACPI: SSDT 0x1ffff234 008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | AcpiOsMapMemory(1ffffb11, 24) = bffb11 io | ACPI: APIC 0x1ffffb11 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | AcpiOsMapMemory(1ffffb89, 24) = bffb89 io | ACPI: HPET 0x1ffffb89 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | AcpiOsMapMemory(1fffe040, 1180) = bfe040 io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 144 Objects with 18 Devices 52 Methods 8 Regions io | AcpiOsMapMemory(1ffff234, 8dd) = bff234 io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 155 Objects with 32 Devices 42 Methods 1 Regions io | tbxface-0601 [02] TbLoadNamespace : ACPI Tables successfully acquired io | enable ACPI subsystem io | evxfevnt-0184 [02] Enable : Transition to ACPI mode successful io | AcpiOsMapMemory(1fffe000, 40) = bfe000 io | evgpeblk-1129 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | /home/mlange/projects/l4re/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:57:AcpiOsInstallInterruptHandler: UNINPLEMENTED io | initialize ACPI objects io | Completing Region/Field/Buffer/Package initialization:..................................... io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | evgpeblk-1234 [03] EvInitializeGpeBlock : Found 0 Wake, Enabled 16 Runtime GPEs in this block io | Interpreter enabled io | scanning for PCI root bridge io | Found PCI root bridge... io | Using IOAPIC for interrupt routing io | ACPICA-Version:20091214, System in ACPI MODE, 32bit timer io | WARNING: phys mmio resource allocation failed io | IOMEM * [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM * [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) io | IGNORE ACPI RES: 1 io | WARNING: phys mmio resource allocation failed io | IOMEM [000000000c0000-000000000fffff 40000] non-pref (32bit) (align=3ffff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [000000000c0000-000000000fffff 40000] non-pref (32bit) (align=3ffff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [0000000009f000-0000000009ffff 1000] non-pref (32bit) (align=fff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [0000000009f000-0000000009ffff 1000] non-pref (32bit) (align=fff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [00000000000000-00000000000fff 1000] non-pref (32bit) (align=fff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [00000000000000-00000000000fff 1000] non-pref (32bit) (align=fff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) io | WARNING: phys mmio resource allocation failed io | IOMEM [000000000a0000-000000000bffff 20000] non-pref (32bit) (align=1ffff flags=c002) io | WARNING: device 'PS2' already assigned to an other virtual bus. io | WARNING: device 'S18_' already assigned to an other virtual bus. io | Service registration failed: 'froyo_bus' io | Ready. Waiting for request. mag | Hello from MAG fb | Trying execution of ``set VBE mode'' using x86emu fb | VBE BIOS not present. fb | Failed to setup Framebuffer mag | Error: Exception: Void capability invoked: requesting goos info: backtrace ... mag | 1002e2f mag | 103f4a5 mag | 1000dcb mag | 10026de mag | 105390c mag | 10000e1 mag | mag | MAG: destroy FB svc Ned[lua]: Hm, cpapbility 436000 does not support the meta protocol: -2004 Ned: ERROR: rom/lx_ginger.cfg:82: attempt to call method 'create' (a nil value) rtc | Date:21.07.2014 Time:16:18:35 Br, Cem Akpolat

2 1

Timer Interrupt Handler
by Xavier LEBARS 21 Jul '14

21 Jul '14

Hi everyone, I'm always trying to configure the timer for my Zedboard and the system clock doesn't advance. I checked this in the Timer::system_clock() function In order to construct my timer driver, I use mptimer option, so I configured the private timer of my board in the file timer-arm-mptimer.cpp. Private Timers call the function interval() which use the global timer of the board (bsp/zynq/ timer-arm-mptimer-zynq.cpp file) Here is a part of the implementation of my global timer (I just launch counter) : Mmio_register_block t(Kmem::mmio_remap(Mem_layout::Gpt_phys_base)); t.write<Mword>(0, GPT_CR); t.write<Mword>(0, GPT_CNT0); t.write<Mword>(0, GPT_CNT1); t.modify<Mword>(GPT_CR_EN, 0, GPT_CR); Mword vc = start_as_counter(); while (t.read<Mword>(GPT_CNT0) < Gpt_ticks) ; Mword interval = (vc - stop_counter()) / Ticks; t.write<Mword>(0, GPT_CR); return interval; The private timers are bind to the GIC with the IRQ 27, so I mentioned this value in the static unsigned irq() function. GIC is initialized in the bsp/zynq/pic-arm-zynq.cpp file (similar to the iMX6 architecture) Pic::init() { typedef Irq_mgr_multi_chip<Gic_sz> M; M *m = new Boot_object<M>(1); gic.construct(Kmem::mmio_remap(Mem_layout::Gic_cpu_phys_base), Kmem::mmio_remap(Mem_layout::Gic_dist_phys_base)); m->add_chip(0, gic, gic->nr_irqs()); Irq_mgr::mgr = m; } To finish I saw timer_tick class. It seems to be a good way to update system clock because there are interrupts handler which call the update_system_clock function. So I added a call to the Timer_tick::setup() function in my startup-arm.cpp file after timer initialization. But when I boot the sytem I obtain the following message Panic - Could not allocate scheduling IRQ 27 The origin of this problem is the allocate_irq() function So do I have to modify something in my IRQ manager or did I forget one step during the construction of my timer driver ? Thanks in advance Best regards, Xavier Le Bars

2 4

Fiasco bug
by Zahi Rima 18 Jul '14

18 Jul '14

Hello, When building Fiasco like told here : https://os.inf.tu-dresden.de/fiasco/build.html I got the following errors : In file included from /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/kern/context.cpp:22, from /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/kern/switch_lock.cpp:85, from /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/kern/helping_lock.cpp:4, from /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/kern/lock.cpp:3, from /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/kern/kobject.cpp:3, from /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/kern/kobject_mapdb.cpp:5, from auto/kobject_mapdb.cc:3: /home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/src/lib/libk/cxx/function:34: error: 'cxx::functor<Res(Args ...)>::functor(cxx::functor<Res(Args ...)>&&)' cannot be defaulted make[1]: *** [kobject_mapdb.o] Error 1 make[1]: Leaving directory `/home/rima/Documents/FK/l4re-snapshot-2014053111/src/kernel/fiasco/mybuild' make: *** [all] Error 2 What Can I do to fix the problem ? Regards, Rima ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

2 1

l4lx_memory_map_virtual_page messages ending in internal error
by Uwe Geuder 18 Jul '14

18 Jul '14

Hi! As mentioned in a previous thread I tried xz compression of my initramfs image in L4Linux on ARM. When L4Linux tried to decompress the following messages occured: > Trying to unpack rootfs image as initramfs... > l4lx_memory_map_virtual_page: Already used, existing is 2400020 > l4lx_memory_map_virtual_page: cannot attach vpage (2ca64000, 2816324f): -99 > l4lx_memory_map_virtual_page: Already used, existing is 2400020 and the same messages (with increasing address) repeated for a zillion of times until it eventually ended like this: > l4lx_memory_map_virtual_page: cannot attach vpage (2ee44000, 25d4324f): -99 > l4linux | Non-resolvable page fault at 2ca64003, ip 2168884. > l4linux | Page fault (non-resolved): pfa=2ca64003 pc=2168884 > Unable to handle kernel paging request at virtual address 2ca64000 > pgd = 0234b000 > [2ca64000] *pgd=25d51811, *pte=2816324f, *ppte=00000000 > Internal error: Oops: 410807 [#1] ARM > Modules linked in: > CPU: 0 PID: 1 Comm: swapper Not tainted 3.14.0-l4 #14 > task: 2a03ba40 ti: 2a03c000 task.ti: 2a03c000 > PC is at dict_repeat.part.5+0x58/0x90 > LR is at lzma_main+0x984/0x990 > pc : [<02168884>] lr : [<02169240>] psr: 20000013 > sp : 2a03dd4c ip : 01c1f000 fp : 04205590 > r10: 00000003 r9 : 00000005 r8 : 2a12eee8 > r7 : 00006ee4 r6 : 00000000 r5 : 2a03ddf8 r4 : 2ae45000 > r3 : 00000042 r2 : 00000000 r1 : 01c1f000 r0 : 2a128018 > vcpu: b3000c00 vcpu-state: 00000000 > Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel > Process swapper (pid: 1, stack limit = 0x2a03c238) > Stack: (0x2a03dd4c to 0x2a03e000) > dd40: 2a128000 00000002 00000000 25eb0548 32e00000 > dd60: 00000000 2a128000 2a03ddf8 00000000 00006ee4 2a12eee8 00000005 00000003 > dd80: 04205590 021698e4 00000000 002457cc 00000000 00000003 00000000 2a03ddf8 > dda0: 2a0ec000 00000003 00000001 021681d4 02321480 02309f44 02321480 02321480 > ddc0: 00001000 002457cc 00001000 00000000 00001000 00000000 02350054 02309cd4 > dde0: 2a0ec000 00000000 00000000 32e00000 00000000 02317cdc 32e00000 002457cc > de00: 0444ad5c 2a0c7000 00000000 00001000 00000005 00000000 00000000 0444ad5c > de20: 32e00000 02321480 02321480 02350054 02309b64 0230a0f4 00000000 02350054 > de40: 02309b64 0230a670 00000000 00000000 0235004c 022cb7d0 022b4b24 02326db8 > de60: 02350050 00000000 02350000 0230a670 0000003d 02350050 0235004c 0230a6e4 > de80: 0000000a 00000000 023462a0 0231fee4 00000000 02249f60 00000005 02349a60 > dea0: 00000000 021c9620 2a03ba40 02349a60 02349a60 02350000 02346284 02346284 > dec0: 02353b0c 02346284 00000000 02326bcc 00000005 02350000 02350000 0230a670 > dee0: 0000003d 2a03c030 00000000 02000444 0224f3c0 020da7d8 0233d430 022bd31c > df00: 2a05f800 0224f3c0 000000db 00000000 00000000 00000005 023357fc 00000001 > df20: 2a899e3b 0225af94 0000003d 02032e5c 022f16d8 00000005 2a899e50 00000005 > df40: 023357f0 02326bcc 00000005 02350000 02350000 0230819c 0000003d 02321400 > df60: 023213f0 02308880 00000005 00000005 0230819c 0233e900 2a03b700 00000001 > df80: 00000000 00000000 02243ed8 00000000 00000000 00000000 00000000 00000000 > dfa0: 00000000 02243ee0 00000000 02007da8 00000000 00000000 00000000 00000000 > dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 > dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 > [<02168884>] (dict_repeat.part.5) from [<00000002>] (0x2) > Code: e281c001 e580c008 e282c001 e7d42002 (e7c42001) > ---[ end trace 0aaf617cdd732ae2 ]--- > Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b > > panic: going to sleep forever, bye > l4linux | panic: going to sleep forever, bye > What can I learn from these messages? The same image could be decompressed on the same hardware with a native Linux kernel. I know that my compression options were probably not optimal and the algorithm might have used a lot of memory. But I have seen out of memory messages from Moe and L4Linux before and they were easy to understand. So could this really be some time of internal error, i.e. bug? Regards, Uwe Geuder Nomovok Ltd. Tampere, Finland uwe.gxuder(a)nomovok.com (bot test: humans correct 1 obvious spelling error)

2 4

Question about function l4_sched_set_cpu_set
by Yuxin Ren 15 Jul '14

15 Jul '14

Hi I cannot understand the second and third arguments of this function. Could someone tell me how to use those arguments? Thank you Yuixn

2 1

Question about _wq in the class Sender
by Yuxin Ren 15 Jul '14

15 Jul '14

Hi, I note in the Sender class there is a variable "_wq". What is the role of this variable? And in the IPC, we set it to the sender_list of receiver. Why? Thank you. Yuxin

2 3

How to enable scheduling time in one-shot model
by Yuxin Ren 14 Jul '14

14 Jul '14

Hi All, I know in previous Fiasco kernel, there is a kernel option to use scheduling timer in one-shot model. But I cannot find this option in the latest Fiasco kernel. So now how can I enable this feature? In addition, where is the code for timer interrupt handler? Could someone give me some hints about that code? Thank you very much. Yuxin

3 2

User space filesystems for L4Linux
by Uwe Geuder 14 Jul '14

14 Jul '14

Hi! When looking at the examples and forum archives I get the impression that L4Linux users tend to work with ramdisks. However, in general I understand that in the Linux world ramdisks are considered mostly obsolete. Initramfs is the preferred solution https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/D… I replaced my disk image with a cpio archive suitable for initramfs and everything still works fine. Linux can dynamically recognize whether it is cpio or not. I understand my filesystem can grow dynamically until Linx runs out of memory. I dropped the ramdisk_size parameter from the kernel command line. Are there any drawbacks or pitfalls I am missing? The next step is compression. Both ramdisks and cpio archives can be compressed, again Linux can dynamically recognize that and uncompress before usage. (I have only tested cpio.gz so far, but I understand also disk images work and both faster lzo and more aggressive bzip2 and xz are supported.) However, when I tried to used my cpio.gz archive, the effect was zero. Someone had magically uncompressed my archive before making the U-Boot image. I tracked it down to the script src/l4/pkg/bootstrap/server/src/build.pl. > system("$prog_gzip -dc $file > $modname.ugz 2> /dev/null"); > $file = "$modname.ugz" if !$?; It unpacks everything that is gzip compressed. Maybe that is necessary for object or executable files, I see some assembly manipulation a couple of lines further down, which I have not analyzed. However, for disk images or initramfs archives I cannot see the point. So I made the following hack diff --git a/src/l4/pkg/bootstrap/server/src/build.pl b/src/l4/pkg/bootstrap/server/src/build.pl index 22382d6..a31743e 100755 --- a/src/l4/pkg/bootstrap/server/src/build.pl +++ b/src/l4/pkg/bootstrap/server/src/build.pl @@ -75,8 +75,13 @@ sub build_obj($$$) printf STDERR "Merging image %s to %s [%dkB]\n", $file, $modname, ((-s $file) + 1023) / 1024; # make sure that the file isn't already compressed - system("$prog_gzip -dc $file > $modname.ugz 2> /dev/null"); - $file = "$modname.ugz" if !$?; + if ($file =~ m/ramdisk-arm.rd$/) { + system("false"); + } else { + system("$prog_gzip -dc $file > $modname.ugz 2> /dev/null"); + } + $file = "$modname.ugz" if !$? ; + print "using ", $file ; system("$prog_objcopy -S $file $modname.obj 2> /dev/null") if $strip && !$no_strip; system("$prog_cp $file $modname.obj") This worked as expected, my disk image remained compressed and Linux could uncompress it a boot time. Of course it is a hack, because the file name should not be hard-coded there. Same question as before, am I missing anything here? Also build.pl would fail to do the uncompression if a module is compressed with lzo, bzip2 or xz. Yes, I have found the variable BOOTSTRAP_UIMAGE_COMPRESSION. It worked fine during image creation, but during boot U-Boot failed with > Verifying Checksum ... OK > Uncompressing Kernel Image ... Error: inflate() returned -5 > GUNZIP: uncompress, out-of-mem or overwrite error - must RESET board to recover > resetting ... I assume this could be fixed by modiyfing the memory map. However, because my kernel is very small compared to the user space image and Linux has this nice dynamic support for various compression schemes I think I prefer an uncompressed U-Boot image containing a compressed user space image. Regards, Uwe Geuder Nomovok Ltd. Tampere, Finland uwe.gxuder(a)nomovok.com (bot test: humans correct 1 obvious spelling error)

2 2

Pid 1 crashing under L4Linux
by Uwe Geuder 09 Jul '14

09 Jul '14

Hi! I'm pretty new to L4 so I hope this is not an FAQ. I tried to search the forum archives but couldn't find an answer. I'm using L4 on an i.MX6 device. Building fiasco, L4Re and L4Linux succeeded without any errors as far as I can tell. A small ramdisk containing busybox works fine and I can play around on the command line. (The system actually has framebuffer support, so I can even get something on the screen.) Now I replaced the small "demo" ramdisk by one containing a bigger distro. This bigger ramdisk runs without problems on a native Linux kernel. However, on L4Linux I always get > RAMDISK: ext2 filesystem found at block 0 > RAMDISK: Loading 262144KiB [1 disk] into ram disk... > EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities > EXT4-fs (ram0): couldn't mount as ext2 due to feature incompatibilities > EXT4-fs (ram0): mounted filesystem with ordered data mode. Opts: (null) > VFS: Mounted root (ext4 filesystem) readonly on device 1:0. > Freeing unused kernel memory: 116K (022f9000 - 02316000) > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 > > CPU: 0 PID: 1 Comm: sh Not tainted 3.14.0-l4 #7 > [<0200c47c>] (unwind_backtrace) from [<02005618>] (show_stack+0x10/0x14) > [<02005618>] (show_stack) from [<02238d08>] (panic+0x8c/0x1c8) > [<02238d08>] (panic) from [<020186bc>] (complete_and_exit+0x0/0x1c) > [<020186bc>] (complete_and_exit) from [<00000001>] (0x1) > panic: going to sleep forever, bye > l4linux | panic: going to sleep forever, bye > The stack trace is the same for init=/bin/sh and the default systemd. Looks like for some reason user space processes in this setup just crash pretty soon. The console log before that looks pretty unsuspicious to me. But I can of course post it should it be necessary to understand what is going on. What comes to my mind is that my user space is built for armv7tnhl, i. e. thumb instruction set, NEON, and hard-float. > -march=armv7-a -mfloat-abi=hard -mfpu=neon -mthumb Can any of these options be a problem under L4? (The small busybox ramdisk, which works fine was built by a colleague of mine who is on holidays at the moment. I'm not sure how he built it, but I assume it's neither hard-float nor thumb. Well, I could disassemble something to be sure I guess...) If armv7tnhl does not cause obvious problems, do you have any debugging hints/pointers how to find out why/where pid 1 is crashing? Address 0x1 is nonsense I suppose, but if tells anything then that the processor is in thumb mode. Which is what I would expect from my user space. Regards, Uwe Geuder Nomovok Ltd. Tampere, Finland uwe.gxuder(a)nomovok.com (bot test: humans correct 1 obvious spelling error)

2 2

MOE uses memory originally from IO device
by Martin Schröder 09 Jul '14

09 Jul '14

My board is equipped with 128MB external DRAM: > L4 Bootstrapper > Build: #1234 Do 3. Jul 17:34:17 CEST 2014, 4.6.2 > Scanning up to 128 MB RAM > Memory size is 128MB (40000000 - 47ffffff) > RAM: 0000000040000000 - 0000000047ffffff: 131072kB > Total RAM: 128MB In addition the CPU has 128kb internal RAM (so called On-Chip-RAM) which is located at address 0 - 0001ffff. I want to expose this OCRAM as a virtual device to a (already existing) kernel driver within l4linux, so I added these few lines to my config: > OCRAM => new Device() { > .hid= "ocram"; > new-res Mmio(0x00000000 .. 0x0001FFFF); > } > > client0 => new System_bus() { > ... > "ocram" = wrap(hw-root.OCRAM); > } Unfortunately IO cannot map this device, but maps instead something else which is of no use for me: > io | <0x1bff0>IOMEM [00000000000000-0000000001ffff 20000] non-pref (32bit) (align=1ffff flags=4002) > io | WARNING: phys mmio resource allocation failed > io | <0x1bff0>IOMEM [00000000000000-0000000001ffff 20000] non-pref (32bit) (align=1ffff flags=4002) > io | allocated resource: <0x1bff0>IOMEM [00000001000000-0000000101ffff 20000] non-pref (align=1ffff flags=4002) But a few lines up I see: > MOE: Hello world! > MOE: found 109032 KByte free memory > MOE: found RAM from 40000000 to 47000000 > ... Probably MOE assumes this as normal ram and adds it to its pool. But how can I inhibit MOE grabbing this piece of RAM and instead assign it to the OCRAM device in IO? Best regards, Martin

2 4

Fwd: Problems using qemu devices from l4re
by Maria Soler 08 Jul '14

08 Jul '14

Hello, I am running l4re on qemu (qemu-system-arm) and I have been trying to use a qemu device from l4re, but I have been unsuccessful so far. This device creates a file in the host and that is how I have been testing if I was actually writing/reading on the device: I was trying to write from the guest and read from the host (didn't work) and trying to write from the host and read from the guest, but didn't work either. What I have tried so far: - I have tried to use sigma0_map_iomem like this: --------------------------------------------- string = malloc(SIZE); l4sigma0_map_iomem(L4_BASE_PAGER_CAP, 0xXXXXXXXX, string, SIZE, 1); //I have tried both cached and uncached. printf("Received: %s\n",string); //prints nothing, regardless of the content of the file in the host memset(p,'a',SIZE); //the file in the host remains unchanged --------------------------------------------- The qemu device is mapped in address 0xXXXXXXXX and its size is bigger than SIZE. SIZE is a multiple of 4KB and so is 0xXXXXXXXX. I have tried to use this option by itself and combined with an io server (I actually tried this first, but now that I have seen that there is no difference in the behavior if I add it or remove it, I think they are maybe unrelated or most probably I am not using them the right way). To create the io server I have included an app.io file as follows: --------------------------------------------- -- Example configuration for io local hw = Io.system_bus() -- Configure two platform devices to be known to io Io.hw_add_devices { comm = Io.Hw.Device { hid = "COMM"; Io.Res.irq(63); Io.Res.mmio(BASE_ADDR, TOP_COMM); }, data = Io.Hw.Device { hid = "DATA"; Io.Res.irq(63); Io.Res.mmio(TOP_COMM+0x1000, TOP_DATA); } } Io.add_vbusses { -- Create a virtual bus for a client and give access to the device prodb = Io.Vi.System_bus { comm_bus = wrap(hw:match("comm")); data_bus = wrap(hw:match("data")); } } --------------------------------------------- and added to my .cfg file: --------------------------------------------- vbus = l:new_channel(); -- Start io l:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; input = vbus_prodb:svr(); }, }, "rom/io rom/app.io"); l:start( { prodb = vbus:svr(); log = { "app", "green" } }, "rom/app" , { FSTAB_FILE = "rom/fstab" } ); --------------------------------------------- Both with and without the io server, the application compiles and runs, but there is no communication with the file in the host, so I guess I am not mapping the device in the right way. I have also tried to use libio instead of sigma0 as follows: --------------------------------------------- string = malloc(SIZE); l4io_request_iomem(0xXXXXXXXX, SIZE, 1, string); //I have tried both cached and uncached. printf("Received: %s\n",string); //prints nothing, regardless of the content of the file in the host memset(p,'a',SIZE); //the file in the host remains unchanged --------------------------------------------- And this warning appears: app | libio: Warning: Query of 'vbus' failed! but it runs, so I don't really know what I am doing wrong. There is no complete example that I have found with either libio or sigma0, so I need some hints on this, please. Thank you! María.

4 6

Question abut DRQ handler
by Yuxin Ren 07 Jul '14

07 Jul '14

Hi, When I go through the IPC code, I have some questions about dqr handler. In the remote_ipc_send function within the thread-ipc.cpp file, I find a comment " // trigger remote_ipc_receiver_ready path, because we may need to grab locks // and this is forbidden in a DRQ handler. So transfer the IPC in usual // thread code. However, this induces a overhead of two extra IPIs." I have some questions about this comment. 1. Why cannot we grab locks in a DRQ handler? 2. Where do we need to grab lock? 3. Why can extra IPI solve this problem? Thank you very much. Best, Yuxin

2 5

Delay::measure function
by Xavier LEBARS 04 Jul '14

04 Jul '14

Hi everyone, I’m currently trying to port Fiasco + L4re with the « Hello World » application on a Zedboard which has a Xilinx Zynq z7020 processor (ARM Cortex A9 MPCore). We already configure UART and Timer for the microkernel but boot crash after the step : Calibrating Timer loop… Our problem seems to occur during the execution of Delay::measure() function. Does anyone know what it exactly does and especially update_timer which seems to have no effect in our case. Here is the boot execution trace : # Booting kernel from Legacy Image at 03000000 ... Image Name: L4 Image #42 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 868352 Bytes = 848 KiB Load Address: 01100000 Entry Point: 01100000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 02000000 ... Image Name: Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5619903 Bytes = 5.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02a00000 Booting using the fdt blob at 0x2a00000 Loading Kernel Image ... OK Loading Ramdisk to 1f5d2000, end 1fb2e0bf ... OK Loading Device Tre L4 Bootstrapper Build: #42 Tue Jul 1 15:59:58 CEST 2014, 4.7.3 Scanning up to 512 MB RAM Memory size is 512MB (00100000 - 200fffff) RAM: 0000000000100000 - 00000000200fffff: 524288kB Total RAM: 512MB mod04: 011ba000-011d3578: hello mod03: 011a0000-011b9458: l4re mod02: 0116e000-0119f624: moe mod01: 01164000-0116d33c: sigma0 mod00: 01115000-011638e8: fiasco Moving up to 5 modules behind 1200000 moving module 00 { 1115000-11638e7 } -> { 12bf000-130d8e7 } [321768] moving module 01 { 1164000-116d33b } -> { 130e000-131733b } [37692] moving module 02 { 116e000-119f623 } -> { 1318000-1349623 } [202276] moving module 03 { 11a0000-11b9457 } -> { 1200000-1219457 } [103512] moving module 04 { 11ba000-11d3577 } -> { 121a000-1233577 } [103800] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x110e000-0x110e0e2] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x102000 Regions of list 'regions' [ 101000, 101b3f] { b40} Kern fiasco [ 102000, 15efff] { 5d000} Kern fiasco [ 190000, 1965fb] { 65fc} Sigma0 sigma0 [ 198000, 19e17b] { 617c} Sigma0 sigma0 [ 240000, 26cacb] { 2cacc} Root moe [ 270000, 286f0f] { 16f10} Root moe [ 1100000, 11143f3] { 143f4} Boot bootstrap [ 110a000, 110a0a6] { a7} Boot mbi [ 110e000, 110e1df] { 1e0} Root Multiboot info [ 1114048, 111409f] { 58} Boot mbi [ 1200000, 1233577] { 33578} Root Module API Version: (87) experimental Sigma0 config ip:00190100 sp:01113de4 Roottask config i�Hello from Startup::stage2 Number of IRQs available at this GIC: 96 Cache config: ON ID_PFR[01]: 00001231 00000011 ID_[DA]FR0: 00010444 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00102111 L2: ID=410000c8 Type=9e300300 Aux=72360000 WMask=ff S=0 L2: Type L2C-310 Size = 512kB SERIAL ESC: allocated IRQ 59 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: f5bb6d4 compiled with gcc 4.7.3 for zynq [] Build: #69 Tue Jul 1 15:59:21 CEST 2014 Calibrating timer loop... Thanks in advance Best Regards Xavier

2 3

Doubts about File Systems on FIASCO on ARM (Cortex-A15)
by Maria Soler 03 Jul '14

03 Jul '14

Hello, I would need to use file system facilities, but I am not sure how this is done. I can already use rom/ and also tmpfs, but neither is exactly what I need. I need to create persistent files that are written in disk from applications running on FIASCO (directly, not using L4Linux as an intermediary). I would also need to load (these or other) files from disk in run time (loading all files as modules in rom may not be the best solution, specially since we need to create new files "on the go" and be able to load them from other applications. Is there any module/library/whatever in FIASCO that offers this? If there is one, how can we use it/where can we find information about it? In case this is relevant, our applications are in C and we are to run FIASCO in TrustZone Crotex-A15 (in secure mode). Best regards, María.

4 7

Re: Thanks Martin !! I got Ethernet on L4 Linux !!
by Taeung 02 Jul '14

02 Jul '14

Hi, Martin Sorry for late answer. I was very busy because of my company. On 06/26/2014 05:58 PM, Martin Schröder wrote: > Am 26.06.2014 09:05, schrieb Taeung: >> Hi, Martin >> >> Great to see again :-) >> > > Yeah :-) > >> The reason of that I disabled 'L4_CLK_NOOP' is as below. >> When I added SD/MMC device driver and etc options in menuconfig, I met >> error message as below. > > >> So, in order to solve this problem, I modified source code at first and >> amended Kconfig file thereafter. >> > > Ok, that makes sense. > > What about your progress with fiasco? I've succeeded in loading two L4Linux and running MPI program in each. And I've succeeded in getting Ethernet which can connect external network. > Did you manage to get everything running you need? Interesting to hear > that SD/MMC is running on your system. But I've failed in getting SD/MMC despite loading MMC driver and registering MMC device in IO server. I guess that there is problems in mach-setup.c (about PHY?) like previous a problem of Ethernet. Somehow I guess that some modification in mach-setup.c is needed. > I use it only temporary for booting U-Boot and will be removed later. Me,too I can't use SD card in L4 Linux yet. > > What I am missing is support for NAND and NOR (via SPI), but next week > I will start this task. > > Currently I am stumbling with IPC. I have about 12 different Linux > processes communicating via Unix Sockets in each direction. Now I want > to have 6 on one l4linux an 6 on another l4linux. I got it working by > using the l4shmnet driver and TCP-Sockets, but IP is not allowed and > the Linux IP-Stack must be removed, so I have to use something else. > Unfortunately I don't know of any ready-to-use alternative, so I have > to do it on my own. > I haven't try to do IPC in two L4 Linux. Did you make sure you enable it as below? =============================== L4Linux configuration ---> Features ---> Make Linux be a server Stub drivers ---> l4shm based network driver =============================== > Best regards from Berlin, > Martin. > > >

1 0