From: Stanislaw Gruszka <sgruszka@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: Thu, 5 Jan 2012 12:39:40 +0100 [thread overview]
Message-ID: <20120105113939.GC2222@redhat.com> (raw)
In-Reply-To: <012e01ccc67b$bfe90be0$3fbb23a0$@kutulu.org>
On Thu, Dec 29, 2011 at 05:46:48PM -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?
Are you sure this is 2.6.39 -> 3.0 regression. There are not many
changes in iwlegacy driver between these
$ git log v2.6.39..v3.0 --oneline --no-merges -- drivers/net/wireless/iwlegacy/
51e6525 iwlegacy: fix channel switch locking
51892db iwl4965: set tx power after rxon_assoc
dfe2158 iwl4965: correctly validate temperature value
aac11c1 iwl4965: fix 5GHz operation
8220ba3 iwlegacy: Silence DEBUG_STRICT_USER_COPY_CHECKS=y warning
2245090 iwlegacy: remove sync_cmd_mutex
28a6e57 iwlegacy: more priv->mutex serialization
81e6326 iwlegacy: fix enqueue hcmd race conditions
93fd74e iwlegacy: comment typo fix diable -> disable
7a55237 iwlegacy: remove scan_tx_antennas
5855c7d iwlegacy: remove unneeded __packed
8eb0ac7 iwlegacy: remove unneeded disable_hw_scan check
3e41de8 iwlegacy: simplify init geos
a078a1f iwlegacy: enable only rfkill interrupt when device is down
ab42b40 iwlegacy: remove duplicate initialization in iwl4956_down()
85ee7a1 treewide: cleanup continuations and remove logging message whitespace
0477ad7 iwlegacy: use pci_dev->revision
a22e93f iwl4965: drop a lone pr_err()
and none of it looks suspicious.
Problem looks more like software scanning issue, which we enable
by default on 2.6.39. Can you check if disable_hw_scan=0 module
parameter helps?
Thanks
Stanislaw
next prev parent reply other threads:[~2012-01-05 11:39 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
2012-01-05 11:39 ` Stanislaw Gruszka [this message]
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=20120105113939.GC2222@redhat.com \
--to=sgruszka@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).