Comment 25 for bug 99356

I went ahead and followed this troubleshooting recommendation for
completeness, but it didn't solve the problem.

After playing around with it some more, I have figured out that it has to do
with interaction with the acpi interface. Here is my reasoning....

1. acpi=off in the kernel parameters seems stops the bug.
2. when acpi is on, acpi is off and hal is off, the bug stops.
3. if either hal or acpid is on when acpi is enabled into the kernel, the
bug is present (both acpid and hal interact with the kernel's acpi
interface)
4. When I simply "cat /proc/acpi/battery/BAT0/status" the bug uncovers
itself and is reproducable.

This indicates that the bug is definitely in the kernel acpi interface when
ever there is some sort of interaction with it. Since hal and acpid both
poll/interact with it, the bug is produced.

Do you have any idea as to why the kernel acpi drivers/modules/interface is
doing this when I poll anything in /proc/acpi ? If we fix that, then I
think we will fix this bug.

For what it's worth, I'm a Senior Linux SA, however I don't have much
experience with the ACPI kernel interface, so any advanced requests you may
have would be okay.

-Rick