Additionally, this time with NLDBG=4:
DBG<3>: Attempting to read from 0x107a28f0 DBG<3>: recvmsgs(0x107a28f0): Read 1028 bytes DBG<3>: recvmsgs(0x107a28f0): Processing valid message... DBG<2>: msg 0x107ebc98: Allocated new message, maxlen=1028 lt-NetworkManager[29481]: <debug> [1361825388.37820] [nm-netlink-monitor.c:226] event_msg_ready(): TRACE DBG<4>: Allocated new object 0x107e2270 DBG<4>: Allocated new object 0x107f2018 lt-NetworkManager[29481]: <debug> [1361825388.37972] [nm-netlink-monitor.c:167] link_msg_handler(): netlink link message: iface idx 2 flags 0x11043 DBG<4>: Returned object reference 0x107f2018, 0 remaining DBG<4>: Freed object 0x107f2018 DBG<4>: Returned object reference 0x107e2270, 0 remaining DBG<4>: Freed object 0x107e2270 DBG<4>: Returned message reference 0x107ebc98, 0 remaining DBG<2>: msg 0x107ebc98: Freed The above is one complete sequence of which is repeated over and over, constantly. I assume this means it is getting some nl event from the kernel constantly, which would probably make it a kernel bug rather than a NetworkManager bug. I'll continue check in order to confirm this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1111926 Title: NetworkManager increases CPU utilization Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: Observed in systems if gnome gui is installed. NetworkManager will usually one of the cores to 100%. Killing unused services like avahi and cups didn't seem to help. Restarting the dbus service fixes the issue /etc/init.d/dbus restart Need to find root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1111926/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
