[Bug 89913] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [960], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

matthias.a.lee at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW
           Assignee|intel-gfx-bugs at lists.freede |matthias.a.lee at gmail.com
                   |sktop.org                   |

--- Comment #3 from matthias.a.lee at gmail.com ---
Created attachment 115009
  --> https://bugs.freedesktop.org/attachment.cgi?id=115009&action=edit
another dump file

It looks like the issue has happened again:
[ 2768.504078] [drm] stuck on render ring
[ 2768.506913] [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [931], reason:
Ring hung, action: reset
[ 2768.506914] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 2768.506915] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 2768.506915] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 2768.506916] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 2768.506917] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2768.512055] drm/i915: Resetting chip after gpu hang


This is on Kernel 4.0 RC7

Error file has been attached

-- 
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/20150410/0b6274bb/attachment.html>