From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: reinette chatre <reinette.chatre@intel.com>,
Nico -telmich- Schottelius
<nico-linux-ipw3945-devel@schottelius.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ipw3945-devel] 2.6.29-wl-36116-g6a982a0: connection loss
Date: Tue, 31 Mar 2009 20:45:57 +0300 [thread overview]
Message-ID: <8763hpsi0a.fsf@litku.valot.fi> (raw)
In-Reply-To: <1238520041.5970.112.camel@johannes.local> (Johannes Berg's message of "Tue\, 31 Mar 2009 19\:20\:41 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
>> Perhaps the new beacon filtering work [1] is changing more than it
>> intended?
>
> I think it only changed the messages here. Previously, that message
> simply wouldn't have been there, instead you'd only have seen the "No
> ProbeResp from current AP - assume out of range" thing.
At least I have been using latest wireless-testing with iwl3945 all the time
(for example right now) and I haven't noticed any problems.
But your comment makes me think is the "beacon loss" message too
verbose. Maybe we should remove it?
BTW, what are the AP settings (beacon interval, DTIM)? Was power save
enabled in the driver? If the beacon interval is really long, like 1
second, our timer is far from optimal and missing beacon only once
might trigger the warning. We should fix that properly at some point.
--
Kalle Valo
next prev parent reply other threads:[~2009-03-31 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090331044946.GA10616@denkbrett.schottelius.org>
2009-03-31 17:15 ` [ipw3945-devel] 2.6.29-wl-36116-g6a982a0: connection loss reinette chatre
2009-03-31 17:20 ` Johannes Berg
2009-03-31 17:45 ` Kalle Valo [this message]
2009-03-31 17:57 ` Christian Lamparter
2009-03-31 18:01 ` Johannes Berg
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=8763hpsi0a.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nico-linux-ipw3945-devel@schottelius.org \
--cc=reinette.chatre@intel.com \
/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).