Sorry - my assumption was too fast ... At the fourth reboot i got the problem even with the reverted patches from Amit. Sorry for the noise :-( [ 15.118888] wlan0: authenticate with bc:05:43:94:1a:da [ 15.122519] wlan0: send auth to bc:05:43:94:1a:da (try 1/3) [ 15.160486] wlan0: authenticated [ 15.160625] wlan0: waiting for beacon from bc:05:43:94:1a:da [ 15.189007] iwlwifi 0000:02:00.0: ACTIVATE a non DRIVER active station id 0 addr bc:05:43:94:1a:da [ 28.270782] wlan0: authenticate with bc:05:43:94:1a:da [ 28.274505] wlan0: send auth to bc:05:43:94:1a:da (try 1/3) [ 28.277125] wlan0: authenticated [ 28.277184] wlan0: waiting for beacon from bc:05:43:94:1a:da [ 28.306245] iwlwifi 0000:02:00.0: ACTIVATE a non DRIVER active station id 0 addr bc:05:43:94:1a:da [ 41.427670] wlan0: authenticate with bc:05:43:94:1a:da [ 41.431301] wlan0: send auth to bc:05:43:94:1a:da (try 1/3) [ 41.434021] wlan0: authenticated [ 41.434668] wlan0: associate with bc:05:43:94:1a:da (try 1/3) [ 41.437357] wlan0: RX AssocResp from bc:05:43:94:1a:da (capab=0x431 status=0 aid=3) [ 41.437363] wlan0: associated [ 41.447928] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Regards, Oliver On 26.03.2012 17:13, Oliver Hartkopp wrote: > > 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
