[Bug 85689] New: stuck on render ring, reporting as told in dmesg

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 85689
           Summary: stuck on render ring, reporting as told in dmesg
           Product: DRI
           Version: XOrg CVS
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: karolherbst at me.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

dmesg output:

[ 2086.402678] [drm] stuck on render ring
[ 2086.403370] [drm] GPU HANG: ecode 0:0x00200000, in kwin_x11 [2320], reason:
Ring hung, action: reset
[ 2086.403371] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 2086.403372] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 2086.403372] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 2086.403372] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 2086.403373] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2086.403425] [drm:intel_pipe_set_base] *ERROR* pin & fence failed
[ 2105.418015] [drm] stuck on render ring
[ 2105.418751] [drm] GPU HANG: ecode 0:0x00200000, in kwin_x11 [2320], reason:
Ring hung, action: reset

the X server was nearly completly frozen after this error, but restarting
kwin_x11 from tty helped.

software I am using:

linux-3.17.1
xorg-server-1.16.1
xf86-video-intel-2.99.916
libdrm-2.4.58
mesa-git-1a17098

-- 
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/20141031/22629231/attachment-0001.html>