Bug 111565

Summary: [CI][DRMTIP] igt@kms_chamelium@dp-link-status - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: not set    
Priority: not set CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: ICL, KBL i915 features: display/Other

Description Lakshmi 2019-09-05 09:51:31 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_359/fi-icl-u2/igt@kms_chamelium@dp-link-status.html

Starting subtest: dp-link-status
(kms_chamelium:1123) CRITICAL: Test assertion failure function test_link_status, file ../tests/kms_chamelium.c:672:
(kms_chamelium:1123) CRITICAL: Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)
Subtest dp-link-status failed.
**** DEBUG ****
Comment 1 CI Bug Log 2019-09-05 09:53:23 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* fi-icl-u2: igt@kms_chamelium@dp-link-status - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT)
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_359/fi-icl-u2/igt@kms_chamelium@dp-link-status.html
Comment 2 CI Bug Log 2019-09-11 13:54:51 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-icl-u2: igt@kms_chamelium@dp-link-status - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT) -}
{+ fi-kbl-7500u, fi-icl-u2, : igt@kms_chamelium@dp-link-status - fail - Failed assertion: igt_hotplug_detected(mon, HOTPLUG_TIMEOUT) +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_366/fi-kbl-7500u/igt@kms_chamelium@dp-link-status.html
Comment 3 emersion 2019-09-12 10:50:26 UTC
Seems like this happens every few days on fi-kbl-7500u and fi-icl-u4. Actually, the test never succeeds in CI, but succeeds when I test locally (SNB).

User impact: using a screen with a bad cable might result in a black screen, instead of falling back to a lower resolution.
Comment 4 Stanislav Lisovskiy 2019-10-09 09:02:17 UTC
The test triggers link failure with Chamelium and then expects a hotplug event. 
However because HOTPLUG event timeout sometimes seems to be way to short, we get a link failure hotplug event however only after test case fails:

<6> [839.991645] [IGT] kms_chamelium: exiting, ret=98
<7> [840.532587] [drm:gen8_de_irq_handler [i915]] hotplug event received, stat 0x02000000, dig 0x000088a8, pins 0x00000080, long 0x00000080
<7> [840.532778] [drm:intel_hpd_irq_handler [i915]] digital hpd on [ENCODER:238:DDI D] - long
<7> [840.532966] [drm:intel_hpd_irq_handler [i915]] Received HPD interrupt on PIN 7 - cnt: 10
<7> [840.533421] [drm:intel_dp_hpd_pulse [i915]] got hpd irq on [ENCODER:238:DDI D] - long
<7> [840.533687] [drm:i915_hotplug_work_func [i915]] running encoder hotplug functions
<7> [840.533945] [drm:i915_hotplug_work_func [i915]] Connector DP-2 (pin 7) received hotplug event.
<7> [840.534315] [drm:intel_dp_detect [i915]] [CONNECTOR:239:DP-2]
<7> [840.534869] [drm:intel_encoder_hotplug [i915]] [CONNECTOR:239:DP-2] status updated from connected to disconnected
<7> [840.535295] [drm:drm_fb_helper_hotplug_event.part.15] 

So now there we have even more reasons for this patch to land:

https://patchwork.freedesktop.org/series/67441/
Comment 5 Stanislav Lisovskiy 2019-10-09 09:05:07 UTC
Similar issue we have with https://bugs.freedesktop.org/show_bug.cgi?id=111663,
however there we fail after Chamelium reset while also waiting for hotplug.
Comment 6 Martin Peres 2019-11-29 19:26:09 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/396.

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.