[Bug 94408] New: [drm] stuck on render ring

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Mar 5 23:09:08 UTC 2016


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

            Bug ID: 94408
           Summary: [drm] stuck on render ring
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: olivier at bluefish.openoffice.nl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 122121
  --> https://bugs.freedesktop.org/attachment.cgi?id=122121&action=edit
GPU crash dump saved to /sys/class/drm/card0/error

while playing Team Fortress:

[1386590.432674] [drm] stuck on render ring
[1386590.432692] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[1386590.432695] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[1386590.432706] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[1386590.432713] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[1386590.432715] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[1386590.438564] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo
(0xfb94000 ctx 1) at 0xfb95320
[1386596.430946] [drm] stuck on render ring
[1386602.405246] [drm] stuck on render ring

This is the first time this happened. And I have played this game many times.
Could be a cosmic ray hitting the GPU ;-)

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


More information about the intel-gfx-bugs mailing list