<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - GPU HANG in gnome-shell"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103871">103871</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG in gnome-shell
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>e.vakhromtsev@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=135689" name="attach_135689" title="GPU crash dump saved to /sys/class/drm/card0/error">attachment 135689</a> <a href="attachment.cgi?id=135689&action=edit" title="GPU crash dump saved to /sys/class/drm/card0/error">[details]</a></span>
GPU crash dump saved to /sys/class/drm/card0/error
dmesg log:
[ 854.445160] asynchronous wait on fence i915:gnome-shell[1006]/1:3a73 timed
out
[ 854.453484] [drm] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell [1006],
reason: Hang on rcs0, action: reset
[ 854.453485] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 854.453486] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 854.453486] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 854.453487] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 854.453487] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 854.453568] drm/i915: Resetting chip after gpu hang
[ 854.453734] [drm] RC6 on
[ 854.458160] [drm] GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin
[version 9.14])
[ 862.338514] drm/i915: Resetting chip after gpu hang
[ 862.338726] [drm] RC6 on
[ 862.342461] [drm] GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin
[version 9.14])
[ 865.538406] asynchronous wait on fence i915:gnome-shell[1006]/1:3a77 timed
out
[ 870.445302] drm/i915: Resetting chip after gpu hang
[ 870.445489] [drm] RC6 on
[ 870.449616] [drm] GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin
[version 9.14])
[ 878.338780] drm/i915: Resetting chip after gpu hang
[ 878.338962] [drm] RC6 on
[ 878.343032] [drm] GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin
[version 9.14])
[ 886.445588] drm/i915: Resetting chip after gpu hang
[ 886.445818] [drm] RC6 on
[ 886.449838] [drm] GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin
[version 9.14])
[ 886.514726] rfkill: input handler enabled
[ 922.662083] rfkill: input handler disabled
[ 1181.081070] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU
pipe A FIFO underrun</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>