Re: Battery status reading problems

[Nils Faerber <nils-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>]

Am Di, 2003-09-23 um 14.14 schrieb Bas Mevissen:
> Alan Cox wrote:
> > Several vendors implement the actual battery reading logic as an SMI
> > trap and disable interrupts during their slow chat with the battery.
> > There isnt much anyone can do about that bit alas (except read it a lot
> > less often)
> OK. I'll check with Win XP and Linux with latest ACPI CA to see if I 
> notice a speed difference between Windows and Linux. The XP battery 
> indicator detects AC/battery power changes in a few seconds, so I expect 
> the batery status polling in Windows to occur at the same speed.
> (or does the AC/battery power work with an event? The my assumption 
> won't hold then)

I could very well accept CPU load.
I would even accept delays, given they are small.
But I experienced kernel hangs, i.e. short periods of no I/O activity at
all when querying the battery status. And even that could be acceptable.
What was not acceptable were very bizarre happenings that lokked like
lost interrupts!? Events that did not cause the reaction they should
have. Less severe were lost mouse events but more severe was packet loss
on network.

So for me it looks more like a bug in the ACPI code than just a
performnce issue or hardware misdesign.
The other thing that leads to this assumption is that so many of us see
this happening, with various notebooks by various manufacturers. It is
not bound to certain or limited number of "bad" machines.

> Bas.
CU
  nils faerber

-- 
kernel concepts          Tel: +49-271-771091-12
Dreisbachstr. 24         Fax: +49-271-771091-19
D-57250 Netphen          D1 : +49-170-2729106
--



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf