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
Date: Sat, 14 Jan 2006 14:06:29 +0100 [thread overview]
Message-ID: <20060114130629.GJ3945@suse.de> (raw)
In-Reply-To: <20060114044152.GA3127@redhat.com>
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
next prev parent reply other threads:[~2006-01-14 13:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 1:00 2.6.15-ck1 Con Kolivas
2006-01-04 19:05 ` 2.6.15-ck1 Dave Jones
2006-01-04 19:57 ` 2.6.15-ck1 Dave Jones
2006-01-04 20:33 ` 2.6.15-ck1 Arjan van de Ven
2006-01-04 21:22 ` 2.6.15-ck1 Dave Jones
2006-01-04 21:40 ` [ck] 2.6.15-ck1 Radoslaw Szkodzinski
2006-01-05 0:12 ` 2.6.15-ck1 Con Kolivas
2006-01-05 0:27 ` 2.6.15-ck1 Dave Jones
2006-01-05 0:49 ` 2.6.15-ck1 Con Kolivas
2006-01-05 1:14 ` 2.6.15-ck1 Dave Jones
2006-01-05 1:22 ` 2.6.15-ck1 Andi Kleen
2006-01-05 1:36 ` 2.6.15-ck1 Con Kolivas
2006-01-05 6:04 ` 2.6.15-ck1 Dave Jones
2006-01-05 6:42 ` 2.6.15-ck1 Vojtech Pavlik
2006-01-05 6:55 ` [ck] 2.6.15-ck1 Con Kolivas
2006-01-05 15:19 ` 2.6.15-ck1 Andi Kleen
2006-01-05 16:30 ` 2.6.15-ck1 Vojtech Pavlik
2006-01-05 16:39 ` 2.6.15-ck1 Andi Kleen
2006-01-05 17:13 ` 2.6.15-ck1 Dmitry Torokhov
2006-01-05 17:28 ` 2.6.15-ck1 Andi Kleen
2006-01-05 1:50 ` 2.6.15-ck1 Tony Lindgren
2006-01-04 23:10 ` 2.6.15-ck1 Con Kolivas
2006-01-05 1:57 ` 2.6.15-ck1 Tony Lindgren
2006-01-05 18:47 ` [ck] 2.6.15-ck1 Kevin Radloff
2006-01-12 18:51 ` Daniel Petrini
2006-01-04 20:38 ` 2.6.15-ck1 Grant Coady
2006-01-04 20:56 ` 2.6.15-ck1 Dave Jones
2006-01-12 22:11 ` 2.6.15-ck1 Adam Belay
2006-01-12 23:03 ` 2.6.15-ck1 Dave Jones
2006-01-13 0:42 ` 2.6.15-ck1 Adam Belay
2006-01-13 0:46 ` 2.6.15-ck1 Dave Jones
2006-01-16 20:28 ` 2.6.15-ck1 Ben Slusky
2006-01-14 3:42 ` 2.6.15-ck1 Philipp Rumpf
2006-01-14 4:41 ` 2.6.15-ck1 Dave Jones
2006-01-14 13:06 ` Jens Axboe [this message]
2006-01-05 17:58 ` 2.6.15-ck1 Tomasz Torcz
2006-01-05 23:22 ` 2.6.15-ck1 Con Kolivas
2006-01-07 13:16 ` 2.6.15-ck1 Tomasz Torcz
[not found] ` <9268368b0601131119n639c345cgcf2a5dadd7cb423c@mail.gmail.com>
2006-01-14 20:54 ` 2.6.15-ck1 Tomasz Torcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060114130629.GJ3945@suse.de \
--to=axboe@suse.de \
--cc=ck@vds.kolivas.org \
--cc=davej@redhat.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prumpf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox