Not all monitors connected on the dock display correctly when the system resumes from restart or suspend on AMD platform
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux-oem-6.11 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
AceLan Kao | ||
linux-oem-6.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Fix Released
|
Undecided
|
AceLan Kao |
Bug Description
[Impact]
Not all monitors display well after resume from restart/power off/suspend when connect one/two/three monitors on the dock.
[Fix]
AMD provides a series of patches which are included in 6.15-rc6 fixes the issue
65924ec69b292 drm/amd/display: Fix wrong handling for AUX_DEFER case
3924f45d4de72 drm/amd/display: Copy AUX read reply data whenever length > 0
396dc51b3b7ea drm/amd/display: Remove incorrect checking in dmub aux handler
bc70e11b550d3 drm/amd/display: Fix the checking condition in dmub aux handling
5a3846648c052 drm/amd/display: Shift DMUB AUX reply command if necessary
[Test]
1. Connect one/two/three monitors with dock to AMD platform
2. Let the system into restart/power off/suspend, all monitors should all display after resume from restart/power off/suspend
[Where problems could occur]
Hard to evaluate, but only one commit doesn't CC stable, so we eventually will include those patches.
CVE References
- 2025-37797
- 2025-37799
- 2025-37800
- 2025-37801
- 2025-37802
- 2025-37803
- 2025-37804
- 2025-37805
- 2025-37806
- 2025-37807
- 2025-37808
- 2025-37809
- 2025-37810
- 2025-37811
- 2025-37812
- 2025-37813
- 2025-37814
- 2025-37815
- 2025-37816
- 2025-37817
- 2025-37818
- 2025-37819
- 2025-37820
- 2025-37821
- 2025-37822
- 2025-37823
- 2025-37824
- 2025-37825
- 2025-37826
- 2025-37827
- 2025-37828
- 2025-37829
- 2025-37830
- 2025-37831
- 2025-37832
- 2025-37833
- 2025-37834
- 2025-37876
- 2025-37877
- 2025-37878
- 2025-37879
- 2025-37880
- 2025-37881
- 2025-37882
- 2025-37883
- 2025-37884
- 2025-37885
- 2025-37886
- 2025-37887
- 2025-37888
Changed in linux-oem-6.11 (Ubuntu Noble): | |
status: | New → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
tags: | added: jira-wtn-226 oem-priority wtn |
tags: | added: jira-stella-1749 stella |
tags: | removed: jira-stella-1749 |
Changed in linux-oem-6.11 (Ubuntu Noble): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-noble-linux-oem-6.11 removed: verification-needed-noble-linux-oem-6.11 |
Changed in linux-oem-6.14 (Ubuntu Noble): | |
status: | New → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-6.14 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-6.11 (Ubuntu): | |
status: | New → Invalid |
description: | updated |
description: | updated |
description: | updated |
tags: | added: jira-wtn-224 |
Changed in linux-oem-6.14 (Ubuntu Noble): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-noble-linux-oem-6.14 removed: verification-needed-noble-linux-oem-6.14 |
This bug is awaiting verification that the linux-oem- 6.11/6. 11.0-1023. 23 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!