users

users@lists.genode.org

2357 discussions

GRUB Error 16: Inconsistent filesystem structure when try to load core in Genode/NOVA demo
by Bill Chappell 02 Nov '12

02 Nov '12

I am trying to run the Genode(12.08)/NOVA demo as a boot option under Legacy GRUB following the "official" Genode instructions. When GRUB executes the line "module <path>/core", it halts with Error 16 as in the subject line. Also if I use full paths, no symlinks. When I edit the Genode Demo entry as GRUB runs and delete everything below the "kernel hypervisor" line, NOVA loads, reports 2 cores, and halts because "no ELF". "file core" reports that core is a 32 bit ELF. I have successfully run the Genode demo on top of Ubuntu 12.04 LTS and the Genode/NOVA demo on top of Ubuntu 12.04 LTS. GRUB savedefault is false. I tried the patch to stage2/fsys_iso9660.c with no luck. I have used both an IBM ThinkCentre and an HP laptop (6530b) with both Legacy GRUB and Legacy GRUB with Trusted GRUB patches. "The Google" is out of suggestions. Thank you.

2 2

Issue in Arora
by Ivan Loskutov 30 Oct '12

30 Oct '12

Hello. In the latest version of Genode didn't work Arora browser. I have messages in log: no RM attachment (READ pf_addr=0 pf_ip=14b05e4 from 60e000) virtual void Genode::Pager_activation_base::entry(): Could not resolve pf=0 ip=14b05e4 I tried to investigate this issue. I launched Arora with gdb-server: Program received signal SIGSEGV, Segmentation fault. 0x000632e3 in l4_ipc_call (timeout=..., snd_tag=<optimized out>, dest=<optimized out>, u=<optimized out>) at /home/ivan/projects/genode/ genode-ksyslabs-staging/_build.foc_x86_32/include/x86/l4f/l4/sys/ipc -l42-gcc3-nopic.h:54 54 ); (gdb) bt #0 0x000632e3 in l4_ipc_call (timeout=..., snd_tag=<optimized out>, dest=<optimized out>, u=<optimized out>) at /home/ivan/projects/genode/ genode-ksyslabs-staging/_build.foc_x86_32/include/x86/l4f/l4/sys/ipc -l42-gcc3-nopic.h:54 #1 l4_irq_receive_u (utcb=<optimized out>, to=<optimized out>, irq=<optimized out>) at /home/ivan/projects/genode/genode-ksyslabs -staging/_build.foc_x86_32/include/l4/sys/irq.h:254 #2 l4_irq_receive (to=<optimized out>, irq=<optimized out>) at /home/ivan /projects/genode/genode-ksyslabs-staging/_build.foc_x86_32/include/l4/sys/ irq.h:303 #3 thread_stop_myself () at /home/ivan/projects/genode/genode-ksyslabs -staging/base-foc/src/base/lock/lock_helper.h:105 #4 Genode::Cancelable_lock::lock (this=0x11b6648) at /home/ivan/projects/ genode/genode-ksyslabs-staging/base/src/base/lock/lock.cc:100 #5 0x011b65d8 in _stack_low () #6 0x011b6648 in _stack_low () #7 0x01096ba2 in Genode::Lock::lock (this=0x11b6614) at /home/ivan /projects/genode/genode-ksyslabs-staging/base/include/base/lock.h:35 #8 0x01096fa4 in block (this=0x11b6614) at /home/ivan/projects/genode/ genode-ksyslabs-staging/base/include/base/semaphore.h:46 #9 down (this=0x11b65d4) at /home/ivan/projects/genode/genode-ksyslabs -staging/base/include/base/semaphore.h:155 #10 main (argc=18572648, argv=0x0) at /home/ivan/projects/genode/genode- ksyslabs-staging/qt4/src/lib/qt_main/qt_main.cc:70 What may cause this error? How to debug in such cases? -- Ivan Loskutov

2 1

gdb_monitor_interactive & noux_gdb script problem on pandaboard
by 서재권 30 Oct '12

30 Oct '12

2 1

Issue in lwip
by Ivan Loskutov 26 Oct '12

26 Oct '12

Hello, I have an issue in lwip again. I ported the xmlrpc++ library to genode but simple test is failed. I have messages in log: no RM attachment (READ pf_addr=28 pf_ip=1183823 from 2df000) invalid signal-context capability virtual void Genode::Pager_activation_base::entry(): Could not resolve pf=28 ip=1183823 I tried to trace the error and found then the issue occurred in select function in lwip. Xmlrpc++ server does this call and sometime occurred this error. The error occurred in select function and control doesn't return to server code. The same code on host worked without issues. Sample code is in commit https://github.com/Ksys-labs/genode/commit/f567619f5f0a50e7eed74e9565ddae13… I ran the server in qemu and client from xmlrpc++ on my host. Any ideas? -- Ivan Loskutov

2 3

Trouble porting linux driver to DDE Kit
by Alexander Tarasikov 25 Oct '12

25 Oct '12

Hi, Genode crowd! I've been porting the MUSB OTG driver for the OMAP4 platform to the Genode Framework. I have implemented the following: * some linux routines for platform devices (to manage resources) * added code for some stubs in dde kit (strings, mutexes, spin locks) * the I2C driver class for Genode and ported the OMAP4 I2C driver * the TWL controller routines to read/write registers * misc omap4 phy init (clocks and other registers) This has allowed me to compile and run the musb driver and the gadget drivers (zero, ethernet) from the linux kernel. However, I've been desperately trying to figure out why it is not working. I have enabled all the levels of debugging in the usb drivers and have dumped the MUSB FIFO in both linux and genode. The good thing is that the data is not all zeroes or all ones, but correct usb requests starting with 0x80. I think this indicates memory IO is working. The bad thing is that under linux I get the correct usb requests (80 06, that is, GET_DESCRIPTOR). Under genode I either get SET_DESCRIPTOR or SET_ADDRESS all the time and the host (desktop) says "device descriptor read/64, error -32". Does anyone have any idea what may have gone wrong? IO and register access seems to work so I'm lost here. I have pushed the code to my github if you may want to try it out yourself git://github.com/astarasikov/genode.git The branch is omap4-otg-dirty. I have also pushed the 'contrib' directory because I was lazy to prepare the patches and fight Makefiles until the driver is working. My run script is called "panda_otg.run" (in my personal directory, astarasikov/run). I have also made the kernel message dumps in linux and genode so that it's possible to compare how usb behaves. I have also disabled L2 cache in uboot since it caused a lot of trouble with framebuffer previously. http://pastebin.ca/2239708 http://pastebin.ca/2239709 Note that I have the commented out the setting up interrupts part for the omap4 twl. Actually, zero is returned as the default irq number which is timer. I have tested with both the correct irq number and the zero interrupt, it does not affect anything - in both cases the device does detect when the cable is plugged, but fails to set up the connection. -- Regards, Alexander

5 15

Using negative cache index
by Ildar Ismagilov 22 Oct '12

22 Oct '12

In function Req_cache::remove on ports-foc/src/lib/l4lx/genode_block.cc file: void remove(void *packet, void **request) { int idx = _find(packet); if (idx < 0) { *request = 0; PERR("Req cache entry not found!"); } *request = _cache[idx].req; // <--- if idx is -1, this negative index used for access _cache array elements _cache[idx].pkt = 0; _cache[idx].req = 0; } should be: void remove(void *packet, void **request) { int idx = _find(packet); if (idx < 0) { *request = 0; PERR("Req cache entry not found!"); } else { *request = _cache[idx].req; _cache[idx].pkt = 0; _cache[idx].req = 0; } } -- Best regards Ildar

3 3

Bug of 1G memory use.
by v.shilkin 15 Oct '12

15 Oct '12

Bug of 1G memory use. *Description:* When allow system using more than 512M of memory, user level apps execution can cause ‘Segmentation fault’ or glibc error. * Reproduction:* *On PandaBoard:* _In bootstrap_: in /base-foc/contrib/l4/mk/platforms/pandaboard.conf/ if set /PLATFORM_RAM_SIZE_MB = *1024*/ (whole physical memory present on PandaBoard)// // And if allow L4Linux using more than 512M memory: when modify run script: ‘/ports-foc/run/linux_panda.run’:/__ <start name="vmlinux.1" priority="-1"> <binary name="l4linux"/> <resource name="RAM" quantum="796M"/> <config args="mem=*754M* l4x_rd=initrd.gz"> <block label="sda" /> </config> </start> *(754M* is given for example*)* System boots up. But user level apps can cause ‘Segmentation fault’ or glibc error. Error is stable on command ‘*find*’ on fresh-booted system. *On**QEMU:*** To support 1G of memory on Realview platform file ‘/base-foc/contrib/l4/pkg/bootstrap/server/src/platform/rv.cc’/ (attached) was modified. (Address regions got from platform documentation.) On system boot below error occurs: /Assertion failed: 'idx < _nchips' [ret=0xf006f214]/ //Projects/l4bsdd/base-foc/contrib/kernel/fiasco/src/kern/irq_mgr_multi_chip.cpp:76 at f0007c00/ There is no such error if Fiasco.OC was built with –O1 gcc option (only with –O2), but L4Linux can’t boot anyway because of memory allocation error. Best regards, Vladimir Shilkin

2 1

Power saving feature in Genode and Fiasco.OC
by Steve 12 Oct '12

12 Oct '12

I really appreciate you for sharing this excellent platform. :) As I titled, I'm wondering if Genode and Fiasco.OC have power saving features, especially on a Panda board. For example, reducing voltage, lowering frequency, and so on. I heard that Genode and Fiasco.OC with L4Linux consume more power than a native linux in the idle state (on the Panda board). Best regards, Steve

2 1

Non-existing service tolerance
by Markus Partheymueller 11 Oct '12

11 Oct '12

Hi Folks, I recently stumbled across an issue when connecting to a service that is non-essential for the child. Currently, the connection attempt, although surrounded by a try-catch block, leads to an abort call by init. While this seems logical for essential services, it is not intended for service connections that are optional. I'd rather that one could try to connect to the service and react to a failure of this attempt in a way the client has to define. If the client can live without the service, it should be allowed to carry on. In my opinion, this decision should be up to the client, not to the service framework of genode. Is there any chance to find out if a service exists without getting aborted? Any hint would be appreciated. Cheers Markus

3 2

Service Nic not yet available
by Markus Partheymueller 11 Oct '12

11 Oct '12

Hi Folks, I'm trying to use the dde_ipxe NIC driver, but when I connect to the service from within a launchpad-launched app, I get this message: [init -> launchpad] init: service Nic not yet available - sleeping But prior to that, the service was actually announced: [init] child "nic_drv" announces service "Nic" When I create the connection in the launchpad app, it works fine. The relevant config snippets are: <start name="nic_drv"> <resource name="RAM" quantum="2M"/> <provides> <service name="Nic"/> </provides> <route> <any-service><any-child/><parent/></any-service> </route> </start> <start name="launchpad"> <resource name="RAM" quantum="2G"/> <configfile name="launchpad-config"/> <route> <any-service><any-child/><parent/></any-service> </route> </start> And within the launchpad-config: <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> <service name="SIGNAL"/> <service name="Nitpicker"/> <service name="Timer"/> <service name="Nic"/> </parent-provides> <start name="testapp"> <binary name="testapp"/> <resource name="RAM" quantum="4M"/> <route> <service name="Timer"><parent/></service> <service name="Input"><child name="fb"/></service> <service name="Framebuffer"><child name="fb"/></service> <any-service><parent/></any-service> </route> </start> Am I missing something? Cheers, Markus

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users