From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Len Brown <len.brown@intel.com>, Jack Steiner <steiner@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: Resume from Memory very slow on 2.6.37+
Date: Mon, 17 Jan 2011 23:49:06 +0100 [thread overview]
Message-ID: <201101172349.06993.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTimBEnKTuR5aQyXvpZX8grQPw1eCaVgP-k9yBXhv@mail.gmail.com>
On Monday, January 17, 2011, Jeff Chua wrote:
> I've just tried the recent linux git pull
> (e78bf5e6cbe837daa6ab628a5f679548742994d3) and suspend-to-memory
> works, but resume takes a very long time (30 seconds doing nothing).
>
> Bisected and it says first bad commit is
> ca9b600be38c73b7d25acfb8b7e4e9a9e941d881
Hmm. That's probably because acpi_os_unmap_memory() does the
synchronize_rcu(), but I have no idea why it might cause a problem to
occur in suspend_nvs_free().
What happens if you replace the acpi_os_map_memory() in
suspend_nvs_save() with ioremap_cache() and the acpi_os_unmap_memory() in
suspend_nvs_free() with iounmap() ?
Rafael
> commit ca9b600be38c73b7d25acfb8b7e4e9a9e941d881
> Author: Rafael J. Wysocki <rjw@sisk.pl>
> Date: Fri Jan 7 01:45:58 2011 +0100
>
> ACPI / PM: Make suspend_nvs_save() use acpi_os_map_memory()
>
> It turns out that the NVS memory region that suspend_nvs_save()
> attempts to map has been already mapped by acpi_os_map_memory(), so
> suspend_nvs_save() should better use acpi_os_map_memory() for mapping
> memory to avoid conflicts.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> Signed-off-by: Len Brown <len.brown@intel.com>
>
>
> I reverted the following commits, and system resumes without waiting ...
>
> commit ca9b600be38c73b7d25acfb8b7e4e9a9e941d881
> Author: Rafael J. Wysocki <rjw@sisk.pl>
> Date: Fri Jan 7 01:45:58 2011 +0100
>
> ACPI / PM: Make suspend_nvs_save() use acpi_os_map_memory()
>
> commit 6d5bbf00d251cc73223a71422d69e069dc2e0b8d
> Author: Len Brown <len.brown@intel.com>
> Date: Fri Jan 7 01:46:40 2011 +0100
>
> ACPI: Use ioremap_cache()
>
> commit d146df18c13d16e321efa8ef9b57c95c3bec1722
> Author: Rafael J. Wysocki <rjw@sisk.pl>
> Date: Fri Jan 7 01:44:28 2011 +0100
>
> ACPI / PM: Update file information and the list of includes in nvs.c
>
>
> Notebook is Lenovo X201s. 8GB RAM. 256GB SSD.
>
>
> Thanks,
> Jeff
>
>
next prev parent reply other threads:[~2011-01-17 22:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimBEnKTuR5aQyXvpZX8grQPw1eCaVgP-k9yBXhv@mail.gmail.com>
2011-01-17 18:55 ` Resume from Memory very slow on 2.6.37+ Brown, Len
2011-01-17 22:49 ` Rafael J. Wysocki [this message]
2011-01-18 0:14 ` [linux-pm] " Rafael J. Wysocki
2011-01-18 1:14 ` Jeff Chua
2011-01-18 1:35 ` Rafael J. Wysocki
2011-01-18 5:19 ` Jeff Chua
2011-01-18 20:20 ` Rafael J. Wysocki
2011-01-19 1:20 ` Jeff Chua
2011-01-19 1:38 ` Rafael J. Wysocki
2011-01-19 14:13 ` Jeff Chua
2011-01-19 21:19 ` Rafael J. Wysocki
2011-01-19 21:27 ` [1/2] ACPI: Introduce acpi_os_ioremap() Rafael J. Wysocki
2011-01-19 21:27 ` [2/2] ACPI / PM: Call suspend_nvs_free() earlier during resume Rafael J. Wysocki
2011-01-20 1:21 ` [linux-pm] Resume from Memory very slow on 2.6.37+ Jeff Chua
2011-01-20 1:50 ` 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=201101172349.06993.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jeff.chua.linux@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=steiner@sgi.com \
--cc=torvalds@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