<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@* - dmesg-warn - [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5, then *ERROR* Failed to probe lspcon" href="https://bugs.freedesktop.org/show_bug.cgi?id=108529#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@* - dmesg-warn - [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -5, then *ERROR* Failed to probe lspcon" href="https://bugs.freedesktop.org/show_bug.cgi?id=108529">bug 108529</a> from <a class="email" href="mailto:shashank.sharma@intel.com" title="shashank.sharma@intel.com <shashank.sharma@intel.com>"> shashank.sharma@intel.com</a> <pre>Swati tested LSPCON probing on Bangalore APL system, where: - LSPCON HW is on port B, - VBT was bad, and was showing LSPCON on all ports A, B C - On Port B, the probe was successful, but probe was failure on port A and C (as there was no LSPCON) - On FI-CI Build APL system: - the VBT seems showing LSPCON only on Port B - but we are seeing a failure during the probe itself, even on LSPCON port So technically, Swati is not able to reproduce this issue yet (as the probe failures were on non-LSPCON ports A and C, due to wrong VBT reports) Next steps for debug: Lakshmi: Can you please share the BIOS(VBT) which is being flashed on CI- APL system where the failure has been observed ? Swati: Please flash this BIOS(VBT) on Bangalore APL system, and see if you are able to reproduce this issue. - If yes: Lets debug this issue further and root cause. - If no: We might need to get access to CI-APL system, for root causing.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>