Bug 74060

Summary: [drm] stuck on render ring
Product: DRI Reporter: holgersson
Component: DRM/IntelAssignee: Chris Wilson <chris>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
log from /sys/class/drm/card0/error none

Description holgersson 2014-01-25 23:54:25 UTC
Created attachment 92789 [details]
log from /sys/class/drm/card0/error

[ 3687.336359] [drm] stuck on render ring
[ 3687.336371] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 3687.336375] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 3687.336378] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 3687.336382] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 3687.336385] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 3687.345748] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x9603000 ctx 0) at 0x962c67c
i915 crashes from time to time (sometimes after severals minutes uptime, sometimes works hours flawless).

Machine: gentoo/amd64 with gentoo-sources 3.13.0-r1

The error message:

[ 3775.542181] type=1006 audit(1390674600.081:5): pid=9385 uid=0 old auid=4294967295 new auid=1000 old ses=4294967295 new ses=4 res=1
[ 4455.336276] [drm] stuck on render ring
[ 4455.336395] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x935e000 ctx 0) at 0x935e0e0
[ 4543.339569] [drm] stuck on render ring
[ 4543.340574] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x943c000 ctx 0) at 0x9461450
[ 4575.339558] [drm] stuck on render ring
Comment 1 Chris Wilson 2014-01-26 09:43:38 UTC

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

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.