On Sat, Mar 29, 2014 at 11:55:42AM +0100, Michael Biebl wrote: > Hi Josh, > > Am 29.03.2014 04:43, schrieb Josh Triplett: > > Ever since upgrading network-manager from 0.9.8.0-5 to 0.9.8.8-4, after > > a while network-manager starts reporting all interfaces as "unmanaged", > > and they're all down (breaking connectivity). Restarting > > network-manager fixes this, bringing the devices back to being managed. > > Can you send me a debug log? > Run "NetworkManager --no-daemon --log-level=DEBUG"
I can try that, though it seems to take a while to reproduce. But I did manage to find some useful data in syslog this most recent time: Mar 29 01:19:47 leaf NetworkManager[3000]: <info> sleep requested (sleeping: no enabled: yes) Mar 29 01:19:47 leaf NetworkManager[3000]: <info> sleeping or disabling... Mar 29 01:19:47 leaf NetworkManager[3000]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] Mar 29 01:19:47 leaf NetworkManager[3000]: <info> (eth0): cleaning up... Mar 29 01:19:47 leaf NetworkManager[3000]: <info> (eth0): taking down device. Mar 29 01:19:47 leaf NetworkManager[3000]: <info> NetworkManager state is now ASLEEP Mar 29 01:19:47 leaf NetworkManager[3000]: <info> (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Mar 29 01:19:47 leaf NetworkManager[3000]: <info> (wlan0): deactivating device (reason 'sleeping') [37] Mar 29 01:19:48 leaf NetworkManager[3000]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 3032 Does that help? I don't see what *caused* NetworkManager to think it was OK to sleep, but more importantly there doesn't seem to be any way to wake it up once it has done so. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
