From: Ted Ts'o <tytso@mit.edu>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, ilw@linux.intel.com,
linux-wireless@vger.kernel.org
Subject: Re: REGRESSION: v3.2-rcX: iwlagn refuses to associate with my AP's
Date: Tue, 13 Dec 2011 20:59:59 -0500 [thread overview]
Message-ID: <20111214015959.GA6276@thunk.org> (raw)
In-Reply-To: <20111213201752.GA5094@thunk.org>
On Tue, Dec 13, 2011 at 03:17:52PM -0500, Ted Ts'o wrote:
> Well, this patch seems to fix things for the non-authenticated case.
> I can now associate with the GoogleGuest SSID without any problems.
> I'm still having problems associating with the EAP-TLS encrypted
> network, but that looks like it's a different bug. (And that may
> explain why I had so much trouble bisecting this; there are two issues
> that have very similar symptoms.)
... and the second problem I had with associating with EAP-TLS
encrypted SSID's was solved by Wey-Yi's patch:
iwlwifi: allow to switch to HT40 if not associated yet
... found in the thread "iwlagn regression in v3.1.5"
So with these two patches applied, things are now stable for me.
One thing: out of curiosity, I assume there is a pretty good testing
infrastructure at Intel --- how was it that this didn't caught
earlier? Is it because different access points do things a little
different? Would it be useful if I can find out the model of access
point that we're using, so you could hopefully augment your library of
test hardware? I'm asking out of purely selfish reasons, of course,
since this took me the better part of a day to bisect each of these
problems.
- Ted
next prev parent reply other threads:[~2011-12-14 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 19:42 REGRESSION: v3.2-rcX: iwlagn refuses to associate with my AP's Theodore Ts'o
2011-12-13 17:26 ` Ted Ts'o
2011-12-13 17:54 ` [Ilw] " wwguy
2011-12-13 18:06 ` Johannes Berg
2011-12-13 18:22 ` Johannes Berg
2011-12-13 20:17 ` Ted Ts'o
2011-12-14 1:59 ` Ted Ts'o [this message]
2011-12-14 3:14 ` Guy, Wey-Yi
2011-12-21 21:12 ` Ted Ts'o
2011-12-21 21:16 ` David Miller
2011-12-21 23:18 ` Ted Ts'o
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=20111214015959.GA6276@thunk.org \
--to=tytso@mit.edu \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.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).