Skip to contentSkip to conversation

New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure

Bug 215725 [email protected] 2 participants 10 messages Mar 22, 2022 – Oct 3, 2022

Subsystems (2)
Bluetooth drivers Regressions
lore
Share & tools
lore

[email protected]

author
#0 lore 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: [email protected]
          Reporter: [email protected]
        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

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

Hi, this is your Linux kernel regression tracker.

Quoted 5 lines · On 22.03.22 14:38, [email protected] wrote:

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

Hey bluetooth maintainers, what's up here? That's a report about a regression that was submitted more than a week ago. Has anything happened to get it fixed? Reminder: this ideally should be fixed in 5.17.y before 5.16.y becomes EOL, which I guess will happen in round about two or three weeks from now.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.

author
#2 lore raw

[Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure

In reply to [email protected]

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

--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- Hi, this is your Linux kernel regression tracker.

Quoted 5 lines · On 22.03.22 14:38, [email protected] wrote:

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

Hey bluetooth maintainers, what's up here? That's a report about a regression that was submitted more than a week ago. Has anything happened to get it fixed? Reminder: this ideally should be fixed in 5.17.y before 5.16.y becomes EOL, which I guess will happen in round about two or three weeks from now.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.

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.
author
#3 lore raw

[Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure

In reply to [email protected]

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

Luiz Von Dentz ([email protected]) changed:

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

--- Comment #2 from Luiz Von Dentz ([email protected]) --- (In reply to Winston Wu from comment #0)

Quoted 3 lines

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.

Could you please attach the HCI trace using btmon -w?

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.
#4 lore raw

Re: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot

In reply to [email protected]

TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter.

About a week ago a regression was reported to bugzilla.kernel.org that seems to be handled there already, nevertheless I'd like to add to the tracking to ensure it's not forgotten.

#regzbot introduced: v5.16..v5.17
#regzbot from: Winston Wu <[email protected]>
#regzbot title: net: bluetooth: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215725

Quote:

Quoted 19 lines · On 22.03.22 14:38, [email protected] wrote:

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: [email protected]
          Reporter: [email protected]
        Regression: No
Quoted 3 lines

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.

See the ticket for details, there were a few replies already.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.

#5 lore raw

Re: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot

Quoted 8 lines · Thorsten Leemhuis

TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter.

About a week ago a regression was reported to bugzilla.kernel.org that seems to be handled there already, nevertheless I'd like to add to the tracking to ensure it's not forgotten.

Quoted 5 lines

#regzbot introduced: v5.16..v5.17
#regzbot from: Winston Wu <[email protected]>
#regzbot title: net: bluetooth: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215725

#regzbot monitor:
https://lore.kernel.org/all/[email protected]%2F/
#regzbot ignore-activity

author
#7 lore raw

[Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure

In reply to [email protected]

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

The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) changed:

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

--- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- (In reply to Luiz Von Dentz from comment #2)

Quoted 7 lines

(In reply to Winston Wu from comment #0)

Quoted 1 line

I am using AX201 wireless card (lsusb shows Bus 001 Device 004: ID

8087:0026

Quoted 2 lines

Intel Corp. AX201 Bluetooth) and the mouse stopped working with bluetooth mode under 5.17. 5.16 does not have such problem.

Could you please attach the HCI trace using btmon -w?

Winston Wu, did you miss this, are you having trouble with this, or what's the status here?

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.
author
#8 lore raw

[Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure

In reply to [email protected]

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

--- Comment #4 from Winston Wu ([email protected]) --- Hi it seems that the problem no longer presents after 5.17.3 or so…

Quoted 31 lines · 在 2022年5月4日，上午9:12，[email protected] 写道：

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

The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) changed:

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

--- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) ---
(In reply to Luiz Von Dentz from comment #2)

Quoted 7 lines

(In reply to Winston Wu from comment #0)

Quoted 1 line

I am using AX201 wireless card (lsusb shows Bus 001 Device 004: ID

8087:0026

Quoted 2 lines

Intel Corp. AX201 Bluetooth) and the mouse stopped working with bluetooth mode under 5.17. 5.16 does not have such problem.

Could you please attach the HCI trace using btmon -w?

Winston Wu, did you miss this, are you having trouble with this, or what's the
status here?

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

You are receiving this mail because:
You reported the bug.
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.
#6 lore raw

Re: [Bug 215725] New: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #forregzbot

In reply to Thorsten Leemhuis
Quoted 15 lines · Thorsten Leemhuis
Quoted 8 lines · Thorsten Leemhuis

TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter.

About a week ago a regression was reported to bugzilla.kernel.org that seems to be handled there already, nevertheless I'd like to add to the tracking to ensure it's not forgotten.

Quoted 5 lines

#regzbot introduced: v5.16..v5.17
#regzbot from: Winston Wu <[email protected]>
#regzbot title: net: bluetooth: Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215725

Quoted 3 lines

#regzbot monitor:
https://lore.kernel.org/all/[email protected]%2F/
#regzbot ignore-activity

#regzbot invalid: doesn#t happen anymore with 5.17.3

author
#9 lore raw

[Bug 215725] Basilisk X Hyperspeed Bluetooth LE mouse fail to connect under 5.17 with Opcode 0x2043 failure

In reply to [email protected]

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

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #5 from Paul Menzel ([email protected]) --- (In reply to Winston Wu from comment #4)

Quoted 1 line

Hi it seems that the problem no longer presents after 5.17.3 or so…

Thank you for reporting back. If you have time, it’d be great if you could figure out the exact commit. Otherwise, it’d be great if you closed the issue/bug report.

PS: If you reply via email, please do not quote/cite the original email, as the quote is not hidden in the Bugzilla comment, making it hard to read.

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.