System will auto resume from sleep on receiving LE ADV after paired with BT LE devices (Intel 9560 HrP)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux-firmware (Ubuntu) |
Invalid
|
Undecided
|
You-Sheng Yang | ||
Bionic |
Fix Released
|
Undecided
|
You-Sheng Yang | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
[Impact]
On some platform, with Intel 9560 Bluetooth fw ver REL0450, deep
suspend (S3) will be interrupted and resume automatically once it has
been paired with a BLE device. The device doesn't have to remain
connected, as long as there are BLE devices near by broadcasting LE
ADV.
[Fix]
This can be fixed with newer release of fw blob
intel/ibt-
Eoan.
[Test Case]
1. pair with BLE device and turn off the device. It should be listed
as Disconnected in System Bluetooth settings. Close the settings
app as well.
2. run `sudo btmon -t` in the background, make sure LE ADV packets
pop up.
3. run `sudo btmon -t` on another host to make sure there are LE ADV
packets during the suspend period.
3. trigger system deep suspend (S3) on DUT.
4. wait for around 1 minutes (depending on the surrounding
environment) and see if the DUT is resumed unsolicitedly.
[Regression Risk]
Low. Update only affected systems.
========== original bug description ==========
Similar to bug 1849779, on systems with Intel 9560 Bluetooth fw ver REL0450, deep suspend will be interrupted and resume automatically once it has been paired with a BLE device. The device doesn't have to remain connected, as long as there are BLE devices near by broadcasting LE ADV.
This can be fixed by updating intel/ibt-
Steps to reproduce:
1. pair with BLE device and turn off the device. It should be listed as Disconnected in System Bluetooth settings. Close the settings app as well.
2. run `sudo btmon -t` in the background, make sure LE ADV packets pop up.
3. run `sudo btmon -t` on another host to make sure there are LE ADV packets during the suspend period.
3. trigger system deep suspend (S3) on DUT.
4. wait for around 1 minutes (depending on the surrounding environment) and see if the DUT is resumed unsolicitedly.
Expects:
DUT only resumes when power button pressed or on other explicit requests.
Actual:
DUT resumes unsolicitedly within 1 minutes.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Dependencies:
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.14
PackageArchitec
ProcVersionSign
Tags: bionic
Uname: Linux 4.15.0-1066-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
tags: | added: oem-priority originate-from-1856797 stella |
Changed in linux-firmware (Ubuntu): | |
assignee: | nobody → You-Sheng Yang (vicamo) |
status: | New → In Progress |
Changed in linux-firmware (Ubuntu Bionic): | |
status: | New → In Progress |
assignee: | nobody → You-Sheng Yang (vicamo) |
Changed in linux-firmware (Ubuntu): | |
status: | In Progress → Invalid |
Changed in linux-firmware (Ubuntu Disco): | |
status: | New → Won't Fix |
description: | updated |
Changed in hwe-next: | |
status: | New → Fix Released |
apport information