Fix non-working QCA Rome Bluetooth after S3
Bug #1812812 reported by
Kai-Heng Feng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Sometimes QCA Rome Bluetooth USB host doesn't work after S3:
[ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_
[ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)
This is due to USB core enables LPM two times after S3.
[Fix]
Only enable LPM once.
[Test]
The Bluetooth USB works all the time after applying the fix.
[Regression Potential]
Low. Enabling a hardware feature twice in a row isn't right, I'd be surprise if any hardware relies on this driver behavior.
CVE References
tags: | added: originate-from-1783725 somerville |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Committed |
Changed in linux (Ubuntu Cosmic): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in hwe-next: | |
status: | New → Fix Released |
To post a comment you must log in.
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 1812812
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.