https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_402/fi-skl-guc/igt@gem_eio@kms.html <3> [205.576972] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful <3> [205.980474] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful <3> [206.569543] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful <3> [206.855115] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful <3> [207.031355] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful <3> [207.208430] [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SKL: igt@gem_eio@kms - fail - *ERROR* Link Training Unsuccessful - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_402/fi-skl-guc/igt@gem_eio@kms.html
This looks like it's probably an issue with the physical link. The system initially links trains successfully at 162000 with 2 lanes, but after running for a while that configuration fails and it has to downgrade to 1 lane. Even with 1 lane there are a few sporadic failures and since we're already at the lowest rate and lowest lane count we get the error messages from the log here. We may need to double check that the cable hasn't come loose on this machine and/or replace it with a new cable. As far as I can see, this doesn't appear to be a software issue.
SKL-GUC is running with two dummy displays: HDMI and VGA dongles. Failing DP probe is probably the VGA dongle, looking at the 1024x resolution. As this VGA dongle is not a good representative of real hardware, we could consider this transient issue with this particular dongle and continue without it. Would this be good resolution for this issue?
(In reply to Tomi Sarvela from comment #3) > SKL-GUC is running with two dummy displays: HDMI and VGA dongles. Failing DP > probe is probably the VGA dongle, looking at the 1024x resolution. > > As this VGA dongle is not a good representative of real hardware, we could > consider this transient issue with this particular dongle and continue > without it. Would this be good resolution for this issue? Makes sense. That sounds reasonable to me.
A CI Bug Log filter associated to this bug has been updated: {- SKL: igt@gem_eio@kms - fail - *ERROR* Link Training Unsuccessful -} {+ SKL: Random tests - fail - *ERROR* Link Training Unsuccessful +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_407/fi-skl-guc/igt@kms_plane_lowres@pipe-b-tiling-x.html
A CI Bug Log filter associated to this bug has been updated: {- SKL: Random tests - fail - *ERROR* Link Training Unsuccessful -} {+ SKL: Random tests - fail - *ERROR* Link Training Unsuccessful +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_408/fi-skl-guc/igt@kms_universal_plane@cursor-fb-leak-pipe-a.html
-- 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/603.
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.