[Bug 100738] New: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1543], reason: Engine(s) hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 100738
           Summary: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1543],
                    reason: Engine(s) hung, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: alt.ya-5e0t5ys at yopmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 130943
  --> https://bugs.freedesktop.org/attachment.cgi?id=130943&action=edit
/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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
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-gfx-bugs/attachments/20170420/5536f5da/attachment.html>