linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Michael Buesch <mb@bu3sch.de>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
	Jaswinder Singh Rajput <jaswinder@kernel.org>,
	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, 06 Apr 2009 13:23:53 +0300	[thread overview]
Message-ID: <87tz52xepy.fsf@litku.valot.fi> (raw)
In-Reply-To: <200904061217.31134.mb@bu3sch.de> (Michael Buesch's message of "Mon\, 6 Apr 2009 12\:17\:30 +0200")

Michael Buesch <mb@bu3sch.de> writes:

>> 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.
>
> Yeah OK. While scanning it's expected to lose some frames.
>
> However, the driver should probably protect against this by using the
> scan notification callbacks. It could disable beacon-loss reporting
> while scanning.

That case is already covered. In sw_scan mac80211 will disable power
save and hence beacon filter is also disabled. With hw_scan the firmware
should be clever enough to not emit beacon loss events when scanning.

But ath9k nor iwlwifi don't support beacon filtering and this is a
problem in mac80211. We need to disable the beacon loss check in
mac80211, most probably by stopping the associated timer whenever
scanning.

-- 
Kalle Valo

  reply	other threads:[~2009-04-06 10:23 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
2009-04-06  9:04             ` Kalle Valo
2009-04-06 10:17         ` Michael Buesch
2009-04-06 10:23           ` Kalle Valo [this message]
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=87tz52xepy.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=davem@davemloft.net \
    --cc=helmut.schaa@googlemail.com \
    --cc=jaswinder@kernel.org \
    --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).