Message ID | 20240814164507.996303-1-prestwoj@gmail.com |
---|---|
Headers | show |
Series | wifi: ath10k: improvement on key removal failure | expand |
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
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