Bug 215872

Summary: QCA6390 firmware crashes after some time
Product: Drivers Reporter: Kai Mast (mail)
Component: BluetoothAssignee: linux-bluetooth (linux-bluetooth)
Status: NEW ---    
Severity: normal CC: jan.hicken, kubakici, kvalo, mark.herbert42
Priority: P1    
Hardware: x86-64   
OS: Linux   
Kernel Version: 5.17.3-arch1-1 Tree: Mainline
Regression: No
Attachments: dmesg | grep Bluetooth
dmesg | grep ath11k
find /lib/firmware/ath11k/ -type f | xargs md5sum
lspci -mnn

Description Kai Mast 2022-04-21 20:07:13 UTC
Created attachment 300786 [details]
dmesg | grep Bluetooth

I'm on arch Linux. For a while now (multiple kernel versions since 5.15 at least) my qca firwmare seems to crash. Weirdly bluetooth stops working and WiFi still works fine.
There is nothing in particular that seems to trigger this. I just have to wait for a while. Sometimes a few minutes after boot sometimes a few hours. 

Rebooting without a power connection or booting into Windows usually resolves this issue.

I'm on a 2020 Dell XPS 9500. Fimrware is up to date at 1.13.

Output of uname -a: Linux kai-xps 5.17.3-arch1-1 #1 SMP PREEMPT Thu, 14 Apr 2022 01:18:36 +0000 x86_64 GNU/Linux
Comment 1 Kai Mast 2022-04-21 20:07:58 UTC
Created attachment 300787 [details]
dmesg | grep ath11k
Comment 2 Kai Mast 2022-04-21 20:08:28 UTC
Created attachment 300788 [details]
find /lib/firmware/ath11k/ -type f | xargs md5sum
Comment 3 Kai Mast 2022-04-21 20:08:47 UTC
Created attachment 300789 [details]
lspci -mnn
Comment 4 Kalle Valo 2022-04-27 07:33:11 UTC
ath11k is a Wi-Fi driver and has nothing to do with bluetooth, so removing ath11k from title.
Comment 6 Mark Herbert 2022-12-27 16:00:57 UTC
(In reply to Jakub Kicinski from comment #5)
> I believe this is closed by
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/
> ?id=d44e1dbda36fff5d7c2586683c4adc0963aef908 upstream.

It is not. QCA6390 bluetooth is not USB, it is serial device. So all btusb changes can not help here at all.

It is still crashes from at least 5.17 up to 6.2-rc1, and what is bad it can not be reactivated by any means except of total power off. Reboot does not help - unless it is reboot to Windows.