l4-hackers October 2011

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

17 participants
16 discussions

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

13 Oct '11

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

2 3

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

07 Oct '11

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

2 5

Ankh examples
by Ivan Loskutov 05 Oct '11

05 Oct '11

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

2 2

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

05 Oct '11

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

3 3

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

03 Oct '11

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

2 1

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

02 Oct '11

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

3 8

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers October 2011