Bug 80691

Summary: [snb] GPU HANG: ecode 0:0xf4e9fffe, in X [2924], reason: Ring hung, action: reset
Product: Drivers Reporter: Toralf Förster (toralf.foerster)
Component: Video(DRI - Intel)Assignee: intel-gfx-bugs (intel-gfx-bugs)
Status: RESOLVED MOVED    
Severity: normal CC: chris, intel-gfx-bugs
Priority: P3    
Hardware: All   
OS: Linux   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=54226
Kernel Version: 3.15.6 Subsystem:
Regression: No Bisected commit-id:
Attachments: /var/tmp/i915_error_state.20140719-200222.txt.gz

Description Toralf Förster 2014-07-19 18:08:05 UTC
Created attachment 143521 [details]
/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
Comment 1 Jani Nikula 2014-09-23 14:28:18 UTC
Chris, care to take a look at this one please?
Comment 2 Chris Wilson 2014-09-24 12:06:28 UTC
Another fdo bug 54226.
Comment 3 Jani Nikula 2014-09-24 12:29:36 UTC
(In reply to Chris Wilson from comment #2)
> Another fdo bug 54226.

Thanks Chris.

Closing, we'll track this at https://bugs.freedesktop.org/show_bug.cgi?id=54226. Thanks for the report.