This bug happened for me on an Acer desktop machine: Veriton 7200 (mobo S81M, even after upgrading to latest bios revision: R01-F3).
The machine has Debian on its hard drive, and Debian's 2.6.18-6-686 doesn't have the problem. Debian's 2.6.24-etchnhalf.1-686 _does_ have the problem. It's very repeatable by running burnP6 or burnK7. yacpi hangs until burnK7 is stopped and the temp comes down, while kacpi_notify uses lots of CPU... Debian's 2.6.25 backport (linux-image-2.6.25-2-68 2.6.25-6~bpo40+1) doesn't have the problem, so that's what I'm going to run here. Intrepid's i386 Desktop alpha 4 (kernel 2.6.26-5.15-generic) doesn't have the problem. I don't think I've tried Hardy. (The machine's CDROM drive door is stuck closed, and it doesn't boot from its USB1.1 ports. I booted intrepid by copying vmlinuz and initrd.gz to the HD, and loading them with GRUB, with iso-scan/filename=... Whoever though of and implemented iso-scan/filename=, nice job!) So this is a good sign that this bug is in fact going away in newer kernels. If I had found the problem with Intrepid's kernel, I would have followed up on bugzilla.kernel.org. -- runaway kacpi_notify https://bugs.launchpad.net/bugs/75174 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
