<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:0x00ababab, in systemd-logind [248], reason: Ring hung, action: reset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88727">88727</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm] GPU HANG ecode 0:0x00ababab, in systemd-logind [248], reason: Ring hung, 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-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>cache.1024mb@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=112696" name="attach_112696" title="Error log">attachment 112696</a> <a href="attachment.cgi?id=112696&action=edit" title="Error log">[details]</a></span>
Error log
I actually didn't know what happen, but as I open dmesg it shows this, so I
just submit this.
System is Archlinux 64-bit, Kernel 3.18 (as shown in the error log).
The dmesg tells 2 error, but only produce 1 error log, for a reason I just
don't know. Quoting dmesg:
[182837.319770] [drm] GPU HANG: ecode 0:0x00ababab, in systemd-logind [248],
reason: Ring hung, action: reset
[182837.319772] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[182837.319774] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[182837.319775] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[182837.319776] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[182837.319777] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[183084.318376] [drm] stuck on render ring
[183084.319809] [drm] GPU HANG: ecode 0:0x003d3d3d, in systemd-logind [248],
reason: Ring hung, action: reset</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>