You are not logged in.

#1 2019-11-22 20:53:50

seintz
Member
Registered: 2019-11-22
Posts: 3

ath10k_pci firmware crashed!

Hi all!

In the last couple of weeks I have been having this problem, sometimes on boot I cannot connect to the wireless network of my home (it doesn't happen every boot) and usually with a reboot it get fixed, but it's still annoying so I'll post some infos about my system and some logs so maybe someone of you can tell me a definitive fix for this.

Thanks in advance for your help!

journalctl | grep ath10k_pci

Nov 22 18:35:38 junky kernel: ath10k_pci 0000:3b:00.0: enabling device (0000 -> 0002)
Nov 22 18:35:38 junky kernel: ath10k_pci 0000:3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Nov 22 18:35:39 junky kernel: ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Nov 22 18:35:39 junky kernel: ath10k_pci 0000:3b:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
Nov 22 18:35:39 junky kernel: ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
Nov 22 18:35:39 junky kernel: ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to receive control response completion, polling..
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000001 at 0x00034430: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00034444: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x0000001e at 0x00034430: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000001 at 0x00034830: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000001 at 0x00035430: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035444: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x0000001e at 0x00035430: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x0000001e at 0x00034830: -110
Nov 22 18:35:40 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000001 at 0x00034c30: -110
Nov 22 18:35:42 junky kernel: ath10k_pci 0000:3b:00.0: ctl_resp never came in (-110)
Nov 22 18:35:42 junky kernel: ath10k_pci 0000:3b:00.0: failed to connect to HTC: -110
Nov 22 18:35:45 junky kernel: ath10k_warn: 107 callbacks suppressed
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0xffffffff at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0xffffffff at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0x00000000 at 0x0003a028: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for write32 of 0xffffffff at 0x00000800: -110
Nov 22 18:35:45 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00034444: -110
Nov 22 18:35:50 junky kernel: ath10k_warn: 136 callbacks suppressed
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:50 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:51 junky kernel: ath10k_pci 0000:3b:00.0: failed to read device register, device is gone
Nov 22 18:35:55 junky kernel: ath10k_warn: 138 callbacks suppressed
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: failed to read device register, device is gone
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: could not init core (-110)
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: could not probe fw (-110)
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: firmware crashed! (guid ff7210fb-6a3a-4c2e-ac90-1ce4bb1f7c4f)
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 00000000
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: htt-ver 0.0 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Nov 22 18:36:00 junky kernel: ath10k_warn: 138 callbacks suppressed
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: failed to read firmware dump area: -16
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: Copy Engine register dump:
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_warn: 139 callbacks suppressed
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035c44: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035c40: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035c48: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003603c: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036040: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036048: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: cannot restart a device that hasn't been started

Same as above but i cut out the part of the crash

Nov 22 18:35:55 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003a028: -110
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: failed to read device register, device is gone
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: could not init core (-110)
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: could not probe fw (-110)
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: firmware crashed! (guid ff7210fb-6a3a-4c2e-ac90-1ce4bb1f7c4f)
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 00000000
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
Nov 22 18:35:57 junky kernel: ath10k_pci 0000:3b:00.0: htt-ver 0.0 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Nov 22 18:36:00 junky kernel: ath10k_warn: 138 callbacks suppressed
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:00 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: failed to read firmware dump area: -16
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: Copy Engine register dump:
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: [00]: 0x00034400 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: [01]: 0x00034800 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:04 junky kernel: ath10k_pci 0000:3b:00.0: [02]: 0x00034c00 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [03]: 0x00035000 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [04]: 0x00035400 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [05]: 0x00035800 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_warn: 139 callbacks suppressed
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035c44: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035c40: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00035c48: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [06]: 0x00035c00 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x0003603c: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036044: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036040: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: failed to wake target for read32 at 0x00036048: -110
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: [07]: 0x00036000 4294967295 4294967295 4294967295 4294967295
Nov 22 18:36:05 junky kernel: ath10k_pci 0000:3b:00.0: cannot restart a device that hasn't been started

linux firware package version

linux-firmware-git 20191029.4065643-1

lspci -k

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
	Subsystem: Dell 8th Gen Core Processor Host Bridge/DRAM Registers
	Kernel driver in use: skl_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
	Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
	DeviceName:  Onboard IGD
	Subsystem: Dell UHD Graphics 630 (Mobile)
	Kernel driver in use: i915
	Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
	Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
	Subsystem: Dell Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH Thermal Controller
	Kernel driver in use: intel_pch_thermal
	Kernel modules: intel_pch_thermal
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH USB 3.1 xHCI Host Controller
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
	Subsystem: Dell Cannon Lake PCH Shared SRAM
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
	Subsystem: Dell Cannon Lake PCH Serial IO I2C Controller
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10)
	Subsystem: Dell Cannon Lake PCH Serial IO I2C Controller
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH HECI Controller
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10)
	Subsystem: Dell Cannon Lake Mobile PCH SATA AHCI Controller
	Kernel driver in use: ahci
	Kernel modules: ahci
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0)
	Kernel driver in use: pcieport
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0)
	Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
	Subsystem: Dell Device 087c
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
	Subsystem: Dell Cannon Lake PCH cAVS
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH SMBus Controller
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
	Subsystem: Dell Cannon Lake PCH SPI Controller
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)
	Kernel driver in use: nouveau
	Kernel modules: nouveau
3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
	Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
	Kernel driver in use: ath10k_pci
	Kernel modules: ath10k_pci
3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
	Subsystem: Dell RTS525A PCI Express Card Reader
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci
3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
	Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
	Kernel driver in use: nvme

pacman -Fl | grep ath10k

linux usr/lib/modules/5.3.7-arch1-2-ARCH/kernel/drivers/net/wireless/ath/ath10k/
linux usr/lib/modules/5.3.7-arch1-2-ARCH/kernel/drivers/net/wireless/ath/ath10k/ath10k_core.ko.xz
linux usr/lib/modules/5.3.7-arch1-2-ARCH/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko.xz
linux usr/lib/modules/5.3.7-arch1-2-ARCH/kernel/drivers/net/wireless/ath/ath10k/ath10k_sdio.ko.xz
linux usr/lib/modules/5.3.7-arch1-2-ARCH/kernel/drivers/net/wireless/ath/ath10k/ath10k_usb.ko.xz

pacman -Qs linux

local/alsa-lib 1.2.1.1-1
    An alternative implementation of Linux sound support
local/alsa-utils 1.2.1-1
    An alternative implementation of Linux sound support
local/archlinux-keyring 20191018-2
    Arch Linux PGP keyring
local/avahi 0.7+18+g1b5f401-3
    Service Discovery for Linux using mDNS/DNS-SD -- compatible with Bonjour
local/bridge-utils 1.6-4
    Utilities for configuring the Linux ethernet bridge
local/filesystem 2019.10-2
    Base Arch Linux files
local/iptables 1:1.8.3-3
    Linux kernel packet control tool (using legacy interface)
local/keyutils 1.6.1-3
    Linux Key Management Utilities
local/kmod 26-3
    Linux kernel module management tools and library
local/libaio 0.3.112-2
    The Linux-native asynchronous I/O facility (aio) library
local/libiec61883 1.2.0-5
    A higher level API for streaming DV, MPEG-2 and audio over Linux IEEE 1394
local/libraw1394 2.1.2-2
    Provides an API to the Linux IEEE1394 (FireWire) driver
local/libutil-linux 2.34-6
    util-linux runtime libraries
local/libva 2.5.0-1
    Video Acceleration (VA) API for Linux
local/libxshmfence 1.3-1
    a library that exposes a event API on top of Linux futexes
local/linux 5.3.12.1-1
    The Linux kernel and modules
local/linux-api-headers 5.3.1-2
    Kernel headers sanitized for use in userspace
local/linux-firmware-git 20191029.4065643-1
    Firmware files for Linux
local/linux-headers 5.3.12.1-1
    Headers and scripts for building modules for the Linux kernel
local/man-pages 5.03-2
    Linux man pages
local/mdadm 4.1-2
    A tool for managing/monitoring Linux md device arrays, also known as Software RAID
local/ndctl 67-1
    Utility library for managing the libnvdimm (non-volatile memory device) sub-system in the Linux kernel
local/net-tools 1.60.20181103git-2
    Configuration tools for Linux networking
local/pacman-mirrorlist 20191001-2
    Arch Linux mirror list for use by pacman
local/python-distro 1.4.0-3
    Linux OS platform information API
local/skypeforlinux-stable-bin 8.54.0.91-1
    Skype for Linux - Stable/Release Version
local/util-linux 2.34-6
    Miscellaneous system utilities for Linux
local/v4l-utils 1.16.7-1
    Userspace tools and conversion library for Video 4 Linux

uname -a

Linux junky 5.3.12-arch1-1 #1 SMP PREEMPT Wed, 20 Nov 2019 19:45:16 +0000 x86_64 GNU/Linux

Offline

#2 2019-11-23 14:36:56

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,949

Re: ath10k_pci firmware crashed!

I have the same hardware and the same firmware version and no issues, what kind of connection are you connecting to? Is this a laptop do you have PCI/wireless card power saving enabled ? FWIW in cases like these it's often sufficient to reload ath10k_pci instead of full rebooting

sudo modprobe -r ath10k_pci 
sudo modprobe ath10k_pci

Last edited by V1del (2019-11-23 14:39:13)

Offline

#3 2019-11-23 21:23:02

seintz
Member
Registered: 2019-11-22
Posts: 3

Re: ath10k_pci firmware crashed!

I am trying to connect to my home wireless network, and yes it's a laptop Dell XPS 15 but I'll look into power saving things I may have, thanks for the tip

EDIT: I found out that I have no package for power management, I am still having problems, not as "firmware crashed" but it happens that I can't navigate or ping or ssh into my raspberry in my network, I restart NetworkManager and everything goes well for a couple of minutes than it goes down again

I will post some more logs that may be more useful, right now I don't understand if the problem is the firmware, NetworkManager or something else

Any help is really appreciated, Thanks!

Nov 25 23:08:39 junky kernel: ath10k_pci 0000:3b:00.0: enabling device (0000 -> 0002)
Nov 25 23:08:39 junky kernel: ath10k_pci 0000:3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Nov 25 23:08:40 junky NetworkManager[721]: <info>  [1574719720.4364] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:3b:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0 wlp59s0: renamed from wlan0
Nov 25 23:08:40 junky kernel: ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536
Nov 25 23:08:41 junky kernel: ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536
Nov 25 23:09:46 junky kernel: ath10k_pci 0000:3b:00.0: failed to receive scan abortion completion: timed out
Nov 25 23:09:46 junky kernel: ath10k_pci 0000:3b:00.0: failed to abort scan: -110
Nov 25 23:09:57 junky kernel: ath10k_pci 0000:3b:00.0: failed to synchronize thermal read
Nov 25 23:10:20 junky kernel: ath10k_pci 0000:3b:00.0: wmi command 12289 timeout, restarting hardware
Nov 25 23:10:20 junky kernel: ath10k_pci 0000:3b:00.0: failed to start hw scan: -11
Nov 25 23:10:20 junky kernel: ath10k_pci 0000:3b:00.0: failed to read hi_board_data address: -16
Nov 25 23:10:20 junky kernel: ath10k_pci 0000:3b:00.0: unsupported HTC service id: 1536
Nov 25 23:10:20 junky kernel: ath10k_pci 0000:3b:00.0: device successfully recovered
Nov 25 23:19:30 junky NetworkManager[3014]: <info>  [1574720370.2511] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:3b:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)

Last edited by seintz (2019-11-25 22:24:24)

Offline

#4 2019-11-27 10:08:20

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,949

Re: ath10k_pci firmware crashed!

With what kind of connection are you connecting to I'm more interested into actual technical information, as in which wireless band (2.4Ghz or 5GHz or mixed, is it possible to just configure a single one of the two)? WPA or open, anything else of interest?

Offline

#5 2019-11-27 18:22:29

seintz
Member
Registered: 2019-11-22
Posts: 3

Re: ath10k_pci firmware crashed!

Actually it was the 5GHz one, yesterday I tried the 2.4GHz and I haven't had problem since then so I guess the problem is the band (I don't know if it's mine at home or every 5GHz, I'll give it a try), they are both WPA2 PSK

Thank you very much for the help

Offline

#6 2019-11-30 15:47:18

sapjunior
Member
Registered: 2019-10-27
Posts: 2

Re: ath10k_pci firmware crashed!

I also encouter this issue as well on Dell XPS 9370 (QC6174) when connect to 5GHz network. I think it happen since kernel 5.3 and still occur with 5.4. Too bad that my university use same SSID name for both 2.4 and 5 GHz make internet randomly drop

Offline

Board footer

Powered by FluxBB