Fix drm/amd/pm: enable ASPM by default
Bug #1966680 reported by
koba
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Critical
|
koba | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
koba | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
koba | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
koba | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
koba | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200&rx540 gpus encounter the resume&hange issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend&resume machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
CVE References
description: | updated |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
Changed in linux (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
tags: | added: oem-priority originate-from-1952981 somerville |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | Confirmed → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Focal): | |
status: | Confirmed → Invalid |
Changed in hwe-next: | |
importance: | Undecided → Critical |
status: | New → Incomplete |
Changed in hwe-next: | |
assignee: | nobody → koba (kobako) |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
Changed in hwe-next: | |
status: | Incomplete → In Progress |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | Fix Committed → Invalid |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in hwe-next: | |
status: | In Progress → Fix Committed |
Changed in hwe-next: | |
status: | Fix Committed → Fix Released |
tags: | added: verification-done-jammy |
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 |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.