some codecs stop working after S3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Critical
|
Hui Wang | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Critical
|
Hui Wang | ||
linux-oem (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
To fix this bug, B/OEM-B/C needs only 1 patch, while v5.0-rc1 introduced
a new patch which affect this issue, so the DISCO needs 2 patches.
[Impact]
After S3, some codecs (alc236, alc255, alc891 and some HDMI codec) stop
working, they can't detect jack plugging/unplugging or the audio device
can't show up in the gnome-sound-setting
[Fix]
After S3, if it runs runtime_resume(), the codec works again. We change
the driver to let system_resume() trigger runtime_resume()
[Test Case]
This issue is reported from OEM project, some codecs can't detect
jack pluggin/unplugging, some codecs can't show up in the UI, after
applying this patch, all related bugs are fixed.
[Regression Potential]
Low. have tested on many machines (with this issue or without this issue),
all worked well.
Changed in linux (Ubuntu): | |
importance: | Undecided → Critical |
description: | updated |
tags: | added: originate-from-1817519 somerville |
tags: | added: originate-from-1811173 |
Changed in linux (Ubuntu Disco): | |
status: | Incomplete → Fix Committed |
tags: |
added: verification-done-bionic verification-done-cosmic removed: verification-needed-bionic verification-needed-cosmic |
Changed in linux-oem (Ubuntu): | |
status: | New → Fix Released |
Changed in hwe-next: | |
status: | New → Fix Released |
tags: | added: cscc |
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 1820930
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.