Fix broken MSI interrupt after HDA controller was suspended
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.6 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Unassigned | ||
Groovy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
After HDA controller gets suspended and resumed, no MSI interrupt raised
when plugging headset to the audio jack.
[Fix]
Power up the Realtek codec when HDA controller runtime resumes.
[Test]
1) Make sure both codec and HDA controller are runtime suspended.
2) Runtime resume the HDA controller without runtime resume the codec.
3) Plug a headset and see if the system can detect anything.
With the fix applied, we can see azx_interrupt() is working again by
using ftrace.
[Regression Potential]
If there's any system that is not affected by this issue, runtime-resume
the HDA controller will take a slightly longer time. It's rather
unlikely, since _all_ systems with Realtek codec we tested have this
issue, regardless of AMD or Intel.
CVE References
Changed in linux (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Groovy): | |
status: | New → Confirmed |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Groovy): | |
importance: | Undecided → Medium |
Changed in linux-oem-5.6 (Ubuntu Groovy): | |
status: | New → Invalid |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: oem-priority originate-from-1896576 somerville |
no longer affects: | linux (Ubuntu) |
no longer affects: | linux (Ubuntu Focal) |
no longer affects: | linux (Ubuntu Groovy) |
no longer affects: | linux-oem-5.6 (Ubuntu Groovy) |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | Confirmed → In Progress |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
no longer affects: | linux-oem-5.6 (Ubuntu Focal) |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Fix Released |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Fix Released |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
Changed in linux (Ubuntu Groovy): | |
status: | New → Fix Committed |
Changed in linux-oem-5.6 (Ubuntu Groovy): | |
status: | New → Invalid |
tags: |
added: verification-done-groovy removed: verification-needed-groovy |
Changed in hwe-next: | |
status: | New → Fix Released |
This bug is awaiting verification that the 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!