Bug 108888 - [CI][SHARDS] igt@gem_exec_fence@basic-await-default - fail - Failed assertion: out[n] == 0
Summary: [CI][SHARDS] igt@gem_exec_fence@basic-await-default - fail - Failed assertion...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-28 14:23 UTC by Martin Peres
Modified: 2018-12-03 12:30 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2018-11-28 14:23:52 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5211/shard-hsw1/igt@gem_exec_fence@basic-await-default.html

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5210/shard-hsw6/igt@gem_exec_fence@basic-await-default.html

Starting subtest: basic-await-default
(gem_exec_fence:2990) CRITICAL: Test assertion failure function test_fence_await, file ../tests/i915/gem_exec_fence.c:403:
(gem_exec_fence:2990) CRITICAL: Failed assertion: out[n] == 0
(gem_exec_fence:2990) CRITICAL: error: 0x1 != 0
Subtest basic-await-default failed.
Comment 1 Chris Wilson 2018-12-03 12:28:57 UTC
commit f36c071f6344e0a335ed4b4e0b3a38c0dd54648b
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Dec 3 11:36:56 2018 +0000

    drm/i915/ringbuffer: Clear semaphore sync registers on ring init
    
    Ensure that the sync registers are cleared every time we restart the
    ring to avoid stale values from creeping in from random neutrinos.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108888
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20181203113701.12106-3-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.