public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@linux-foundation.org>, Greg KH <greg@kroah.com>
Cc: linux-pm@lists.linux-foundation.org,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: 2.6.25-mm1: suspend-to-disk warning, resume failure
Date: Fri, 18 Apr 2008 22:38:44 +0200	[thread overview]
Message-ID: <200804182238.45512.rjw@sisk.pl> (raw)
In-Reply-To: <200804182214.14376.rjw@sisk.pl>

On Friday, 18 of April 2008, Rafael J. Wysocki wrote:
> On Friday, 18 of April 2008, Rafael J. Wysocki wrote:
> > On Friday, 18 of April 2008, Alan Stern wrote:
> > > On Thu, 17 Apr 2008, Andrew Morton wrote:
> > > 
> > > > But this:
> > > > 
> > > > <cold boot>
> > > > <suspend-to-ram>
> > > > <resume-from-ram>
> > > > <suspend-to-disk>
> > > > <resume-from-disk>
> > > > 
> > > > hangs at the end of resume-from-disk.
> > > > 
> > > > 
> > > > During the suspend-to-disk I saw:
> > > > 
> > > > ipw2200: Radio Frequency Kill Switch is On:
> > > > Kill switch must be turned off for wireless networking to work.
> > > > PM: Device usb1 failed to (unknown PM event): error -113
> > > > PM: Device usb2 failed to (unknown PM event): error -113
> > > > PM: Device usb3 failed to (unknown PM event): error -113
> > > > PM: Device usb4 failed to (unknown PM event): error -113
> > > 
> > > These -113 errors can be ignored.  They are fallout from the recent 
> > > conversion of the driver core's suspend/resume API.  Matching changes 
> > > have not yet been added to the USB core.
> > > 
> > > The "(unknown PM event)" strings look like a bug, though.
> > 
> > Yes, it does.
> > 
> > I'm trying to figure this out.
> 
> This particular problem should be fixed by the appended patch.

The following patch is also necessary to make hibernation work as documented
in pm.h.

Thanks,
Rafael

---
From: Rafael J. Wysocki <rjw@sisk.pl>

Make hibernation work as documented in include/linux/pm.h .

In pm.h it is documented that device_power_up() and device_resume()
will be called with PMSG_RECOVER if the creation of a hibernation
image fails or the restoration of memory contents from a
hibernation image fails.  Otherwise, it should be called either
with PMSG_THAW or with PMSG_RESTORE, depending on the context.
Make that happen.

Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
 kernel/power/disk.c |    8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

Index: linux-2.6/kernel/power/disk.c
===================================================================
--- linux-2.6.orig/kernel/power/disk.c
+++ linux-2.6/kernel/power/disk.c
@@ -225,7 +225,8 @@ static int create_image(int platform_mod
 	/* NOTE:  device_power_up() is just a resume() for devices
 	 * that suspended with irqs off ... no overall powerup.
 	 */
-	device_power_up(in_suspend ? PMSG_RECOVER : PMSG_RESTORE);
+	device_power_up(in_suspend ?
+		(error ? PMSG_RECOVER : PMSG_THAW) : PMSG_RESTORE);
  Enable_irqs:
 	local_irq_enable();
 	device_pm_unlock();
@@ -282,7 +283,8 @@ int hibernation_snapshot(int platform_mo
  Finish:
 	platform_finish(platform_mode);
  Resume_devices:
-	device_resume(in_suspend ? PMSG_RECOVER : PMSG_RESTORE);
+	device_resume(in_suspend ?
+		(error ? PMSG_RECOVER : PMSG_THAW) : PMSG_RESTORE);
  Resume_console:
 	resume_console();
  Close:
@@ -332,7 +334,7 @@ static int resume_target_kernel(void)
 	swsusp_free();
 	restore_processor_state();
 	touch_softlockup_watchdog();
-	device_power_up(PMSG_THAW);
+	device_power_up(PMSG_RECOVER);
  Enable_irqs:
 	local_irq_enable();
 	device_pm_unlock();

  reply	other threads:[~2008-04-18 20:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080417222125.99e807b6.akpm@linux-foundation.org>
2008-04-18  9:40 ` 2.6.25-mm1: suspend-to-disk warning, resume failure Pavel Machek
2008-04-18 11:08 ` Pavel Machek
     [not found] ` <20080418110440.GA5455@elf.ucw.cz>
2008-04-18 11:33   ` Andrew Morton
2008-04-18 15:19 ` Alan Stern
2008-04-18 16:05   ` Greg KH
2008-04-18 16:45     ` Alan Stern
2008-04-18 16:54       ` Greg KH
2008-04-18 18:47   ` Rafael J. Wysocki
2008-04-18 20:14     ` Rafael J. Wysocki
2008-04-18 20:38       ` Rafael J. Wysocki [this message]
2008-04-18 21:23         ` Greg KH
2008-04-18 21:30           ` Rafael J. Wysocki
2008-04-18 22:16             ` Greg KH
2008-04-18 23:16               ` Rafael J. Wysocki
2008-04-28 23:29                 ` Greg KH
     [not found]                 ` <20080428232917.GA4171@kroah.com>
2008-04-29 20:20                   ` Rafael J. Wysocki
2008-04-18 23:19         ` Pavel Machek
2008-04-18  5:21 Andrew Morton

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=200804182238.45512.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-usb@vger.kernel.org \
    /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