ath0 timeout was "Re: (more) bugs fixed in -HEAD, AP mode is now
mostly (again) stable!"
Adrian Chadd
adrian at freebsd.org
Sun Mar 11 01:58:23 UTC 2012
Hiya,
Next time it happens, do the sysctl before the scan.
The sysctl will tell me how deep each hardware TX queue is.
I should likely add some further debugging to tell me how deep the
per-TID software queues are; that'd be helpful here.
What you're seeing there is something weird which is causing the TX
frames to be queued in software/hardware and not be transmitted, to
the point of buffer exhaustion. See "total TX buffers: 0" ? That means
the frames can't go out for some reason. There's nothing in the
hardware queue, so that also has me slightly concerned.
I wonder if this is a problem with aggregation and buffer exhaustion.
Hm, can you do "wlandebug +11n" and see if it's trying to exchange
ADDBA frames (and failing) ? There's a known bug where
Thanks,
Adrian
More information about the freebsd-wireless
mailing list