QCA6174 SDIO crashing after few days

[Kalle Valo]

Adam Porter <porter.adam at gmail.com> writes:

> Firmware WLAN.RMH.4.1.1-00014-QCARMSWPZ-1
>
> Using branch ath10k-pending-sdio-usb

What commit id? BTW, I'm planning to add a tag everytime I rebase that
branch so that it's easier to find older commits and identify what
version is used.

> I'm using this module as an access point. After a while of uptime, it
> appears that all communication with the module ceases. Hostapd goes to
> disassociate clients due to inactivity, then I see in the log the
> resulting failures:
>
> [94216.098042] ath10k_sdio mmc0:0001:1: failed to install key for vdev
> 0 peer c8:21:58:10:b3:b4: -110
> [94219.170075] ath10k_sdio mmc0:0001:1: failed to install key for vdev
> 0 peer b8:27:eb:f2:52:22: -110
> [94219.191719] ath10k_sdio mmc0:0001:1: cipher 0 is not supported
> [94219.207948] ath10k_sdio mmc0:0001:1: failed to remove peer wep key 0: -95
> [94219.222155] ath10k_sdio mmc0:0001:1: failed to clear all peer wep
> keys for vdev 0: -95
> [94219.237937] ath10k_sdio mmc0:0001:1: failed to disassociate
> station: c8:21:58:10:b3:b4 vdev 0: -95
>
> It seems that I can reproduce this issue faster by connecting more
> clients and pushing a lot of throughput. So perhaps this is a resource
> leak in the firmware?

I would blame ath10k first :) Can you estimate how much data needs to be
transferred before this happens?

-- 
Kalle Valo