users October 2012

users@lists.genode.org

18 participants
14 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users October 2012