iwl4965 can't reconnect if AP is lost and then comes back

[ViktorNagy]

I can connect with WPA to the AP, I can also disconnect and then reconnect

but if the AP is switched off while I am connected, then I have to restart in order to get wifi working again

I would be happy to try rmmod or restarting services, but I need instructions for it, as until now I did everything at the same time, and finally nothing worked

I have a Thinkpad T61 (766418G) with Intel(R) Wireless WiFi Link 4965AGN

daemon.log:
Jan 16 05:02:02 vikti NetworkManager: <info> wlan0: link timed out.
Jan 16 05:02:02 vikti NetworkManager: <info> SWITCH: found better connection 'wlan0/Triumvirat' than current connection 'wlan0/Triumvirat'. same_ssid=1, have_link=0
Jan 16 05:02:02 vikti NetworkManager: <info> Will activate connection 'wlan0/Triumvirat'.
Jan 16 05:02:02 vikti NetworkManager: <info> Device wlan0 activation scheduled...
Jan 16 05:02:02 vikti NetworkManager: <info> Deactivating device wlan0.
Jan 16 05:02:02 vikti dhclient: There is already a pid file /var/run/dhclient.wlan0.pid with pid 23345
Jan 16 05:02:02 vikti dhclient: killed old client process, removed PID file
Jan 16 05:02:02 vikti dhclient: wmaster0: unknown hardware address type 801
Jan 16 05:02:02 vikti dhclient: wmaster0: unknown hardware address type 801
Jan 16 05:02:02 vikti dhclient: DHCPRELEASE on wlan0 to 192.168.0.254 port 67
Jan 16 05:02:03 vikti avahi-daemon[5612]: Withdrawing address record for 192.168.0.12 on wlan0.
Jan 16 05:02:03 vikti avahi-daemon[5612]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.12.
Jan 16 05:02:03 vikti avahi-daemon[5612]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jan 16 05:02:03 vikti avahi-daemon[5612]: Withdrawing address record for fe80::213:e8ff:fe9c:5b91 on wlan0.
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) started...
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 16 05:02:03 vikti NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jan 16 05:02:03 vikti NetworkManager: <info> DHCP daemon state is now 11 (unknown) for interface wlan0
Jan 16 05:02:03 vikti NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0/wireless): access point 'Triumvirat' is encrypted, but NO valid key exists. New key needed.
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'Triumvirat'.
Jan 16 05:02:03 vikti NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0) New wireless user key for network 'Triumvirat' received.
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jan 16 05:02:04 vikti NetworkManager: <info> Activation (wlan0/wireless): access point 'Triumvirat' is encrypted, and a key exists. No new key needed.
Jan 16 05:02:05 vikti NetworkManager: <info> supplicant_interface_init() - connect to global ctrl socket (0/10).
Jan 16 05:02:05 vikti NetworkManager: <info> supplicant_interface_init() - connect to global ctrl socket (1/10).
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant6^I'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> supplicant_init() - connect to device ctrl socket (1/10).
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was '0'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid xxxxxxxxxxxxxxx'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jan 16 05:02:05 vikti NetworkManager: <info> SUP: response was 'OK'
Jan 16 05:02:05 vikti NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jan 16 05:04:05 vikti NetworkManager: <info> Activation (wlan0/wireless): association took too long (>120s), failing activation.
Jan 16 05:04:05 vikti NetworkManager: <info> Activation (wlan0) failure scheduled...
Jan 16 05:04:05 vikti NetworkManager: <info> Activation (wlan0) failed for access point (Triumvirat)
Jan 16 05:04:05 vikti NetworkManager: <info> Activation (wlan0) failed.
Jan 16 05:04:05 vikti NetworkManager: <info> Deactivating device wlan0.
Jan 16 05:04:20 vikti NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one.
Jan 16 05:06:34 vikti NetworkManager: <WARN> request_and_convert_scan_results(): card took too much time scanning. Get a better one.

and the last message repeats until I rebooted

kern.log:
Jan 16 00:25:19 vikti kernel: [114953.096000] wlan0: associated
Jan 16 05:01:42 vikti kernel: [131535.860000] wlan0: No ProbeResp from current AP xx:xx:xx:xx:xx:xx - assume out of range
Jan 16 05:02:04 vikti kernel: [131558.052000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan 16 05:02:05 vikti kernel: [131558.788000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 16 05:04:20 vikti kernel: [131694.152000] ADDRCONF(NETDEV_UP): wlan0: link is not ready

[ViktorNagy (viktor-nagy)]

I had this problem again, but now I was able to solve it.

1. I disabled the wifi at the applet, then
2. ifconfig showed that it is really off.
3. sudo rmmod iwl4965 iwlwifi_mac80211, and finally
4. sudo modprobe -a iwl4965
5. enabled wireless at nm-applet

after circa 30secs of waiting my computer connected to the network

[Martin Schwenke (martin-meltin)]

I can confirm that I saw this problem regularly under Gutsy.

[Doug (doug-m)]

I also see this very frequently on Ubuntu 7.10 kernel 2.6.22-15-generic.

[Daniel T Chen (crimsun)]

Does it also occur in 8.10 or 9.04?

[ViktorNagy (viktor-nagy)]

No, I never had any problems with Hardy. For me it's safe to close this bug.

[Peter Magnusson (kmpm)]

Not seen any of it in 8.10

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-ubuntu-modules-2.6.22 task.