Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.178.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: linux-firmware (Ubuntu Disco)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1849779

Title:
  System will auto resume from sleep on receiving LE ADV after paired
  with BT LE devices

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Disco:
  Fix Committed

Bug description:
  System, with Intel 9260 Bluetooth fw ver < REL0472, 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. Known affected fw
  versions are:

  |commit|fw rev/kernel|4.15.0-66-generic|series|
  |-|-|-|-|
  |c2d8f1b7f820|0329|waked up|bionic|
  |ae90c3bce108|0386|waked up| |
  |046d1085b19e|0420|waked up|disco|
  |1e8253bbaafb|0450|waked up| |
  |7444ca40083a|0472|ok| |
  |fe48882708de|0482|ok|eoan| 

  This doesn't seem to apply to all platform with 9260, as there are
  some platforms with identical chip and fw version but are immune from
  this issue.

  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
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.9
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 25 06:50:31 2019
  Dependencies:
   
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1849779/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to