From: Wojciech Dubowik <Wojciech.Dubowik@neratec.com>
To: linux-wireless@vger.kernel.org
Subject: [BUG] Beacon loss event every second
Date: Mon, 11 Feb 2013 14:47:46 +0100 [thread overview]
Message-ID: <5118F682.8000502@neratec.com> (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
next reply other threads:[~2013-02-11 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 13:47 Wojciech Dubowik [this message]
2013-02-11 14:27 ` [BUG] Beacon loss event every second Johannes Berg
2013-02-11 14:42 ` Wojciech Dubowik
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=5118F682.8000502@neratec.com \
--to=wojciech.dubowik@neratec.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.