[Bug 112191] [CI][SHARDS] igt at gem_ctx_persistence@smoketest - fail - Failed assertion: sync_fence_status(spin->out_fence) == expected

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 1 09:47:59 UTC 2019


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

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

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

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 4a3174152147da1159f7135e90e1831fba74da34 (HEAD -> drm-intel-next-queued,
drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Oct 31 09:01:04 2019 +0000

    drm/i915/gem: Refine occupancy test in kill_context()

    Don't just look at the very last request in a queue when deciding if we
    need to evict the context from the GPU, as that request may still be in
    the submission queue while the rest of the context is running!

    Instead, walk back along the queued requests looking for the active
    request and checking that.

    Fixes: 2e0986a58cc4 ("drm/i915/gem: Cancel contexts when hangchecking is
disabled")
    Testcase: igt/gem_ctx_persistence/queued
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Cc: Matthew Auld <matthew.auld at intel.com>
    Reviewed-by: Matthew Auld <matthew.auld at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20191031090104.22245-1-chris@chris-wilson.co.uk

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


More information about the intel-gfx-bugs mailing list