Bug 175025
Summary: | 100% CPU usage by kacpid if hald running | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jordan Schwarz <flightline1836> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED WORKSFORME | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | acpi-bugzilla, pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-07 22:36:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jordan Schwarz
2005-12-05 19:36:37 UTC
Is this a laptop? I wonder if it's polling the battery. Does booting with acpi_serialize help ? I booted with acpi_serialize, and that seemed to make my problem go away. Thanks a lot! Yes, this is on a laptop (Gateway 450ROG). Is the fix to this problem to boot with acpi_serialize from now on, or is there something else I should be doing instead? "I'm sorry, Dave..." Looks like I misspoke in my earlier comment. I have now determined the following: I turned hald and apmd off and acpid on. Turning hald off gets rid of the CPU usage problem. When hald is running (even if acpid isn't), acpi_serialize does *not* stop the CPU usage problem. So, my rather primitive guess is that there's some bad interaction going on between the hal daemon and kacpid. I've got hal-0.5.2-2. So, for now, my CPU usage problem is fixed, although I'm not sure why hal is misbehaving. Thanks for your help! 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. Thank you. I've upgraded to 2.6.15, and I can't seem to duplicate this problem anymore. So, at least from my standpoint, it's fixed. Good job! |