[Bug 102294] [CI][BAT] *ERROR* LSPCON read(0x80, 0x41) failed

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=102294

--- Comment #20 from shashank.sharma at intel.com <shashank.sharma at intel.com> ---
(In reply to Marta Löfstedt from comment #19)
> (In reply to shashank.sharma at intel.com from comment #16)
> > From the given logs, I can see that the LSPCON FW version is still old (1.60)
> > DP branch device present: yes
> >                 Type: HDMI
> >                 ID: MC2800
> >                 HW: 2.2
> >              -> SW: 1.60
> >                 Max TMDS clock: 600000 kHz
> >                 Max bpc: 16
> > 
> > This was a problem in MCA LSPCON FW. We have worked with MCA, to get this
> > problem fixed in, and MCA has released FW version 1.70 (which is already
> > deployed in KBL devices in Grid, by Tomi).
> > 
> > We are also working on making a Linux based FW flashing tool. Once this is
> > done, we will make the FW and tool available to end users, so that they can
> > get rid of this issue. 
> > 
> > - Shashank
> 
> Shashank, we are still seeing the issue on KBL see bug 103313 also see the
> link training bugs KBL 103558, CFL bug 104056, SKL bug 101144.

Most of the *ERROR* LSPCON read(0x80, 0x41) failed issues are fixed with LSPCON
FW V1.72. The issues which we see on KBL are the link training failures. These
are two different issues, and we should not mix it. Probably once we are able
to communicate to the external world on how to flash and upgrade LSPCON FW,
some of the noise will go down, and we should be able to reach the actual
issue. 

There are many variables which can affect the LSPCON issues:
- LSPCON FW version, anything below V1.70 will cause problems for sure.
- KVM device Vs Direct HDMI: Many KVM machine with old KVM FW trigger the issue
of Link training more often, so we have to make sure we have the right setup. 
- Link training failures after above setup: These are the actual issues which
we want to target. 

- Shashank

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171214/43df3cfa/attachment.html>