On Tue, Sep 02, 2008 at 11:10:38AM -0400, Dan Williams wrote: > On Tue, 2008-09-02 at 17:58 +0300, Michael S. Tsirkin wrote: > > On Tue, Sep 02, 2008 at 09:30:01AM -0400, Dan Williams wrote: > > > On Tue, 2008-09-02 at 16:04 +0300, Michael S. Tsirkin wrote: > > > > On Tue, Sep 02, 2008 at 08:10:09AM +0200, Johannes Berg wrote: > > > > > "by local choice" means wext requested this, not a kernel bug. Well.. The disassociation part not, but what is trickering that (association/authentication timeout) may still be ;-). > > I put up a (sanitized) -dd output here > > http://bugzilla.kernel.org/show_bug.cgi?id=11476 Would it be possible to get unsanitized version and with -t (i.e., timestamps)? If you don't want to post it publicly, feel free to send one directly to me. The one attached to that bug removed quite a bit of information that would have been useful in figuring out what happened. > Logs seem to indicate a normal failure of the 4 way handshake; are you > sure your PSK is correct? It actually looks like the AP doesn't ever > get message #2 from your machine, and just retransmits message #1 of the > handshake. I'm pretty sure that if > 8ab65b03b7893da4a49009e7e356e36e27b0c407 had anything to do with it, you > wouldn't be getting this far and the AP would have denied association in > the first place. There are more than one different types of issues shown in the log. I'm not sure which one would be the key one here. Anyway, I would agree that the commit that removed an empty ext. supp rates IE has nothing to do with this. As far as suspend is concerned, which distro is used here? Does it unload the driver (i.e., remove the netdev) on suspend? If yes, you will need to update wpa_supplicant 0.6.4 which handles that disappearing and reappearing interface. If this is something else, I would need to get more complete debug log from wpa_supplicant.. -- Jouni Malinen PGP id EFC895FA -- 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
