K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2013-01-17T16:26:40.047668Z
K 7
svn:log
V 407
Add a quick work-around if ath_beacon_config() to not die if it's called
when an interface is going down.

Right now it's quite possible (but very unlikely!) that ath_reset()
or similar is called, leading to a beacon config call, in parallel with
the last VAP being destroyed.

This likely should be fixed by making sure the bmiss/bstuck/watchdog
taskqueues are canceled whenever the last VAP is destroyed.

END