Bug 110039

Summary:	[CI][SHARDS] igt@i915_selftest@mock_fence - dmesg-fail - Fence with future expiration (\d+ jiffies) already signaled
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	RESOLVED FIXED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	high	CC:	intel-gfx-bugs
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	SKL	i915 features:	GEM/Other

Description Martin Peres 2019-03-13 15:54:06 UTC

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5737/shard-skl1/igt@i915_selftest@mock_fence.html

<6> [73.498919] [IGT] i915_selftest: executing
<6> [73.611711] [IGT] i915_selftest: starting subtest mock_fence
<5> [74.160079] Setting dangerous option enable_psr - tainting kernel
<5> [74.160118] Setting dangerous option mock_selftests - tainting kernel
<6> [74.347656] i915: Performing mock selftests with st_random_seed=0x3bd1ebdd st_timeout=1000
<6> [74.347680] i915: Running fence
<6> [74.347784] i915: Running i915_sw_fence_mock_selftests/test_self
<6> [74.348201] i915: Running i915_sw_fence_mock_selftests/test_dag
<6> [74.348292] i915: Running i915_sw_fence_mock_selftests/test_AB
<6> [74.362905] i915: Running i915_sw_fence_mock_selftests/test_ABC
<6> [74.363800] i915: Running i915_sw_fence_mock_selftests/test_AB_C
<6> [74.365063] i915: Running i915_sw_fence_mock_selftests/test_C_AB
<6> [74.365782] i915: Running i915_sw_fence_mock_selftests/test_chain
<6> [75.302068] i915: Running i915_sw_fence_mock_selftests/test_ipc
<6> [75.311865] i915: Running i915_sw_fence_mock_selftests/test_timer
<3> [75.315240] Fence with future expiration (2 jiffies) already signaled
<3> [75.315515] i915/i915_sw_fence_mock_selftests: test_timer failed with error -22
<6> [75.837152] [IGT] i915_selftest: exiting, ret=99

Comment 1 CI Bug Log 2019-03-13 15:54:36 UTC

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@i915_selftest@mock_fence - dmesg-fail - Fence with future expiration (\d+ jiffies) already signaled
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5737/shard-skl1/igt@i915_selftest@mock_fence.html

Comment 2 Chris Wilson 2019-03-13 15:57:15 UTC

Bet on a fluke; something preempted the test for a jiffie+. We must have over a thousand runs with these mock tests?, so I'm not too worried about false positive error rate yet.

Comment 3 Chris Wilson 2019-03-14 11:50:08 UTC

And hopefully swept back under the carpet with,

commit d2eeaf2bc04941444bfd52285b6183d6c84c262c (HEAD -> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Mar 13 20:59:44 2019 +0000

    drm/i915/selftests: Disable preemption while setting up fence-timers
    
    The impossible happens and a future fence expired while we were still
    initialising. The probable cause is that the test was preempted and we
    lost our scheduler cpu slice. Disable preemption during this test to
    rule out preemption as a source of timer disruption.
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=110039
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20190313205944.5768-1-chris@chris-wilson.co.uk

Comment 4 Martin Peres 2019-04-17 14:27:28 UTC

(In reply to Chris Wilson from comment #3)
> And hopefully swept back under the carpet with,
> 
> commit d2eeaf2bc04941444bfd52285b6183d6c84c262c (HEAD ->
> drm-intel-next-queued, drm-intel/drm-intel-next-queued)
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Wed Mar 13 20:59:44 2019 +0000
> 
>     drm/i915/selftests: Disable preemption while setting up fence-timers
>     
>     The impossible happens and a future fence expired while we were still
>     initialising. The probable cause is that the test was preempted and we
>     lost our scheduler cpu slice. Disable preemption during this test to
>     rule out preemption as a source of timer disruption.
>     
>     References: https://bugs.freedesktop.org/show_bug.cgi?id=110039
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>     Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20190313205944.5768-1-
> chris@chris-wilson.co.uk

Thanks, it never happened again!

Comment 5 CI Bug Log 2019-04-17 14:27:36 UTC

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

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.