Summary: | [CI] [KBL not shards only] igt@* - dmesg-warn - *ERROR* Link Training Unsuccessful &| *ERROR* LSPCON mode hasn't settled | ||
---|---|---|---|
Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
Component: | DRM/Intel | Assignee: | Swati Sharma <swati2.sharma> |
Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs, shashank.sharma, swati2.sharma |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | KBL | i915 features: | display/LSPCON |
Bug Depends on: | |||
Bug Blocks: | 105979 |
Description
Marta Löfstedt
2018-03-19 14:04:23 UTC
Here are somelinks from recent drmtip runs. I will not paste all links on this bug please check the bug in https://intel-gfx-ci.01.org/cibuglog/ and the results from running the shards testlist on the BAT machines: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip2.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_flip@absolute-wf_vblank-interruptible.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_atomic_transition@plane-all-transition-fencing.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_flip@dpms-off-confusion-interruptible.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_color@pipe-b-degamma.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_ccs@pipe-b-bad-aux-stride.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_flip@flip-vs-absolute-wf_vblank.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_universal_plane@universal-plane-pipe-a-functional.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@pm_rpm@cursor.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7567u/igt@kms_busy@extended-modeset-hang-oldfb-with-reset-render-b.html Here are a couple of links from drmtip_5: [ 238.597585] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@kms_busy@basic-modeset-b.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@gem_eio@hibernate.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@kms_vblank@pipe-c-wait-idle.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@kms_cursor_crc@cursor-128x42-sliding.html [ 249.457994] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@kms_rotation_crc@primary-rotation-90.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@kms_flip@plain-flip-ts-check-interruptible.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_5/fi-kbl-7567u/igt@kms_vblank@pipe-b-wait-idle-hang.html Some of the new hits from drmtip_8: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_8/fi-kbl-7567u/igt@kms_chv_cursor_fail@pipe-b-256x256-bottom-edge.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_8/fi-kbl-7567u/igt@kms_cursor_crc@cursor-256x256-random.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_8/fi-kbl-7567u/igt@perf_pmu@idle-vcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_8/fi-kbl-7567u/igt@kms_cursor_legacy@nonblocking-modeset-vs-cursor-atomic.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_8/fi-kbl-7567u/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html Update: this issue has been reproduced with APL NUCs when using HDMI output. The hardware and firmware version of LSPCon at the time of failure: Connector info -------------- connector 81: type DP-1, status: connected name: physical dimensions: 620x340mm subpixel order: Unknown CEA rev: 3 DPCD rev: 12 audio support: yes DP branch device present: yes Type: HDMI ID: MC2800 HW: 2.2 SW: 1.60 Max TMDS clock: 600000 kHz Max bpc: 16 New FW in testing on CI now. Still happening with latest FW 1.75 in every round of IGT/CI_DRM/Drmtip execution https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5052/shard-kbl2/igt@pm_rpm@cursor-dpms.html Last seen CI_DRM_5634 (1 hour, 49 minutes / 1 runs ago) https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5634/fi-kbl-7500u/igt@kms_chamelium@common-hpd-after-suspend.html (In reply to Lakshmi from comment #8) > Last seen CI_DRM_5634 (1 hour, 49 minutes / 1 runs ago) > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5634/fi-kbl-7500u/ > igt@kms_chamelium@common-hpd-after-suspend.html As seen from dmesg- happening for parade. A CI Bug Log filter associated to this bug has been updated: {- LSPCON: igt@drv_module_reload@ - *ERROR* LSPCON init failed on port|Failed to probe lspcon -} {+ LSPCON: igt@drv_module_reload@ - *ERROR* LSPCON init failed on port / Failed to probe lspcon +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6759/fi-kbl-7567u/igt@i915_pm_rpm@module-reload.html Bug assessment: the following bugs are all related: bug 103313, bug 105602, bug 108833 and bug 108131 (with the same "LSPCON mode hasn't settled" error message). This bug continues to happen frequently, 39% repro rate (despite FW updates). If we are ignoring the bug should we decrease the priority so we don't have to assess it often? Copying Shashank/Swati. A CI Bug Log filter associated to this bug has been updated: {- apl,kbl: all tests - dmesg-warn - *ERROR* Link Training Unsuccessful -} {+ All machines: all tests - dmesg-warn - *ERROR* Link Training Unsuccessful +} No new failures caught with the new filter A CI Bug Log filter associated to this bug has been updated: {- All machines: all tests - dmesg-warn - *ERROR* Link Training Unsuccessful -} {+ All machines: all tests - dmesg-warn - *ERROR* Link Training Unsuccessful +} No new failures caught with the new filter A CI Bug Log filter associated to this bug has been updated: {- All machines: all tests - dmesg-warn - *ERROR* Link Training Unsuccessful -} {+ KBL: all tests - dmesg-warn - *ERROR* Link Training Unsuccessful +} No new failures caught with the new filter There are similar failures as in this bug on TGL as well. For TGL, a separate issue created bug 112233. Let's keep this bug for KBL/LSPCON. Agree, no lspcon on this tgl -- 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/92. |
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.