Fix WD22TB4 suspend and resume, two external monitor can not output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
koba | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Resume SUT from suspend mode, found external monitors can not output, but display setting can recognize external monitors.
[Fix]
The WD22TB4 Thunderbolt dock at least will revert its DP_MAX_LINK_RATE
from HBR3 to HBR2 after system suspend/resume if the DP_DP13_DPCD_REV
registers are not read subsequently also as required.
Fix this by reading DP_DP13_DPCD_REV registers as well, matching what is
done during connector detection. While at it also fix up the same call
in drm_dp_
[Test Case]
1. Connect two 4K external monitor to WD22TB4.
2. Put SUT into suspend mode and wait 30sec
3. Resume SUT from suspend mode, found external monitors can not output.
[Where problems could occur]
low
Related branches
CVE References
description: | updated |
tags: | added: oem-priority originate-from-1959016 somerville |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Incomplete |
status: | Incomplete → Invalid |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | New → In Progress |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → Fix Committed |
Changed in hwe-next: | |
importance: | Undecided → Critical |
Changed in hwe-next: | |
assignee: | nobody → koba (kobako) |
tags: |
added: verification-done-focal removed: verification-needed-focal |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
Changed in linux (Ubuntu Focal): | |
status: | Incomplete → Invalid |
Changed in linux (Ubuntu Jammy): | |
status: | Incomplete → In Progress |
Changed in hwe-next: | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | In Progress → Fix Committed |
Changed in hwe-next: | |
status: | In Progress → Fix Committed |
Changed in hwe-next: | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in linux (Ubuntu Kinetic): | |
status: | New → Fix Released |
Changed in linux-oem-5.14 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
This bug is awaiting verification that the linux-oem- 5.14/5. 14.0-1045. 51 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- focal' to 'verification- done-focal' . If the problem still exists, change the tag 'verification- needed- focal' to 'verification- failed- focal'.
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!