New: ath11k: QCA6390 firmware crashes after some time

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

            Bug ID: 215872
           Summary: ath11k: QCA6390 firmware crashes after some time
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.17.3-arch1-1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 300786
--> https://bugzilla.kernel.org/attachment.cgi?id=300786&action=edit
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

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

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

--- Comment #1 from Kai Mast ([email protected]) ---
Created attachment 300787
--> https://bugzilla.kernel.org/attachment.cgi?id=300787&action=edit
dmesg | grep ath11k

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

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

--- Comment #2 from Kai Mast ([email protected]) ---
Created attachment 300788
--> https://bugzilla.kernel.org/attachment.cgi?id=300788&action=edit
find /lib/firmware/ath11k/ -type f | xargs md5sum

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

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

--- Comment #3 from Kai Mast ([email protected]) ---
Created attachment 300789
--> https://bugzilla.kernel.org/attachment.cgi?id=300789&action=edit
lspci -mnn

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

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

Kalle Valo ([email protected]) changed:

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

                 CC|                            |[email protected]
            Summary|ath11k: QCA6390 firmware    |QCA6390 firmware crashes
                   |crashes after some time     |after some time

--- Comment #4 from Kalle Valo ([email protected]) ---
ath11k is a Wi-Fi driver and has nothing to do with bluetooth, so removing ath11k from title.

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

Hi, this is your Linux kernel regression tracker.

I noticed below regression report in bugzilla.kernel.org that afaics nobody acted upon since it was reported about a week ago, that's why I decided to step in here. Could somebody take a look into below issue? Or was this discussed somewhere else already? Or even fixed?

Anyway, to get this tracked:

#regzbot introduced: v5.15..v5.17
#regzbot from: Kai Mast <[email protected]>
#regzbot title: bluetooth: QCA6390 firmware crashes after some time #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215872

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

P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.

Additional information about regzbot:

If you want to know more about regzbot, check out its web-interface, the
getting start guide, and the references documentation:

https://linux-regtracking.leemhuis.info/regzbot/
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The last two documents will explain how you can interact with regzbot
yourself if your want to.

Hint for reporters: when reporting a regression it's in your interest to
CC the regression list and tell regzbot about the issue, as that ensures
the regression makes it onto the radar of the Linux kernel's regression
tracker -- that's in your interest, as it ensures your report won't fall
through the cracks unnoticed.

Hint for developers: you normally don't need to care about regzbot once
it's involved. Fix the issue as you normally would, just remember to
include 'Link:' tag in the patch descriptions pointing to all reports
about the issue. This has been expected from developers even before
regzbot showed up for reasons explained in
'Documentation/process/submitting-patches.rst' and
'Documentation/process/5.Posting.rst'.

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.

Likely fixed, according to
https://bugzilla.kernel.org/show_bug.cgi?id=215872#c5

#regzbot fixed-by: d44e1dbda36ff

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

Jakub Kicinski ([email protected]) changed:

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

--- Comment #5 from Jakub Kicinski ([email protected]) --- I believe this is closed by
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d44e1dbda36fff5d7c2586683c4adc0963aef908
upstream.

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

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

Mark Herbert ([email protected]) changed:

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

--- Comment #6 from Mark Herbert ([email protected]) --- (In reply to Jakub Kicinski from comment #5)

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.

You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.