Bug 111872

Summary: [CI][SHARDS] igt@i915_selftest@* - dmesg-fail - probe of 0000:00:02.0 failed with error -5
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: major    
Priority: high CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: CFL, ICL, TGL i915 features: GEM/Other

Description Lakshmi 2019-10-01 08:52:57 UTC
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)
Comment 1 Lakshmi 2019-10-01 08:54:02 UTC
> (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?
Comment 3 Chris Wilson 2019-10-01 10:17:10 UTC
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
Comment 4 Francesco Balestrieri 2019-10-02 05:08:37 UTC
Seems to have a big impact in CI, setting impact to major and priority to high.
Comment 5 Chris Wilson 2019-10-04 20:12:52 UTC
Experiment over.
Comment 6 CI Bug Log 2019-10-07 12:30:21 UTC
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
Comment 7 Lakshmi 2019-10-07 13:17:19 UTC
(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?
Comment 8 CI Bug Log 2019-10-09 18:38:26 UTC
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
Comment 9 CI Bug Log 2019-10-09 18:38:48 UTC
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
Comment 10 Lakshmi 2019-10-09 18:40:53 UTC
@Chris, This issue is still occurring regularly.
Comment 11 Chris Wilson 2019-10-09 21:50:15 UTC
(In reply to Lakshmi from comment #10)
> @Chris, This issue is still occurring regularly.

No, wrong bug.
Comment 12 CI Bug Log 2019-10-10 11:18:01 UTC
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.