[Bug 99359] New: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1016], reason: Hang on render ring, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 11 10:28:42 UTC 2017


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

            Bug ID: 99359
           Summary: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1016],
                    reason: Hang on render ring, action: reset
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: bugzilla at rvanderhoff.org.uk
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 128888
  --> https://bugs.freedesktop.org/attachment.cgi?id=128888&action=edit
GPU crash dump

[389854.637836] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU
pipe A FIFO underrun
[389867.846601] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1016], reason:
Hang on render ring, action: reset
[389867.846604] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[389867.846606] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[389867.846608] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[389867.846609] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[389867.846611] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[389867.846802] drm/i915: Resetting chip after gpu hang

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list 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/20170111/35f68b8e/attachment.html>


More information about the intel-gfx-bugs mailing list