>-----Original Message-----
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED] On Behalf Of Jan De Luyck
>Sent: Monday, September 05, 2005 9:17 AM
>To: linux-kernel@vger.kernel.org
>Subject: Re: Kernel 2.6.13 repeated ACPI events?
>
>I'm seeing repeated ACPI events too, but of the battery kind:
>
>[Mon Sep  5 15:13:52 2005] received event "battery BAT2 
>00000080 00000001"
>[Mon Sep  5 15:13:52 2005] completed event "battery BAT2 
>00000080 00000001"
>[Mon Sep  5 15:14:53 2005] received event "battery BAT1 
>00000080 00000001"
>[Mon Sep  5 15:14:53 2005] completed event "battery BAT1 
>00000080 00000001"
>[Mon Sep  5 15:14:53 2005] received event "battery BAT2 
>00000080 00000001"
>[Mon Sep  5 15:14:53 2005] completed event "battery BAT2 
>00000080 00000001"
>[Mon Sep  5 15:15:55 2005] received event "battery BAT1 
>00000080 00000001"
>[Mon Sep  5 15:15:55 2005] completed event "battery BAT1 
>00000080 00000001"
>[Mon Sep  5 15:15:55 2005] received event "battery BAT2 
>00000080 00000001"
>[Mon Sep  5 15:15:55 2005] completed event "battery BAT2 
>00000080 00000001"
>
>going on forever and ever...
>
>Jan

The kernel doesn't created these messages -- presumably
they're from acpid or some other user-level daemon
that is monitoring /proc/acpi/event.  Unlikely that
logging these events is necessary...

Event 0x80 on the battery device is a "Battery Status Changed"
which you'd expect to see when plugging/charging/discharging
a battery.  How frequent they are depends on the rate,
the battery and the firmware that is talking to it.

Is there a GUI or something reading the battery status files?
Do these events stop when running in text mode?

Did this not happen on this box with earlier kernels?

Do the /proc/acpi/battery* files look sane --
is the status really changing?

thanks,
-Len
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to