public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Oliver Neukum <oneukum@suse.de>,
	linux-pm@lists.linux-foundation.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: better oopsing when frozen
Date: Fri, 29 Jul 2011 22:27:54 +0200	[thread overview]
Message-ID: <201107292227.54948.rjw@sisk.pl> (raw)
In-Reply-To: <20110729195430.GB1720@ucw.cz>

On Friday, July 29, 2011, Pavel Machek wrote:
> 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.

This only applies to hibernation and only when we're going to restore
from the image the presumably hasn't been saved yet, right?

However, there's another problem I didn't think of before.  Namely,
we cannot thaw tasks before resuming devices in case we've already
suspended them, because that will defeat the very purpose of the
freezing in the first place.

Thanks,
Rafael

  parent reply	other threads:[~2011-07-29 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201107251043.19932.oneukum@suse.de>
2011-07-25 10:10 ` better oopsing when frozen Borislav Petkov
2011-07-26 22:24 ` Rafael J. Wysocki
     [not found] ` <201107270024.11194.rjw@sisk.pl>
2011-07-26 22:45   ` Andrew Morton
     [not found]   ` <20110726154502.14c7b51b.akpm@linux-foundation.org>
2011-07-27  9:21     ` Rafael J. Wysocki
     [not found]     ` <201107271121.21348.rjw@sisk.pl>
2011-07-27 10:23       ` Oliver Neukum
2011-07-29 19:54 ` Pavel Machek
     [not found] ` <20110729195430.GB1720@ucw.cz>
2011-07-29 20:27   ` Oliver Neukum
2011-07-29 20:27   ` Rafael J. Wysocki [this message]
2011-07-29 21:04     ` Oliver Neukum
     [not found]     ` <201107292304.10738.oliver@neukum.org>
2011-07-29 21:09       ` Rafael J. Wysocki
     [not found]       ` <201107292309.44877.rjw@sisk.pl>
2011-07-29 21:17         ` Oliver Neukum
     [not found]         ` <201107292317.42737.oliver@neukum.org>
2011-07-29 21:30           ` Rafael J. Wysocki
     [not found]   ` <201107292227.36424.oliver@neukum.org>
2011-07-29 20:29     ` Rafael J. Wysocki
2011-07-25  8:43 Oliver Neukum

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=201107292227.54948.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=oneukum@suse.de \
    --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