[Bug 101604] New: GPU HANG: ecode 6:0:0x85fffffc, in PrisonArchitect [14305], reason: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jun 27 04:44:09 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=101604
Bug ID: 101604
Summary: GPU HANG: ecode 6:0:0x85fffffc, in PrisonArchitect
[14305], reason: Hang on render ring, action: reset
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: naoliv at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 132272
--> https://bugs.freedesktop.org/attachment.cgi?id=132272&action=edit
Error output from /sys/class/drm/card0/error
While playing Prison Architect I am seeing some freezes in the system.
In dmesg I can see:
=====
[117160.350557] [drm] GPU HANG: ecode 6:0:0x85fffffc, in PrisonArchitect
[14305], reason: Hang on render ring, action: reset
[117160.350559] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[117160.350559] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[117160.350560] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[117160.350560] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[117160.350561] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[117160.350592] drm/i915: Resetting chip after gpu hang
[117445.409355] drm/i915: Resetting chip after gpu hang
=====
error output is attached.
System is running a Debian's 4.9.0-3-amd64 kernel
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170627/129e25b6/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list