https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb6/igt@i915_selftest@live_requests.html (i915_selftest:1428) igt_kmod-WARNING: --------------------------------- (i915_selftest:1428) igt_kmod-WARNING: waiting for 4/60 fences (last 18800:10) on vcs0 timed out! (i915_selftest:1428) igt_kmod-WARNING: Dumping ftrace buffer: (i915_selftest:1428) igt_kmod-WARNING: waiting for 4/23 fences (last 187c5:18) on vcs1 timed out! (i915_selftest:1428) igt_kmod-WARNING: (ftrace buffer empty) (i915_selftest:1428) igt_kmod-WARNING: waiting for 15/23 fences (last 187ab:26) on bcs0 timed out! (i915_selftest:1428) igt_kmod-WARNING: Dumping ftrace buffer: (i915_selftest:1428) igt_kmod-WARNING: (ftrace buffer empty) (i915_selftest:1428) igt_kmod-WARNING: waiting for 11/23 fences (last 187dc:22) on rcs0 timed out! (i915_selftest:1428) igt_kmod-WARNING: Dumping ftrace buffer: (i915_selftest:1428) igt_kmod-WARNING: (ftrace buffer empty) (i915_selftest:1428) igt_kmod-WARNING: Completed 447 waits for 14419 fences across 5 engines and 8 cpus (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_disable [i915]] disabling always-on (i915_selftest:1428) igt_kmod-WARNING: i915/i915_request_live_selftests: live_breadcrumbs_smoketest failed with error -5 (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling always-on (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling DC off (i915_selftest:1428) igt_kmod-WARNING: [drm:gen9_set_dc_state [i915]] Setting DC state from 02 to 00 (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_combo_phy_init [i915]] Combo PHY A already enabled, won't reprogram it. (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_combo_phy_init [i915]] Combo PHY B already enabled, won't reprogram it. (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 2 (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 3 (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 4 (i915_selftest:1428) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling power well 5 (i915_selftest:1428) igt_kmod-WARNING: [drm:swsci [i915]] SWSCI request timed out (i915_selftest:1428) igt_kmod-WARNING: i915: probe of 0000:00:02.0 failed with error -5 (i915_selftest:1428) igt_kmod-CRITICAL: Test assertion failure function igt_kselftest_execute, file ../lib/igt_kmod.c:548: (i915_selftest:1428) igt_kmod-CRITICAL: Failed assertion: err == 0 (i915_selftest:1428) igt_kmod-CRITICAL: kselftest "i915 igt__20__live_requests=1 live_selftests=-1 disable_display=1 st_filter=" failed: Input/output error [5] (i915_selftest:1428) igt_core-INFO: Stack trace: (i915_selftest:1428) igt_core-INFO: #0 ../lib/igt_core.c:1696 __igt_fail_assert() (i915_selftest:1428) igt_core-INFO: #1 [igt_kselftest_execute+0x2e5] (i915_selftest:1428) igt_core-INFO: #2 ../lib/igt_kmod.c:582 igt_kselftests() (i915_selftest:1428) igt_core-INFO: #3 ../tests/i915/i915_selftest.c:43 __real_main29() (i915_selftest:1428) igt_core-INFO: #4 ../tests/i915/i915_selftest.c:29 main() (i915_selftest:1428) igt_core-INFO: #5 ../csu/libc-start.c:344 __libc_start_main() (i915_selftest:1428) igt_core-INFO: #6 [_start+0x2a] **** END **** Subtest live_requests: FAIL (40.066s)
> (i915_selftest:1428) igt_kmod-WARNING: i915: probe of 0000:00:02.0 failed > with error -5 > (i915_selftest:1428) igt_kmod-CRITICAL: Test assertion failure function > igt_kselftest_execute, file ../lib/igt_kmod.c:548: > (i915_selftest:1428) igt_kmod-CRITICAL: Failed assertion: err == 0 > (i915_selftest:1428) igt_kmod-CRITICAL: kselftest "i915 > igt__20__live_requests=1 live_selftests=-1 disable_display=1 st_filter=" > failed: Input/output error [5] NOTOURBUG?
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14592/fi-tgl-u2/igt@i915_selftest@live_requests.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14592/fi-tgl-u2/igt@i915_selftest@live_execlists.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14594/fi-tgl-u2/igt@i915_selftest@live_requests.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14594/fi-tgl-u2/igt@i915_selftest@live_execlists.html - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_5101/fi-tgl-u2/igt@i915_selftest@live_requests.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14595/fi-tgl-u2/igt@i915_selftest@live_requests.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb6/igt@i915_selftest@live_requests.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb6/igt@i915_selftest@live_evict.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6979/shard-tglb6/igt@i915_selftest@live_execlists.html
No, it's just a lot slower due to the sensitive interrupt avoidance scheme. commit d9fbb8f48f0ef537bf1c7cd81da1e46595617fe3 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Sep 30 20:49:28 2019 +0100 TGL HAX drm/i915/tgl: Magic interrupt shadow to relieve some random lockups
Seems to have a big impact in CI, setting impact to major and priority to high.
Experiment over.
A CI Bug Log filter associated to this bug has been updated: {- TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 -} {+ CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7002/fi-icl-u2/igt@i915_selftest@live_execlists.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7005/fi-icl-u2/igt@i915_selftest@live_execlists.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7016/fi-cfl-guc/igt@i915_selftest@live_execlists.html
(In reply to CI Bug Log from comment #6) > A CI Bug Log filter associated to this bug has been updated: > > {- TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with > error -5 -} > {+ CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 > failed with error -5 +} > > New failures caught by the filter: > > * > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7002/fi-icl-u2/ > igt@i915_selftest@live_execlists.html > * > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7005/fi-icl-u2/ > igt@i915_selftest@live_execlists.html > * > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7016/fi-cfl-guc/ > igt@i915_selftest@live_execlists.html @Chris, Are these failures are part of this bug?
A CI Bug Log filter associated to this bug has been updated: {- CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 -} {+ CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5216/shard-hsw1/igt@i915_selftest@live_hangcheck.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7030/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5217/fi-hsw-4770r/igt@i915_selftest@live_hangcheck.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7038/shard-hsw7/igt@i915_selftest@live_hangcheck.html
A CI Bug Log filter associated to this bug has been updated: {- CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 -} {+ HSW CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 +} No new failures caught with the new filter
@Chris, This issue is still occurring regularly.
(In reply to Lakshmi from comment #10) > @Chris, This issue is still occurring regularly. No, wrong bug.
A CI Bug Log filter associated to this bug has been updated: {- HSW CFL ICL TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 -} {+ TGL: igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5 +} No new failures caught with the new filter
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.