<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 - i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111981">111981</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>not set
</td>
</tr>
<tr>
<th>Priority</th>
<td>not set
</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>dgilbert@redhat.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=145713" name="attach_145713" title="contents of /sys/class/drm/card0/error">attachment 145713</a> <a href="attachment.cgi?id=145713&action=edit" title="contents of /sys/class/drm/card0/error">[details]</a></span>
contents of /sys/class/drm/card0/error
My dmesg told me to report this, who am I to argue!
(I didn't notice a hang, just noticed it in the dmesg).
Lenovo t580 running fedora 31, xfce desktop.
Linux dgilbert-t580.localhost 5.3.5-300.fc31.x86_64 #1 SMP Tue Oct 8 13:07:42
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[Fri Oct 11 17:53:37 2019] i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000,
hang on rcs0
[Fri Oct 11 17:53:37 2019] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Fri Oct 11 17:53:37 2019] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Fri Oct 11 17:53:37 2019] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Fri Oct 11 17:53:37 2019] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Fri Oct 11 17:53:37 2019] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Fri Oct 11 17:53:37 2019] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0</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>