On 02/12/2013 11:04 AM, Kalle Valo wrote:
Wojciech Dubowik <Wojciech.Dubowik@xxxxxxxxxxx> writes:
I have connection without sending any data.
I have seen that ieee80211_sta_rx_notify doesn't count beacons
so the time is not resetted. What was the reason not to count them
for beacon loss work? Something connected with PS?
Anyway I should get the event every
IEEE80211_BEACON_LOSS_COUNT * bcn period
which in my case should be 7 * 30 ms = 210 ms and not 1 second.
I will keep on digging.
What driver are you using?
I have a test pc with 3x AR9590 and 2x AR9390. Machine is based on i7
and hyperthreading is on so I have 8 cores.
I am using latest wireless testing ath9k and 3.8rc7 kernel.
What I see is that for some extended periods odf time beacons are not
processed in ieee80211_rx_mgmt_beacon
and that's why I get beacon loss. I am using 30ms beacon period.
What is really funny, that I get this beacon loss message every second.
Like is sth was locking ifmgd->mtx mutex
at constant intervals.
I will try to disable all cores and run in again to see if it's rcu problem.
Wojtek
--
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