kern/165306: [ath] race conditions between scanning and beacon
adrian at freebsd.org
Mon Feb 20 02:47:32 UTC 2012
On 19 February 2012 18:43, <adrian at freebsd.org> wrote:
> Synopsis: [ath] race conditions between scanning and beacon timeout programming
This bug is ridiculously subtle and took me a while to figure out what
was going on. Grr.
I'm very tempted to just always flip on the beacon interrupt
programming by writing the last known TSF if there was one, then
updating it the next time we see a beacon. That way we don't end up in
this situation where we never register that the AP has disappeared.
More information about the freebsd-wireless