[Bug 110039] [CI][SHARDS] igt at i915_selftest@mock_fence - dmesg-fail - Fence with future expiration (\d+ jiffies) already signaled

[bugzilla-daemon at freedesktop.org]

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

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> ---
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 at 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 at chris-wilson.co.uk>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20190313205944.5768-1-chris@chris-wilson.co.uk

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