From: Brian Perkins <bperk-7GtV0IYKK74tA4QZiFxQkx2eb7JE58TQ@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Excessive S3 battery drain on R32
Date: Thu, 18 Dec 2003 00:31:07 -0500 [thread overview]
Message-ID: <3FE13B9B.4000808@throb.netspace.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720C3C-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Yu, Luming wrote:
> How do you know this should be more like 24 hrs?
That's what it gets using apm and what it got under windows. (some time ago)
> How long did your battery can last if suspend in single user mode?
I just had it sleep for about 9 hours and at that rate it would have
drained in 24 hours. This is a bit faster than I remember in the past,
but much better than 9-12 hours. Batteries do go bad after all.
> Maybe some devices haven't been in proper D state.
> Could you figure out which one?
I'll look into this. Any hints on what to look for?
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-18 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 3:37 Excessive S3 battery drain on R32 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C3C-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-18 5:31 ` Brian Perkins [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 7:48 Yu, Luming
2003-12-17 18:15 Brian Perkins
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=3FE13B9B.4000808@throb.netspace.org \
--to=bperk-7gtv0iykk74ta4qzifxqkx2eb7je58tq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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