users

users@lists.genode.org

2285 discussions

Start a nNew thread

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

l4linux block driver bugs
by i.ismagilov 10 Oct '12

10 Oct '12

Thanks for fast fixing of 'SD card doesn't start due to I/O pages caching' bug. But SD card still doesn't normally work on PandaBoard. It seems that there are 2 more problems with it. * * *Bug 1.* File cache subsystem generates an interrupt processing error _at intensive read/write access to SD card_: in Vcpu interrupts are disabled in the place where they should be allowed (/ports-foc/contrib/l4linux/fs/buffer.c:1231/). The same error occurs in qemu in other sub-system (/ports-foc/contrib/l4linux/kernel/softirq.c:159/) *Solution:* Function prototype in /ports-foc/src/lib/l4lx/include/linux.h/: /FASTCALL void l4x_irq_save(unsigned long *flags*); /should be: /FASTCALL void l4x_irq_save(unsigned long **flags*);/ So, value of interrupt state (enabling/disabling) was not properly stored before above correction. *Bug 2.* L4Linux 'hangs' because of problem with its virtual block device _at intensive read/write access to SD card on PandaBoard_. In Genode block driver memory for storing of packages sent via IPC sometimes is over /(ports-foc/src/lib/l4lx/genode_block.cc:281)/. In such case L4Linux virtual block driver is blocked on semaphore /(ports-foc/src/drivers/genode_block.c:98)/. When memory for IPC packages storage in Genode block driver becomes ready for use, driver sends signal to the thread '*blk-signal-thread*' /(ports-foc/src/lib/l4lx/genode_block.cc:126)/. Thread 'blk-signal-thread' catches the signal and generates interrupt by calling function '*l4_irq_trigger*' /(ports-foc/src/lib/l4lx/genode_block.cc:154)/. But, L4Linux doesn't catch the interrupt and hangs. In normal case interrupt is to be catched and interrupt handler '*event_interrupt*' /(ports-foc/src/drivers/genode_block.c:172)/ should be called; increment semaphore counter by 1 (/ports-foc/src/drivers/genode_block.c:146/) and thus un-block L4Linux driver.

2 3

SD service of Genode master branch for Fiasco.OC / PandaBoard doesn’t start
by i.ismagilov 04 Oct '12

04 Oct '12

*_Bug:_* SD service of Genode master branch _for Fiasco.OC / PandaBoard_ doesn’t start with *"SD command error"* (occurs in /os/src/drivers/sd_card/omap4/mmchs.h/:824). *_ _* *_Description:_**__* L4_FPAGE_BUFFERABLE constant (/base-foc/src/base/ipc/pager.cc/:91) is used to configure I/O memory region. In *Fiasco.OC *this constant is prepared as Page::*BUFFERED* (/base-foc/contrib/kernel/fiasco/src/kern/arm/paging-arm.cpp/:65). In *Fiasco.OC revision* *38* this constant is equal to *0x04* (for both ARMv6 and ARMv7). In revision 40 it was changed to *0x40*. This modification causes SD card driver error (and possible other driver errors) for ARMv6 and v7 architectures. *0x04*value seems to correspond to *‘Device’ memory type* (for I/O). Memory pages corresponding to I/O are non-cacheable. *0x40*value is seems for ‘Normal’ memory type. *Pages are cached* in this case but *this is not allowed for I/O* and causes SD card error. *_Solutions:_* 1) Page::*BUFFERED* constant seems to be _used for I/O only_, not for RAM (currently). So, we propose to set Page::BUFFERED constant to 0x40 in rev. 40 as it was in rev. 38 (*see attached patch*). 2) If Page::BUFFERED constant is planned to use _for RAM memory also_, some other constant for I/O memory pages configuring and related workaround in Genode driver to be added.

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users