From: Tejun Heo <tj@kernel.org>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: linux-ide@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Long delays while hibernating
Date: Sat, 26 Dec 2009 10:26:55 +0900 [thread overview]
Message-ID: <4B35665F.20001@kernel.org> (raw)
In-Reply-To: <74fd948d0912251010y2bba5bd6nf7aa3a34a7946c31@mail.gmail.com>
(cc'ing Rafael)
On 12/26/2009 03:10 AM, Pedro Ribeiro wrote:
>> Oh... Can you please try this one then?
>
> Sorry, still hangs with this patch :(
>
> This only happens in hibernation... suspend is fine.
Hmmm... the patch does apply to both suspend and hibernation. Rafael,
Pedro's ThinkPad T400 burns cpu cycle for 30secs on "Atomic
copy/restore" step of hibernation if the ultrabay is powered off. The
original report can be found at...
http://thread.gmane.org/gmane.linux.ide/44190
Please note that it's with TuxOnIce patches. Anyways, ata_piix on
certain configurations have similar issues where after the OS is done
suspending and powering off the piix controller, the BIOS tries to
access it and ends up burning cpu cycles which can be worked around by
leaving the controller on after suspend. Applying the same workaround
didn't resolve the issue. Do you know what can make cpu burn for
30secs on the atomic copy/restore step?
Pedro, can you please try to reproduce the problem without TuxOnIce
patches?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-12-26 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 3:50 Long delays while hibernating Pedro Ribeiro
2009-12-23 7:47 ` Tejun Heo
2009-12-23 13:50 ` Pedro Ribeiro
2009-12-24 7:45 ` Tejun Heo
2009-12-24 14:34 ` Pedro Ribeiro
2009-12-24 15:59 ` Pedro Ribeiro
2009-12-25 14:56 ` Tejun Heo
2009-12-25 18:10 ` Pedro Ribeiro
2009-12-26 1:26 ` Tejun Heo [this message]
2009-12-26 16:32 ` Pedro Ribeiro
2009-12-26 21:21 ` Rafael J. Wysocki
2009-12-26 22:35 ` Pedro Ribeiro
2009-12-27 14:09 ` Rafael J. Wysocki
2009-12-27 17:59 ` Pedro Ribeiro
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=4B35665F.20001@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=pedrib@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).