From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure
Date: Tue, 22 Mar 2022 13:38:15 +0000 [thread overview]
Message-ID: <bug-215725-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215725
Bug ID: 215725
Summary: Basilisk X Hyperspeed Bluetooth LE mouse fail to
connect under 5.17 with Opcode 0x2043 failure
Product: Drivers
Version: 2.5
Kernel Version: 5.17
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: winstonwu91@gmail.com
Regression: No
I am using AX201 wireless card (lsusb shows Bus 001 Device 004: ID 8087:0026
Intel Corp. AX201 Bluetooth) and the mouse stopped working with bluetooth mode
under 5.17. 5.16 does not have such problem.
dmesg:
[ 2.341184] Bluetooth: Core ver 2.22
[ 2.341206] Bluetooth: HCI device and connection manager initialized
[ 2.341209] Bluetooth: HCI socket layer initialized
[ 2.341210] Bluetooth: L2CAP socket layer initialized
[ 2.341213] Bluetooth: SCO socket layer initialized
[ 2.553340] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[ 2.553425] Bluetooth: hci0: Boot Address: 0x24800
[ 2.553427] Bluetooth: hci0: Firmware Version: 126-5.22
[ 2.553428] Bluetooth: hci0: Firmware already loaded
[ 2.589714] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.589716] Bluetooth: BNEP filters: protocol multicast
[ 2.589719] Bluetooth: BNEP socket layer initialized
[ 6.742276] Bluetooth: hci0: Opcode 0x2043 failed: -110
[ 6.742288] Bluetooth: hci0: request failed to create LE connection: err
-110
[ 6.872510] Bluetooth: hci0: ACL packet for unknown connection handle 3586
[ 6.872587] Bluetooth: hci0: ACL packet for unknown connection handle 3586
[ 6.872663] Bluetooth: hci0: ACL packet for unknown connection handle 3586
...(repeat)
[ 21.535407] Bluetooth: RFCOMM TTY layer initialized
[ 21.535414] Bluetooth: RFCOMM socket layer initialized
[ 21.535418] Bluetooth: RFCOMM ver 1.11
journalctl -b -u bluetooth:
3月 22 09:15:37 darenguodu systemd[1]: Starting Bluetooth service...
3月 22 09:15:37 darenguodu bluetoothd[618]: Bluetooth daemon 5.64
3月 22 09:15:37 darenguodu bluetoothd[618]: src/main.c:check_config() Unknown
group Controller in /etc/bluetooth/main.conf
3月 22 09:15:37 darenguodu systemd[1]: Started Bluetooth service.
3月 22 09:15:37 darenguodu bluetoothd[618]: Starting SDP server
3月 22 09:15:37 darenguodu bluetoothd[618]: Bluetooth management interface 1.21
initialized
3月 22 09:15:37 darenguodu bluetoothd[618]: Failed to set mode: Busy (0x0a)
3月 22 09:15:38 darenguodu bluetoothd[618]:
profiles/battery/battery.c:parse_battery_level() Trying to update an
unregistered battery
3月 22 09:15:56 darenguodu bluetoothd[618]: Player registered: sender=:1.56
path=/media_player0
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/ldac
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSink/aptx_hd
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aptx_hd
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSink/aptx
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aptx
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aac
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSink/sbc
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/sbc
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSink/sbc_xq
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/sbc_xq
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aptx_ll_1
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aptx_ll_0
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/faststream
3月 22 09:15:56 darenguodu bluetoothd[618]: Endpoint registered: sender=:1.56
path=/MediaEndpoint/A2DPSource/faststream_duplex
3月 22 09:16:03 darenguodu bluetoothd[618]: src/profile.c:record_cb() Unable to
get Hands-Free Voice gateway SDP record: Host is down
--
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:[~2022-03-22 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:38 bugzilla-daemon [this message]
2022-03-29 8:01 ` [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure Thorsten Leemhuis
2022-03-29 8:01 ` [Bug 215725] " bugzilla-daemon
2022-03-29 21:04 ` bugzilla-daemon
2022-04-09 11:00 ` [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot Thorsten Leemhuis
2022-05-04 13:12 ` [Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure bugzilla-daemon
2022-05-04 14:21 ` bugzilla-daemon
2022-10-03 10:54 ` 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-215725-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).