[Bug 91976] New: GPU HANG: ecode 4:1:0x01000000, reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Sep 11 04:50:15 PDT 2015


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

            Bug ID: 91976
           Summary: GPU HANG: ecode 4:1:0x01000000, reason: Ring hung,
                    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: jikos at jikos.cz
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 118215
  --> https://bugs.freedesktop.org/attachment.cgi?id=118215&action=edit
/sys/class/drm/card0/error contents after resume

Currentl mainline kernel (HEAD == b0a1ea51) gives me this on resume from
hibernation:

[   78.816182] [drm] stuck on bsd ring
[   78.824503] [drm] GPU HANG: ecode 4:1:0x01000000, reason: Ring hung, action:
reset
[   78.824779] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[   78.824784] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[   78.824789] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[   78.824793] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[   78.824798] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   78.826876] drm/i915: Resetting chip after gpu hang


Attaching /sys/class/drm/card0/error contents as well.

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


More information about the intel-gfx-bugs mailing list