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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 9 08:30:17 UTC 2016


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

            Bug ID: 97252
           Summary: [drm] stuck on render ring
           Product: DRI
           Version: XOrg git
          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: bzb at poczta.onet.pl
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 125625
  --> https://bugs.freedesktop.org/attachment.cgi?id=125625&action=edit
system log and gpu crash dump

>From time to time when I start some WebGL application in chrome, I get this
error:

[64414.495102] [drm] stuck on render ring
[64414.496855] [drm] GPU HANG: ecode 7:0:0x85dffffc, in chrome [3388], reason:
Ring hung, action: reset
[64414.496859] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[64414.496862] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[64414.496864] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[64414.496866] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[64414.496869] [drm] GPU crash dump saved to /sys/class/drm/card0/error


I get this error on both Mesa 11.2 (ubuntu 16.04) and 12.1 (updated from
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers)

GPU crash dump is attached.

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


More information about the intel-gfx-bugs mailing list