From: Dan Williams <dcbw@redhat.com>
To: Mike Edenfield <kutulu@kutulu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl3945: disassociating from current AP on rescan with kernels > 3.0
Date: Wed, 04 Jan 2012 10:31:02 -0600 [thread overview]
Message-ID: <1325694662.2622.7.camel@d430> (raw)
In-Reply-To: <012e01ccc67b$bfe90be0$3fbb23a0$@kutulu.org>
On Thu, 2011-12-29 at 17:46 -0500, Mike Edenfield wrote:
> After upgrading to a v3.0 kernel, my Intel wireless adapter stopped working
> when used with any UI-based wpa_supplicant front-end that does periodic
> scans, such as NetworkManager and wicd. Whenever the software asks for an AP
> scan, the device disconnects from its current AP and blacklists it, making
> it impossible to reconnect until I kill wpa_supplicant. If I manually
> configure wpa_supplicant and launch it directly, the adapter stays
> associated with the AP properly.
>
> I was able to reproduct this behavior with kernel version 3.0.4, 3.1.4, and
> 3.1.5, but downgrading to 2.6.39 or lower solves the problem. I haven't seen
> any other reports of this problem specific to 3.x -- did I miss some other
> step I need to do when upgrading?
There shouldn't be any; the driver should be ensuring that the current
association stays valid across scans as long as the AP is still in
range. This sounds like a driver or mac80211 bug.
Dan
next prev parent reply other threads:[~2012-01-04 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 22:46 iwl3945: disassociating from current AP on rescan with kernels > 3.0 Mike Edenfield
2012-01-04 16:31 ` Dan Williams [this message]
2012-01-05 11:39 ` Stanislaw Gruszka
2012-01-07 4:44 ` Mike Edenfield
2012-01-18 14:07 ` Stanislaw Gruszka
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=1325694662.2622.7.camel@d430 \
--to=dcbw@redhat.com \
--cc=kutulu@kutulu.org \
--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).