Fix missing external headset after resume problem for Cirrus CS8409 sound driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Chris Chiu | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
Jammy |
Won't Fix
|
Undecided
|
Chris Chiu | ||
linux-oem-5.13 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume.
[Fix]
Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume.
[Test]
Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected.
[Where problem could occur]
Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem.
================== Original Bug Description =======
[Summary] System can't detect external headset after suspend
[Steps to reproduce]
1. install manifest and boot into OS
2. plug-in an external headset in front headset port
3. un-plug external headset
4. suspend system
5. resume system from suspend
6. plug-in an external headset
[Expected result]
System could detect external headset after suspend
[Actual result]
System can't detect external headset after suspend
[Failure rate]
3/3
[Additional information]
CID: 202110-29567
SKU: DLPV-SFF-DVT-C1
Image: canonical-
system-
system-
bios-version: 0.13.73
CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
GPU: 0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c)
kernel-version: 5.13.0-1019-oem
[Stage]
Issue reported and logs collected right after it happened
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
status: | New → In Progress |
tags: | added: oem-priority originate-from-1951215 somerville |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → Chris Chiu (mschiu77) |
status: | Incomplete → Triaged |
Changed in linux (Ubuntu Focal): | |
status: | Incomplete → Won't Fix |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.13 (Ubuntu Jammy): | |
status: | New → Invalid |
Changed in hwe-next: | |
status: | New → Fix Released |
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 1952385
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.