[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

2018-02-12 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.13.0-1020.21

---
linux-oem (4.13.0-1020.21) xenial; urgency=low

  * linux-oem: 4.13.0-1020.21 -proposed tracker (LP: #1746017)

  [ Stefan Bader ]
  * Firmware upgrade interface for CAC Reader BCM58102 (LP: #1744041)
- SAUCE: Support fw upgrade for CAC Reader BCM58102

  * the wifi driver is always hard blocked on a lenovo laptop (LP: #1743672)
- ACPI: EC: Fix possible issues related to EC initialization order

  * ath9k can't connect to wifi AP (LP: #1727228)
- ath9k: add MSI support
- ath9k: add a quirk to set use_msi automatically

  * boot failure on AMD Raven + WesternXT (LP: #1742759)
- SAUCE: drm/amdgpu: add atpx quirk handling (v2)

  * x86: CFL missing from early quirks (LP: #1742755)
- drm/i915: add GT number to intel_device_info
- drm/i915/kbl: Change a KBL pci id to GT2 from GT1.5
- SAUCE: x86/gpu: add CFL to early quirks

  * [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device  (LP: #1741166)
- Bluetooth: btusb: Add support for 0cf3:e010

  * QCA Rome bluetooth failed to work after applying reset-resume quirk
(LP: #1741206)
- Revert "Bluetooth: btusb: fix QCA Rome suspend/resume"
- usb: quirks: Add reset-resume quirk for Dell DW1820 QCA Rome Bluetooth

  * [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working,
2-ring mic not working, both not shown in sound settings  (LP: #1740974)
- ALSA: hda - Add MIC_NO_PRESENCE fixup for 2 HP machines

  * Two front mics can't work on a lenovo machine (LP: #1740973)
- ALSA: hda - change the location for one mic on a Lenovo machine

  * No external microphone be detected via headset jack on a dell machine
(LP: #1740972)
- ALSA: hda - fix headset mic detection issue on a Dell machine

  *  Can't detect external headset via line-out jack on some Dell machines
(LP: #1740971)
- ALSA: hda/realtek - Fix Dell AIO LineOut issue

 -- Timo Aaltonen   Mon, 29 Jan 2018
16:51:18 +0200

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

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released

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

  [Fix]
  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
  stack.

  [Test]
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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


[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

2018-02-02 Thread Kai-Heng Feng
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

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

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

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

  [Fix]
  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
  stack.

  [Test]
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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


[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

2018-02-02 Thread Timo Aaltonen
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-
xenial'.

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 https://wiki.ubuntu.com/Testing/EnableProposed 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.
https://bugs.launchpad.net/bugs/1741206

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

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

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

  [Fix]
  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
  stack.

  [Test]
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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


[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

2018-01-23 Thread Timo Aaltonen
** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu Xenial)
   Status: New => Invalid

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New

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

  [Fix]
  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
  stack.

  [Test]
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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


[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

2018-01-11 Thread Timo Aaltonen
** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem package in Ubuntu:
  New

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

  [Fix]
  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
  stack.

  [Test]
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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


[Kernel-packages] [Bug 1741206] Re: QCA Rome bluetooth failed to work after applying reset-resume quirk

2018-01-04 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

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

Status in linux package in Ubuntu:
  Triaged

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

  [Fix]
  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
  stack.

  [Test]
  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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741206/+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