Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Medium
|
koba | ||
Kinetic |
Fix Released
|
Medium
|
koba | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
koba | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-6.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
koba | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
SUT can't displayed after resume from WB/CB with dGFX installed.
Recovery: SUT can display when the DP cable unplug and plug .
[Fix]
Use quirk to block the affected SKUes.
[Test Case]
1.Install Ubuntu 22.04 on SUT with dGFX card.
2.Connect the DP cable to the dGFX port.
3.SUT do power off/restart.
4.SUT can display.
[Where problems could occur]
Add SKU's id to a quirk table, the impact would be small.
[Other Info]
* For the pure Jammy, Confronted the error of compilation.
1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work
~~~
drivers/
18848 1449 | adev->dm.
18849 | ^~~~~~~
18850 | hdcp_create_
~~~
2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter
~~~
drivers/
18838 1505 | if (dm_should_
~~~
* hpd_disconnect_
* Result from CBD
~~~
Jammy,
remote: *** kernel-cbd *******
remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt
remote: * For results: ssh cbd ls kobako-
remote: * 192/672 cores busy (2/7 hosts), 0 builds queued
remote: 2022-12-15 17:09:15 kobako-
remote: 2022-12-15 17:11:13 kobako-
remote: 2022-12-15 17:07:30 kobako-
remote: 2022-12-15 17:10:17 kobako-
remote: 2022-12-15 17:04:55 kobako-
remote: *******
To 54.69.112.
~~~
Kinetic
remote: *** kernel-cbd *******
remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt
remote: * For results: ssh cbd ls kobako-
remote: * 0/672 cores busy (0/7 hosts), 0 builds queued
remote: 2022-12-15 17:41:37 kobako-
remote: 2022-12-15 17:42:13 kobako-
remote: 2022-12-15 17:35:54 kobako-
remote: 2022-12-15 17:40:54 kobako-
remote: 2022-12-15 17:34:47 kobako-
remote: *******
To 54.69.112.
~~~
CVE References
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
Changed in linux-oem-6.0 (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
Changed in linux (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
Changed in linux (Ubuntu Kinetic): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
description: | updated |
tags: | added: oem-priority originate-from-1982388 somerville |
description: | updated |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-6.0 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-6.0 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-6.0 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux (Ubuntu Jammy): | |
status: | In Progress → Invalid |
Changed in linux (Ubuntu Kinetic): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | Invalid → In Progress |
Changed in linux (Ubuntu Kinetic): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-kinetic removed: verification-needed-kinetic |
tags: |
added: verification-done-kinetic removed: verification-needed-kinetic |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1999836
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.