<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#c5">Comment # 5</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>FWIW I have an r600+si dual-radeon system that until recently has been trucking along like a champ (after I fix the output name duplication bug which I have filed a bug for here and a patch). Lately I get these lockups all the damn time. I see stack traces somewhat like yours, OP. Best way I have to trigger them, although they are infuriatingly intermittent and unpredictable, is to play wine video games -- I didn't realize the fullscreen component but I usually have something fullscreen on one screen or another so that may be the same here. FWIW I run the bleeding-edge KF5 compositor. I am reluctant to leave my system in the state these lockups leave me and debug them because I'm scared about shit burning up on me (although sometimes it happens when I'm not around and sits there for hours in this state I admit). I haven't entirely ruled out bad hardware on either side of the PCIe bus, but I have more-or-less ruled out thermal crisis as the root cause.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>