** Description changed: [Impact] + Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. + The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] + CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. + The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] + 1. plug docking station on the host + 2. bring up the host and get into desktop. + 3. flip docking station's cable. + 4. check if the external monitor works well [Where problems could occur] + Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further.
** Description changed: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. - The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. + The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] - CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. + CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. + + [Misc] + Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, + so skip Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2021949 Title: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: New Bug description: [Impact] Enabling CL1 (Controller Low Power) states during discovery of existing tunnels established by the system firmware can interfere with the operation of those tunnels. The DisplayPort tunnel establishment timeout of 1.5 seconds can be insufficient for some docking stations, leading to blank displays. [Fix] CL1 states are now not enabled during discovery of existing tunnels. The TMU settings also remain unchanged. The timeout is increased to 3 seconds to allow more time for the DisplayPort connection manager handshake, fixing the issue of displays remaining blank. [Test Cases] 1. plug docking station on the host 2. bring up the host and get into desktop. 3. flip docking station's cable. 4. check if the external monitor works well [Where problems could occur] Low, If the handshake actually requires even more than 3 seconds in some cases, the timeout may still need to be increased further. [Misc] Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a huge, so skip Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
