Date: Sat, 14 Jan 2006 14:06:29 +0100
From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@redhat.com>, Philipp Rumpf <prumpf@gmail.com>,
       Con Kolivas <kernel@kolivas.org>, ck list <ck@vds.kolivas.org>,
       linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: 2.6.15-ck1
Message-ID: <20060114130629.GJ3945@suse.de>
References: <200601041200.03593.kernel@kolivas.org> <20060104190554.GG10592@redhat.com> <e5bb8d810601131942r53712423kbd924757195f398b@mail.gmail.com> <20060114044152.GA3127@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060114044152.GA3127@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1156
Lines: 27

On Fri, Jan 13 2006, Dave Jones wrote:
> On Fri, Jan 13, 2006 at 09:42:26PM -0600, Philipp Rumpf wrote:
>  > Out of curiosity, why didn't you do the monitoring using
>  > /proc/acpi/battery/.../{state,info} (while running off battery)?  I
>  > think that should have much finer granularity, and avoid various
>  > capacitors that might be in the way and explain the effect you
>  > noticed.
> 
> ACPI battery reporting seems hit-or-miss at times.
> Sometimes it seems to not update for ages, and then suddenly
> there's a burst when suddenly 5% of the battery drains in
> seconds.   As an overall 'how much battery is left' thing it seems
> ok, but I don't trust it for accurate measurements of power drain.
> 
> Whether this is a firmware deficiency causing us not to see
> regular interrupts, or a problem with the acpi parser I don't know.

Or could very well be a problem with your battery.

-- 
Jens Axboe

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