Bug 82277 - stuck on render and blitter rings "[drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning!"
Summary: stuck on render and blitter rings "[drm:i915_context_is_banned] *ERROR* gpu h...
Status: CLOSED DUPLICATE of bug 54226
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) other
: medium normal
Assignee: Jani Nikula
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-07 04:46 UTC by NP-Hardass
Modified: 2017-07-24 22:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Gentoo's emerge --info (17.75 KB, text/plain)
2014-08-07 04:47 UTC, NP-Hardass 		no flags Details
/sys/class/drm/card0/error (2.12 MB, text/plain)
2014-08-07 04:49 UTC, NP-Hardass 		no flags Details
View All

Description NP-Hardass 2014-08-07 04:46:47 UTC 
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!
Comment 1 NP-Hardass 2014-08-07 04:47:28 UTC 
Created attachment 104191 [details]
Gentoo's emerge --info

provide system information
Comment 2 NP-Hardass 2014-08-07 04:49:00 UTC 
Created attachment 104192 [details]
/sys/class/drm/card0/error

gpu crash dump
Comment 3 Chris Wilson 2014-08-07 05:43:52 UTC 

*** This bug has been marked as a duplicate of bug 54226 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.