This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-xenial

** Changed in: linux-oem (Ubuntu Xenial)
       Status: New => Fix Committed

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  QCA Rome bluetooth failed to work after applying reset-resume quirk

Status in linux package in Ubuntu:
Status in linux-oem package in Ubuntu:
Status in linux source package in Xenial:
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  Some QCA ROME bluetooth devices does not work after runtime suspend/resume 
after SRU LP: #1734020.

  The commit let btusb reset at second time it resume, i.e. btusb_open(). The 
btusb stops working because the reset happens *after* btusb_open(). The reset 
should be done at hub port initialization, before btusb_probe().

  Revert the bad commit and use the reset-resume quirk in USB core

  Cherry-picked the commit into Artful/OEM kernel and the issue is fixed.

  [Regression Potential]
  Low. This is limited to QCA Rome, also verified by the original quirk author.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to