<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: ecode 9:0:0x85dfbeff, in Xorg [882], reason: Hang on rcs0, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105305">105305</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU HANG: ecode 9:0:0x85dfbeff, in Xorg [882], reason: Hang on rcs0, action: reset
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86 (IA32)
</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>sjoerd@acm.org
</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=137714" name="attach_137714" title="GPU crash dump from /sys/class/drm/card0/error">attachment 137714</a> <a href="attachment.cgi?id=137714&action=edit" title="GPU crash dump from /sys/class/drm/card0/error">[details]</a></span>
GPU crash dump from /sys/class/drm/card0/error
Some pertinent lines from journalctl:
Mar 01 09:49:30 HOSTNAME kernel: [drm] GPU HANG: ecode 9:0:0x85dfbeff, in Xorg
[882], reason: Hang on rcs0, action: reset
Mar 01 09:49:30 HOSTNAME kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Mar 01 09:49:30 HOSTNAME kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Mar 01 09:49:30 HOSTNAME kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Mar 01 09:49:30 HOSTNAME kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
Mar 01 09:49:30 HOSTNAME kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Mar 01 09:49:30 HOSTNAME kernel: i915 0000:00:02.0: Resetting rcs0 after gpu
hang
Mar 01 09:49:38 HOSTNAME kernel: i915 0000:00:02.0: Resetting rcs0 after gpu
hang
Mar 01 09:49:46 HOSTNAME kernel: i915 0000:00:02.0: Resetting rcs0 after gpu
hang
Mar 01 09:49:54 HOSTNAME kernel: i915 0000:00:02.0: Resetting rcs0 after gpu
hang
Mar 01 09:50:02 HOSTNAME kernel: i915 0000:00:02.0: Resetting rcs0 after gpu
hang
Mar 01 09:50:02 HOSTNAME at-spi-bus-launcher[1594]: XIO: fatal IO error 11
(Resource temporarily unavailable) on X server ":0"
Mar 01 09:50:02 HOSTNAME at-spi-bus-launcher[1594]: after 110868 requests
(110868 known processed) with 0 events remaining.
Mar 01 09:50:02 HOSTNAME unknown[1567]: xfce4-notifyd: Fatal IO error 11
(Resource temporarily unavailable) on X server :0.
After this several more programs report failures and crashes, the screen went
black and came back with the login screen. Last entry before these lines was
about a half hour earlier.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>