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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html