When ath(4) is operating in hostap mode, it would randomly "stop" working during normal Internet usage (wifi devices streaming, browsing the web, etc...). Some symptoms of the problem included several and frequent "stuck beacon" messages in dmesg and sudden unresponsive behavior that required the ath(4) module to be unloaded and then reloaded to function again (restarting hostapd, bringing interface up/down, destroying/creating wlan# again was not sufficient).
Fix: Adrian Chadd recommended a code snippet from HEAD which resolved the problem with stuck beacons and it apparently solved this problem too. The attached patch has been tested and successfully used since 2/17/2013.
Patch attached with submission follows:
How-To-Repeat: The exact causes are not known. It's not reproducible.
For bugs that match the following
- Status Is In progress
- Untouched since 2018-01-01.
- Affects Base System OR Documentation
Reset to open status.
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.