linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [BUG] Beacon loss event every second
Date: Mon, 11 Feb 2013 15:42:09 +0100	[thread overview]
Message-ID: <51190341.40806@neratec.com> (raw)
In-Reply-To: <1360592857.8738.30.camel@jlt4.sipsolutions.net>

On 02/11/2013 03:27 PM, Johannes Berg wrote:
> On Mon, 2013-02-11 at 14:47 +0100, Wojciech Dubowik wrote:
>> 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
>
> johannes
>


  reply	other threads:[~2013-02-11 14:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 13:47 [BUG] Beacon loss event every second Wojciech Dubowik
2013-02-11 14:27 ` Johannes Berg
2013-02-11 14:42   ` Wojciech Dubowik [this message]
2013-02-12 10:04     ` Kalle Valo
2013-02-12 10:13       ` Wojciech Dubowik
2013-02-12 10:23         ` Kalle Valo
2013-02-12 10:24           ` Wojciech Dubowik
2013-02-12 10:46             ` Wojciech Dubowik
2013-02-13 12:45               ` Wojciech Dubowik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51190341.40806@neratec.com \
    --to=wojciech.dubowik@neratec.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).