[Bug 93979] New: GPU HANG: ecode 7:0:0x84dfbffe, in chromium
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 3 09:41:50 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93979
Bug ID: 93979
Summary: GPU HANG: ecode 7:0:0x84dfbffe, in chromium
Product: DRI
Version: XOrg git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: rrs at researchut.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 121485
--> https://bugs.freedesktop.org/attachment.cgi?id=121485&action=edit
gpu hang sysfs
I have an INtel Haswell chipset and I've now been frequently running into this
GPU hang issue.
[15012.843308] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[15016.375660] [drm] stuck on render ring
[15016.377093] [drm] GPU HANG: ecode 7:0:0x84dfbffe, in chromium [4778],
reason: Ring hung, action: reset
[15016.377096] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[15016.377098] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[15016.377100] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[15016.377102] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[15016.377104] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[15016.379009] drm/i915: Resetting chip after gpu hang
2016-02-03 / 15:07:55 ♒♒♒ ☺
--
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/20160203/38644e4e/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list