Vaclav Slavik schrieb:
> Hi again,
> 
> another reply with a bit more information:
> 
> Denis Oliver Kropp wrote:
>>> (!) [ 1076:   19.429] --> Caught signal 4 (at 0xbe826a2c, illegal
>>> trap) <--

If 0xbe826a2c is the intruction pointer you should be able to find
out which function it is in.

>>> (!) FUSION_PROPERTY_LEASE    --> Connection timed out

Most likely due to the clock skew, or a dead lock. Do you know if there
was a feelable delay between this and the previous message?

>>> (!) [ 1076:   19.521] --> Caught signal 11 (at (nil), invalid
>>> address) <--
>>> Killed
>> Do you also have kernel messages regarding this?
> 
> No, just tons of  messages like "Fusion: fusion_ioctl (0x40040403)".


#if 0  <-=
#define DEBUG(x...)  printk (KERN_DEBUG "Fusion: " x)
#else
#define DEBUG(x...)  do {} while (0)
#endif

You might want to set it back to "0" for performance reasons.

>>> Unfortunately, using no-vt-switching doesn't help much: we don't
>>> get that assumption failure above, but the app still receives
>>> SIGILL (on resume this time), with useless gdb backtrace.
>> Please build with "--enable-trace" that maintains a copy of the
>> call stack and therefore even helps if you have stack corruption.
> 
> It didn't help, the stack was too corrupted for DFB's code too.
> 
> We found out that the app produces SIGILL when any signal is sent to 
> it after resume. Furthermore, the vt_thread receives an unexpected 
> signal when suspending:
> 
> (-) [VT Switcher     187.483] ( 1122) DirectFB/core/layers: suspended.
> (-) [VT Switcher     187.483] ( 1122) DirectFB/core/screens: 
> suspending...
> (-) [VT Switcher     187.484] ( 1122) DirectFB/core/screens: 
> suspended.
> (-) [VT Switcher     187.487] ( 1122) FBDev/VT:          ...vt_thread 
> (signal -1)

The -1 just indicates that the vt_thread() loop is waiting for signals
again.

-- 
Best regards,
   Denis Oliver Kropp

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/                 |
"------------------------------------------"

_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to