Public bug reported:

Binary package hint: gnome-power-manager

Running Gutsy 64-bit on a dual-core AMD 64-bit laptop (Compaq V3000z).
for the past 2 days my gnome-power-manager has been using between 2 and
10% of my cpu.  Beagle was also showing up on the top list at about the
same usage, but after killing beagle, g-p-m still showed up.

I 'strace -f -p 'd gnome-power-manager and at least one thread seemed to
be stuck in a poll loop... i don't know if this is normal or not:

...
[pid  6726] read(22, 
"\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\357?\240#\0\0"..., 128) = 32
[pid  6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1, 
-1) = 1
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00ec50) = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00f000) = 0
[pid  6726] ioctl(24, USBDEVFS_IOCTL, 0x2aaaac009300) = 0
[pid  6726] ioctl(23, 0x4122, 0x4800000000000000) = 0
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00ec50) = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00f000) = 0
[pid  6726] ioctl(24, USBDEVFS_IOCTL, 0x2aaaac009300) = 0
[pid  6726] ioctl(23, 0x4122, 0x4800000000000000) = 0
[pid  6726] read(22, 
"\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\325\303\345$\0"..., 128) = 32
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1, 
-1) = 1
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] read(22, 
"\1\0\0\0\0\201\377\377\tb\245F\0\0\0\0\272G+&\0\0\0\0\1"..., 128) = 32
[pid  6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1, 
-1) = 1
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00ec50) = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00f000) = 0
[pid  6726] ioctl(24, USBDEVFS_IOCTL, 0x2aaaac009300) = 0
[pid  6726] ioctl(23, 0x4122, 0x4800000000000000) = 0
[pid  6726] read(22, 
"\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\242\343p\'\0\0"..., 128) = 32
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00ec50) = 0
[pid  6726] ioctl(23, 0x4122, 0x2aaaac00f000) = 0
[pid  6726] ioctl(24, USBDEVFS_IOCTL, 0x2aaaac009300) = 0
[pid  6726] ioctl(23, 0x4122, 0x4800000000000000) = 0
[pid  6726] read(22, 0x41801bf0, 128)   = -1 EAGAIN (Resource temporarily 
unavailable)
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1, 
-1) = 1
[pid  6726] ioctl(23, 0x4122, 0x3)      = 0
[pid  6726] ioctl(23, 0x4122, 0x45b82)  = 0
[pid  6726] ioctl(23, 0x4122, 0)        = 0
[pid  6726] read(22, 
"\1\0\0\0\377\377\377\377\tb\245F\0\0\0\0\211g\266(\0\0"..., 128) = 32
[pid  6726] poll([{fd=22, events=POLLIN|POLLERR|POLLNVAL, revents=POLLIN}], 1, 
-1) = 1
....

It was spinning in this poll loop at a -very- fast rate...i.e., there
was no waiting in the 'poll()' call in strace.... The even weirder part?
PID 6726 didn't exist on my system.

I 'kill -15'd gnome-power-manager and restarted it by hand and it seems
to be ok now.  and strace of that process shows the much more expected
scenario of poll actually pausing a few seconds each through.

Given the strace output of the badly behaving process shows several
-EAGAIN returns (only one posted here, but there are several in the full
screen dump..sorry, didn't save it to a file, i'm cutting from my xterm
back buffer), I'm guessing something wasn't getting cleared from the
poll loop.. but that's just wild speculation.

I know it's not much to go on, but it was keeping my cpu from running
completely idle and thus made my cpu run hot all day.

If it happens again, I'll run some more straces and post those.  Sorry I
can't give any more info now.

** Affects: gnome-power-manager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
gnome-power-manager using between 2% and 10% of cpu.
https://bugs.launchpad.net/bugs/127868
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

Reply via email to