From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Oliver Neukum <oliver@neukum.org>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] better oopsing when frozen
Date: Fri, 29 Jul 2011 22:29:02 +0200 [thread overview]
Message-ID: <201107292229.02402.rjw@sisk.pl> (raw)
In-Reply-To: <201107292227.36424.oliver@neukum.org>
On Friday, July 29, 2011, Oliver Neukum wrote:
> Am Freitag, 29. Juli 2011, 21:54:30 schrieb Pavel Machek:
> > On Mon 2011-07-25 10:43:19, Oliver Neukum wrote:
> > > Hi Rafael,
> > >
> > > I had a problem with the kernel stopping the machine forever because I got an
> > > oops while tasks were frozen. It seems to me that we should thaw when this
> > > happens. How about this approach?
> >
> > Danger, Will Robinson. You must not write to the filesystems after
> > hibernation started. By thawing, you may do just that.
> >
> > It should be safe to thaw as long as final suspend signature is not
> > on disk and will not be written there.
>
> Yes. But this applies only if I use kernel-space hibernation, doesn't it?
> So I need a second flag for the signature being written. Any other problem?
Yes, please see my reply to Pavel.
Thanks,
Rafael
next prev parent reply other threads:[~2011-07-29 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 8:43 Oliver Neukum
2011-07-25 10:10 ` Borislav Petkov
2011-07-26 22:24 ` Rafael J. Wysocki
2011-07-26 22:45 ` Andrew Morton
2011-07-27 9:21 ` Rafael J. Wysocki
2011-07-27 10:23 ` Oliver Neukum
2011-07-29 19:54 ` [linux-pm] " Pavel Machek
2011-07-29 20:27 ` Oliver Neukum
2011-07-29 20:29 ` Rafael J. Wysocki [this message]
2011-07-29 20:27 ` Rafael J. Wysocki
2011-07-29 21:04 ` Oliver Neukum
2011-07-29 21:09 ` Rafael J. Wysocki
2011-07-29 21:17 ` Oliver Neukum
2011-07-29 21:30 ` Rafael J. Wysocki
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=201107292229.02402.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=oliver@neukum.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome