Bug 205311 - Ath10K_pci firmware crashes
Summary: Ath10K_pci firmware crashes
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 high
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-25 13:29 UTC by Haxk20
Modified: 2021-04-07 16:08 UTC (History)
3 users (show)

See Also:
Kernel Version: linux-next
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (103.75 KB, text/plain)
2019-10-25 13:29 UTC, Haxk20
Details
dmesg output showing my problem (15.48 KB, text/plain)
2020-10-16 14:24 UTC, richts
Details
crash trace (6.12 KB, text/plain)
2020-10-27 21:49 UTC, richts
Details

Description Haxk20 2019-10-25 13:29:35 UTC
Created attachment 285647 [details]
dmesg

As the title says. After upgrading today from 5.4rc4 to linux-next tree the atheros wifi firmware started crashing and is unable to connect to any network.
I think dmesg will describe it better then i can. So here it is.
Comment 1 Haxk20 2019-10-25 13:31:12 UTC
Oh i almost forgot. Wifi chipset is Qualcomm Atheros QCA6174
Comment 2 Haxk20 2019-10-27 23:33:22 UTC
Updated board-2.bin firmware and every file for the card that was out of date. Still crashes so something must be in driver.
Comment 3 richts 2020-10-16 14:23:33 UTC
I'm on 
> Linux juergen 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000
> x86_64 GNU/Linux

and experience the same issue since several weeks. Yesterday I also updated the firmware blob to the very latest version but the problem didn't change. See my dmesg (excerpt) for details.

Disconnecting and reconnecting to the wifi network works (using network manager), but it doesn't recover without that.
Comment 4 richts 2020-10-16 14:24:34 UTC
Created attachment 293039 [details]
dmesg output showing my problem
Comment 5 Haxk20 2020-10-16 15:29:48 UTC
I switched to Wifi 6 card from Intel so i do not suffer from this bug anymore. But i will leave it opened since it is still an issue.
Comment 6 richts 2020-10-18 09:04:54 UTC
Here is another one:

~~~
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: firmware crashed! (guid 3739be6b-66fd-4150-8ccf-3c0ef2e95dc0)
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 318825bf
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[Sun Oct 18 10:52:18 2020] ath10k_warn: 12 callbacks suppressed
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [00]: 0x00034400  11  11   3   3
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [01]: 0x00034800  21  20 129 130
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [02]: 0x00034c00  59  58 121 122
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [03]: 0x00035000   9   9  11   9
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [04]: 0x00035400 6423 6399 192 128
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [06]: 0x00035c00  14  12  28  26
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: [07]: 0x00036000   0   1   0   1
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[Sun Oct 18 10:52:18 2020] ieee80211 phy0: Hardware restart was requested
[Sun Oct 18 10:52:18 2020] ath10k_pci 0000:02:00.0: device successfully recovered
~~~
Comment 7 richts 2020-10-27 21:49:35 UTC
Created attachment 293269 [details]
crash trace

just happened, I'm not sure if this should go to a separate bug I'm posting it here.
Comment 8 richts 2020-12-26 10:49:04 UTC
Since I deactivated wifi powersave in networkmanager the issue never occurred.

This can be done by adding the file `wifi-powersave-off.conf` with the content

~~~
[connection]
# Values are 0 (use default), 1 (ignore/don't touch), 2 (disable) or 3 (enable).
wifi.powersave = 2
~~~

to `/etc/NetworkManager/conf.d`

Note You need to log in before you can comment on or make changes to this bug.