<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - DRI_PRIME crash with fullsceen programs." href="https://bugs.freedesktop.org/show_bug.cgi?id=91491#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - DRI_PRIME crash with fullsceen programs." href="https://bugs.freedesktop.org/show_bug.cgi?id=91491">bug 91491</a> from <a class="email" href="mailto:gmt@be-evil.net" title="Greg Turner <gmt@be-evil.net>"> Greg Turner</a> <pre>(In reply to Greg Turner from <a href="show_bug.cgi?id=91491#c10">comment #10</a>) > Unfortunately, I tried DRI3 and it was way, way worse, suggesting Kristian > and I don't have the same problem (except maybe "memory corruption"). Scratch that. Just found that backporting (maybe that's not technically the right word -- I simply applied the patch without incident) commit 25eca802656 from xorg-server to 1.18.0 fixes the DRI3-mode trouble I was formerly able to repeatably cause by moving gl windows around between crtc's. That makes it much more plausible OP and I suffer from the same bug since, but for this known and already-fixed-upstream problem, my issue also seems to be fixed by moving to DRI3. Also, after my huge full-system rebuild I see much better behavior overall on this box. So, as I kind of suspected, some kind of toolchain or reverse-dependency issue remains a plausible cause of my non-repeatable lockups under DRI2. I'll move back to DRI2 now*, stress the hell out of this machine (I do so naturally in the course of my day-to-day activities) and if everything works we can infer my issue was caused by something other than a bug in xorg. -- * For a while, at least. DRI3 is /so/ much less janky here than DRI2 was, I'm fairly eager to migrate for good.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>