2010/6/29 Felix Fietkau <nbd@xxxxxxxxxxx>: > 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? Yup, seems to be a hardware reset. Added an ath_print ("Reset HW!") at the beginning of ath9k_hw_reset() and used debug mask 0x101: ... Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 3 [tsf 14863367 tsftu 14515 intval 100] vif (null) Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 2 [tsf 14888967 tsftu 14540 intval 100] vif (null) Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 1 [tsf 14914568 tsftu 14565 intval 100] vif (null) Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Reset HW! Jan 1 00:01:59 OpenWrt user.debug kernel: ath: ah->misc_mode 0xc Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Setting CFG 0x10a Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 0 [tsf 80123 tsftu 78 intval 100] vif 80945e70 Jan 1 00:01:59 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Reset HW! Jan 1 00:01:59 OpenWrt user.debug kernel: ath: ah->misc_mode 0xc Jan 1 00:01:59 OpenWrt user.debug kernel: ath: Setting CFG 0x10a Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 0 [tsf 80989 tsftu 79 intval 100] vif 80945e70 Jan 1 00:01:59 OpenWrt user.debug kernel: ath: missed 1 consecutive beacons Jan 1 00:01:59 OpenWrt user.debug kernel: ath: resume beacon xmit after 1 misses Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 3 [tsf 117792 tsftu 115 intval 100] vif (null) Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 2 [tsf 143368 tsftu 140 intval 100] vif (null) Jan 1 00:01:59 OpenWrt user.debug kernel: ath: slot 1 [tsf 168967 tsftu 165 intval 100] vif (null) ... > - Felix > /Björn -- 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