Loic Poulain <loic.poulain@xxxxxxxxxx> wrote:
> We observe unexpected connection drops with some APs due to
> non-acked mac80211 generated null data frames (keep-alive).
> After debugging and capture, we noticed that null frames are
> submitted at standard data bitrate and that the given APs are
> in trouble with that.
>
> After setting the null frame bitrate to control bitrate, all
> null frames are acked as expected and connection is maintained.
>
> Not sure if it's a requirement of the specification, but it seems
> the right thing to do anyway, null frames are mostly used for control
> purpose (power-saving, keep-alive...), and submitting them with
> a slower/simpler bitrate/modulation is more robust.
>
> Cc: stable@xxxxxxxxxxxxxxx
> Fixes: 512b191d9652 ("wcn36xx: Fix TX data path")
> Signed-off-by: Loic Poulain <loic.poulain@xxxxxxxxxx>
> Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
Patch applied to ath-next branch of ath.git, thanks.
d3fd2c95c1c1 wcn36xx: Fix (QoS) null data frame bitrate/modulation
--
https://patchwork.kernel.org/project/linux-wireless/patch/1634560399-15290-1-git-send-email-loic.poulain@xxxxxxxxxx/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
