From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: better oopsing when frozen Date: Fri, 29 Jul 2011 23:30:09 +0200 Message-ID: <201107292330.09797.rjw@sisk.pl> References: <201107251043.19932.oneukum@suse.de> <201107292309.44877.rjw@sisk.pl> <201107292317.42737.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201107292317.42737.oliver@neukum.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Oliver Neukum Cc: Andrew Morton , linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org List-Id: linux-pm@vger.kernel.org On Friday, July 29, 2011, Oliver Neukum wrote: > Am Freitag, 29. Juli 2011, 23:09:44 schrieb Rafael J. Wysocki: > > On Friday, July 29, 2011, Oliver Neukum wrote: > > > Am Freitag, 29. Juli 2011, 22:27:54 schrieb Rafael J. Wysocki: > > > > 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. > > > > > > That purpose is already defeated. The machine cannot be deader than dead. > > > > OK, so what exactly is the purpose of the thawing, then? > > We may be lucky enough to get the oops written out to disk. The oops may happen > in a driver rarely used and be late in the sequence. OK, so is there any guarantee that we won't corrupt things this way? Rafael