public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-pm@lists.linux-foundation.org,
	Zhang Rui <rui.zhang@intel.com>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: [linux-pm] [RFC] why do we need run disk sync before entering?S3
Date: Sat, 23 May 2009 10:50:18 +0200	[thread overview]
Message-ID: <20090523085018.GA8782@elf.ucw.cz> (raw)
In-Reply-To: <200905230959.23018.oliver@neukum.org>

On Sat 2009-05-23 09:59:22, Oliver Neukum wrote:
> Am Freitag, 22. Mai 2009 17:33:57 schrieb Pavel Machek:
> > > Take ACPI for example, ACPI defines two ACPI battery states, one is
> > > "low" and another is "critical".
> > > OS enters S3/S4 when battery is low, while it performs an emergency
> > > shutdown when battery is in critical state. (ACPI spec 3.0b 3.9.4)
> > > So I'm wondering if it's right to enter S3 when we know that the system
> > > may lost power at anytime.
> >
> > Well, battery only lasts like 30 hours in S3. So if you leave your
> > notebook unattended for 30 hours, you'll loose recent changes.
> 
> Even if the battery is very low you get 30 hours?

That will of course be less. 30 hours is really best case, on "good"
notebook.

What I was trying to point out is that even if you go into s3 with
machine fully charged, you'll loose your data after like 30 hours.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-05-23  8:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13  1:20 [RFC] why do we need run disk sync before entering S3 Zhang Rui
2009-05-13  2:01 ` [linux-pm] " Alan Stern
2009-05-13  8:03   ` Rafael J. Wysocki
2009-05-13  8:45     ` Pavel Machek
2009-05-13  8:53       ` Rafael J. Wysocki
2009-05-13  8:57         ` Pavel Machek
2009-05-13 14:06         ` Alan Stern
2009-05-13 14:16           ` Rafael J. Wysocki
2009-05-14  9:42             ` Pavel Machek
2009-05-15  1:00               ` Henrique de Moraes Holschuh
2009-05-15  9:08                 ` suspending machine from kernel (was Re: [linux-pm] [RFC] why do we need run disk sync before entering S3) Pavel Machek
2009-05-15 21:15                   ` Henrique de Moraes Holschuh
2009-05-15 14:36               ` [linux-pm] [RFC] why do we need run disk sync before entering S3 Rafael J. Wysocki
2009-05-18  7:25                 ` Zhang Rui
2009-05-22 15:33                   ` Pavel Machek
2009-05-23  7:59                     ` Oliver Neukum
2009-05-23  8:50                       ` Pavel Machek [this message]
2009-05-23  9:05                         ` [linux-pm] [RFC] why do we need run disk sync before entering?S3 Oliver Neukum
2009-05-23  9:45                           ` Pavel Machek
2009-05-24 21:02                             ` Oliver Neukum
2009-05-24 21:14                               ` Pavel Machek
2009-05-19  1:03     ` [RFC] why do we need run disk sync before entering S3 Nigel Cunningham

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=20090523085018.GA8782@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=oliver@neukum.org \
    --cc=rui.zhang@intel.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