Bug 112191 - [CI][SHARDS] igt@gem_ctx_persistence@smoketest - fail - Failed assertion: sync_fence_status(spin->out_fence) == expected
Summary: [CI][SHARDS] igt@gem_ctx_persistence@smoketest - fail - Failed assertion: syn...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-01 08:59 UTC by Lakshmi
Modified: 2019-11-04 10:23 UTC (History)
1 user (show)

See Also:
i915 platform: BXT, GLK, ICL, KBL, SKL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-11-01 08:59:34 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5254/shard-apl8/igt@gem_ctx_persistence@smoketest.html
Starting subtest: smoketest
(gem_ctx_persistence:5649) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5649) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5649) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5653) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5653) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5653) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5643) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5643) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5643) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5648) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5648) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5648) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5652) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5652) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5652) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5644) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5644) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5644) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5651) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5651) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5651) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5650) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5650) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5650) CRITICAL: error: 1 != -5
(gem_ctx_persistence:5645) CRITICAL: Test assertion failure function __smoker, file ../tests/i915/gem_ctx_persistence.c:644:
(gem_ctx_persistence:5645) CRITICAL: Failed assertion: sync_fence_status(spin->out_fence) == expected
(gem_ctx_persistence:5645) CRITICAL: error: 1 != -5
Subtest smoketest failed.
No log.
Subtest smoketest: FAIL (20.180s)
Comment 2 Chris Wilson 2019-11-01 09:07:22 UTC
Here we go, the real bug!

https://patchwork.freedesktop.org/series/68807/
Comment 3 Chris Wilson 2019-11-01 09:47:59 UTC
commit 4a3174152147da1159f7135e90e1831fba74da34 (HEAD -> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@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@chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Cc: Matthew Auld <matthew.auld@intel.com>
    Reviewed-by: Matthew Auld <matthew.auld@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20191031090104.22245-1-chris@chris-wilson.co.uk


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.