<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][SHARDS] igt@i915_selftest@live_workarounds - incomplete"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109626">bug 109626</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][SHARDS] igt@i915_selftest@live_workarounds - incomplete"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109626#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - [CI][SHARDS] igt@i915_selftest@live_workarounds - incomplete"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109626">bug 109626</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=109626#c3">comment #3</a>)
<span class="quote">> commit c836eb79c033c2be13aa8b41729b28d2ab1f72ab (HEAD ->
> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Wed Feb 13 22:48:05 2019 +0000
>
> drm/i915/selftests: Always use an active engine while resetting
>
> Currently, we only try to reset a live engine for checking the whitelist
> retention across a per-engine reset. For safety, it appears we need to
> prime the system with a hanging spinner before performing a full-device
> reset. (Figuring out the root cause behind the instability with handling
> a reset during a no-op request is a challenge for another test, the
> whitelist test has its own purpose.)
>
> Bugzilla: <a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - [CI][SHARDS] igt@i915_selftest@live_workarounds - incomplete"
href="show_bug.cgi?id=109626">https://bugs.freedesktop.org/show_bug.cgi?id=109626</a>
> Signed-off-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/20190213224805.32021-1">https://patchwork.freedesktop.org/patch/msgid/20190213224805.32021-1</a>-
> <a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>
> Reviewed-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
>
> should prevent it from occurring, and CI hints that
>
> commit 9a3b19a16dc28ab717cf1663d09ffee0715b735a
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Wed Feb 13 23:20:47 2019 +0000
>
> drm/i915: Only try to park engines after a failed reset
>
> Currently we try to stop the engine by programming the ring registers to
> be disabled before we perform the reset. Sometimes, we see the context
> image also have invalid ring registers, which one presumes may be
> actually caused by us doing so. Lets risk not doing programming the
> ring to zero on the first attempt to avoid preserving that corruption
> into the context image, leaving the w/a in place for subsequent
> reset attempts.
>
> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Cc: Mika Kuoppala <<a href="mailto:mika.kuoppala@intel.com">mika.kuoppala@intel.com</a>>
> Reviewed-by: Mika Kuoppala <<a href="mailto:mika.kuoppala@linux.intel.com">mika.kuoppala@linux.intel.com</a>>
> Link:
> <a href="https://patchwork.freedesktop.org/patch/msgid/20190213232047.8486-1">https://patchwork.freedesktop.org/patch/msgid/20190213232047.8486-1</a>-
> <a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>
>
> might be the real deal.</span >
No idea if this was what fixed it, but it most definitely is fixed! 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>