Arch Linux

fanf42

Member

Registered: 2023-07-03

Posts: 1

Bluetooth: hci0: Failed to send headers (or body or access otp area)

Hello,

I have a lenovo T14S AMD Gen 3 with a Qualcomm NFA725A Wi-Fi card (which is actually reported by lspci as QCNFA765):

lspci -k -s 01:00.0
01:00.0 Network controller: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter (rev 01)
	Subsystem: Lenovo QCNFA765 Wireless Network Adapter
	Kernel driver in use: ath11k_pci
	Kernel modules: ath11k_pci

I never got bluetooth work on it in the past 8 months in the many kernels and linux-firmware there was in that time.

On boot, I get an error message about header not being sent:

kernel: thinkpad_acpi: radio switch found; radios are enabled
kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
...
rfkill[6774]: unblock set for type bluetooth
sudo[6773]: pam_unix(sudo:session): session closed for user root
kernel: usb 1-3.1: new full-speed USB device number 3 using xhci_hcd
kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01
kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
boltd[935]: probing: started [1000]
kernel: Bluetooth: Core ver 2.22
kernel: NET: Registered PF_BLUETOOTH protocol family
kernel: Bluetooth: HCI device and connection manager initialized
kernel: Bluetooth: HCI socket layer initialized
kernel: Bluetooth: L2CAP socket layer initialized
kernel: Bluetooth: SCO socket layer initialized
kernel: usbcore: registered new interface driver btusb
systemd[1328]: Reached target Bluetooth.
kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin
kernel: Bluetooth: hci0: QCA: patch rome 0x130201 build 0x5073, firmware rome 0x130201 build 0x38e6
kernel: Bluetooth: hci0: Failed to send headers (-71)
systemd[1]: Starting Bluetooth service...
bluetoothd[6866]: Bluetooth daemon 5.66
systemd[1]: Started Bluetooth service.
systemd[1]: Reached target Bluetooth Support.
bluetoothd[6866]: Starting SDP server
bluetoothd[6866]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
bluetoothd[6866]: src/plugin.c:plugin_init() Failed to init vcp plugin
bluetoothd[6866]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
bluetoothd[6866]: src/plugin.c:plugin_init() Failed to init mcp plugin
bluetoothd[6866]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
bluetoothd[6866]: src/plugin.c:plugin_init() Failed to init bap plugin
kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
kernel: Bluetooth: BNEP filters: protocol multicast
kernel: Bluetooth: BNEP socket layer initialized
bluetoothd[6866]: Bluetooth management interface 1.22 initialized
kernel: usb 1-3.1: USB disconnect, device number 3
systemd[1328]: Stopped target Bluetooth.
systemd[1]: Stopped target Bluetooth Support.

Then, rfkill reports bluetooth as being soft-lock:

sudo rfkill
ID TYPE      DEVICE                   SOFT      HARD
 0 bluetooth tpacpi_bluetooth_sw   blocked unblocked
 1 wlan      phy0                unblocked unblocked

If I try to unlock it, I get errors in journald - sometime error about header not sent, sometime about body.

rfkill[105640]: unblock set for type bluetooth
sudo[105639]: pam_unix(sudo:session): session closed for user root
kernel: usb 1-3.1: new full-speed USB device number 4 using xhci_hcd
kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01
kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin
kernel: Bluetooth: hci0: QCA: patch rome 0x130201 build 0x5073, firmware rome 0x130201 build 0x38e6
kernel: Bluetooth: hci0: Failed to send body at 40 of 142192 (-71)
kernel: usb 1-3.1: USB disconnect, device number 4
boltd[935]: probing: started [1000]
systemd[1328]: Reached target Bluetooth.
systemd[1328]: Stopped target Bluetooth.
systemd[1]: Reached target Bluetooth Support.
systemd[1]: Stopped target Bluetooth Support.

I tried to remove kernel moduls (`bluetooth`, `btusb`, etc) and modprobe them back, and I get the same kind of logs after `rfkill unblock bluetoot`:

rfkill[106483]: unblock set for type bluetooth
sudo[106482]: pam_unix(sudo:session): session closed for user root
kernel: usb 1-3.1: new full-speed USB device number 5 using xhci_hcd
kernel: usb 1-3.1: New USB device found, idVendor=10ab, idProduct=9309, bcdDevice= 0.01
kernel: usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
kernel: usb 1-3.1: Failed to access otp area (-71)
kernel: usb 1-3.1: USB disconnect, device number 5
boltd[935]: probing: started [1000]
systemd[1328]: Reached target Bluetooth.
systemd[1]: Reached target Bluetooth Support.
systemd[1328]: Stopped target Bluetooth.
systemd[1]: Stopped target Bluetooth Support.
boltd[935]: probing: timeout, done: [3001068] (2000000)

I found rare old messages about bluetooth problems with that card like
https://bugs.debian.org/cgi-bin/bugrepo … ug=1021157, but they were related to missing firmware that I checked and have in my system.

What should I do/read to try to debug that?

Thanks,