Comment 8 for bug 759051

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Thanks.

I think we probably have enough information now. I suspect a driver issue with mixed-mode itself:

Apr 9 00:25:09 rde-richw-2 wpa_supplicant[1490]: Trying to associate with 00:1f:33:b6:cd:82 (SSID='Wales276Mosher-A' freq=5260 MHz)
Apr 9 00:25:09 rde-richw-2 NetworkManager[1321]: <info> (wlan0): supplicant connection state: scanning -> associating
Apr 9 00:25:09 rde-richw-2 kernel: [169127.033183] wlan0: authenticate with 00:1f:33:b6:cd:82 (try 1)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.033844] wlan0: authenticated
Apr 9 00:25:09 rde-richw-2 kernel: [169127.033912] wlan0: associate with 00:1f:33:b6:cd:82 (try 1)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.034470] wlan0: RX AssocResp from 00:1f:33:b6:cd:82 (capab=0x11 status=18 aid=0)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.034475] wlan0: 00:1f:33:b6:cd:82 denied association (code=18)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.034490] wlan0: deauthenticating from 00:1f:33:b6:cd:82 by local choice (reason=3)
Apr 9 00:25:19 rde-richw-2 wpa_supplicant[1490]: Authentication with 00:1f:33:b6:cd:82 timed out.

I think this is sufficient to assign it to the 'linux' package for further investigation at the kernel level.