[Bug 98309] New: [SKL] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X [447], reason: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Oct 18 14:11:27 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98309
Bug ID: 98309
Summary: [SKL] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X
[447], reason: Hang on render ring, action: reset
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: mads at ab3.no
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
With drm-intel-nightly
commit 5b633f423e27af3a7f30d303e243f5a2e82917ae
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Tue Oct 18 14:27:24 2016 +0100
drm-intel-nightly: 2016y-10m-18d-13h-24m-11s UTC integration manifest
[ 66.622400] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X [447], reason: Hang
on render ring, action: reset
[ 66.622402] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 66.622403] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 66.622404] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 66.622405] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 66.622406] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Happens all the time after starting X (after a minute or so). Virtualbox is
installed so that taints the kernel I guess, but I post the
/sys/class/drm/card0/error anyway.
This is on a Dell XPS 9550.
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact 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/20161018/384d7c41/attachment.html>
More information about the intel-gfx-bugs
mailing list