<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=106342#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=106342">bug 106342</a> from <a class="email" href="mailto:thiago@kde.org" title="Thiago Macieira <thiago@kde.org>"> Thiago Macieira</a> <pre>Created <a href="attachment.cgi?id=139619" name="attach_139619" title="card0_error 2018-05-17">attachment 139619</a> <a href="attachment.cgi?id=139619&action=edit" title="card0_error 2018-05-17">[details]</a> card0_error 2018-05-17 dmesg: [89982.954152] [drm] GPU HANG: ecode 9:0:0x8adfb5fe, in krunner [2949], reason: Hang on rcs0, action: reset [89982.954155] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [89982.954156] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [89982.954156] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [89982.954157] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [89982.954157] [drm] GPU crash dump saved to /sys/class/drm/card0/error [89982.954178] i915 0000:00:02.0: Resetting rcs0 after gpu hang [89984.169411] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [89984.169486] i915 0000:00:02.0: Resetting chip after gpu hang [89985.386115] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [89986.148508] asynchronous wait on fence i915:X[2695]/0:171977 timed out [89986.708558] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [89988.032543] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [89988.140506] i915 0000:00:02.0: Failed to reset chip The only difference this time is that it did not happen immediately after resuming from hibernation, but after about a minute. I managed to log in and see my desktop. It wasn't until I tried to use krunner that the hang was reported. I'm going to go now one week without using the USB-C dock. Let's see if the hang happens without that.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>