Summary: |
drm/i915 GPU HANG: stuck on render ring |
Product: |
DRI
|
Reporter: |
Simmo Saan <simmo.saan> |
Component: |
DRM/Intel | Assignee: |
Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: |
CLOSED
INVALID
|
QA Contact: |
Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: |
normal
|
|
|
Priority: |
medium
|
CC: |
intel-gfx-bugs
|
Version: |
unspecified | |
|
Hardware: |
x86-64 (AMD64) | |
|
OS: |
Linux (All) | |
|
Whiteboard: |
|
i915 platform:
|
|
i915 features:
|
GPU hang
|
Attachments: |
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 135015 [details] /sys/class/drm/card0/error dump After coming back to my locked laptop (Xubuntu 16.04) the screen was unresponsive. SSHing in had this in dmesg: [12352.526878] [drm] stuck on render ring [12352.527343] [drm] GPU HANG: ecode 8:0:0xbf746ffe, in Xorg [1157], reason: Ring hung, action: reset [12352.527345] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [12352.527346] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [12352.527347] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [12352.527348] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [12352.527349] [drm] GPU crash dump saved to /sys/class/drm/card0/error [12352.529474] drm/i915: Resetting chip after gpu hang [12358.527200] [drm] stuck on render ring [12358.527677] [drm] GPU HANG: ecode 8:0:0xbf746ffe, in Xorg [1157], reason: Ring hung, action: reset [12358.527757] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [12358.528992] drm/i915: Resetting chip after gpu hang [13092.568048] [drm] stuck on render ring [13092.568632] [drm] GPU HANG: ecode 8:0:0x0a177ffe, in Postman [9474], reason: Ring hung, action: reset [13092.570766] drm/i915: Resetting chip after gpu hang