mbox series

[RFC,0/1] wifi: ath10k: improvement on key removal failure

Message ID 20240814164507.996303-1-prestwoj@gmail.com
Headers show
Series wifi: ath10k: improvement on key removal failure | expand

Message

James Prestwood Aug. 14, 2024, 4:45 p.m. UTC 
This is in regard to my earlier question [1]. After some testing with
adding an artificial 3 second delay between auth and assoc frames I
saw that the device would fail to roam 100% of the time. This further
backed up my theory that this firmware failure is causing some
timeout on the AP, and resulting it either ignoring the reassociation
or rejecting it.

Changing kernel behavior to fix a vendor quirk isn't great, but
in this situation since the key removal is non-fatal and it
improves general performance when the firmware does time out I
thought it was an acceptable compromise. I am also pursuing the
vendor to fix this, and allow a greater delay between auth and
assoc.

The reason I'm sending this as an RFC is that I have no idea about
other hardware, firmwares, etc, that use ath10k. I have only tested
on the QCA6174. Maybe different configurations _do_ need 3 seconds
to remove a key? Maybe this timeout needs to be a hw_param?

[1] https://lore.kernel.org/linux-wireless/9eafac85-2262-4f92-a70b-32109f65c05a@gmail.com/T/#t



James Prestwood (1):
  wifi: ath10k: reduce timeout for disabling a key

 drivers/net/wireless/ath/ath10k/mac.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

Comments

Felix Kaechele Aug. 17, 2024, 12:53 a.m. UTC | #1 
I was somewhat hoping that it could fix the issues I'm having with my 
QCA9379 as well, but it seems that's not the case.
Still getting

[ 7660.485652] ath10k_sdio mmc1:0001:1: failed to install key for vdev 0 
peer 76:ac:b9:xx:xx:xx: -110
[ 7660.485679] wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to 
hardware (-110)
[ 7660.509935] wlan0: deauthenticating from 76:ac:b9:xx:xx:xx by local 
choice (Reason: 1=UNSPECIFIED)
[ 7661.836653] wlan0: authenticate with b2:8b:a9:xx:xx:xx (local 
address=de:56:bb:xx:xx:xx)
[ 7661.836685] wlan0: send auth to b2:8b:a9:xx:xx:xx (try 1/3)
[ 7661.849449] wlan0: authenticated
[ 7661.853884] wlan0: associate with b2:8b:a9:xx:xx:xx (try 1/3)
[ 7661.902242] wlan0: RX AssocResp from b2:8b:a9:xx:xx:xx (capab=0x1111 
status=0 aid=2)
[ 7661.913192] wlan0: associated
[ 7662.187718] wlan0: Limiting TX power to 24 (24 - 0) dBm as advertised 
by b2:8b:a9:xx:xx:xx

once every hour.

That's unfortunate.

Regards,
Felix
James Prestwood Aug. 19, 2024, 11:49 a.m. UTC | #2 
Hi Felix,

On 8/16/24 5:53 PM, Felix Kaechele wrote:
> I was somewhat hoping that it could fix the issues I'm having with my 
> QCA9379 as well, but it seems that's not the case.
> Still getting
>
> [ 7660.485652] ath10k_sdio mmc1:0001:1: failed to install key for vdev 
> 0 peer 76:ac:b9:xx:xx:xx: -110
> [ 7660.485679] wlan0: failed to set key (2, ff:ff:ff:ff:ff:ff) to 
> hardware (-110)
> [ 7660.509935] wlan0: deauthenticating from 76:ac:b9:xx:xx:xx by local 
> choice (Reason: 1=UNSPECIFIED)
> [ 7661.836653] wlan0: authenticate with b2:8b:a9:xx:xx:xx (local 
> address=de:56:bb:xx:xx:xx)
> [ 7661.836685] wlan0: send auth to b2:8b:a9:xx:xx:xx (try 1/3)
> [ 7661.849449] wlan0: authenticated
> [ 7661.853884] wlan0: associate with b2:8b:a9:xx:xx:xx (try 1/3)
> [ 7661.902242] wlan0: RX AssocResp from b2:8b:a9:xx:xx:xx 
> (capab=0x1111 status=0 aid=2)
> [ 7661.913192] wlan0: associated
> [ 7662.187718] wlan0: Limiting TX power to 24 (24 - 0) dBm as 
> advertised by b2:8b:a9:xx:xx:xx
>
> once every hour.
>
> That's unfortunate.
In your case it looks like a failure on a group re-key, which makes 
sense that you would see a disconnect. Definitely unfortunate.
>
> Regards,
> Felix