<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@gem_eio@in-flight-*-(10ms|1us|immediate) - fail - Failed assertion: elapsed < 250e6" href="https://bugs.freedesktop.org/show_bug.cgi?id=107799#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@gem_eio@in-flight-*-(10ms|1us|immediate) - fail - Failed assertion: elapsed < 250e6" href="https://bugs.freedesktop.org/show_bug.cgi?id=107799">bug 107799</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=107799#c6">comment #6</a>) > (In reply to Martin Peres from <a href="show_bug.cgi?id=107799#c4">comment #4</a>) > > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_135/fi-bwr-2160/">https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_135/fi-bwr-2160/</a> > > igt@<a href="mailto:gem_eio@wait-immediate.html">gem_eio@wait-immediate.html</a> > > > > Starting subtest: wait-immediate > > (gem_eio:882) CRITICAL: Test assertion failure function check_wait, file > > ../tests/i915/gem_eio.c:258: > > (gem_eio:882) CRITICAL: Failed assertion: elapsed < 250e6 > > (gem_eio:882) CRITICAL: Wake up following reset+wedge took 290.703ms > > Subtest wait-immediate failed. > > Fwiw, bwr appears to be slowed down by display post-reset probing. Tempting > to move that into its own thread, if it can't be dramatically sped up since > the state is known. Well, that could explain :) (In reply to Joonas Lahtinen from <a href="show_bug.cgi?id=107799#c5">comment #5</a>) > After some discussion, agreement is that the issue is actually an > intermittent scheduling delay for the userspace process. So it is an issue, > but not really high and could also be something outside of our scope. > Changing importance to low for reconsideration. Scheduling delay resulting in over 1s latency? That sounds odd and could easily be worked-around by changing the scheduling policy to realtime. Anyway, right now, we suppress: - SNB BYT BSW GLK: igt@gem_eio@in-flight-*-(10ms|1us|immediate) - fail - Failed assertion: elapsed < 250e6 - BWR: igt@gem_eio@wait-immediate - fail - Failed assertion: elapsed < 250e6 If you think the customer impact is really warranting a low, then go for it. Otherwise, bump the priority to what you thing is acceptable.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>