wireless authentication always times out after standby

[Stefan Bethge]

After updating from saucy to trusty, putting the system to standby makes wireless stop working after wake up. Rebooting the system fixes it until next time standby is entered.

I've tried various hints about unloading modules, restarting the network-manager service or nm-applet, nmcli nm sleep false
or using rfkill / the hardware kill switch. None of these changed the behaviour or seemed wrong. After following https://wiki.gnome.org/Projects/NetworkManager/Debugging, I was able to get the attached lines in /var/log/syslog.
The driver works fine after wake up and scanning for networks works too. Upon trying authentication, the request fails after 5 seconds with a timeout. I managed to make the connection working again by killing wpa_supplicant so it must somehow be stuck.

$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
(current today, April 10th 2014)

wpasupplicant version is 2.1-0ubuntu1

System: Lenovo Thinkpad R61
Wireless Driver: iwl3945
$ uname -a
Linux <hostname> 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[Stefan Bethge (kjyv)]

A quick and dirty workaround is changing line 15 of /usr/lib/pm-utils/sleep.d/60_wpa_supplicant to read

resume|thaw)
    $WPACLI terminate

instead of

resume|thaw)
    $WPACLI resume

[Stefan Bethge (kjyv)]

One more thing I tried: After wake up, regardless of calling resume or not, wpa_supplicant is reacting to wpa_cli ping and also does some stuff as can be seen in the log. So it is probably not stuck but in a wrong internal state.
Additionally, it takes about 30 seconds after authentication until the network is able to actually connect to ips.

[Stefan Bethge (kjyv)]

A correction about comment #2 : "wpa_cli terminate" can make the connection work after the system is woken up. It does however not work at the time sleep.d is processed. So it seems wpa_cli can't connect to wpa_supplicant at that time.
I have because of that replaced "$WPACLI resume" with "pkill wpa_supplicant" and my connection works again after wake up.

[Steve Hemingway (steve-hemingway)]

I made the change suggested in comment #4 and it works like a dream. I would like to thank Stefan for helping me work around this annoying bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[X-Coder (x-coder)]

Thank you Stefan, your suggestion from comment #4 helped me too on my Thinkpad T60 with trusty and iwl3945 driver.

[Dennis-martin-herbers (dennis-martin-herbers)]

I tracked down the issue where WiFi would fail after suspend in that it doesn't associate anymore (tries to connect but fails), and it's a bug in wpa-supplicant that was fixed in the current version (Ubuntu uses 2.1, newest is 2.3). Replacing Ubuntu's wpa-supplicant 2.1 with Debian's wpa-supplicant 2.3 and rebooting immediately fixed the issue.

https://packages.debian.org/sid/wpasupplicant