[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1948898
Title:
Bluetooth HCI reset fail during airplane mode switch stress tests
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Won't Fix
Status in linux-oem-5.13 source package in Focal:
Won't Fix
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Won't Fix
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
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
[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 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:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Won't Fix
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
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
[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 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:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
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
[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests
** Also affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.10 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-oem-5.13 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => High
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 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:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
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
[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests
** Attachment added: "btmon.5.13.0-1017-oem_BIOS-0.12.71_AX210"
https://bugs.launchpad.net/bugs/1948898/+attachment/5537450/+files/btmon.5.13.0-1017-oem_BIOS-0.12.71_AX210
** Attachment added: "dmesg.5.13.0-1017-oem"
https://bugs.launchpad.net/bugs/1948898/+attachment/5537451/+files/dmesg.5.13.0-1017-oem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 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:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
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
