[Bug 80691] New: GPU HANG: ecode 0:0xf4e9fffe, in X [2924], reason: Ring hung, action: reset

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=80691

            Bug ID: 80691
           Summary: GPU HANG: ecode 0:0xf4e9fffe, in X [2924], reason:
                    Ring hung, action: reset
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.15.6
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: toralf.foerster at gmx.de
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 143521
  --> https://bugzilla.kernel.org/attachment.cgi?id=143521&action=edit
/var/tmp/i915_error_state.20140719-200222.txt.gz

either with recent 3.15.x ekrnels or with recent KDE 4.13.x this bug seems to
appear (slightly) more oftne than before :


Jul 19 20:02:12 n22 kernel: [drm] stuck on render ring
Jul 19 20:02:12 n22 kernel: [drm] stuck on blitter ring
Jul 19 20:02:12 n22 kernel: [drm] GPU HANG: ecode 0:0xf4e9fffe, in X [2924],
reason: Ring hung, action: reset
Jul 19 20:02:12 n22 kernel: [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
Jul 19 20:02:12 n22 kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Jul 19 20:02:12 n22 kernel: [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
Jul 19 20:02:12 n22 kernel: [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
Jul 19 20:02:12 n22 kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Jul 19 20:02:12 n22 kernel: [drm:i915_context_is_banned] *ERROR* gpu hanging
too fast, banning!
Jul 19 20:02:14 n22 kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp
on

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.