On 2010-06-29 5:20 PM, Björn Smedman wrote: > 2010/6/29 Felix Fietkau <nbd@xxxxxxxxxxx>: >> IMHO the most likely problem source is stuck beacons. Please compile the >> driver with the debug option enabled and load it with >> insmod ath9k debug=0x00000100 > > It looks like it could be: > > ... > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 2 [tsf 1986567 > tsftu 1940 intval 100] vif (null) > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 1 [tsf 2012168 > tsftu 1965 intval 100] vif (null) > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 0 [tsf 2037767 > tsftu 1990 intval 100] vif 80945e70 > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 0 [tsf 79033 > tsftu 77 intval 100] vif 80945e70 > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: resume beacon xmit > after 1 misses > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 3 [tsf 117790 > tsftu 115 intval 100] vif (null) > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 2 [tsf 143368 > tsftu 140 intval 100] vif (null) > Jan 1 00:06:21 OpenWrt user.debug kernel: ath: slot 1 [tsf 168967 > tsftu 165 intval 100] vif (null) > ... > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 1 [tsf 14197768 > tsftu 13865 intval 100] vif (null) > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 0 [tsf 14223368 > tsftu 13890 intval 100] vif 80945e70 > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 3 [tsf 14248967 > tsftu 13915 intval 100] vif (null) > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 0 [tsf 79180 > tsftu 77 intval 100] vif 80945e70 > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: resume beacon xmit > after 1 misses > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 3 [tsf 117791 > tsftu 115 intval 100] vif (null) > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 2 [tsf 143366 > tsftu 140 intval 100] vif (null) > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 1 [tsf 168967 > tsftu 165 intval 100] vif (null) > Jan 1 00:09:08 OpenWrt user.debug kernel: ath: slot 0 [tsf 194567 > tsftu 190 intval 100] vif 80945e70 > ... > > What can cause a missed beacon? Are they just a "fact of life"? > > In any case I can't find any code that resets the tsf in this (single > missed beacon) case. Will the hardware reset the tsf automatically > whenever a single beacon is missed? Isn't that a bit overkill? Will it > not cause problems for clients? One beacon miss should never cause a TSF reset. Only a lot of consecutive beacon misses trigger a hardware reset, which then resets the TSF. Looking at your log, it appears that the beacon miss is a symptom rather than a cause of the TSF jumps. Can you add a debug statement to the hw reset function to see if it's called before the TSF jumps? - Felix -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
