| Summary: | [BAT] 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: | shashank.sharma <shashank.sharma> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | critical | ||
| Priority: | highest | CC: | intel-gfx-bugs, jani.saarinen |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | CFL | i915 features: | display/Other |
|
Description
Marta Löfstedt
2017-10-10 10:14:01 UTC
*** Bug 103026 has been marked as a duplicate of this bug. *** Note duplicate of 103026 is only due to link training issues. The lockdep was solved from 4.14.0-rc3. Is this a LSPCON port on CFL? Not sure if this is LSPCON related issue or another DP timeout issue on CFL. Manasi This can be a LSPCON issue, so it needs testing with my patchset https://patchwork.freedesktop.org/series/31639/ Only when this patch series is merged, we would be able to comment on if this is a new issue, or one among the existing ones. - Shashank Probably fixed by these commits in drm-intel-next-queued: commit f687e25a7a245952349f1f9f9cc238ac5a3be258 Author: Shashank Sharma <shashank.sharma@intel.com> Date: Thu Oct 12 22:10:08 2017 +0530 drm: Add retries for lspcon mode detection commit d18aef0f75436abb95894a230b504432df26c167 Author: Shashank Sharma <shashank.sharma@intel.com> Date: Tue Oct 10 15:37:43 2017 +0530 drm/i915: Don't give up waiting on INVALID_MODE commit a2fc4bd61e7ec3bb1f7c8b3d47272be813f88aea Author: Shashank Sharma <shashank.sharma@intel.com> Date: Tue Oct 10 15:37:44 2017 +0530 drm/i915: Add retries for LSPCON detection This system needs still fw update. This is is still reproducible: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3240/fi-cfl-s/igt@gem_exec_suspend@basic-s3.html new subtests:CI_DRM_3294 fi-cfl-s It appear to have started on: igt@debugfs_test@read_all_entries https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3294/fi-cfl-s/igt@debugfs_test@read_all_entries.html [ 51.206919] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to start channel equalization igt@drv_getparams_basic@basic-eu-total https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3294/fi-cfl-s/igt@drv_getparams_basic@basic-eu-total.html [ 51.622067] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [ 51.704281] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training igt@drv_getparams_basic@basic-subslice-total https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3294/fi-cfl-s/igt@drv_getparams_basic@basic-subslice-total.html [ 52.147955] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training igt@drv_hangman@error-state-basic.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3294/fi-cfl-s/igt@drv_hangman@error-state-basic.html [ 52.269911] i915 0000:00:02.0: Resetting rcs0 after gpu hang [ 52.523708] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training [ 52.523798] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Also, here: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3308/fi-cfl-s/igt@gem_exec_suspend@basic-s3.html Marta,
Can you please confirm that the LSPCON FW version is 1.70 not 1.63 and older ?
Cat /sys/kernel/debug/dri/0/i915_display_info
Look for connector DP-1/2 (where we have LSPCON attached)
There would be branch device info like this:
> DP branch device present: yes
> Type: HDMI
> ID: MC2800
> HW: 2.2
> SW: 1.63
(In reply to shashank.sharma@intel.com from comment #10) > Marta, > Can you please confirm that the LSPCON FW version is 1.70 not 1.63 and older > ? > > Cat /sys/kernel/debug/dri/0/i915_display_info > Look for connector DP-1/2 (where we have LSPCON attached) > There would be branch device info like this: > > DP branch device present: yes > > Type: HDMI > > ID: MC2800 > > HW: 2.2 > > SW: 1.63 From IRC: <marta_> tsa, shashank_sharma wanted to verify LSPCON FW version on CFL-s, I tried to ssh to it but got "Connection closed...", tsa, could you cat /sys/kernel/debug/dri/0/i915_display_info and update in https://bugs.freedesktop.org/show_bug.cgi?id=103186 <tsa> marta_: 1.63 still. I haven't been able to update the FW Thanks for the confirmation Marta. We need to test this issue with LSPCON FW V1.70, as this issue is fixed on several KBL devices using this FW version. - Shashank https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3313/fi-cfl-s/igt@gem_basic@create-close.html [ 25.491005] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful [ 25.820995] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3313/fi-cfl-s/igt@gem_basic@create-fd-close.html [ 26.134438] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful Patchwork: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6980/fi-cfl-s/igt@gem_basic@bad-close.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6980/fi-cfl-s/igt@drv_hangman@error-state-basic.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6980/fi-cfl-s/igt@drv_getparams_basic@basic-subslice-total.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6980/fi-cfl-s/igt@drv_getparams_basic@basic-eu-total.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_6980/fi-cfl-s/igt@debugfs_test@read_all_entries.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3329/fi-cfl-s/igt@prime_busy@basic-after-default.html [ 501.968918] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3329/fi-cfl-s/igt@prime_vgem@basic-fence-flip.html [ 505.388885] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b-frame-sequence.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@read-crc-pipe-a.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@read-crc-pipe-a-frame-sequence.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@read-crc-pipe-b.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@prime_busy@basic-after-default.html https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7110/fi-cfl-s/igt@prime_vgem@basic-fence-flip.html CFL-S no replaced with CFL-S2, is this issue seen there. On CFL-2" now: DP branch device present: yes Type: HDMI ID: MC2800 HW: 2.2 SW: 1.72 Max TMDS clock: 600000 kHz Max bpc: 16 (In reply to Jani Saarinen from comment #20) > CFL-S no replaced with CFL-S2, is this issue seen there. > On CFL-2" now: > DP branch device present: yes > Type: HDMI > ID: MC2800 > HW: 2.2 > SW: 1.72 > Max TMDS clock: 600000 kHz > Max bpc: 16 If it was an issue on the cfl-s2 I would have filed that issue on this bug. SO, NO this and no other of the cfl-s bugs have so far not affected cfl-s2. I meant to say: "CFL-S now replaced with CFL-S2, is this issue seen there." So was this seen only on Old FW version (1.63) and not surfaced later? (In reply to Jani Saarinen from comment #23) > So was this seen only on Old FW version (1.63) and not surfaced later? Again this bug was for the old cfl-s, this bug was archived from cibuglog when cfl-s was replaced with cfl-s2. The similar bug for cfl-s2 is bug 104056 OK, resolving this then. |
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.