misc/170433: [ath] TX hang after a stuck beacon message with active
adrian at FreeBSD.org
Tue Aug 7 00:40:04 UTC 2012
>Synopsis: [ath] TX hang after a stuck beacon message with active traffic
>Arrival-Date: Tue Aug 07 00:40:03 UTC 2012
>Originator: Adrian Chadd
>Release: 9.0-STABLE, HEAD net80211/ath
When doing iperf tests to a FreeBSD AP in 2.4GHz, a stuck beacon event would result in traffic stalls.
This can be flushed by one or more "sysctl dev.ath.X.forcebstuck=1" commands.
IT didn't show up in 5GHz mode because I never saw a stuck beacon issue.
The problem is in ath_legacy_tx_dma_restart(). It was initialising the wrong link pointer and so the TX queue would end up with incorrect link information.
More information about the freebsd-bugs