On Thu, 2011-10-20 at 13:59 +0900, Norbert Preining wrote: > so I am now at the university, and it seems your last patch > did wonder. Here a log after waking up from suspend at university... For some value of wonder ... > [17394.896199] wlan0: associated > [17394.974620] iwlagn 0000:06:00.0: Encounter TX_STATUS_FAIL_PASSIVE_NO_RX, am I on 5.2G band? (2) > [17394.976930] iwlagn 0000:06:00.0: Encounter TX_STATUS_FAIL_PASSIVE_NO_RX, am I on 5.2G band? (2) > [17409.608674] iwlagn 0000:06:00.0: Tx aggregation enabled on ra = 00:24:c4:ab:bd:ef tid = 0 > [17409.616748] wlan0: direct probe to 00:24:c4:ab:bd:e0 (try 1/3) > [17409.816093] wlan0: direct probe to 00:24:c4:ab:bd:e0 (try 2/3) > [17410.016083] wlan0: direct probe to 00:24:c4:ab:bd:e0 (try 3/3) > [17410.216086] wlan0: direct probe to 00:24:c4:ab:bd:e0 timed out > [17419.285141] iwlagn 0000:06:00.0: Encounter TX_STATUS_FAIL_PASSIVE_NO_RX, am I on 5.2G band? (0) > [17419.285315] iwlagn 0000:06:00.0: Encounter TX_STATUS_FAIL_PASSIVE_NO_RX, am I on 5.2G band? (0) > [17419.286583] wlan0: deauthenticating from 00:24:c4:ab:bd:ef by local choice (reason=2) > [17419.300296] cfg80211: Calling CRDA for country: JP > [17419.309278] wlan0: authenticate with 00:24:c4:ab:bd:ef (try 1) > [17419.310105] wlan0: authenticated > [17419.317900] wlan0: associate with 00:24:c4:ab:bd:ef (try 1) It seems a bit like the 5 GHz AP (:e0) just fails, and wpa_supplicant selects a 2.4 GHz AP (:ef) now? Pure conjecture, I guess the AP could also be on the same channel -- did you have scan information for these APs? 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
