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>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] PM: acquire device locks prior to suspending
Date: Fri, 14 Dec 2007 02:05:59 +0100	[thread overview]
Message-ID: <200712140205.59942.rjw@sisk.pl> (raw)
In-Reply-To: <20071213162224.ea5aec25.akpm@linux-foundation.org>

On Friday, 14 of December 2007, Andrew Morton wrote:
> On Fri, 14 Dec 2007 01:08:37 +0100
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> 
> > On Thursday, 13 of December 2007, Rafael J. Wysocki wrote:
> > > On Thursday, 13 of December 2007, Andrew Morton wrote:
> > > > On Fri, 21 Sep 2007 15:37:40 -0400 (EDT) Alan Stern <stern@rowland.harvard.edu> wrote:
> > > > 
> > > > > This patch (as994) reorganizes the way suspend and resume
> > > > > notifications are sent to drivers.  The major changes are that now the
> > > > > PM core acquires every device semaphore before calling the methods,
> > > > > and calls to device_add() during suspends will fail.
> > > > 
> > > > Causes my t61p to deadlock during suspend-to-RAM.  Really late - the little
> > > > moon symbol has started to flash but the LCD is still powered and the
> > > > cursor still blinks.  Only a poweroff restores control.
> > > 
> > > Most probably, one of the drivers or a CPU hotplug notifier unregisters a
> > > device during suspend (wrong).
> > > 
> > > Please boot with no_console_suspend and check if the box survives (with this
> > > patch applied):
> > > 
> > > # echo 8 > /proc/sys/kernel/printk
> > > # echo processors > /sys/power/pm_test
> > > # echo mem > /sys/power/state
> > > 
> > > If it doesn't, you can try 
> > > 
> > > # echo platform > /sys/power/pm_test
> > > # echo mem > /sys/power/state
> > > 
> > > and
> > > 
> > > # echo devices > /sys/power/pm_test
> > > # echo mem > /sys/power/state
> > 
> > Ah, that won't work, because git-acpi-build-fix.patch killed
> > /sys/power/pm_test altogether.  Sorry.
> 
> I was wondering..
> 
> What's going on with git-acpi-build-fix.patch anyway?  Is there
> something different we should do?

Yes.  I've sent a patch to you and Len, here:
http://marc.info/?l=linux-acpi&m=119758974523027&w=2

  reply	other threads:[~2007-12-14  1:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 19:37 [PATCH] PM: acquire device locks prior to suspending Alan Stern
2007-09-21 20:16 ` Rafael J. Wysocki
2007-10-10 20:42 ` patch pm-acquire-device-locks-prior-to-suspending.patch added to gregkh-2.6 tree gregkh
2007-12-13  7:42 ` [PATCH] PM: acquire device locks prior to suspending Andrew Morton
2007-12-13 16:02   ` Alan Stern
2007-12-13 21:38     ` Andrew Morton
2007-12-14 15:32       ` Alan Stern
2007-12-13 16:58   ` Rafael J. Wysocki
2007-12-14  0:08     ` Rafael J. Wysocki
2007-12-14  0:22       ` Andrew Morton
2007-12-14  1:05         ` Rafael J. Wysocki [this message]
2007-12-14  7:20     ` Andrew Morton
2007-12-14  7:31     ` Andrew Morton
2007-12-14 16:49       ` Alan Stern
2007-12-15  0:17         ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2007-12-17 22:50 Alan Stern

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=200712140205.59942.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-pm@lists.linux-foundation.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