<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@i915_selftest@live_execlists - incomplete - GEM_BUG_ON(i915_active_is_idle(&ce->active))" href="https://bugs.freedesktop.org/show_bug.cgi?id=111937#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@i915_selftest@live_execlists - incomplete - GEM_BUG_ON(i915_active_is_idle(&ce->active))" href="https://bugs.freedesktop.org/show_bug.cgi?id=111937">bug 111937</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=111937#c2">comment #2</a>) > During reset, the context idled. Which also shouldn't have happened -- I > think the engine parked, but we are after the set-wedged (and after the > GEM_TRACE) so it is retired immediately. Hmm. Seems possible. intel_gt_set_wedged() takes the intel_engine_pm before marking it as wedged, so we should not be able to discard the idle barrier so easily. Except for switch_to_kernel_context: rq = __i915_request_create(engine->kernel_context, GFP_NOWAIT); if (IS_ERR(rq)) /* Context switch failed, hope for the best! Maybe reset? */ goto out_unlock; Otherwise there should have been an idle request in flight keeping the retired context active. It might interesting to stick an intel_engine_pm_is_awake() into the reset code, but first need to think how that upsets the replay or note.</pre> </div> <hr> You are receiving this mail because: <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>