Skip to contentSkip to conversation

New: AX201 Bluetooth unusable after: Shutdown controller after workqueues are flushed or cancelled

Bug 214273 [email protected] 1 participant 4 messages Sep 2, 2021 – Nov 18, 2021 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=214273

Bug ID: 214273
Summary: AX201 Bluetooth unusable after: Shutdown controller
after workqueues are flushed or cancelled
Product: Drivers
Version: 2.5
Kernel Version: 5.14
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: No

I've been using 5.14 since today, and I have had to revert 60789afc02f592b8d91217b60930e7a76271ae07 so that bluetooth works again with a 8087:0026 Intel Corp. AX201 Bluetooth on a Dell XPS 9300.

This is the dmesg:

------

[   16.531286] Bluetooth: Core ver 2.22
[   16.531306] Bluetooth: HCI device and connection manager initialized
[   16.531309] Bluetooth: HCI socket layer initialized
[   16.531312] Bluetooth: L2CAP socket layer initialized
[   16.531314] Bluetooth: SCO socket layer initialized
[   16.649289] Bluetooth: hci0: Firmware revision 0.0 build 191 week 21 2021
[   16.768878] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.768883] Bluetooth: BNEP filters: protocol multicast
[   16.768886] Bluetooth: BNEP socket layer initialized
[   19.048260] Bluetooth: RFCOMM TTY layer initialized
[   19.048267] Bluetooth: RFCOMM socket layer initialized
[   19.048272] Bluetooth: RFCOMM ver 1.11
[ 7043.393714] Bluetooth: hci0: unexpected event for opcode 0x0500
[ 7043.394091] Bluetooth: hci0: Firmware revision 0.0 build 191 week 21 2021
[25277.172310] Bluetooth: hci0: unexpected event for opcode 0x0500
[25277.173307] Bluetooth: hci0: Firmware revision 0.0 build 191 week 21 2021
[32499.334342] Bluetooth: hci0: unexpected event for opcode 0x0500
[32511.644752] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[32605.228360] Bluetooth: hci0: urb 000000009218d7b4 failed to resubmit (113)
[32614.898106] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[32956.688532] Bluetooth: hci0: urb 000000002e945dc3 failed to resubmit (113)
[32966.471603] Bluetooth: hci0: Failed to read MSFT supported features (-110)

Best regards,
François

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[Bug 214273] AX201 Bluetooth unusable after: Shutdown controller after workqueues are flushed or cancelled

https://bugzilla.kernel.org/show_bug.cgi?id=214273

Dmitry ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Dmitry ([email protected]) --- I have exactly same issue on Pop Os

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 214273] AX201 Bluetooth unusable after: Shutdown controller after workqueues are flushed or cancelled

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=214273

M ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from M ([email protected]) ---
In my case it just does not work at all. Using Debian and a Lenovo Yoga. This worked fine for me until Kernel 5.11 (Ubuntu) and also works well still on Debian 11 with Kernel 5.10.

The problem also persist in the new 5.15 kernel.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#3 lore raw

[Bug 214273] AX201 Bluetooth unusable after: Shutdown controller after workqueues are flushed or cancelled

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=214273

--- Comment #3 from M ([email protected]) --- (In reply to M from comment #2)

Quoted 5 lines

In my case it just does not work at all. Using Debian and a Lenovo Yoga. This worked fine for me until Kernel 5.11 (Ubuntu) and also works well still on Debian 11 with Kernel 5.10.

The problem also persist in the new 5.15 kernel.

I apologize. Please ignore my comment.
This was not a kernel issue. Works fine in Fedora with any kernel I have tried.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.