public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: kernel-testers@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@suse.cz>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: BISECTED: 2.6.29-rc2 regression: hibernation hang on eeepc-701
Date: Thu, 22 Jan 2009 11:30:41 +0000	[thread overview]
Message-ID: <497858E1.5070303@tuffmail.co.uk> (raw)
In-Reply-To: <9b2b86520901180345j434eacbdn7386958991ee50b@mail.gmail.com>

Alan Jenkins wrote:
> Hibernation hangs just after writing the image.  With s2disk I can see
> this from the console messages.  The same hang happens with kernel
> swsusp ('echo disk | sudo tee /sys/power/state'), and I can see that
> the image has been written from the HDD led.
>
> In either case, I can still hard-power-off and resume from hibernation.
>
> It doesn't hang if I use the shutdown method (either 'echo shutdown |
> sudo tee /sys/power/disk' or  's2disk -P "shutdown method=shutdown"').
>   

I've bisected this to commit 571ff7584bb9e05fca0eb79752ae55a46faf3a98. 
It doesn't revert cleanly from RC2.

I think it's distinct from the other two reported suspend regressions. 
I'm not using acpi-cpufreq, and the issue doesn't affect resume.

Alan


commit 571ff7584bb9e05fca0eb79752ae55a46faf3a98
Author: Rafael J. Wysocki <rjw@sisk.pl>
Date:   Wed Jan 7 13:05:05 2009 +0100

    PCI PM: Power-manage devices without drivers during suspend-resume

    PCI devices without drivers can be put into low power states during
    suspend with the help of pci_prepare_to_sleep() and prevented from
    generating wake-up events during resume with the help of
    pci_enable_wake().  However, it's better not to put bridges into
    low power states during suspend, because that might result in entire
    bus segments being powered off.

    Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
    Acked-by: Pavel Machek <pavel@suse.cz>
    Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

:040000 040000 6b6fb7bfa561583f14bdf55b084473dcf9cd1765
d72fbda87eff26db8f2574e868a793b79deb9f92 M      drivers

  parent reply	other threads:[~2009-01-22 11:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 11:45 2.6.29-rc2 regression: hibernation hang on eeepc-701 (method "platform" only) Alan Jenkins
2009-01-18 19:19 ` Alan Jenkins
2009-01-22 11:30 ` Alan Jenkins [this message]
2009-01-22 12:44   ` BISECTED: 2.6.29-rc2 regression: hibernation hang on eeepc-701 Rafael J. Wysocki
2009-01-22 13:23     ` Alan Jenkins
2009-01-22 22:05       ` Rafael J. Wysocki
2009-01-23  9:45         ` Alan Jenkins
2009-01-23 22:06           ` Rafael J. Wysocki
2009-01-24 11:15             ` Alan Jenkins
2009-01-24 13:43               ` Rafael J. Wysocki
2009-01-24 14:01                 ` Alan Jenkins
2009-01-24 14:24                   ` Alan Jenkins
2009-01-24 16:27               ` Jesse Barnes
2009-01-24 20:53                 ` 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=497858E1.5070303@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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