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. > [ 29.434897] wlan0: authenticate with bc:05:43:94:1a:da > [ 29.445634] wlan0: send auth to bc:05:43:94:1a:da (try 1/3) > [ 29.448168] wlan0: authenticated > [ 29.448229] wlan0: waiting for beacon from bc:05:43:94:1a:da > [ 29.473633] iwlwifi 0000:02:00.0: ACTIVATE a non DRIVER active station id 0 addr bc:05:43:94:1a:da So this repeats, I suspect the 15 second retry timer is in wpa_supplicant. > [ 55.773770] wlan0: authenticate with bc:05:43:94:1a:da > [ 55.784316] wlan0: send auth to bc:05:43:94:1a:da (try 1/3) > [ 55.786758] wlan0: authenticated > [ 55.787407] wlan0: associate with bc:05:43:94:1a:da (try 1/3) > [ 55.791114] wlan0: RX AssocResp from bc:05:43:94:1a:da (capab=0x431 status=0 aid=4) > [ 55.791121] wlan0: associated So when it succeeds it basically doesn't do the beacon wait thing. I guess that is the problem then. Do you think you could collect some tracing info? trace-cmd record -e mac80211 -e iwlwifi would be useful. > [ 73.059911] netlink: 12 bytes leftover after parsing attributes. This is interesting, I wonder where that came from, but I don't think it's related. johannes -- 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
