2019-10-20 10:34:05

by Christian Hewitt

[permalink] [raw]
Subject: Broadcom SDIO module failures since 5.4-rc1

Since bumping from 5.3.x to 5.4-rcX I have seen a bluetooth failure on all Amlogic SoC boards that I test with, using a range of different Ampak (Broadcom) SDIO modules. The following is from a board with BCM4359 wireless/BT (SDIO):

VIM3:~ # dmesg | grep -i Blue
[ 5.594409] Bluetooth: Core ver 2.22
[ 5.594500] Bluetooth: HCI device and connection manager initialized
[ 5.594515] Bluetooth: HCI socket layer initialized
[ 5.594520] Bluetooth: L2CAP socket layer initialized
[ 5.594537] Bluetooth: SCO socket layer initialized
[ 5.625023] Bluetooth: HCI UART driver ver 2.3
[ 5.625031] Bluetooth: HCI UART protocol H4 registered
[ 5.626880] Bluetooth: HCI UART protocol Broadcom registered
[ 5.627042] Bluetooth: HCI UART protocol QCA registered
[ 5.869597] Bluetooth: hci1: Frame reassembly failed (-84)
[ 5.869671] Bluetooth: hci1: Frame reassembly failed (-84)
[ 7.944140] Bluetooth: hci1: command 0xfc18 tx timeout
[ 16.050803] Bluetooth: hci1: BCM: failed to write update baudrate (-110)
[ 16.050808] Bluetooth: hci1: Failed to set baudrate
[ 18.184134] Bluetooth: hci1: command 0x0c03 tx timeout
[ 26.077475] Bluetooth: hci1: BCM: Reset failed (-110)

Kernel defconfig: https://github.com/chewitt/LibreELEC.tv/blob/amlogic-master/projects/Amlogic/linux/linux.aarch64.conf

Kernelci Amlogic images (https://kernelci.org/soc/amlogic/job/amlogic/) are showing the same "Frame reassembly failed (-84)” error.

This sounds similar: https://www.spinics.net/lists/linux-bluetooth/msg81600.html but modules will use hci_bcm not hci_qca.

Any ideas?

Christian