Wojciech Dubowik wrote: > Jan 15 08:43:44 wlanTS kernel: [ 1177.026210] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/53/-34 > Jan 15 08:43:44 wlanTS kernel: [ 1177.028515] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/55/-32 > Jan 15 08:43:44 wlanTS kernel: [ 1177.028768] ath: phy0: Set HW Key > Jan 15 08:43:44 wlanTS kernel: [ 1177.028827] ath: phy0: Set HW Key > Jan 15 08:43:44 wlanTS kernel: [ 1177.032695] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/53/-34 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032710] ath: phy0: bmiss: 10 sleep: 15360 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032716] ath: phy0: next DTIM 106306560 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032717] ath: phy0: next beacon 106306560 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032718] ath: phy0: beacon period 15360 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032719] ath: phy0: DTIM period 15360 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032749] cfg80211: Found new beacon on frequency: 5180 MHz (Ch 36) on phy0 > Jan 15 08:43:44 wlanTS kernel: [ 1177.032758] cfg80211: Pending regulatory request, waiting for it to be processed... > Jan 15 08:43:44 wlanTS kernel: [ 1177.048561] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/39/-48 > Jan 15 08:43:44 wlanTS kernel: [ 1177.063921] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/37/-50 > Jan 15 08:43:44 wlanTS kernel: [ 1177.079283] NOISE/RSSI/SIGNAL for 04:f0:21:04:56:9e: -87/33/-54 I can reproduce this issue too and this happens only once - right after association. After association, running a background scan doesn't show any problems. Sujith -- 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
