Beacon loss event every second

BUG Wojciech Dubowik 3 participants 9 messages Feb 11, 2013 – Feb 13, 2013

lore

Share & tools

lore

Wojciech Dubowik

author

2013-02-11 13:53 UTC #0 lore raw

Hello,

On latest testing and mac80211-next I am getting beacon loss event
every second even when connection is perfect.

Feb 11 14:49:52 wlanTS kernel: [14148.599482] wlan0: cancelling probereq poll due to a received beacon
Feb 11 14:49:53 wlanTS kernel: [14149.565491] wlan0: detected beacon loss from AP - sending probe request
Feb 11 14:49:53 wlanTS kernel: [14149.578845] wlan0: cancelling probereq poll due to a received beacon
Feb 11 14:49:54 wlanTS kernel: [14150.561985] wlan0: detected beacon loss from AP - sending probe request
Feb 11 14:49:54 wlanTS kernel: [14150.588223] wlan0: cancelling probereq poll due to a received beacon
Feb 11 14:49:56 wlanTS kernel: [14152.554968] wlan0: detected beacon loss from AP - sending probe request
Feb 11 14:49:56 wlanTS kernel: [14152.578055] wlan0: cancelling probereq poll due to a received beacon
Feb 11 14:49:57 wlanTS kernel: [14153.551461] wlan0: detected beacon loss from AP - sending probe request
Feb 11 14:49:57 wlanTS kernel: [14153.556825] wlan0: cancelling probereq poll due to a received beacon
Feb 11 14:49:58 wlanTS kernel: [14154.595765] wlan0: detected beacon loss from AP - sending probe request
Feb 11 14:49:58 wlanTS kernel: [14154.597777] wlan0: cancelling probereq poll due to a received beacon

and so on...

Has somebody already fixed it? Just asking before I start digging in.

Br,
Wojtek

Johannes Berg

2013-02-11 14:27 UTC #1 lore raw

Quoted 9 lines · Wojciech Dubowik

Hello,
On latest testing and mac80211-next I am getting beacon loss event
every second even when connection is perfect.
Feb 11 14:49:52 wlanTS kernel: [14148.599482] wlan0: cancelling probereq 
poll due to a received beacon
Has somebody already fixed it? Just asking before I start digging in.

I'm not aware of that.

johannes

Wojciech Dubowik

author

2013-02-11 14:47 UTC #2 lore raw

Quoted 10 lines · Johannes Berg

Quoted 8 lines · Wojciech Dubowik
Hello,
On latest testing and mac80211-next I am getting beacon loss event
every second even when connection is perfect.
Feb 11 14:49:52 wlanTS kernel: [14148.599482] wlan0: cancelling probereq
poll due to a received beacon
Has somebody already fixed it? Just asking before I start digging in.
I'm not aware of that.

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.

Wojtek

Quoted 3 lines

johannes

Kalle Valo

2013-02-12 10:04 UTC #3 lore raw

Quoted 6 lines · Wojciech Dubowik

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?

Quoted 7 lines

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?

Signature · 1 line

Kalle Valo

Wojciech Dubowik

author

2013-02-12 10:19 UTC #4 lore raw

Quoted 8 lines · Kalle Valo

Quoted 6 lines · Wojciech Dubowik
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?

Quoted 9 lines

Quoted 7 lines
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

Kalle Valo

2013-02-12 10:23 UTC #5 lore raw

Quoted 9 lines · Wojciech Dubowik

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.

Quoted 6 lines

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.

You could also try wireless-next or wireless-testing to pinpoint if the problem is in wireless code or not.

Signature · 1 line

Kalle Valo

Wojciech Dubowik

author

2013-02-12 10:30 UTC #6 lore raw

Quoted 11 lines · Kalle Valo

Quoted 9 lines · Wojciech Dubowik
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.

Quoted 9 lines

Quoted 6 lines
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.
You could also try wireless-next or wireless-testing to pinpoint if the problem is in wireless code or not.

I see it on wireless-testing and mac80211-next. I will try with other driver later today.

I can see also other problem like authentication frame always timing out the first time but I will handle it later.

Wojciech Dubowik

author

2013-02-12 10:52 UTC #7 lore raw

Quoted 17 lines · Wojciech Dubowik

Quoted 16 lines · Kalle Valo
Quoted 14 lines · Wojciech Dubowik
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.

Quoted 8 lines

Quoted 4 lines
Quoted 1 line
I will try to disable all cores and run in again to see if it's rcu problem.
You could also try wireless-next or wireless-testing to pinpoint if the problem is in wireless code or not.
I see it on wireless-testing and mac80211-next. I will try with other driver later today.
I can see also other problem like authentication frame always timing out the first time but I will handle it later.

It has turned out that I had bad irq, switch to polling problem. Without interrupts for wireless cards I will for sure see such problems.

Sorry for spamming.

Wojtek

Quoted 4 lines

Signature · 3 lines

To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Wojciech Dubowik

author

2013-02-13 12:50 UTC #8 lore raw

Quoted 22 lines · Wojciech Dubowik

Quoted 21 lines · Wojciech Dubowik
Quoted 20 lines · Kalle Valo
Quoted 9 lines · Wojciech Dubowik
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.
Quoted 6 lines
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.
You could also try wireless-next or wireless-testing to pinpoint if the problem is in wireless code or not.

Quoted 6 lines

Quoted 4 lines
I see it on wireless-testing and mac80211-next. I will try with other driver later today.
I can see also other problem like authentication frame always timing out the first time but I will handle it later.
It has turned out that I had bad irq, switch to polling problem. Without interrupts for wireless cards I will for sure see such problems.

After solving the bad irq problems I can still see the issue.

It has turned out that when I set beacon interval to less than 40ms I get beacon loss events.

My setup is ath9k AP and ath9k STA on the same pc connected with rf cable and 40dB attenuator.

I have seen this problem also with earlier versions of wireless testing and next.

Wojtek

Quoted 13 lines

Sorry for spamming.

Wojtek

Quoted 4 lines

Signature · 3 lines

To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 3 lines

To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html