<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [skl] Hard lockup (Freeze) after reset failure: GPU HANG: ecode 9:0:0x85dffffb" href="https://bugs.freedesktop.org/show_bug.cgi?id=109949#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [skl] Hard lockup (Freeze) after reset failure: GPU HANG: ecode 9:0:0x85dffffb" href="https://bugs.freedesktop.org/show_bug.cgi?id=109949">bug 109949</a> from <a class="email" href="mailto:arcadiy@ivanov.biz" title="Arcadiy Ivanov <arcadiy@ivanov.biz>"> Arcadiy Ivanov</a> <pre>My machine just survived a GPU hang on F30 5.0.13 and remained operational. [ 4860.674981] [drm] GPU HANG: ecode 9:2:0xa8dfbffd, in chromium-vaapi [4647], reason: hang on vcs0, action: reset [ 4860.674984] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 4860.674985] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 4860.674986] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 4860.674986] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 4860.674987] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 4860.675052] i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 [ 4868.658707] i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 [ 4876.658545] i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 [ 4884.659343] i915 0000:00:02.0: Resetting vcs0 for hang on vcs0 [ 4892.658365] i915 0000:00:02.0: Resetting vcs0 for hang on vcs0</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>