Fix resume on AMD platforms when TBT monitor is plugged
Bug #1990920 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned | ||
Kinetic |
Fix Released
|
Medium
|
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
|
Medium
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
When TBT monitor is connected to AMD platform, system resume will hit
stack corruption or BUG_ON() macro.
[Fix]
Revert the offending commit and handle MST properly.
[Test]
The system can resume normally and no more kernel splat.
[Where problems could occur]
The new logic is restriced to MST hub, so normal DP/HDMI usage should be
unaffected.
CVE References
Changed in linux (Ubuntu Kinetic): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Jammy): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Kinetic): | |
importance: | Undecided → Medium |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: oem-priority originate-from-1988032 stella |
tags: | added: verification-done-jammy |
Changed in linux (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
Changed in hwe-next: | |
importance: | Undecided → Critical |
Changed in linux-oem-5.14 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | New → Fix Committed |
tags: | added: verification-done-focal |
Changed in hwe-next: | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Kinetic): | |
status: | Confirmed → Fix Committed |
Changed in hwe-next: | |
status: | Fix Committed → Fix Released |
tags: |
added: verification-done-kinetic removed: verification-needed-kinetic |
To post a comment you must log in.
This bug is awaiting verification that the linux-oem- 5.17/5. 17.0-1019. 20 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- jammy' to 'verification- done-jammy' . If the problem still exists, change the tag 'verification- needed- jammy' to 'verification- failed- jammy'.
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!