<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<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#c5">Comment # 5</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:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=112226#c3">comment #3</a>)
<span class="quote">>
> 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?</span >
It does, but in the case of a whole GPU reset, vram is lost after a reset so
the buffers from all processes that use the GPU are lost. Depending on the
nature of the hang, a whole GPU reset may be required rather than just killing
the shader wave.</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>