| Summary: | GPU HANG: ecode 9:0:0x42edb95c, in Xorg [3895], reason: Hang on render ring, action: reset | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Erik Falor <ewfalor> | ||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Status: | CLOSED DUPLICATE | 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: | ||||||
| Attachments: |
|
||||||
commit bafb2f7d4755bf1571bd5e9a03b97f3fc4fe69ae Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Sep 21 14:51:08 2016 +0100 drm/i915/execlists: Reset RING registers upon resume There is a disparity in the context image saved to disk and our own bookkeeping - that is we presume the RING_HEAD and RING_TAIL match our stored ce->ring->tail value. However, as we emit WA_TAIL_DWORDS into the ring but may not tell the GPU about them, the GPU may be lagging behind our bookkeeping. Upon hibernation we do not save stolen pages, presuming that their contents are volatile. This means that although we start writing into the ring at tail, the GPU starts executing from its HEAD and there may be some garbage in between and so the GPU promptly hangs upon resume. Testcase: igt/gem_exec_suspend/basic-S4 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=96526 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/20160921135108.29574-3-ch ris@chris-wilson.co.uk *** This bug has been marked as a duplicate of bug 96526 *** |
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 134624 [details] /sys/class/drm/card0/error contents Some Google Chrome and Opera gets into a state where their windows do not update, and the programs appear unresponsive. Some of their child processes will begin using 100% CPU. My other X11 programs remain unaffected (mostly urxvt). Logging out of Xorg is not sufficient to restore functionality; I must I go down to runlevel 1 and back the problem goes away. I finally noticed the following in my dmesg: [ +4.013261] [drm] GPU HANG: ecode 9:0:0x42edb95c, in Xorg [3895], reason: Hang on render ring, action: reset [ +0.000003] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ +0.000001] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ +0.000001] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ +0.000001] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ +0.000002] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ +0.000058] drm/i915: Resetting chip after gpu hang [ +0.001575] [drm] RC6 on [ +0.016133] [drm] GuC firmware load skipped [ +9.965862] drm/i915: Resetting chip after gpu hang [ +0.001992] [drm] RC6 on [ +0.018227] [drm] GuC firmware load skipped Please find the dri error log attached