<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [kbl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg" href="https://bugs.freedesktop.org/show_bug.cgi?id=105146#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [kbl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg" href="https://bugs.freedesktop.org/show_bug.cgi?id=105146">bug 105146</a> from <a class="email" href="mailto:simonmorgan@slimjimsoftware.co.uk" title="Simon <simonmorgan@slimjimsoftware.co.uk>"> Simon</a> <pre>Hopefully this may help. I've had the same issue since an upgrade to Mesa 17.3.4. This was easily and consistently reproducible when using NetBeans 8.2, opening a file browser and clicking on an empty area of the horizontal scroll bar so as to get the file browser to jump further along the files list. Every time I tried this it would consistently cause the screen to hang, the mouse would work but nothing else responded. After a couple of minutes I would be dropped out of the desktop andf back to the login manager. Running dmesg gave me not much more than the following: [ 5072.768779] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [11414], reason: Hang on rcs0, action: reset [ 5072.768785] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 5086.777610] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 5096.761705] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 5104.761736] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 5112.761783] i915 0000:00:02.0: Resetting rcs0 after gpu hang I tried all of the Intel driver fixes posted around various forums across the internet but nothing worked, the only thing that has finally stopped this was downgrading to Mesa 17.3.2. After the downgrade to Mesa 17.3.2 I can no longer reproduce this error. This is an Arch Linux system with the latest vanilla 4.14.20 kernel running the Plasma (KDE) desktop.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>