<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI] igt@gem_eio@* - fail - Test assertion failure function trigger_reset - Failed assertion: igt_seconds_elapsed(&ts) < 2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105957">bug 105957</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>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI] igt@gem_eio@* - fail - Test assertion failure function trigger_reset - Failed assertion: igt_seconds_elapsed(&ts) < 2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105957#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI] igt@gem_eio@* - fail - Test assertion failure function trigger_reset - Failed assertion: igt_seconds_elapsed(&ts) < 2"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105957">bug 105957</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>commit 89ae332745e31a075747a63ac5acc5baccf75769
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Fri May 11 18:58:59 2018 +0100
tests/gem_eio: Only wait-for-idle inside trigger_reset()
trigger_reset() imposes a tight time constraint (2s) so that we verify
that the reset itself completes quickly. In the middle of this check, we
call gem_quiescent_gpu() which may invoke an rcu_barrier() or two to
clear out the freed memory (DROP_FREED). Those barriers may have
unbounded latency pushing beyond the 2s timeout, so restrict the
operation to only wait-for-idle (DROP_ACTIVE).
Bugzilla: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [CI] igt@gem_eio@* - fail - Test assertion failure function trigger_reset - Failed assertion: igt_seconds_elapsed(&ts) < 2"
href="show_bug.cgi?id=105957">https://bugs.freedesktop.org/show_bug.cgi?id=105957</a>
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Cc: Tvrtko Ursulin <<a href="mailto:tvrtko.ursulin@intel.com">tvrtko.ursulin@intel.com</a>>
Reviewed-by: Tvrtko Ursulin <<a href="mailto:tvrtko.ursulin@intel.com">tvrtko.ursulin@intel.com</a>>
Optimistically marking as fixed to see what happens. It's doubtful that the
rcu_barrier alone is causing the grief, so I suspect there might be an outside
timing influence -- as far as I can tell, the driver is doing the right thing
and isn't causing the delay itself.</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>