From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Firefox/1.0.2 Fedora/1.0.2-3
Description of problem:
hal daemon runs fine when I only have the main battery installed -- but if I have the second battery in the laptop, hal eats lots of CPU.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot laptop with two batteries
2. Start hal daemon
3. Watch CPU usage skyrocket
Expected Results: Hal shouldn't eat so much CPU.
Gateway 450rog laptop (centrino), up to date BIOS, /proc seems correct...
See also bug 154481, which has to do with the second battery...
Since bug 154481 suggests that this also happens with battstat applet, this is
not a hal bug. FYI both hal and the battstat applet polls the /proc-files for
battery status only every thirty seconds.
Reassigning to kernel.
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (18.104.22.168). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
Do two batteries still consume CPU with 2.6.15 or FC5-T2?
If yes, how about the latest -mm tree, or 2.6.15 plus the latest
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.