Bug 111663 - [CI][DRMTIP] igt@kms_chamelium@dp-link-status - fail - Failed assertion: false, Timed out waiting for DP-3 to get connected
Summary: [CI][DRMTIP] igt@kms_chamelium@dp-link-status - fail - Failed assertion: fals...
Status: NEW
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-09-11 14:09 UTC by Lakshmi
Modified: 2019-10-01 07:57 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-09-11 14:09:19 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_366/fi-icl-u4/igt@kms_chamelium@dp-link-status.html

Starting subtest: dp-link-status
(kms_chamelium:1320) CRITICAL: Test assertion failure function wait_for_connector, file ../tests/kms_chamelium.c:157:
(kms_chamelium:1320) CRITICAL: Failed assertion: false
(kms_chamelium:1320) CRITICAL: Timed out waiting for DP-3 to get connected
Subtest dp-link-status failed.
**** DEBUG ****
Comment 1 CI Bug Log 2019-09-11 14:10:06 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* fi-icl-u4: igt@kms_chamelium@dp-link-status - fail - Failed assertion: false, Timed out waiting for DP-3 to get connected
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_366/fi-icl-u4/igt@kms_chamelium@dp-link-status.html
Comment 2 CI Bug Log 2019-09-11 14:30:32 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-icl-u4: igt@kms_chamelium@dp-link-status - fail - Failed assertion: false, Timed out waiting for DP-3 to get connected -}
{+ fi-icl-u4: igt@kms_chamelium@dp-link-status - fail - Failed assertion: false, Timed out waiting for DP-3 to get connected +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_366/fi-icl-u4/igt@kms_chamelium@hdmi-mode-timings.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_366/fi-icl-u4/igt@kms_chamelium@hdmi-aspect-ratio.html
Comment 3 CI Bug Log 2019-09-13 07:21:27 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-icl-u4: igt@kms_chamelium@dp-link-status - fail - Failed assertion: false, Timed out waiting for DP-3 to get connected -}
{+ fi-icl-u4: igt@kms_chamelium@dp-link-status - fail - Failed assertion: false, Timed out waiting for DP-3 to get connected +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_367/fi-icl-u4/igt@kms_chamelium@dp-mode-timings.html
Comment 4 Stanislav Lisovskiy 2019-10-01 07:57:43 UTC
I think the reason for all machines connected to Chamelium is pretty simple here: for each of the tests, initially it resets the Chamelium with chamelium_reset function and then waits for connector to come up meanwhile probing it. Sometimes HOTPLUG_TIMEOUT which is 20s is not enough so we time out even though it is visible from dmesg that connector comes up eventually:

7> [488.306978] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3] disconnected
<7> [488.357307] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3]
<7> [488.357435] [drm:intel_dp_detect [i915]] [CONNECTOR:245:DP-3]
<7> [488.357804] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3] disconnected
<7> [488.408154] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3]
<7> [488.408282] [drm:intel_dp_detect [i915]] [CONNECTOR:245:DP-3]
<7> [488.408395] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3] disconnected
<7> [488.458595] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3]
<7> [488.458725] [drm:intel_dp_detect [i915]] [CONNECTOR:245:DP-3]
<7> [488.458910] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3] disconnected
<7> [488.509272] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3]
<7> [488.509399] [drm:intel_dp_detect [i915]] [CONNECTOR:245:DP-3]
<7> [488.509509] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:245:DP-3] disconnected
<6> [488.579246] [IGT] kms_chamelium: exiting, ret=98


So we exit with error however connector comes up just a second later:

<7> [489.397551] [drm:i915_hotplug_work_func [i915]] Connector DP-3 (pin 8) received hotplug event.
<7> [489.407519] [drm:icl_tc_phy_set_safe_mode [i915]] Port E/TC#3: PHY complete clear timed out
<7> [489.407613] [drm:__intel_tc_port_lock [i915]] Port E/TC#3: TC port mode reset (dp-alt -> dp-alt)
<7> [489.413700] [drm:intel_power_well_disable [i915]] disabling power well 3
<7> [489.413774] [drm:intel_power_well_disable [i915]] disabling power well 2
<7> [489.413853] [drm:intel_atomic_commit_tail [i915]] [CRTC:152:pipe B]
<7> [489.413950] [drm:intel_enable_sagv [i915]] Enabling SAGV
<7> [489.414176] [drm:intel_dp_detect [i915]] [CONNECTOR:245:DP-3]
...
<7> [489.594446] [drm:intel_encoder_hotplug [i915]] [CONNECTOR:245:DP-3] status updated from disconnected to connected

So the solution I guess is to simply increase the HOTPLUG_TIMEOUT value up to 30 seconds as I looks like Chamelium restart time varies.


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.