Bug 112193

Summary: [CI][BAT]igt@i915_selftest@live_execlists - dmesg-fail - live_timeslice_preempt failed with error -5
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: not set    
Priority: not set CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
i915 platform: BXT i915 features: GEM/Other

Description Lakshmi 2019-11-01 13:42:33 UTC
(i915_selftest:4937) igt_kmod-WARNING: i915/intel_execlists_live_selftests: live_timeslice_preempt failed with error -5
(i915_selftest:4937) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling always-on
(i915_selftest:4937) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling DC off
(i915_selftest:4937) igt_kmod-WARNING: [drm:gen9_set_dc_state [i915]] Setting DC state from 01 to 00
(i915_selftest:4937) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 2
(i915_selftest:4937) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling dpio-common-a
(i915_selftest:4937) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling dpio-common-bc
(i915_selftest:4937) igt_kmod-WARNING: i915: probe of 0000:00:02.0 failed with error -5
(i915_selftest:4937) igt_kmod-CRITICAL: Test assertion failure function igt_kselftest_execute, file ../lib/igt_kmod.c:548:
(i915_selftest:4937) igt_kmod-CRITICAL: Failed assertion: err == 0
(i915_selftest:4937) igt_kmod-CRITICAL: kselftest "i915 igt__36__live_execlists=1 live_selftests=-1 disable_display=1 st_filter=" failed: Input/output error [5]
Subtest live_execlists failed.

This issue is split from Bug 112046. Not sure if it affects more than BXT. But now I will start with BXT.
Comment 1 CI Bug Log 2019-11-01 13:43:23 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BXT: igt@i915_selftest@live_execlists - dmesg-fail - live_timeslice_preempt failed with error -5
  (No new failures associated)
Comment 2 Chris Wilson 2019-11-01 13:51:43 UTC
It's not very clear as it dropped the pr_err() for which bug it actually was. My guess is

   if (i915_request_wait(head, 0,
                              2 * RUNTIME_INFO(outer->i915)->num_engines * (count + 2) * (count + 3)) < 0) {
                pr_err("Failed to slice along semaphore chain of length (%d, %d)!\n",
                       count, n);
                err = -EIO;

and likely just bad timing. Nothing to worry about unless it becomes disruptive.

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.