From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Michael Buesch <mb@bu3sch.de>,
Sujith <Sujith.Manoharan@atheros.com>,
wireless <linux-wireless@vger.kernel.org>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ath9k becon loss messages
Date: Mon, 6 Apr 2009 10:56:27 +0200 [thread overview]
Message-ID: <200904061056.28495.helmut.schaa@gmail.com> (raw)
In-Reply-To: <873acmyz4x.fsf@litku.valot.fi>
Am Montag, 6. April 2009 schrieb Kalle Valo:
> Helmut Schaa <helmut.schaa@googlemail.com> writes:
>
> >> Then there is something happening in ath9k or your AP which prevents
> >> ath9k from receiving beacons. Try pinging your AP with 100 ms
> >> interval. Do you see anything happening in 120 s intervals?
> >
> > NetworkManager typically scans every 120 seconds and I can also trigger
> > the messages by a manual scan with iwlist. I did not dig any further but
> > the messages seem to appear right at the end of the scan. Tried with iwlagn
> > and both sw_scan and hw_scan.
>
> Thanks, this was valuable info. It might be that my beacon filtering
> patches broke something related to scanning and beacon loss check. I'll
> take a look at this.
Maybe you did not break anything. During a scan we will stay away from the
operating channel for some seconds which indeed prevents us from receiving
beacons. I'd say sending a probe request to the AP in that case won't hurt.
Helmut
next prev parent reply other threads:[~2009-04-06 8:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 9:23 ath9k becon loss messages Jaswinder Singh Rajput
2009-04-05 9:29 ` Michael Buesch
2009-04-05 9:36 ` Michael Buesch
2009-04-05 10:03 ` Kalle Valo
2009-04-05 11:00 ` Jaswinder Singh Rajput
2009-04-05 9:52 ` Jaswinder Singh Rajput
2009-04-05 10:13 ` Kalle Valo
2009-04-06 7:14 ` Helmut Schaa
2009-04-06 8:17 ` Kalle Valo
2009-04-06 8:56 ` Helmut Schaa [this message]
2009-04-06 9:04 ` Kalle Valo
2009-04-06 10:17 ` Michael Buesch
2009-04-06 10:23 ` Kalle Valo
2009-04-06 10:51 ` Helmut Schaa
2009-04-06 11:05 ` Kalle Valo
2009-04-06 15:18 ` Kalle Valo
2009-04-06 18:00 ` John W. Linville
2009-04-07 5:54 ` Kalle Valo
2009-04-07 13:53 ` John W. Linville
2009-04-07 15:19 ` Kalle Valo
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=200904061056.28495.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=davem@davemloft.net \
--cc=jaswinder@kernel.org \
--cc=kalle.valo@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).