Bug 112097 - [CI][BAT]igt@i915_selftest@live_execlists - dmesg-fail - live_timeslice_queue: vcs0: Failed to enable timeslicing!
Summary: [CI][BAT]igt@i915_selftest@live_execlists - dmesg-fail - live_timeslice_queue...
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-22 11:51 UTC by Lakshmi
Modified: 2019-11-01 16:14 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features: GEM/Other

Attachments

Description Lakshmi 2019-10-22 11:51:27 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7143/fi-icl-guc/igt@i915_selftest@live_execlists.html

(i915_selftest:7648) igt_kmod-WARNING: i915_sel-7648    6.... 735707991us : live_timeslice_queue: vcs0: Failed to enable timeslicing!
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4..s. 735709749us : process_csb: vcs0 cs-irq head=7, tail=7
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709877us : __execlists_submission_tasklet: vcs0: expired last=232d9:2, prio=4096, hint=4099
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709879us : __i915_request_unsubmit: vcs0 fence 22e76:96, current 94
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709881us : __i915_request_unsubmit: vcs0 fence 232d9:2, current 1
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709884us : __i915_request_submit: vcs0 fence 22e76:96, current 94
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709887us : __i915_request_submit: vcs0 fence 22e76:98, current 94
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709889us : __i915_request_submit: vcs0 fence 232d9:2, current 1
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709908us : __execlists_submission_tasklet: vcs0: queue_priority_hint:-2147483648, submit:yes
(i915_selftest:7648) igt_kmod-WARNING: ksoftirq-31      4d.s1 735709910us : trace_ports: vcs0: submit { 22e76:98, 232d9:2 }
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710499us : process_csb: vcs0 cs-irq head=7, tail=8
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710499us : process_csb: vcs0 csb[8]: status=0x00000882:0x20000000
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710501us : trace_ports: vcs0: preempted { 232d9:2*, 22e76:96 }
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710502us : trace_ports: vcs0: promote { 22e76:98, 232d9:2 }
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4d.s2 735710512us : __execlists_submission_tasklet: vcs0: queue_priority_hint:-2147483648, submit:no
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710523us : process_csb: vcs0 cs-irq head=8, tail=10
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710524us : process_csb: vcs0 csb[9]: status=0x00000014:0x20000020
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710525us : trace_ports: vcs0: completed { 22e76:98!, 232d9:2 }
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710527us : process_csb: vcs0 csb[10]: status=0x00000018:0x20000000
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4..s1 735710528us : trace_ports: vcs0: completed { 232d9:2!, 0:0 }
(i915_selftest:7648) igt_kmod-WARNING: rcu_pree-10      4d.s2 735710530us : __execlists_submission_tasklet: vcs0: queue_priority_hint:-2147483648, submit:no
(i915_selftest:7648) igt_kmod-WARNING: ---------------------------------
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_power_well_disable [i915]] disabling always-on
(i915_selftest:7648) igt_kmod-WARNING: i915/intel_execlists_live_selftests: live_timeslice_queue failed with error -22
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling always-on
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling DC off
(i915_selftest:7648) igt_kmod-WARNING: [drm:gen9_set_dc_state [i915]] Setting DC state from 02 to 00
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_combo_phy_init [i915]] Combo PHY A already enabled, won't reprogram it.
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_combo_phy_init [i915]] Combo PHY B already enabled, won't reprogram it.
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 2
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 3
(i915_selftest:7648) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 4
(i915_selftest:7648) igt_kmod-WARNING: [drm] GuC communication stopped
(i915_selftest:7648) igt_kmod-WARNING: i915: probe of 0000:00:02.0 failed with error -22
(i915_selftest:7648) igt_kmod-CRITICAL: Test assertion failure function igt_kselftest_execute, file ../lib/igt_kmod.c:548:
(i915_selftest:7648) igt_kmod-CRITICAL: Failed assertion: err == 0
(i915_selftest:7648) igt_kmod-CRITICAL: kselftest "i915 igt__37__live_execlists=1 live_selftests=-1 disable_display=1 st_filter=" failed: Invalid argument [22]
Subtest live_execlists failed.
Comment 1 CI Bug Log 2019-10-22 11:52:04 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@i915_selftest@live_execlists - dmesg-fail - live_timeslice_queue: vcs0: Failed to enable timeslicing!
  (No new failures associated)
Comment 2 Chris Wilson 2019-10-22 12:07:21 UTC 
I was expecting to see it filed as "failed to timeslice into queue". Both are just a timing issue. The former I expected to have been nailed.
Comment 3 Francesco Balestrieri 2019-11-01 05:58:04 UTC 
CI says "no occurrences", is this a valid bug?
Comment 4 Lakshmi 2019-11-01 07:34:11 UTC 
(In reply to Francesco Balestrieri from comment #3)
> CI says "no occurrences", is this a valid bug?

This failure was originally associated with another bug. Since this is a separate issue later I filed this bug. Looks like no new failures are associated to this bug.
Comment 5 Chris Wilson 2019-11-01 16:14:24 UTC 
Should be happy now with a slight bit of extra leniency in the timeout for scheduling lapses.

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.