<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span> changed
<a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - [CI] igt@.* - dmesg-warn/dmesg-fail - *ERROR* rcs0: reset request timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106684">bug 106684</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;">Status</td>
<td>RESOLVED
</td>
<td>CLOSED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - [CI] igt@.* - dmesg-warn/dmesg-fail - *ERROR* rcs0: reset request timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106684#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - [CI] igt@.* - dmesg-warn/dmesg-fail - *ERROR* rcs0: reset request timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106684">bug 106684</a>
from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=106684#c5">comment #5</a>)
<span class="quote">> The behaviour should have substantially changed with
>
> commit f4e60c5cfbf217cc9faa3aeb63742860154fcfef (HEAD ->
> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
> Author: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
> Date: Mon Aug 13 16:01:16 2018 +0300
>
> drm/i915: Force reset on unready engine
>
> If engine reports that it is not ready for reset, we
> give up. Evidence shows that forcing a per engine reset
> on an engine which is not reporting to be ready for reset,
> can bring it back into a working order. There is risk that
> we corrupt the context image currently executing on that
> engine. But that is a risk worth taking as if we unblock
> the engine, we prevent a whole device wedging in a case
> of full gpu reset.
>
> Reset individual engine even if it reports that it is not
> prepared for reset, but only if we aim for full gpu reset
> and not on first reset attempt.
>
> v2: force reset only on later attempts, readability (Chris)
> v3: simplify with adequate caffeine levels (Chris)
> v4: comment about risks and migitations (Chris)
>
> Cc: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Signed-off-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
> Reviewed-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Link:
> <a href="https://patchwork.freedesktop.org/patch/msgid/20180813130116.7250-1-mika">https://patchwork.freedesktop.org/patch/msgid/20180813130116.7250-1-mika</a>.
> <a href="mailto:kuoppala@linux.intel.com">kuoppala@linux.intel.com</a></span >
Seems like it fixed it. Thanks!</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>