From: Ted Ts'o <tytso@mit.edu>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: 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 15:17:52 -0500 [thread overview]
Message-ID: <20111213201752.GA5094@thunk.org> (raw)
In-Reply-To: <1323800557.3355.31.camel@jlt3.sipsolutions.net>
On Tue, Dec 13, 2011 at 07:22:37PM +0100, Johannes Berg wrote:
>
> I think this is. It's interesting though that it is deauthenticating --
> is there anything in the log before? But since you bisected it to the TX
> sync commit, I'd say let's try the below patch. You might have to adjust
> the iwl-mac80211.c file to iwl-agn.c, I'm not entirely sure what version
> has the moved code.
>
> Please let me know -- this commit is probably the right thing to do
> until we get rid of tx_sync completely.
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.)
I did have to slightly modify your patch since at least as of 3.2-rc5,
the functions involved were in a different file (iwl-agn.c).
I tried Wey's patch, but it didn't seem to result in any change in
behavior, as you had suggested.
OK, now to see if I can figure out what's going on with the EAP-TLS
authentication case....
- Ted
>From c1160e3b5dfadc8ac26f5a7ff0ff6ce1e8e7dbae Mon Sep 17 00:00:00 2001
From: Theodore Ts'o <tytso@google.com>
Date: Tue, 13 Dec 2011 14:58:50 -0500
Subject: [PATCH] iwlwifi: disable tx_sync if p2p is not enabled
Test patch sent to LKML from by Johnnes Berg
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
---
drivers/net/wireless/iwlwifi/iwl-agn.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-agn.c b/drivers/net/wireless/iwlwifi/iwl-agn.c
index bacc06c..78ce547 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn.c
+++ b/drivers/net/wireless/iwlwifi/iwl-agn.c
@@ -2850,6 +2850,9 @@ static int iwlagn_mac_tx_sync(struct ieee80211_hw *hw,
int ret;
u8 sta_id;
+ if (!vif->p2p)
+ return 0;
+
IWL_DEBUG_MAC80211(priv, "enter\n");
mutex_lock(&priv->shrd->mutex);
@@ -2898,6 +2901,9 @@ static void iwlagn_mac_finish_tx_sync(struct ieee80211_hw *hw,
struct iwl_vif_priv *vif_priv = (void *)vif->drv_priv;
struct iwl_rxon_context *ctx = vif_priv->ctx;
+ if (!vif->p2p)
+ return;
+
IWL_DEBUG_MAC80211(priv, "enter\n");
mutex_lock(&priv->shrd->mutex);
--
1.7.3.1
next prev parent reply other threads:[~2011-12-13 20:17 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 [this message]
2011-12-14 1:59 ` Ted Ts'o
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=20111213201752.GA5094@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).