<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 - [drm] GPU HANG: ecode 0:0x95fdfffd, in systemd-logind [424], reason: Ring hung, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89865">89865</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm] GPU HANG: ecode 0:0x95fdfffd, in systemd-logind [424], reason: Ring hung, action: reset
</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>freedesktop.org@the-compiler.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=114822" name="attach_114822" title="/sys/class/drm/card0/error">attachment 114822</a> <a href="attachment.cgi?id=114822&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
A Qt application suddently hung and stopped redrawing, a few seconds later my
screen was black quickly and I got this in my dmesg:
kern :info : [Apr 1 21:34] [drm] stuck on render ring
kern :info : [ +0.001517] [drm] GPU HANG: ecode 0:0x95fdfffd, in
systemd-logind [424], reason: Ring hung, action: reset
kern :info : [ +0.000005] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
kern :info : [ +0.000003] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
kern :info : [ +0.000003] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
kern :info : [ +0.000002] [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
kern :info : [ +0.000003] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
kern :info : [ +5.990725] [drm] stuck on render ring
kern :info : [ +0.002213] [drm] GPU HANG: ecode 0:0x85effffd, in
systemd-logind [424], reason: Ring hung, action: reset
kern :err : [ +0.000138] [drm:i915_context_is_banned] *ERROR* gpu hanging
too fast, banning!
This is on Archlinux, Linux 3.18.6-1-ARCH, X.org 1.17.1-3, xf86-video-intel
2.99.917-4.</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>