<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@gem_eio@unwedge-stress - fail - Failed assertion: elapsed < 250e6"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109198#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] igt@gem_eio@unwedge-stress - fail - Failed assertion: elapsed < 250e6"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109198">bug 109198</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>The 250ms was a number plucked out of thin air. To perform a device reset takes
around 10us, so I considered 250ms to have plenty of safety margin built in. In
many ways, not being able to reset and restore control within a frame is a
failure. So... I don't think I want to raise the timeout (with the exception of
say pre-Ironlake where the display engine needs a couple of modesets) and keep
looking for a likely root cause behind the occasional delay.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>