Comment 9 for bug 264881

Revision history for this message
Sebastian (zimmermann+launchpad-net) wrote :

I have a similar problem: The WLAN (iwl3945, Intel Corporation PRO/Wireless 3945ABG) associates, then disassociates about 5 seconds later, then associates, then disassociates, and so on. Also, association takes very long (about 30 seconds).
This happens with linux-image-2.6.27-4-generic in intrepid.

Syslog:

NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
kernel: [ 1730.920804] wlan0: authenticate with AP xx
kernel: [ 1730.920822] wlan0: authenticated
kernel: [ 1730.920828] wlan0: associate with AP xx
kernel: [ 1730.920846] wlan0: RX ReassocResp from xx (capab=0x431 status=0 aid=1)
kernel: [ 1730.920851] wlan0: associated
NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 0
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
kernel: [ 1741.924126] wlan0: disassociating by local choice (reason=3)
NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
kernel: [ 1745.654378] wlan0: deauthenticated
kernel: [ 1745.654776] wlan0: authenticate with AP xx
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 3
NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 0
kernel: [ 1745.660391] wlan0: authenticate with AP xx
kernel: [ 1745.660433] wlan0: authenticated
kernel: [ 1745.660438] wlan0: associate with AP xx
kernel: [ 1745.664160] wlan0: authenticate with AP xx
kernel: [ 1745.664183] wlan0: authenticated
kernel: [ 1745.664188] wlan0: associate with AP xx
NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4
kernel: [ 1745.668771] wlan0: RX ReassocResp from xx (capab=0x431 status=0 aid=1)
kernel: [ 1745.668781] wlan0: associated
NetworkManager: <info> wlan0: link timed out.
NetworkManager: <info> Activation (wlan0/wireless): association took too long.