[Bug 106342] [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=106342

--- Comment #17 from Thiago Macieira <thiago at kde.org> ---
Created attachment 139841
  --> https://bugs.freedesktop.org/attachment.cgi?id=139841&action=edit
card0_error 2018-05-29

Nope, the USB-C dock is not an influence. This GPU hang happened without any
USB-C connection.

[203461.307996] [drm] GPU HANG: ecode 9:0:0x22bfff23, in krunner [51086],
reason: Hang on rcs0, action: reset
[203461.308001] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[203461.308004] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[203461.308006] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[203461.308009] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[203461.308012] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[203461.308074] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[203462.520867] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[203462.520996] i915 0000:00:02.0: Resetting chip after gpu hang
[203463.739120] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[203464.424718] asynchronous wait on fence i915:X[2357]/0:3f9891 timed out
[203465.063100] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[203466.384830] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[203466.492741] i915 0000:00:02.0: Failed to reset chip

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180530/8e56cb06/attachment.html>