[Bug 79500] New: [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 79500
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [drm:ring_stuck] *ERROR* Kicking stuck semaphore on
                    render ring
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: idokan at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg 6.7.0
         Component: DRM/Intel
           Product: DRI

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

Found using dmseg the following comments:
[336793.293018] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[336793.293023] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[336793.293024] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[336793.293024] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[336793.293025] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[336793.293026] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.

I'm using Arch Linux, x86_64 with:
 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)

xf86-video-intel 2.99.911-2

If I'm missing required information, please tell, me, so I could provide it
here.

-- 
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/20140601/e9df7f7e/attachment.html>