l4x_hybrid_return for ovlscreen driver

[Adam Lackorzynski]

Hi Marc,

On Wed Nov 07, 2007 at 11:05:49 +0100, Marc CHALAND wrote:
> With Nitpicker, I try to start X server with ovlscreen driver. After a
> little while, I get the following message :
> l4lx    | l4x_hybrid_return: Invalid hybrid return for 23.00 (0x0688d570, e, 0,
> l4lx    :  -1, f0020d5d)!
> l4lx    | l4x_hybrid_return: Currently running: 00.00
> 
> After some debugging and tracing, I've found that this message happens
> when X server does a rmgr_get_task_id on names. I don't understand why
> this IPC fails as ping_call perfectly works (I enabled traces on
> roottask and saw ping_component call).

I've just tried to reproduce something like this but I had no 'luck'. I
also do not understand how the code path can be taken with the given
values. I suppose your sources are up to date? Is this reliably
reproducible?

> I tried to enable IPC monitoring with I* into jdb, but I get an
> assertion in Fiasco :
> Assertion failed: 'this == current()'
>   in /home/chaland/l4/tudos/kernel/fiasco/src/kern/context.cpp:512
>   at f0023378

Oh. Would you be able to build a test case for me?


Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/