[Bug 74060] New: [drm] stuck on render ring
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Jan 25 15:54:25 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=74060
Priority: medium
Bug ID: 74060
CC: intel-gfx-bugs at lists.freedesktop.org
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [drm] stuck on render ring
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: holgersson at posteo.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 92789
--> https://bugs.freedesktop.org/attachment.cgi?id=92789&action=edit
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
--
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/20140125/5e40a910/attachment.html>
More information about the intel-gfx-bugs
mailing list