Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed"

hi, so it's going to eventually leak? Can we fix the firmware bug too? :) -a On 26 February 2018 at 09:06, wrote: > Hi, > > >> Can you share exactly which resource the firmware ran out of? It would >> seem to >> be a FW bug if it is leaking, so maybe it can be

Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed"

This reverts commit 55884c045d31a29cf69db8332d1064a1b61dd159. When Ath10k is in AP mode and an unassociated STA sends a VHT action frame (Operating Mode Notification for the NSS change) periodically to AP this causes ath10k to call ath10k_station_assoc() which sends WMI_PEER_ASSOC_CMDID

Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed"

Hi, Can you share exactly which resource the firmware ran out of? It would seem to be a FW bug if it is leaking, so maybe it can be fixed as well... Firmware have total user_id = 528 (512 clients + 16 VAPs). Each user_id is allocated to peer when Firmware receive the WMI_PEER_ASSOC_CMDID

Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed"

On 02/25/2018 10:16 PM, Karthikeyan Periyasamy wrote: This reverts commit 55884c045d31a29cf69db8332d1064a1b61dd159. When Ath10k is in AP mode and an unassociated STA sends a VHT action frame (Operating Mode Notification for the NSS change) periodically to AP this causes ath10k to call

Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed"

hi! On 25 February 2018 at 22:16, Karthikeyan Periyasamy wrote: > This reverts commit 55884c045d31a29cf69db8332d1064a1b61dd159. > > When Ath10k is in AP mode and an unassociated STA sends a VHT action frame > (Operating Mode Notification for the NSS change) periodically