From: Len Brown <lenb@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jiri Slaby <jirislaby@gmail.com>, Jiri Slaby <jslaby@suse.cz>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH 1/1] PM: fix oops in suspend/hibernate code
Date: Thu, 06 Jan 2011 16:01:12 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1101061554130.17728@x980> (raw)
In-Reply-To: <201101061738.14581.rjw@sisk.pl>
> ... My theory is that we have mapped the
> same area already using ioremap_cache() and now we're trying to map it again
> using ioremap_nocache(), hence the conflict. I need to confirm this.
On my test box.
BIOS-e820: 0000000077626000 - 0000000077632000 (ACPI NVS)
yet there are at least two tables (FACS and SSDT)
that live in that region, and there are several
run-time AML memory opregions residing in that range too.
So the region has already been mapped by acpi_os_map_memory()
(now using ioremap_cache()) before suspend_nvs_save() runs.
Is there a reason that suspend_nvs_save()
requires a non-cached mapping?
cheers,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2011-01-06 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201012240132.oBO1W8Ub022207@imap1.linux-foundation.org>
[not found] ` <4D232352.2030809@gmail.com>
[not found] ` <4D234F8E.7080102@gmail.com>
2011-01-04 22:57 ` suspend hangs at platform phase [was: mmotm 2010-12-23-16-58 uploaded] Rafael J. Wysocki
2011-01-05 21:36 ` Jiri Slaby
2011-01-05 22:39 ` Rafael J. Wysocki
2011-01-05 22:46 ` Jiri Slaby
2011-01-05 23:28 ` Rafael J. Wysocki
2011-01-06 9:24 ` Jiri Slaby
2011-01-06 15:45 ` Rafael J. Wysocki
[not found] ` <1294305504-5787-1-git-send-email-jslaby@suse.cz>
2011-01-06 15:57 ` [PATCH 1/1] PM: fix oops in suspend/hibernate code Rafael J. Wysocki
2011-01-06 16:09 ` Jiri Slaby
2011-01-06 16:31 ` Jiri Slaby
2011-01-06 16:38 ` Rafael J. Wysocki
2011-01-06 21:01 ` Len Brown [this message]
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=alpine.LFD.2.02.1101061554130.17728@x980 \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg59@srcf.ucam.org \
--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