From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 214273] New: AX201 Bluetooth unusable after: Shutdown controller after workqueues are flushed or cancelled
Date: Thu, 02 Sep 2021 07:49:21 +0000 [thread overview]
Message-ID: <bug-214273-62941@https.bugzilla.kernel.org/> (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: linux-bluetooth@vger.kernel.org
Reporter: kubrick@fgv6.net
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
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-09-02 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 7:49 bugzilla-daemon [this message]
2021-10-19 8:53 ` [Bug 214273] AX201 Bluetooth unusable after: Shutdown controller after workqueues are flushed or cancelled bugzilla-daemon
2021-11-17 7:17 ` bugzilla-daemon
2021-11-18 8:44 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-214273-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.