<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 chrome"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103698">103698</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU hang in chrome
</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>bugzilla@laure.nz
</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>My graphics just froze for some long couple of seconds when I tried to switch
to another tab in Chrome. dmesg tells me to file this bug report. Hopefully
somebody finds this useful. I have the latest Intel drivers, which I got with
Intel's graphic update tool
(<a href="https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.6">https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.6</a>)
I'm on ubuntu-gnome 17.04 on a Thinkpad X1 Yoga 2nd Gen.
$ uname -a
Linux tpxy 4.13.5-041305-generic #201710050600 SMP Thu Oct 5 10:02:44 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dmesg
[15907.677186] [drm] GPU HANG: ecode 9:0:0x85dffffb, in chrome [2632], reason:
Hang on rcs0, action: reset
[15907.677189] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[15907.677190] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[15907.677192] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[15907.677193] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[15907.677194] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[15907.677291] drm/i915: Resetting chip after gpu hang
[15907.677550] [drm] RC6 on
[15910.748597] asynchronous wait on fence i915:gnome-shell[1979]/1:3373a timed
out
[15915.676658] drm/i915: Resetting chip after gpu hang
[15915.676828] [drm] RC6 on
[15923.676576] drm/i915: Resetting chip after gpu hang
[15923.676742] [drm] RC6 on
[15931.676560] drm/i915: Resetting chip after gpu hang
[15931.676727] [drm] RC6 on
[15939.676443] drm/i915: Resetting chip after gpu hang
[15939.676614] [drm] RC6 on
$ file /sys/class/drm/card0/error
/sys/class/drm/card0/error: empty</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>