Continuing with the series of "Initial findings" with Intel-GFX-CI and i915 selftests: drv_selftest@live_hangcheck fails with intel_hangcheck_live_selftests: igt_wait_reset failed with error -5 Examples: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4444/fi-byt-squawks/igt@drv_selftest@live_hangcheck.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4449/fi-byt-n2820/igt@drv_selftest@live_hangcheck.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4444/fi-hsw-peppy/igt@drv_selftest@live_hangcheck.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4451/fi-snb-2600/igt@drv_selftest@live_hangcheck.html
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...
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
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 :(
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.