| 2019-12-27 07:25:28 |
You-Sheng Yang |
bug |
|
|
added bug |
| 2019-12-27 07:50:28 |
You-Sheng Yang |
bug |
|
|
added subscriber Canonical Hardware Enablement |
| 2019-12-27 07:50:33 |
You-Sheng Yang |
tags |
|
oem-priority originate-from-1856797 stella |
|
| 2019-12-27 07:51:05 |
You-Sheng Yang |
linux-firmware (Ubuntu): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2019-12-27 07:51:19 |
You-Sheng Yang |
linux-firmware (Ubuntu): status |
New |
In Progress |
|
| 2019-12-27 08:45:59 |
You-Sheng Yang |
tags |
oem-priority originate-from-1856797 stella |
apport-collected bionic oem-priority originate-from-1856797 stella |
|
| 2019-12-27 08:46:01 |
You-Sheng Yang |
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-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. |
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.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Dependencies:
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.14
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18
Tags: bionic
Uname: Linux 4.15.0-1066-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
|
| 2019-12-27 08:46:02 |
You-Sheng Yang |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1857673/+attachment/5315800/+files/ProcCpuinfoMinimal.txt |
|
| 2019-12-27 08:46:03 |
You-Sheng Yang |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1857673/+attachment/5315801/+files/ProcEnviron.txt |
|
| 2019-12-27 08:57:45 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-12-27 08:57:45 |
You-Sheng Yang |
bug task added |
|
linux-firmware (Ubuntu Bionic) |
|
| 2019-12-27 08:57:53 |
You-Sheng Yang |
linux-firmware (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-12-27 08:57:56 |
You-Sheng Yang |
linux-firmware (Ubuntu Bionic): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2019-12-27 08:58:10 |
You-Sheng Yang |
linux-firmware (Ubuntu): status |
In Progress |
Invalid |
|
| 2019-12-27 08:59:25 |
You-Sheng Yang |
nominated for series |
|
Ubuntu Disco |
|
| 2019-12-27 08:59:25 |
You-Sheng Yang |
bug task added |
|
linux-firmware (Ubuntu Disco) |
|
| 2019-12-27 08:59:40 |
You-Sheng Yang |
linux-firmware (Ubuntu Disco): status |
New |
Won't Fix |
|
| 2019-12-27 09:10:55 |
You-Sheng Yang |
attachment added |
|
dmesg.4.15.0-1066-oem.REL0450 https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1857673/+attachment/5315802/+files/dmesg.4.15.0-1066-oem.REL0450 |
|
| 2019-12-27 09:11:09 |
You-Sheng Yang |
attachment added |
|
dmesg.4.15.0-1066-oem.REL0482 https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1857673/+attachment/5315803/+files/dmesg.4.15.0-1066-oem.REL0482 |
|
| 2020-01-12 14:32:27 |
hugh chao |
bug |
|
|
added subscriber hugh chao |
| 2020-01-27 05:35:43 |
You-Sheng Yang |
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-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.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Dependencies:
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.14
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18
Tags: bionic
Uname: Linux 4.15.0-1066-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
[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-17-16-1.sfi. This patch will SRU 0482 to keep synced with
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-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.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Dependencies:
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.14
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18
Tags: bionic
Uname: Linux 4.15.0-1066-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True |
|
| 2020-01-31 13:27:12 |
Timo Aaltonen |
linux-firmware (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-01-31 13:27:14 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-01-31 13:27:16 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2020-02-03 02:12:53 |
You-Sheng Yang |
tags |
apport-collected bionic oem-priority originate-from-1856797 stella |
apport-collected bionic oem-priority originate-from-1856797 stella verification-done-bionic |
|
| 2020-02-27 17:09:50 |
Launchpad Janitor |
linux-firmware (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-02-27 17:10:04 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-03-18 07:10:26 |
You-Sheng Yang |
hwe-next: status |
New |
Fix Released |
|
