>Number: 165306 >Category: kern >Synopsis: [ath] race conditions between scanning and beacon timeout >programming >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 20 02:40:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Adrian Chadd >Release: 9.0-RELEASE i386 w/ HEAD net80211/ath >Organization: >Environment: >Description: There seem to be issues where net80211 doesn't quite get the "beacon miss" notification. It stays associated, the beacon interrupt/notification isn't occuring.
Adding on reset/beacon debugging (0x20 + 0x80) on ath0 (sysctl dev.ath.0.debug=0xa0) didn't show any beacon miss interrupts, software or hardware. This is with one VAP STA on an AR9280. What I think is happening is: * the transition to -> RUN doesn't program in any beacon timers by default - it waits for the first beacon to be RX'ed before it programs in timers; * but if it loses connectivity during a scan, the beacon timers won't ever be reprogrammed, as no beacons will occur. So it stays associated. >How-To-Repeat: The above should be doable to reproduce - just enable beacon debugging, then do a scan and kill the AP whilst the station is scanning. >Fix: It may be that we need to: * program in some beacon TSF value for the initial state transition to RUN, and hope that a new beacon will come in and reprogram the timers. * .. or also enable swbeacon support too for single-VAP STA mode? >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
