Comment 68 for bug 43154

(In reply to comment #13)
> (In reply to comment #12)
>
> > It probably has something to do with it, but what's the bug number and/or
> > Bugzilla where it was reported? Looking for #8641 in this Bugzilla leads to
> > closed one: "xcb should provide (and use in generated C files) opcode defines."
>
> I found it - it's in the kernel Bugzilla:
> http://<email address hidden>/msg31026.html
>
> These problems look like being connected for me. I'm not a kernel hacker
> (although I've read both Linux Kernel Development, 2nd Edition and
> Understanding Linux Kernel ;-) but if you'd need someone with real hardware to
> help debugging, I'm ready to do this job.
>

Thanks for your offer. We probably would need the real hardware to trigger the same kind of conditions needed to cause this failure. Your dmesg logs should report the error about IRQs as soon as X is loaded. I'm pretty sure we would all see the error message.

I'm not a real kernel hacker either. ;-) It seems to me that if we approach this problem from both ends(both bugs) we may stand a better chance of solving this quickly. Although there is still the possiblity that they may entirely be unrelated.

Another thing we can verify is to put printk's in the kernel in exactly the same way I said and run different games and 3d applications and verify that the same root cause persists. If they are the same, we get added confirmation about the root cause.

We can, in the meantime continue working on this in our spare time and hope for a breakthrough quickly. What seems to be the priority to me is to eliminate libGL, libGLX and pinpoint the bug on the kernel DRM code. All my investigations point to it, but it is always good to be more sure. ;-)