Comment 31 for bug 767192

@Tommy,

The most helpful log for this problem is the syslog, as it includes the logs from the kernel, NetworkManager, and wpa_supplicant all intermixed to get an idea of the order in which things are happening between the separate components. Looking at the kernel log you just attached I don't see the same "direct probe" time-outs as in the original logs you attached. The successful connection in those logs also seems to skip the "direct probe" stage. I'm currently looking at the code to try and determine why that stage would or wouldn't be run. I don't see it happening with my machines (none of which use the ath5k driver).

I asked about connecting to other APs out of curiosity, as your problems could be related to how your AP is set up (e.g. hidden SSID, mac address filtering, etc). You don't have to go out of your way to find another AP to connect to, but if you have an opportunity to try it I'd be interested to hear the result.

We could try bisecting between 2.6.37 and 2.6.38-rc1, but it could be difficult as that period represents the "merge window" when the bulk of the new development work for the 2.6.38 kernel release was being merged. That means that there is a lot of potential for instability. So I'd like to do a little more digging before trying that.

Does removing hwcrypt=1 make any difference on the 2.6.37 kernels?