Alexander, Actually my problem is with NetworkManagerDispatcher but it could be that we are referring to the same issue since it also happens at startup. Yes, It does consume my cpu cycles like the bug I pointed to and the high cpu load disappears after 3 to 5 minutes.
I am using htop instead of top to see a tree of what NetworkManagerDispatcher is doing. I only noticed that its continues to call wpa_supplicant and other files in /etc/network/if-* It looks like the kind of cpu usage one gets when doing an infinite loop. Then all of the sudden it breaks/times out and cpu usage drops to normal. I guess this is happening when its detecting the available networks. -- NetworkManager hangs with 100% cpu https://bugs.launchpad.net/bugs/83623 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
