Bug 109521 - [CI][DRMTIP] igt@kms_chamelium@hdmi-crc-xrgb8888 - Fail - Failed assertion: found - No pipe found for output DP-2
Summary: [CI][DRMTIP] igt@kms_chamelium@hdmi-crc-xrgb8888 - Fail - Failed assertion: f...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-31 15:30 UTC by Lakshmi
Modified: 2019-02-20 14:00 UTC (History)
1 user (show)

See Also:
i915 platform: KBL, SKL
i915 features: display/HDMI


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-01-31 15:30:42 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_202/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-xrgb8888.html

	
Starting subtest: hdmi-crc-xrgb8888
(kms_chamelium:2127) CRITICAL: Test assertion failure function prepare_output, file ../tests/kms_chamelium.c:447:
(kms_chamelium:2127) CRITICAL: Failed assertion: found
(kms_chamelium:2127) CRITICAL: No pipe found for output DP-2
Subtest hdmi-crc-xrgb8888 failed.
**** DEBUG ****
(kms_chamelium:2127) igt_chamelium-DEBUG: Resetting the chamelium
(kms_chamelium:2127) DEBUG: Waiting for DP-2 to disconnect...
(kms_chamelium:2127) DEBUG: Reprobing DP-2...
(kms_chamelium:2127) DEBUG: Test requirement passed: res = drmModeGetResources(data->drm_fd)
(kms_chamelium:2127) igt_chamelium-DEBUG: Plugging DP-2
(kms_chamelium:2127) DEBUG: Waiting for DP-2 to connect...
(kms_chamelium:2127) DEBUG: Reprobing DP-2...
(kms_chamelium:2127) DEBUG: Reprobing DP-2...
(kms_chamelium:2127) DEBUG: Reprobing DP-2...
(kms_chamelium:2127) DEBUG: Reprobing DP-2...
(kms_chamelium:2127) CRITICAL: Test assertion failure function prepare_output, file ../tests/kms_chamelium.c:447:
(kms_chamelium:2127) CRITICAL: Failed assertion: found
(kms_chamelium:2127) CRITICAL: No pipe found for output DP-2
(kms_chamelium:2127) igt_core-INFO: Stack trace:
(kms_chamelium:2127) igt_core-INFO:   #0 ../lib/igt_core.c:1474 __igt_fail_assert()
(kms_chamelium:2127) igt_core-INFO:   #1 ../tests/kms_chamelium.c:449 prepare_output()
(kms_chamelium:2127) igt_core-INFO:   #2 ../tests/kms_chamelium.c:588 test_display_crc_one_mode()
(kms_chamelium:2127) igt_core-INFO:   #3 ../tests/kms_chamelium.c:963 __real_main796()
(kms_chamelium:2127) igt_core-INFO:   #4 ../tests/kms_chamelium.c:796 main()
(kms_chamelium:2127) igt_core-INFO:   #5 ../csu/libc-start.c:344 __libc_start_main()
(kms_chamelium:2127) igt_core-INFO:   #6 [_start+0x2a]
****  END  ****
Subtest hdmi-crc-xrgb8888: FAIL (1.423s)
Comment 1 CI Bug Log 2019-01-31 15:34:17 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* KBL: igt@kms_chamelium@hdmi-crc-xrgb8888 - Fail - Failed assertion: found\n.*No pipe found for output DP-2
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_202/fi-kbl-7500u/igt@kms_chamelium@hdmi-crc-xrgb8888.html
Comment 2 CI Bug Log 2019-02-07 16:31:59 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@kms_chamelium@hdmi-crc-xrgb8888 - Fail - Failed assertion: found\n.*No pipe found for output DP-2 -}
{+ KBL: igt@kms_chamelium@hdmi-crc-* - Fail - Failed assertion: found\n.*No pipe found for output DP-2 +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_203/fi-kbl-7567u/igt@kms_chamelium@hdmi-crc-fast.html
* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_205/fi-kbl-7567u/igt@kms_chamelium@hdmi-crc-bgr565.html
Comment 3 CI Bug Log 2019-02-07 16:32:19 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@kms_chamelium@hdmi-crc-* - Fail - Failed assertion: found\n.*No pipe found for output DP-2 -}
{+ KBL: igt@kms_chamelium@hdmi-crc-* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d +}

 No new failures caught with the new filter
Comment 4 CI Bug Log 2019-02-07 17:10:11 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@kms_chamelium@hdmi-crc-* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d -}
{+ KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_204/fi-kbl-7500u/igt@kms_chamelium@dp-crc-multiple.html
Comment 5 CI Bug Log 2019-02-08 11:03:54 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@kms_chamelium@hdmi-crc-xbgr8888 - Fail - Failed assertion: found\n.*No pipe found for output HDMI-A-\d
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_205/fi-skl-6700k2/igt@kms_chamelium@hdmi-crc-xbgr8888.html
Comment 6 CI Bug Log 2019-02-12 10:12:16 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d -}
{+ KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_214/fi-kbl-7567u/igt@kms_chamelium@hdmi-crc-argb8888.html
Comment 7 CI Bug Log 2019-02-12 10:12:42 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d -}
{+ KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d +}

 No new failures caught with the new filter
Comment 8 CI Bug Log 2019-02-20 14:00:04 UTC
A CI Bug Log filter associated to this bug has been updated:

{- KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d -}
{+ KBL: igt@kms_chamelium@* - Fail - Failed assertion: found\n.*No pipe found for output DP-\d +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_223/fi-kbl-7567u/igt@kms_chamelium@hdmi-cmp-yu12.html


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.