[Bug 88839] New: GPU HANG in gnome-shell. reason: Ring hung, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jan 27 17:14:37 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=88839
Bug ID: 88839
Summary: GPU HANG in gnome-shell. reason: Ring hung, 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: morebikethanman at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 112896
--> https://bugs.freedesktop.org/attachment.cgi?id=112896&action=edit
/sys/class/drm/card0/error
There appear to be various other similar bugs, but the dmesg comment below
suggested creating a new bug report:
[Jan27 07:22] [drm] stuck on render ring
[ +0.001591] [drm] GPU HANG: ecode 0:0x87d3bffa, in gnome-shell [5652],
reason: Ring hung, action: reset
[ +0.000006] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ +0.000005] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ +0.000004] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ +0.000004] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ +0.000004] [drm] GPU crash dump saved to /sys/class/drm/card0/error
This GPU hang happens regularly when using the google-chrome browser. It seems
to be hanging less often now that I have disabled hardware acceleration but it
continues to happen.
I am also running vmware-workstation 10 - maybe that is contributing to the
problem?
--
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/20150128/1065b3a8/attachment.html>
More information about the intel-gfx-bugs
mailing list