[Bug 100956] New: [drm] GPU HANG: ecode 6:0:0xa4fffffc, in Xorg [2659], reason: Hang on render ring, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun May 7 10:27:25 UTC 2017


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

            Bug ID: 100956
           Summary: [drm] GPU HANG: ecode 6:0:0xa4fffffc, in Xorg [2659],
                    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: carcinoma at gmx.net
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 131239
  --> https://bugs.freedesktop.org/attachment.cgi?id=131239&action=edit
/sys/class/drm/card1/error

Hi,

i found this in my dmesg:

[  401.719777] [drm] GPU HANG: ecode 6:0:0xa4fffffc, in Xorg [2659], reason:
Hang on render ring, action: reset
[  401.719778] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[  401.719779] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[  401.719780] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  401.719780] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[  401.719781] [drm] GPU crash dump saved to /sys/class/drm/card1/error
[  401.719822] drm/i915: Resetting chip after gpu hang

an so i do create a _new_ bug report.

I don't know what i did during that time.

-- 
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/20170507/316bea6f/attachment.html>


More information about the intel-gfx-bugs mailing list