[Bug 82277] New: stuck on render and blitter rings "[drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning!"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Aug 6 21:46:47 PDT 2014


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

          Priority: medium
            Bug ID: 82277
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: stuck on render and blitter rings
                    "[drm:i915_context_is_banned] *ERROR* gpu hanging too
                    fast, banning!"
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: other
          Reporter: np.hardass at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Running Gentoo on arch amd64.


/var/log/messages:

[337260.499843] [drm] stuck on render ring
[337260.499847] [drm] stuck on blitter ring
[337260.500552] [drm] GPU HANG: ecode 0:0xf4e9fffe, in X [32567], reason: Ring
hung, action: reset
[337260.500554] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[337260.500555] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[337260.500557] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[337260.500558] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[337260.500559] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[337260.500611] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast,
banning!

-- 
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/20140807/75d9317c/attachment-0001.html>


More information about the intel-gfx-bugs mailing list