[Bug 100898] New: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon May 1 23:50:25 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=100898
Bug ID: 100898
Summary: Hang on render ring, action: reset
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: javierdo1 at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 131170
--> https://bugs.freedesktop.org/attachment.cgi?id=131170&action=edit
error
Following instructions:
Playing a game for a really long time triggered this error. Just upgraded to
new kernel yesterday, Linux sam-endor-txomon-com 4.10.11-1-ARCH #1 SMP PREEMPT
Tue Apr 18 08:39:42 CEST 2017 x86_64 GNU/Linux
[40843.464095] [drm] gpu hang: ecode 9:0:0x85dffffb, in ftl [19224], reason:
hang on render ring, action: reset
[40843.464096] [drm] gpu hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[40843.464097] [drm] please file a _new_ bug report on bugs.freedesktop.org
against dri -> drm/intel
[40843.464097] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[40843.464097] [drm] the gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[40843.464098] [drm] gpu crash dump saved to /sys/class/drm/card0/error
[40843.464204] drm/i915: resetting chip after gpu hang
[40843.464249] [drm] rc6 on
[40843.478939] [drm] guc firmware load skipped
[40863.460949] drm/i915: resetting chip after gpu hang
[40863.461072] [drm] rc6 on
[40863.476338] [drm] guc firmware load skipped
[40883.514335] drm/i915: resetting chip after gpu hang
[40883.514450] [drm] rc6 on
[40883.529686] [drm] guc firmware load skipped
[40900.580967] drm/i915: resetting chip after gpu hang
[40900.581076] [drm] rc6 on
[40900.593201] [drm] guc firmware load skipped
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170501/af9e1dbf/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list