Public bug reported:

Bug 1928838 fixed possible kernel panic when doing rfkill block on Intel
Bluetooth controller. The fix was also upstreamed in v5.14-rc1 as commit
0ea9fd001a14e ("Bluetooth: Shutdown controller after workqueues are
flushed or cancelled") and was backported to v5.10.51, v5.12.18, and
v5.13.3. However, as indicated in https://lore.kernel.org/linux-
bluetooth/8735ryk0o7....@baylibre.com/ , it caused a regression to
mtkbtsdio and was then fixed in upstream commit 0ea53674d07f ("
Bluetooth: Move shutdown callback before flushing tx and rx queue")
since v5.15-rc1 and has been backported to v5.14.3. Current statuses:

* v5.10.x:
  * 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
  * 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
* v5.11.x: N/A
* v5.12.x:
  * 0ea9fd001a14e: backported(v5.12.18)
* v5.13.x:
  * 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
  * 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
* v5.14.x:
  * 0ea9fd001a14e: committed(v5.14-rc1)
  * 0ea53674d07f: backported(v5.14.3)
* v5.15.x:
  * 0ea53674d07f: committed(v5.15-rc1)

As a result, this affects 5.10/11/13 kernels.

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: hwe-bluetooth ihv-intel oem-priority originate-from-1940428 somerville

** Tags added: oem-priority originate-from-1940428 somerville

-- 
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/1948898

Title:
  Bluetooth HCI reset fail during airplane mode switch stress tests

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Bug 1928838 fixed possible kernel panic when doing rfkill block on
  Intel Bluetooth controller. The fix was also upstreamed in v5.14-rc1
  as commit 0ea9fd001a14e ("Bluetooth: Shutdown controller after
  workqueues are flushed or cancelled") and was backported to v5.10.51,
  v5.12.18, and v5.13.3. However, as indicated in
  https://lore.kernel.org/linux-bluetooth/8735ryk0o7....@baylibre.com/ ,
  it caused a regression to mtkbtsdio and was then fixed in upstream
  commit 0ea53674d07f (" Bluetooth: Move shutdown callback before
  flushing tx and rx queue") since v5.15-rc1 and has been backported to
  v5.14.3. Current statuses:

  * v5.10.x:
    * 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
    * 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
  * v5.11.x: N/A
  * v5.12.x:
    * 0ea9fd001a14e: backported(v5.12.18)
  * v5.13.x:
    * 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
    * 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
  * v5.14.x:
    * 0ea9fd001a14e: committed(v5.14-rc1)
    * 0ea53674d07f: backported(v5.14.3)
  * v5.15.x:
    * 0ea53674d07f: committed(v5.15-rc1)

  As a result, this affects 5.10/11/13 kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1948898/+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