I'm having a similar problem. In my case, though, there's only one process - it uses 100% of the CPU, and doesn't actually connect. Just before suspend, I unplugged the ethernet cable, and NetworkManager started connecting to a wireless network - but probably didn't finish. After I resumed the laptop, it was still in the same state (at least, according to nm-applet).
The backtrace: #0 0xb7cefd80 in __pthread_disable_asynccancel () from /lib/tls/i686/cmov/libpthread.so.0 #1 0xb7cf0a00 in ?? () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7da5962 in g_usleep () from /usr/lib/libglib-2.0.so.0 #3 0x0806cbaa in ?? () #4 0x0000c350 in ?? () #5 0xbf82d42c in ?? () #6 0xbf82d408 in ?? () #7 0xb7d821ea in g_source_attach () from /usr/lib/libglib-2.0.so.0 #8 0x08055c85 in nm_device_activation_cancel () #9 0x08055e6a in nm_device_deactivate_quickly () #10 0x08055f01 in nm_device_deactivate () #11 0x080577d6 in nm_device_stop () #12 0x080694f2 in nm_remove_device () #13 0x08069623 in ?? () #14 0x08097330 in ?? () .... -- NetworkManager causes high CPU-usage after suspend https://bugs.launchpad.net/bugs/154254 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
