[Bug 97692] GPU HANG: ecode 9:0:0x85dffffb, in Borderlands2 [3497], reason: Engine(s) hung, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Sep 19 20:05:35 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=97692
--- Comment #8 from marco.grimaldi at gmail.com ---
Hi,
I forgot to add the dmesg output in the last update:
[ 572.424996] [drm] stuck on render ring
[ 572.428208] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Borderlands2 [1288],
reason: Engine(s) hung, action: reset
[ 572.428213] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 572.428216] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 572.428218] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 572.428220] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 572.428223] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 572.431747] drm/i915: Resetting chip after gpu hang
[ 574.425058] [drm] RC6 on
[ 582.428673] [drm] stuck on render ring
[ 582.431709] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Borderlands2 [1288],
reason: Engine(s) hung, action: reset
[ 582.434741] drm/i915: Resetting chip after gpu hang
[ 584.405443] [drm] RC6 on
M.
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160919/79c4270f/attachment.html>
More information about the intel-3d-bugs
mailing list