[Bug 106693] [CI] igt@* - incomplete - intel_engine_unpin_breadcrumbs_irq:226 GEM_BUG_ON(!b->irq_enabled)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 6 19:42:33 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106693

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 209b7955e59e361fe8ba1911fac68f46355ac0cf
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Jul 17 21:29:32 2018 +0100

    drm/i915/guc: Keep guc submission permanently engaged

    We make a decision at module load whether to use the GuC backend or not,
    but lose that setup across set-wedge. Currently, the guc doesn't
    override the engine->set_default_submission hook letting execlists sneak
    back in temporarily on unwedging leading to an unbalanced park/unpark.

    v2: Remove comment about switching back temporarily to execlists on
    guc_submission_disable(). We currently only call disable on shutdown,
    and plan to also call disable before suspend and reset, in which case we
    will either restore guc submission or mark the driver as wedged, making
    the reset back to execlists pointless.
    v3: Move reset.prepare across

    Fixes: 63572937cebf ("drm/i915/execlists: Flush pending preemption events
during reset")
    Testcase: igt/drv_module_reload/basic-reload-inject
    Testcase: igt/gem_eio
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Michał Winiarski <michal.winiarski at intel.com>
    Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Reviewed-by: Michał Winiarski <michal.winiarski at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180717202932.1423-1-chris@chris-wilson.co.uk

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180906/d1f24d0a/attachment.html>


More information about the intel-gfx-bugs mailing list