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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Apr 30 09:39:30 UTC 2017


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

            Bug ID: 100888
           Summary: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1134],
                    reason: Engine(s) hung, action: reset
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: iwypyski at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 131159
  --> https://bugs.freedesktop.org/attachment.cgi?id=131159&action=edit
GPU hang ecode 9:0:0x84dffff8

dmesg:

[10576.039149] [drm] stuck on render ring
[10576.039457] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1134], reason:
Engine(s) hung, action: reset
[10576.039460] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[10576.039463] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[10576.039466] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[10576.039468] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[10576.039470] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[10576.041273] drm/i915: Resetting chip after gpu hang
[10578.039620] [drm] RC6 on

The /sys/class/drm/card0/error is in attachment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170430/546dae03/attachment-0001.html>


More information about the intel-gfx-bugs mailing list