<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [HadesCanyon/regression] GPU hang causes also X server to die"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112226">bug 112226</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>[HadesCanyon] GPU hangs don't anymore recover (although kernel still claims that they do)
</td>
<td>[HadesCanyon/regression] GPU hang causes also X server to die
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [HadesCanyon/regression] GPU hang causes also X server to die"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112226#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [HadesCanyon/regression] GPU hang causes also X server to die"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112226">bug 112226</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Alex Deucher from <a href="show_bug.cgi?id=112226#c1">comment #1</a>)
<span class="quote">> Please attach your dmesg output and xorg log is using X. Please note that
> after a GPU reset, in most cases you need to restart your desktop
> environment because no desktop environments properly handle the loss of
> their contexts at the moment.</span >
Failed tests complain about the invalid MIT-MAGIC-COOKIE-1, so it seems that
later failures are because X went down (and came back up with display manager).
AFAIK reset should affect only the context running in the GPU when it was
reseted, not the others [1], and in this case the problematic client should be
GfxBench (Manhattan test-case, see <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED MOVED - (Recoverable) GPU hangs with GfxBench Manhattan GL tests"
href="show_bug.cgi?id=108898">bug 108898</a>), not X server.
Btw. Why AMD kernel module doesn't tell which process / context had the issue,
like i915 does?
[1] At least that's the case with i915, as long as the whole system doesn't
hang.
(In reply to Eero Tamminen from <a href="show_bug.cgi?id=112226#c0">comment #0</a>)
<span class="quote">> * If latest Mesa is used with drm-tip kernel 5.3, 4/5 times X fails to
> start. This started to happen with Mesa version within couple of days of
> the GPU hang recovery issue, so potentially there are more issue in Mesa
> (HadesCanyon) AMD support</span >
Correction. That issue happens only when using latest Mesa with few months old
X server and (5.3) drm-tip kernel. If latest git versions of all are used, X
starts fine. But since the indicated date, it dies later, when Manhattan
test-case causes problems.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>