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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 7 09:41:23 UTC 2018


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

--- Comment #54 from Romek <lollul at wp.pl> ---
I have Lenovo S300, Kabylake, kernel 4.19.4, Arch, KDE desktop + chromium. Been
getting this issue ever since I've started to use this laptop (a year or so).
Crash happen only after resume from hibernation. Sometimes immediately when
logging back, sometimes in a matter of minutes.

[56572.472400] [drm] GPU HANG: ecode 9:0:0x893bdd9d, in chromium [15360],
reason: hang on rcs0, action: reset
[56572.472402] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[56572.472403] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[56572.472403] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[56572.472404] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[56572.472404] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[56572.473413] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[56572.475145] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[56572.475181] i915 0000:00:02.0: Resetting chip for hang on rcs0
[56572.477939] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[56572.585555] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[56572.692218] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[56572.797101] i915 0000:00:02.0: Failed to reset chip
[56572.799896] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20181207/3cac6684/attachment.html>


More information about the intel-3d-bugs mailing list