<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=111812">111812</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>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>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>freedesktop@inbx.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>I am on latest Arch, all recent. Just experience a GUI-hang with mostly
Terminals, Firefox and Emacs open. All on sway / Wayland. An external
4k-Monitor was attached via USB-C.
HW is a recent Lenovo X390.
[ 9225.720061] i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
[ 9225.720062] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 9225.720063] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 9225.720063] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 9225.720063] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 9225.720064] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 9225.721091] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
/sys/class/drm/card0/error is empty but was created on hang. This is how the
dir looks like:
card0 l
total 0
drwxr-xr-x 9 root root 0 Sep 25 08:05 .
drwxr-xr-x 4 root root 0 Sep 25 08:05 ..
drwxr-xr-x 5 root root 0 Sep 25 08:05 card0-DP-1
drwxr-xr-x 5 root root 0 Sep 25 08:05 card0-DP-2
drwxr-xr-x 6 root root 0 Sep 25 08:05 card0-eDP-1
drwxr-xr-x 3 root root 0 Sep 25 08:05 card0-HDMI-A-1
drwxr-xr-x 3 root root 0 Sep 25 08:05 card0-HDMI-A-2
-r--r--r-- 1 root root 4.0K Sep 25 10:46 dev
lrwxrwxrwx 1 root root 0 Sep 25 08:05 device -> ../../../0000:00:02.0
-rw------- 1 root root 0 Sep 25 10:46 error
-r--r--r-- 1 root root 4.0K Sep 25 10:46 gt_act_freq_mhz
-rw-r--r-- 1 root root 4.0K Sep 25 10:46 gt_boost_freq_mhz
-r--r--r-- 1 root root 4.0K Sep 25 10:46 gt_cur_freq_mhz
-rw-r--r-- 1 root root 4.0K Sep 25 10:46 gt_max_freq_mhz
-rw-r--r-- 1 root root 4.0K Sep 25 10:46 gt_min_freq_mhz
-r--r--r-- 1 root root 4.0K Sep 25 10:46 gt_RP0_freq_mhz
-r--r--r-- 1 root root 4.0K Sep 25 10:46 gt_RP1_freq_mhz
-r--r--r-- 1 root root 4.0K Sep 25 10:46 gt_RPn_freq_mhz
drwxr-xr-x 3 root root 0 Sep 25 10:46 metrics
drwxr-xr-x 2 root root 0 Sep 25 08:05 power
lrwxrwxrwx 1 root root 0 Sep 25 08:05 subsystem -> ../../../../../class/drm
-rw-r--r-- 1 root root 4.0K Sep 25 08:05 uevent</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>