[Bug 100181] New: GPU HANG: ecode 7:0:0xf3cffffe, in compiz [1167], reason: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Mar 13 09:32:51 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=100181
Bug ID: 100181
Summary: GPU HANG: ecode 7:0:0xf3cffffe, in compiz [1167],
reason: Hang on render ring, action: reset
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: me at tobin.cc
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 130189
--> https://bugs.freedesktop.org/attachment.cgi?id=130189&action=edit
output from /sys/class/drm/card0/error
GPU hangs during 'normal' computer usage. Cannot reproduce, happens
approximately ever hour or two.
Desktop System:
Linux 4.11.0-rc1-torvalds #6 SMP x86_64 x86_64 GNU/Linux
Primary applications running:
Firefox, Terminator, Emacs, Rhythmbox
Edited dmesg output
[drm] GPU HANG: ecode 7:0:0xf3cffffe, in compiz [1167], reason: Hang on render
ring, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including
userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not
a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always
attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
Bug present while running all mainline kernels since about 4.10-rc8. Also
present when running Ubuntu kernel 4.4.0-65-generic.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170313/03f20bff/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list