[Bug 82962] New: stuck on render ring

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 82962
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: stuck on render ring
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: michael.mauch at gmx.de
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

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

While using Google Maps in Chromium Version 36.0.1985.125, the Chromium window
hung and got darkened, and the dmesg output told me to file a bug report here:

[ 1323.166255] [drm] stuck on render ring
[ 1323.166264] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1323.166265] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 1323.166266] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 1323.166277] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 1323.166278] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 1323.169518] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo
(0x4868000 ctx 7) at 0x486ab38

This is on Ubuntu 14.04 (recently upgraded from 12.04.5), with an Ubuntu kernel
patched with this DVBSky driver:
http://www.dvbsky.net/download/linux/media_build-bst-13-140619.tar.gz

-- 
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/20140822/79e59a7b/attachment-0001.html>