This bug was fixed in the package network-manager -
0.9.2.0+git201202161854.8572ecf-0ubuntu5
---------------
network-manager (0.9.2.0+git201202161854.8572ecf-0ubuntu5) precise; urgency=low
* debian/patches/git_libnm-glib_ensure_device_state_aef4340.patch: make sure
we also update the device state in libnm-glib when the state-changed signal
gets fired. (LP: #934117)
* debian/control: update Vcs-Bzr; renamed the packaging branch.
* debian/patches/dnsmasq-dont-read-hosts.patch: avoid dnsmasq caching old
entries from /etc/hosts because they were listed when dnsmasq was started:
have dnsmasq not read /etc/hosts at all, the libc resolver can properly
take care of it on its own. (LP: #943339)
-- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com> Thu, 01 Mar 2012 09:36:08
-0500
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
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/934117
Title:
nm-applet is calling poll() at ~10Hz
Status in The Ubuntu Power Consumption Project:
New
Status in “network-manager” package in Ubuntu:
Fix Released
Bug description:
I've noticed that nm-applet is polling at ~10Hz. This seems to occur
only when I am only connected to the network (ethernet or wireless).
A strace of nm-applet is as follows:
recvfrom(3, 0x101e304, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN},
{fd=6, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN}], 6, 100) =
0 (Timeout)
read(4, 0x7fff27127870, 16) = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(3, 0x101e304, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN},
{fd=6, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN}], 6, 0) = 0
(Timeout)
read(4, 0x7fff27127870, 16) = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(3, 0x101e304, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN},
{fd=6, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN}], 6, 100) =
0 (Timeout)
read(4, 0x7fff27127870, 16) = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(3, 0x101e304, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=5, events=POLLIN},
{fd=6, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN}], 6, 0) = 0
(Timeout)
So it seems we have a poll using 100 millisecond timeout and also a 0
millisecond timeout. The 0 millisecond timeout is basically a busy
poll which seems a little excessive. The 100 millisecond timeout is
the root cause of the 10Hz events/second wakeup.
This is causing excessive wakeups which keeps the CPU out of deep C
sleep states and hence reduces battery life. Can this be fixed?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/934117/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
