From: Oliver Neukum <oliver@neukum.org>
To: Pavel Machek <pavel@ucw.cz>
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: Sun, 24 May 2009 23:02:55 +0200 [thread overview]
Message-ID: <200905242302.55640.oliver@neukum.org> (raw)
In-Reply-To: <20090523094518.GB8782@elf.ucw.cz>
Am Samstag, 23. Mai 2009 11:45:18 schrieb Pavel Machek:
> suspend.sf.net, program s2both :-).
Cool. What happens if you crash after unfreezing user space but before you
declare the image invalid?
Regards
Oliver
next prev parent reply other threads:[~2009-05-24 21:02 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 ` [linux-pm] [RFC] why do we need run disk sync before entering?S3 Pavel Machek
2009-05-23 9:05 ` Oliver Neukum
2009-05-23 9:45 ` Pavel Machek
2009-05-24 21:02 ` Oliver Neukum [this message]
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=200905242302.55640.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--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