[Bug 80080] New: [drm] GPU HANG: ecode 0:0xf5f7fffe, in X [2754], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 80080
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [drm] GPU HANG: ecode 0:0xf5f7fffe, in X [2754],
                    reason: Ring hung, action: reset
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: milan at cmm.ki.si
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Intel
           Product: DRI

Created attachment 101144
  --> https://bugs.freedesktop.org/attachment.cgi?id=101144&action=edit
copy of /sys/class/drm/card0/error

It says in dmesg I should file a new bug although 79248 seems similar:

[Mon Jun 16 07:17:49 2014] [drm] stuck on render ring
[Mon Jun 16 07:17:49 2014] [drm] GPU HANG: ecode 0:0xf5f7fffe, in X [2754],
reason: Ring hung, action: reset
[Mon Jun 16 07:17:49 2014] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Mon Jun 16 07:17:49 2014] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Mon Jun 16 07:17:49 2014] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Mon Jun 16 07:17:49 2014] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Mon Jun 16 07:17:49 2014] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Mon Jun 16 07:17:51 2014] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp
off

-- 
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/20140616/f34b25b8/attachment.html>