kacpid consumes most CPU and make huge ACPI log with the same info (only Ubuntu 4.10 is fine)

Bug #127135 reported by Diogo
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,

Since, at least ubuntu Dapper Drake, I've got a problem with kacpid, it consumes most of my cpu. I've reported this bug before in a existent bug, but no feedback from it. Beside that it creates a acpi log with GB of the same information. There are many reports of this bug all over the internet, including here in the launchpad. But if you need any more info, fell free to ask.
I've tested ubuntu 4.10 and the problem isn't there. I've tested fedora 7 and the problem isn't there too.I've tested an gutsy development cd and there is the bug again. I was wondering where is the support you claim? Are you gonna really fix this bug any day?

Best regards,
Diogo

Revision history for this message
Paul Dufresne (paulduf) wrote :

Writing down harvested info:

KACPID is a kernel process.
The package acpid, is the user side package that discuss with KACPID.
One can wonder what happens if acpid is not installed.

Bug #75174 is about the same, but have been made on acpi, that is
just a package giving information about acpi, so seems to me it is on
a bad package. Bug #75174 is triggered only when CPU temperature become too hot.

Upstream kernel bug 3679 http://bugzilla.kernel.org/show_bug.cgi?id=3679
was similar too, but got closed because of missing info. However this one was trigger on a resume rather than high temperature CPU.

Upstream kernel bug 6944 http://bugzilla.kernel.org/show_bug.cgi?id=6944 was interesting too, but was marked invalid. I note following comment there: "I dont know what ive done. but it seems to be behaving now. i installed quite a number of applications and it seems to be working, like gnome-power-manager, acpid and laptop-mode-tools and many others not sure which one actually worked" Sure missing acpid seems very dangerous.

Although acpid seems a reasonable package to put this bug, it seems no contact information is associated with it, making all bugs there not much listen too. Seems the normal place to put this is on linux-source-[version affected].

Revision history for this message
Paul Dufresne (paulduf) wrote :

Other note to myself: Someone said somewhere that removing powernowd package had resolved the problem.

Most say that booting with NO-ACPI (must verify syntax) fix this, but at think one said no.

Revision history for this message
Paul Dufresne (paulduf) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux-source-2.6.22 (Gutsy kernel).

Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "sudo dmidecode > dmidecode.log" and attach the resulting file "dmidecode.log" to this bug report.
5. Extract a relevant piece of acpi log and attach it to this bug report as acpi.log

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Not enough information to proceed. Please reopen you you can provide the information Paul requested.

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.