Comment 0 for bug 1857673

Revision history for this message
You-Sheng Yang (vicamo) wrote :

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-17-16-1.sfi from upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b6427bf4faae9b8864e303d88c3ec8d0df017dac.

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.