Re: battery status events (RE: Kernel 2.6.13 repeated ACPI events?)

[Jan De Luyck <lkml-gY0FE6dpLprYtjvyW6yDsg@public.gmane.org>]

On Wednesday 07 September 2005 22:10, Brown, Len wrote:
> 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.

Ah, okay. I was under the impression that they should only be shown whenever 
there was an actual 'state' change, like battery is flat, is being charged, 
power is unplugged, not for the change of the charge level itself.

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

There is indeed klaptopdaemon running which does monitoring of the battery 
levens.

> Did this not happen on this box with earlier kernels?

I have no idea anymore when it started, but it wasn't there on a certain 
earlier kernel - but then i'm talking pre 2.6.7 era. I just didn't bother 
reporting it earlier, since I attributed it to a faulty dsdt line or so. I've 
read that ACER laptops have their share of bad dsdt's, that's why I didn't 
really bother - it works, it's just a tad annoying.
>
> Do the /proc/acpi/battery* files look sane --
> is the status really changing?

Yups, charge levels :)

Thanks, 

Jan

-- 
Food for thought is no substitute for the real thing.
		-- Walt Kelly, "Potluck Pogo"


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf