[BUG REPORT] Chinese Bluetooth Dongle: Potential broken command in btusb module

[kamikazechaser]

Device: CSR8510 A10

Looks like a broken command in btusb module.

kernel details:

Code: Select all

[    0.000000] Linux version 6.11.2-amd64 (stevep@mxlinux.org) (x86_64-linux-gnu-gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.11.2-1~mx23ahs (2024-10-11)

lsusb output:

Code: Select all

Bus 001 Device 006: ID 10d7:b012  CSR8510 A10

/sys/kernel/debug/usb/devices output:

Code: Select all

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  6 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=10d7 ProdID=b012 Rev=88.91
S:  Product=CSR8510 A10
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  25 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  33 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E:  Ad=03(O) Atr=01(Isoc) MxPS=  49 Ivl=1ms
E:  Ad=83(I) Atr=01(Isoc) MxPS=  49 Ivl=1ms

dmesg output:

Code: Select all

[    0.057064] Spectre V2 : Enabling Speculation Barrier for firmware calls
[    0.264293] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.287156] acpi PNP0A08:00: [Firmware Info]: ECAM [mem 0xf0000000-0xf7ffffff] for domain 0000 [bus 00-7f] only partially covers this bridge
[    6.751579] [drm] Loading DMUB firmware via PSP: version=0x01010028
[    6.752158] [drm] Found VCN firmware Version ENC: 1.22 DEC: 7 VEP: 0 Revision: 1
[   14.797541] Bluetooth: Core ver 2.22
[   14.797595] NET: Registered PF_BLUETOOTH protocol family
[   14.797597] Bluetooth: HCI device and connection manager initialized
[   14.797604] Bluetooth: HCI socket layer initialized
[   14.797607] Bluetooth: L2CAP socket layer initialized
[   14.797613] Bluetooth: SCO socket layer initialized
[ 3202.592672] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 3202.592677] Bluetooth: hci0: HCI Read Transmit Power Level command is advertised, but not supported.
[ 3202.592679] Bluetooth: hci0: HCI LE Set Random Private Address Timeout command is advertised, but not supported.
[ 3204.679799] Bluetooth: hci0: Opcode 0x1004 failed: -110
[ 3265.063745] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 3265.063752] Bluetooth: hci0: HCI Read Transmit Power Level command is advertised, but not supported.
[ 3265.063755] Bluetooth: hci0: HCI LE Set Random Private Address Timeout command is advertised, but not supported.
[ 3267.142067] Bluetooth: hci0: command 0x1004 tx timeout
[ 3267.142073] Bluetooth: hci0: Opcode 0x1004 failed: -110
[ 3281.192036] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 3281.192043] Bluetooth: hci0: HCI Read Transmit Power Level command is advertised, but not supported.
[ 3281.192045] Bluetooth: hci0: HCI LE Set Random Private Address Timeout command is advertised, but not supported.
[ 3283.269449] Bluetooth: hci0: Opcode 0x1004 failed: -110
[ 3283.269449] Bluetooth: hci0: command 0x1004 tx timeout
[ 3417.664189] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 3417.664200] Bluetooth: hci0: HCI Read Transmit Power Level command is advertised, but not supported.
[ 3417.664202] Bluetooth: hci0: HCI LE Set Random Private Address Timeout command is advertised, but not supported.
[ 3419.714654] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 3549.984130] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 3549.984137] Bluetooth: hci0: HCI Read Transmit Power Level command is advertised, but not supported.
[ 3549.984140] Bluetooth: hci0: HCI LE Set Random Private Address Timeout command is advertised, but not supported.
[ 3552.062235] Bluetooth: hci0: command 0x1004 tx timeout
[ 3552.062235] Bluetooth: hci0: Opcode 0x1004 failed: -110

hciconfig hci0 up output:

Code: Select all

Can't init device hci0: Connection timed out (110)

[kamikazechaser]

Just saw this related Kernel upstream patch: https://git.kernel.org/pub/scm/linux/ke ... 28e24d12bc

I'll try and compile/load the upstream module.

[Stevo]

Try the latest 6.11.5 AHS-backported Debian Sid kernel; it has btusb fixes that I think are the same.

[kamikazechaser]

No success on 11.5 or 11.9. However it does work on 6.5.3-1~mx23ahs (2023-09-17).

[kamikazechaser]

This is an upstream related issue. A temporary fix is to change the device identifier here https://git.kernel.org/pub/scm/linux/ke ... 28e24d12bc or to revert to the previous size handling code i.e size = le16_to_cpu(data->intr_ep->wMaxPacketSize);