<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@reset-stress - fail - Failed assertion: elapsed < 250e6" href="https://bugs.freedesktop.org/show_bug.cgi?id=107500#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][SHARDS] igt@gem_eio@reset-stress - fail - Failed assertion: elapsed < 250e6" href="https://bugs.freedesktop.org/show_bug.cgi?id=107500">bug 107500</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>A long shot (one that I've tried earlier with no success) was commit a6476ebd4350d51146ef0492b4b06bc0d31e8827 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Mon Aug 6 15:56:47 2018 +0100 drm/i915: Stop dropping irq around resets A long time ago, we were afraid of handling interrupts and signaling waiters during a reset, worrying that the confusion in request handling would interfere with our attempts to process the reset in an orderly fashion. Since then, we have isolated our irq-driven request handling by virtue of the engine->timeline.lock and control of kthreads where required, eliminating the danger of concurrently processing interrupts. 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@intel.com">mika.kuoppala@intel.com</a>> Link: <a href="https://patchwork.freedesktop.org/patch/msgid/20180806145647.13131-1-chris@chris-wilson.co.uk">https://patchwork.freedesktop.org/patch/msgid/20180806145647.13131-1-chris@chris-wilson.co.uk</a> but at least that confirms that it's not a shadow caused by the disabling of irq across reset. Fresh ideas required.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>