ath10k_ct firmware crashes

[Ben Greear]

On 1/18/22 4:29 AM, Koen Vandeputte wrote:
> Hi Ben,
> 
> After stress testing some wave 1 2x2 radios on multiple boards using openwrt master I noticed this crash on 2 of them.
> Any idea?
> 
> 01:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter
> 
> Thanks,
> 
> Koen
> 
> 
> [   16.441327] ath10k 5.15 driver, optimized for CT firmware, probing pci device: 0x3c.
> [   16.468523] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1 irq_mode 0 reset_mode 0
> [   17.719409] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 19b6:d042
> [   17.728819] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 1 testmode 0
> [   17.740820] ath10k_pci 0000:01:00.0: firmware ver 10.1-ct-8x-__fH-022-ecad3248 api 2 features 
> wmi-10.x,mfp,txstatus-noack,wmi-10.x-CT,ratemask-CT,txrate-CT,get-temp-CT,tx-rc-CT,cust-stats-CT,retry-gt2-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT crc32 
> 1b2a161c
> [   18.063728] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
> [   18.993270] ath10k_pci 0000:01:00.0: 10.1 wmi init: vdevs: 16 peers: 127  tid: 256
> [   19.011087] ath10k_pci 0000:01:00.0: wmi print 'P 128 V 8 T 410'
> [   19.017226] ath10k_pci 0000:01:00.0: wmi print 'msdu-desc: 1424 sw-crypt: 0 ct-sta: 0'
> [   19.025374] ath10k_pci 0000:01:00.0: wmi print 'alloc rem: 25000 iram: 38944'
> [   19.082086] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 2 htt-op 2 cal file max-sta 128 raw 0 hwcrypto 1
> [   19.097374] ath10k_pci 0000:01:00.0: NOTE:  Firmware DBGLOG output disabled in debug_mask: 0x10000000
> [   19.228812] ath: EEPROM regdomain sanitized
> [   19.228825] ath: EEPROM regdomain: 0x64
> [   19.228830] ath: EEPROM indicates we should expect a direct regpair map
> [   19.228849] ath: Country alpha2 being used: 00
> [   19.228854] ath: Regpair used: 0x64
> [   19.282229] usbcore: registered new interface driver option
> [   19.288009] usbserial: USB Serial support registered for GSM modem (1-port)
> [   19.318937] usbcore: registered new interface driver qcserial
> [   19.324852] usbserial: USB Serial support registered for Qualcomm USB modem
> [   19.342601] qcserial 2-1:1.0: Qualcomm USB modem converter detected
> [   19.349298] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB0
> [   19.359080] qcserial 2-1:1.2: Qualcomm USB modem converter detected
> [   19.365777] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB1
> [   19.389826] qcserial 2-1:1.3: Qualcomm USB modem converter detected
> [   19.396484] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB2
> [   19.429616] kmodloader: done loading kernel modules from /etc/modules.d/*
> [   26.341428] eth0: link up (1000Mbps/Full duplex)
> [   26.346711] br-wan: port 1(eth0) entered blocking state
> [   26.352077] br-wan: port 1(eth0) entered disabled state
> [   26.357631] device eth0 entered promiscuous mode
> [   26.375076] br-wan: port 1(eth0) entered blocking state
> [   26.380431] br-wan: port 1(eth0) entered forwarding state
> [   32.696768] ag71xx: max retries for SGMII fixup exceeded
> [   32.702172] eth1: link up (1000Mbps/Full duplex)
> [   32.727999] br-wan: port 2(eth1) entered blocking state
> [   32.733310] br-wan: port 2(eth1) entered disabled state
> [   32.738882] device eth1 entered promiscuous mode
> [   32.808555] br-wan: port 2(eth1) entered blocking state
> [   32.813867] br-wan: port 2(eth1) entered forwarding state
> [   37.660591] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
> [   85.293759] ath10k_pci 0000:01:00.0: 10.1 wmi init: vdevs: 16 peers: 127  tid: 256
> [   85.311655] ath10k_pci 0000:01:00.0: wmi print 'P 128 V 8 T 410'
> [   85.317869] ath10k_pci 0000:01:00.0: wmi print 'msdu-desc: 1424 sw-crypt: 0 ct-sta: 0'
> [   85.326004] ath10k_pci 0000:01:00.0: wmi print 'alloc rem: 25000 iram: 38944'
> [   85.398523] ath10k_pci 0000:01:00.0: pdev param 0 not supported by firmware
> [   85.413584] ath10k_pci 0000:01:00.0: rts threshold -1
> [   85.428114] device wlan0 entered promiscuous mode
> [   85.435115] device wlan0 left promiscuous mode
> [ 5578.497296] ath10k_pci 0000:01:00.0: Failed to synchronize setup for vdev 0 restart 0: -145, will restart firmware
> [ 5578.507831] ath10k_pci 0000:01:00.0: failed to start vdev 0 addr 00:00:00:00:00:00 on freq 5320: -145
> [ 5578.518005] ath10k_pci 0000:01:00.0: firmware crashed! (guid b696878d-15a0-434c-9d17-81052d629e31)

Firmware/hardware hung, so we faked a crash to restart it.  I doubt I can do anything
to fix/improve this.  I assume the radio's came back up OK after they crashed?

In general, wave-2 ath10k-ct seems more stable if you have a choice.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com