<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] stuck on render ring"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87940">87940</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm] stuck on render ring
</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>minor
</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>bruno.pagani@ens-lyon.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=111619" name="attach_111619" title="/sys/class/drm/card0/error">attachment 111619</a> <a href="attachment.cgi?id=111619&action=edit" title="/sys/class/drm/card0/error">[details]</a></span>
/sys/class/drm/card0/error
I’m using ArchLinux.
mesa 10.4.1
linux 3.17.6
xf86-video-intel 2.99.917
When I use the session type switch in SDDM (my login manager), after selecting
one of the option, the display hangs for some seconds, and then everything is
back to the normal. This 100% of time reproducible here.
When looking at dmesg, I see this:
[ 940.205802] [drm] stuck on render ring
[ 940.206915] [drm] GPU HANG: ecode 0:0xf5dffffe, in sddm-greeter [1439],
reason: Ring hung, action: reset
[ 940.206919] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 940.206922] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 940.206925] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 940.206928] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 940.206931] [drm] GPU crash dump saved to /sys/class/drm/card0/error
So, please find the GPU crash dump attached, and tell me if there is anything I
can do to help you fixing this. Since there was a file size limit to 3000 KB,
I’ve simplified the dump by removing all identical line in an hexdump manner,
adding * to signify all lines where identical between the one above and the one
below. If you need the original file, I can upload it elsewhere, or upload a
compressed version.</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>