Bug 107163 - [CI][SNB,BYT,HSW] intel_hangcheck_live_selftests: igt_wait_reset failed with error -5
Summary: [CI][SNB,BYT,HSW] intel_hangcheck_live_selftests: igt_wait_reset failed with ...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-09 08:02 UTC by Tomi Sarvela
Modified: 2018-07-18 00:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Comment 1 Chris Wilson 2018-07-09 08:08:53 UTC
The symptom here is that we never wakeup from i915_request_wait for the final switch-to-kernel-context request (the system is already idle before the switch). Like a missed breadcrumb...
Comment 2 Chris Wilson 2018-07-09 13:18:24 UTC
Hmm, (honestly didn't do it for this reason), but I may have swept this under the carpet:

commit d9a13ce3fa5f396f100ab3f58e5ca127c77a74bb (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Jul 9 13:20:44 2018 +0100

    drm/i915/selftests: Replace wait-on-timeout with explicit timeout
    
    In igt_flush_test() we install a background timer in order to ensure
    that the wait completes within a certain time. We can now tell the wait
    that it has to complete within a timeout, and so no longer need the
    background timer.
    
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
    Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
    Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20180709122044.7028-3-chris@chris-wilson.co.uk
Comment 3 Chris Wilson 2018-07-09 14:01:08 UTC
Should I mark this as worksforme without first adding a test to catch the fail? I already thought I had the right tests to catch it :(
Comment 4 James Ausmus 2018-07-18 00:58:32 UTC
CI has been green on this test since 4453, closing


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.