Comment 155 for bug 296167

Thanks for the update Peter, it's highly appreciated!

> Here's a braindump of what I know so far.
> I have not been able to reproduce the bug yet and since everything so far
> indicates a race condition, this is not an easy one to track down. This
> information is from a (very) remote ssh debugging session.

I'm still able to reproduce it 100% of the time by using a keyboard shortcut in KDE to move a window from one screen to another. As soon as the mouse
cursor in the middle of the moving window crosses the screen border,
the window stops moving -> the keyboard events go somewhere else, too.

Would it help if I set you up a box with two graphic cards and full root access to reproduce the thing? We have an IP ready KVM switch so you could access it from the outside like a normal user. Though reconfiguring all this stuff and putting it in a DMZ will require some time...

> Reports that the bug occurs more frequently under load indicate that too.
> The one lead I have is that mi/mipointer.c stuff is being called both during
> SIGIO handling and during event processing, but I haven't found any
> significant overlap yet.

Hmm, also smells like an -EAGAIN error code issue. Suppose some code is in the middle of a read/write and a signal fires, you're read/write call will be interrupted with -EAGAIN. Even without a signal firing, if a box is under load the kernel can issue -EAGAIN for IO operations f.e. on sockets.