[Bug 2094759] Re: TBT monitor can't be recognized after CB/WB SUT while connected SD25TB5/WD25TB5 dock

This bug is awaiting verification that the linux-oem-6.11/6.11.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.11'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.11' to 'verification-failed-
noble-linux-oem-6.11'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2094759

Title:
TBT monitor can't be recognized after CB/WB SUT while connected
SD25TB5/WD25TB5 dock

Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.11 source package in Noble:
Fix Committed

Bug description:
[Impact]
After CB/WB, Thunderbolt monitor can't be recognized.

The root cause is that the igc driver gets the error from NIC
(provided by K2 dock) while performing NVM read IO. The driver lacks
the mechanism to report the error and further runs the codes
afterwards, which causes the unexpected 40~ sec. sleep and affected
the Thunderbolt.

[Fix]
Cherry-pick the following patch from linux-next fixes the issue:

bd2776e39c2a igc: return early when failing to read EECD register

[Test Plan]
1. Install Ubuntu image and boot into the OS
2. Connect TBT monitor to SUT via K2 dock
3. Check if the monitor is working

[Where problems could occur]
May cause regression regarding some cases which were false positive beforehand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2094759/+subscriptions