[Bug 94101] New: System hangs for seconds repeatedly and sometimes crashes
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Feb 11 19:48:01 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94101
Bug ID: 94101
Summary: System hangs for seconds repeatedly and sometimes
crashes
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: gegenstand+bugs.freedesktop.org at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 121689
--> https://bugs.freedesktop.org/attachment.cgi?id=121689&action=edit
GPU crash dump saved to /sys/class/drm/card0/error
On an Intel NUC6i5SY with Fedora 23 (up to date) and monitor attached via DP
the system hangs for 2-10 secs.
Sometimes the system does not recover at all - only reboot helps.
dmesg prints:
[ 184.013519] [drm] stuck on render ring
[ 184.014589] [drm] GPU HANG: ecode 9:0:0x87f99ff9, in gnome-shell [2466],
reason: Ring hung, action: reset
[ 184.014596] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 184.014600] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 184.014604] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 184.014608] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 184.014613] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 184.016433] drm/i915: Resetting chip after gpu hang
[ 186.008063] [drm] RC6 on
(crash dump attached)
Sometimes it only prints:
[ 5747.043340] [drm] stuck on render ring
[ 5747.044505] [drm] GPU HANG: ecode 9:0:0x85df9fff, in gnome-shell [2466],
reason: Ring hung, action: reset
[ 5747.046854] drm/i915: Resetting chip after gpu hang
[ 5749.044000] [drm] RC6 on
Don't know if related but dmesg also sometimes prints:
--
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/20160211/5e390e5f/attachment.html>
More information about the intel-gfx-bugs
mailing list