Thanks for the log. Putting the interesting excerpt here for
convenience:

Mar 09 23:27:59 fry NetworkManager[1000]: <info> (wlan0): device state change: 
secondaries -> activated (reason 'none') [90 100 0]
Mar 09 23:27:59 fry NetworkManager[1000]: <info> NetworkManager state is now 
CONNECTED_LOCAL
Mar 09 23:27:59 fry NetworkManager[1000]: <info> NetworkManager state is now 
CONNECTED_GLOBAL
[...]
Mar 10 00:37:20 fry NetworkManager[1000]: <info> sleep requested (sleeping: no  
enabled: yes)
Mar 10 00:37:20 fry NetworkManager[1000]: <info> sleeping...
Mar 10 10:04:24 fry NetworkManager[1000]: <info> waking up...
Mar 10 10:04:24 fry NetworkManager[1000]: <info> (wlan0): device state change: 
activated -> unmanaged (reason 'sleeping') [100 10 37]
Mar 10 10:04:24 fry NetworkManager[1000]: <info> (wlan0): deactivating device 
(reason 'sleeping') [37]

So it seems that the "activated -> unmanaged" action should be done
*before* "sleeping...", and then it just forgets to bring it back up
after waking up. Here it has the correct order, so that sounds like a
race condition.

This part (logind interaction) hasn't actually changed in quite some
time. Out of interest, do you get this error under upstart too? This
doesn't actually sound specific to using systemd as init, but it would
be nice to confirm that. Otherwise it's another data point for debugging
this. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422143

Title:
  No wifi connection after suspend with systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to