[Bug 104670] [CI] igt at drv_selftest@mock_fence - dmesg-fail - i915/i915_sw_fence_mock_selftests: test_dma_fence failed with error -22

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Jan 17 17:13:08 UTC 2018


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

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

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

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
Fingers crossed,

commit ba02f4c26b37102ab030aa81d42d8021c81a43ab
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed Jan 17 13:57:13 2018 +0000

    drm/i915/selftests: Wait for the dma-fence timeout

    When testing that the timeout fired, we need to be sure we have waited
    just long enough for the timeout to have occurred and for the softirq
    (on another cpu) to have completed. Sleeping for an arbitrary amount is
    prone to error, so wait for the timeout instead and complain if it was
    too late.

    v2: Use wait_event_timeout to provide an upper bound
    v3: Fix inverted check for wait_event_timeout timing out
    v4: Restore the check that the fences aren't signalled too early, by
    inspecting them before the expected timeout.

    References: https://bugs.freedesktop.org/show_bug.cgi?id=104670
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180117135713.2324-1-chris@chris-wilson.co.uk

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


More information about the intel-gfx-bugs mailing list