From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Johannes Berg <johannes@sipsolutions.net>,
Amit Beka <amit.beka@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
David Spinadel <david.spinadel@intel.com>,
linux-wireless@vger.kernel.org,
David Miller <davem@davemloft.net>,
Intel Linux Wireless <ilw@linux.intel.com>
Subject: Re: 3.4-merge: iwlwifi needs more than 1 minute to connect
Date: Mon, 26 Mar 2012 17:13:06 +0200 [thread overview]
Message-ID: <4F708782.3000400@hartkopp.net> (raw)
In-Reply-To: <4F707AA7.5050401@hartkopp.net>
On 26.03.2012 16:18, Oliver Hartkopp wrote:
> On 26.03.2012 12:05, Johannes Berg wrote:
>
>> Hi Oliver,
>>
>>> i'm using the *very* latest 3.4-merge tree from Linus and my Wifi now needs
>>> more than one minute to connect to my access point.
>>
>>> [ 16.288562] wlan0: authenticate with bc:05:43:94:1a:da
>>> [ 16.299644] wlan0: send auth to bc:05:43:94:1a:da (try 1/3)
>>> [ 16.302060] wlan0: authenticated
>>> [ 16.302492] wlan0: waiting for beacon from bc:05:43:94:1a:da
>>> [ 16.432398] iwlwifi 0000:02:00.0: ACTIVATE a non DRIVER active station id 0 addr bc:05:43:94:1a:da
>>
>> This is an odd message. I need to figure out how that can even happen.
>>
>> What's the beacon interval on your AP? It seems more likely that this is
>> a problem with RX though.
Hi Johannes and Amit,
pointing to the RX path was a good idea!
I checked the commits of the last three weeks and discovered that it turns
out that the patches from Amit caused the regression:
iwlwifi: add testmode command for rx forwarding
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=0aef8ddc8bedac1db4c96fddc9fb1b44b730cf4f
iwlwifi: fixed testmode notifications length
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=8e81f65fdc7f5d292bb3c115b748767d921823c1
I reverted them in the opposite order (of course) and now the issue is gone.
Regards,
Oliver
next prev parent reply other threads:[~2012-03-26 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 18:04 pull request: wireless-next 2012-03-16 John W. Linville
2012-03-16 21:12 ` David Miller
2012-03-23 19:40 ` 3.4-merge: iwlwifi needs more than 1 minute to connect Oliver Hartkopp
2012-03-26 10:05 ` Johannes Berg
2012-03-26 14:18 ` Oliver Hartkopp
2012-03-26 15:13 ` Oliver Hartkopp [this message]
2012-03-26 15:20 ` Oliver Hartkopp
2012-03-29 4:54 ` Oliver Hartkopp
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=4F708782.3000400@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=amit.beka@intel.com \
--cc=davem@davemloft.net \
--cc=david.spinadel@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).