Strange acpi thing with battery

maxxer <[email protected]>
Newsgroups gmane.comp.desktop.xfce.goodies.devel
Organization ginger Gentoo Linux
Message-ID <20050921101517.GA15472@ginger>
Hi

I'm having a little problem with XFCE battery monitor and my acpi.
I've searched around on google and so but I couldn't find someone
experiencing the same problem of mine. When I select the battery monitor
for inclusion in the xfce bar in acpi_listen I get signals 80 and 81
caught at least every second, and in the meantime in acpid logfile 

-
[Tue Sep 20 21:45:01 2005] received event "processor CPU1 00000080
00000000"
[Tue Sep 20 21:45:01 2005] notifying client 8141[1000:100]
[Tue Sep 20 21:45:01 2005] executing action "/etc/acpi/default.sh
processor CPU1 00000080 000000
00"
[Tue Sep 20 21:45:01 2005] BEGIN HANDLER MESSAGES
[Tue Sep 20 21:45:02 2005] END HANDLER MESSAGES
[Tue Sep 20 21:45:02 2005] action exited with status 0
[Tue Sep 20 21:45:02 2005] completed event "processor CPU1 00000080
00000000"
[Tue Sep 20 21:45:02 2005] received event "processor CPU1 00000081
00000000"
[Tue Sep 20 21:45:02 2005] notifying client 8141[1000:100]
[Tue Sep 20 21:45:02 2005] executing action "/etc/acpi/default.sh
processor CPU1 00000081 000000
00"
[Tue Sep 20 21:45:02 2005] BEGIN HANDLER MESSAGES
[Tue Sep 20 21:45:02 2005] END HANDLER MESSAGES
[Tue Sep 20 21:45:02 2005] action exited with status 0
[Tue Sep 20 21:45:02 2005] completed event "processor CPU1 00000081
00000000"

-

I thought it was a X problem, or an acpi problem, but I noticed it only
happens when I have the battery monitor in the bar.
I didn't manage to understand the meaning of that two messages, so I'm
asking here if this behaviour is normal, and in case how can I avoid it
since it's flooding my logs.
My pc is an Asus a2k laptop, running 2.6.13.1 custom kernel (but it's
going this way since at least 2.6.10).

I hope someone can give me a hint.
Many thanks
Maxxer
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.