Bug 112415 - [CI]igt@i915_selftest@live_gt_heartbeat - dmesg-fail - live_idle_flush failed with error -62
Summary: [CI]igt@i915_selftest@live_gt_heartbeat - dmesg-fail - live_idle_flush failed...
Status: RESOLVED DUPLICATE of bug 112405
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-11-27 14:16 UTC by Lakshmi
Modified: 2019-11-29 09:41 UTC (History)
1 user (show)

See Also:
i915 platform: BSW/CHT
i915 features: GEM/Other


Attachments

Description Lakshmi 2019-11-27 14:16:07 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3768/fi-bsw-n3050/igt@i915_selftest@live_gt_heartbeat.html
(i915_selftest:3999) igt_kmod-WARNING: i915/intel_heartbeat_live_selftests: live_idle_flush failed with error -62
(i915_selftest:3999) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling always-on
(i915_selftest:3999) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling display
(i915_selftest:3999) igt_kmod-WARNING: [drm:intel_vga_redisable_power_on [i915]] Something enabled VGA plane, disabling it
(i915_selftest:3999) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling dpio-common-bc
(i915_selftest:3999) igt_kmod-WARNING: [drm:chv_dpio_cmn_power_well_enable [i915]] Enabled DPIO PHY0 (PHY_CONTROL=0x050007fd)
(i915_selftest:3999) igt_kmod-WARNING: [drm:intel_power_well_enable [i915]] enabling dpio-common-d
(i915_selftest:3999) igt_kmod-WARNING: [drm:chv_dpio_cmn_power_well_enable [i915]] Enabled DPIO PHY1 (PHY_CONTROL=0x050007ff)
(i915_selftest:3999) igt_kmod-WARNING: i915: probe of 0000:00:02.0 failed with error -62
(i915_selftest:3999) igt_kmod-CRITICAL: Test assertion failure function igt_kselftest_execute, file ../lib/igt_kmod.c:588:
(i915_selftest:3999) igt_kmod-CRITICAL: Failed assertion: err == 0
(i915_selftest:3999) igt_kmod-CRITICAL: kselftest "i915 igt__21__live_gt_heartbeat=1 live_selftests=-1 disable_display=1 st_filter=" failed: Timer expired [62]
(i915_selftest:3999) igt_core-INFO: Stack trace:
(i915_selftest:3999) igt_core-INFO:   #0 ../lib/igt_core.c:1830 __igt_fail_assert()
(i915_selftest:3999) igt_core-INFO:   #1 [igt_kselftest_execute+0x2e5]
(i915_selftest:3999) igt_core-INFO:   #2 ../lib/igt_kmod.c:622 igt_kselftests()
(i915_selftest:3999) igt_core-INFO:   #3 /usr/include/x86_64-linux-gnu/bits/stdio2.h:64 __real_main29()
(i915_selftest:3999) igt_core-INFO:   #4 ../tests/i915/i915_selftest.c:29 main()
(i915_selftest:3999) igt_core-INFO:   #5 ../csu/libc-start.c:344 __libc_start_main()
(i915_selftest:3999) igt_core-INFO:   #6 [_start+0x2a]
****  END  ****
Subtest live_gt_heartbeat: FAIL (0.697s)
Comment 2 Chris Wilson 2019-11-27 16:13:34 UTC

*** This bug has been marked as a duplicate of bug 112405 ***
Comment 3 CI Bug Log 2019-11-28 06:41:48 UTC
A CI Bug Log filter associated to this bug has been updated:

{- BSW: igt@i915_selftest@live_gt_heartbeat - dmesg-fail - live_idle_flush failed with error -62 -}
{+ BSW GLK: igt@i915_selftest@live_gt_heartbeat - dmesg-fail - live_idle_flush failed with error -62 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7429/shard-glk3/igt@i915_selftest@live_gt_heartbeat.html
Comment 4 CI Bug Log 2019-11-28 06:59:00 UTC
A CI Bug Log filter associated to this bug has been updated:

{- BSW GLK: igt@i915_selftest@live_gt_heartbeat - dmesg-fail - live_idle_flush failed with error -62 -}
{+ BSW KBL GLK: igt@i915_selftest@live_gt_heartbeat - dmesg-fail - live_idle_flush failed with error -62 +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7434/fi-kbl-7560u/igt@i915_selftest@live_gt_heartbeat.html
Comment 5 CI Bug Log 2019-11-29 09:41:23 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


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.