Comment 28 for bug 1730331

Revision history for this message
In , lukas.wolf (lukas.wolf-redhat-bugs) wrote :

Created attachment 1413693
dmesg output, lspci -vv, modinfo ath10k_pci

Description of problem:
After a certain time running (probably every several hours), the ath10k_pci driver crashes and the wireless device stops working. Setting wlan to off and on again will make it work again. This bug was first seen since the last kernel upgrade (from 4.15.9 to 4.15.10). Maybe related to bug 1490172.

Version-Release number of selected component (if applicable):
- Linux HOSTNAME 4.15.10-300.fc27.x86_64 #1 SMP Thu Mar 15 17:13:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
- linux-firmware.noarch 20171215-82.git2451bb22.fc27
- Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
- Dell XPS 13 9370 laptop

How reproducible:

Steps to Reproduce:
1. Upgrade kernel to 4.15.10
2. Use the ath10k_pci driver with the jQualcomm Atheros network card
3. Wait and see

Actual results:

[106670.143021] ath10k_pci 0000:02:00.0: firmware crashed! (guid db1989b3-95dd-4829-a0ef-6902b448f555)
[106670.143052] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[106670.143060] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[106670.144732] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00051-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 c3fd4411
[106670.145862] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 0e26ef70
[106670.145872] ath10k_pci 0000:02:00.0: htt-ver 3.44 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[106670.158902] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[106670.158913] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[106670.158923] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[106670.158941] ath10k_pci 0000:02:00.0: [00]: 0x00034400 2 2 3 3
[106670.158958] ath10k_pci 0000:02:00.0: [01]: 0x00034800 7 7 404 405
[106670.158975] ath10k_pci 0000:02:00.0: [02]: 0x00034c00 4 4 66 67
[106670.158992] ath10k_pci 0000:02:00.0: [03]: 0x00035000 0 0 2 0
[106670.159008] ath10k_pci 0000:02:00.0: [04]: 0x00035400 5585 5523 10 202
[106670.159025] ath10k_pci 0000:02:00.0: [05]: 0x00035800 0 0 64 0
[106670.159041] ath10k_pci 0000:02:00.0: [06]: 0x00035c00 16 15 6 4
[106670.159058] ath10k_pci 0000:02:00.0: [07]: 0x00036000 0 0 0 1
[106670.165254] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[106670.223625] ieee80211 phy0: Hardware restart was requested
[106670.912546] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[106670.915332] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[106671.023012] ath10k_pci 0000:02:00.0: device successfully recovered
[106748.553078] wlp2s0: deauthenticating from c0:c1:c0:d2:1c:5f by local choice (Reason: 3=DEAUTH_LEAVING)
[106753.714651] ath10k_pci 0000:02:00.0: Unknown eventid: 118809
[106753.717648] ath10k_pci 0000:02:00.0: Unknown eventid: 90118
[106753.760424] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Expected results:
Obviously not crashing

Additional info:
See attachments.