Summary: | GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1543], reason: Engine(s) hung, action: reset | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | John M. <alt.ya-5e0t5ys> | ||||
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: | alt.ya-5e0t5ys, intel-gfx-bugs, m.ion | ||||
Version: | XOrg git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
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 130943 [details] /sys/class/drm/card0/error These are dmesg messages: ################################## [drm] stuck on render ring [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1543], reason: Engine(s) hung, action: reset [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm] GPU crash dump saved to /sys/class/drm/card0/error drm/i915: Resetting chip after gpu hang [drm] RC6 on ################################## Enclodes is the value dumped from /sys/class/drm/card0/error