All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: 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>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 1/1] PM: fix oops in suspend/hibernate code
Date: Thu, 06 Jan 2011 17:31:06 +0100	[thread overview]
Message-ID: <4D25EE4A.9010602@gmail.com> (raw)
In-Reply-To: <4D25E943.804@gmail.com>

On 01/06/2011 05:09 PM, Jiri Slaby wrote:
>>> --- a/kernel/power/nvs.c
>>> +++ b/kernel/power/nvs.c
>>> @@ -105,7 +105,7 @@ int suspend_nvs_alloc(void)
>>>  /**
>>>   *	suspend_nvs_save - save NVS memory regions
>>>   */
>>> -void suspend_nvs_save(void)
>>> +int suspend_nvs_save(void)
>>>  {
>>>  	struct nvs_page *entry;
>>>  
>>> @@ -114,8 +114,14 @@ void suspend_nvs_save(void)
>>>  	list_for_each_entry(entry, &nvs_list, node)
>>>  		if (entry->data) {
>>>  			entry->kaddr = ioremap(entry->phys_start, entry->size);
>>
>> I wonder what happens if you simply change the ioremap() here to
>> ioremap_nocache() without any other modifications?
> 
> ioremap *is* ioremap_nocache on x86. And that's the conflict it
> complains about I guess? Don't you mean ioremap_cache?

Using ioremap_cache indeed fixes the problem...

thanks,
-- 
js

  parent reply	other threads:[~2011-01-06 16:31 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24  0:58 mmotm 2010-12-23-16-58 uploaded akpm
2010-12-24  0:58 ` akpm
2010-12-24 12:15 ` Sedat Dilek
2010-12-24 12:15   ` Sedat Dilek
2010-12-24 13:04   ` Andrew Morton
2010-12-24 13:04     ` Andrew Morton
2010-12-24 17:52 ` [PATCH -mmotm] kptr_restrict: fix build when PRINTK not enabled Randy Dunlap
2010-12-24 17:52   ` Randy Dunlap
2010-12-27  2:13 ` mmotm 2010-12-23-16-58 uploaded Randy Dunlap
2010-12-27  2:13   ` Randy Dunlap
2011-01-04 13:40 ` suspend hangs at platform phase [was: mmotm 2010-12-23-16-58 uploaded] Jiri Slaby
2011-01-04 16:49   ` Jiri Slaby
2011-01-04 16:49   ` Jiri Slaby
2011-01-04 22:57     ` Rafael J. Wysocki
2011-01-04 22:57     ` Rafael J. Wysocki
2011-01-05 21:36       ` Jiri Slaby
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 22:46           ` Jiri Slaby
2011-01-05 23:28             ` Rafael J. Wysocki
2011-01-05 23:28             ` Rafael J. Wysocki
2011-01-06  9:18               ` [PATCH 1/1] PM: fix oops in suspend/hibernate code Jiri Slaby
2011-01-06  9:31                 ` Jiri Slaby
2011-01-06 15:57                 ` Rafael J. Wysocki
2011-01-06 15:57                 ` Rafael J. Wysocki
2011-01-06 16:09                   ` Jiri Slaby
2011-01-06 16:09                   ` Jiri Slaby
2011-01-06 16:31                     ` Jiri Slaby
2011-01-06 16:31                     ` Jiri Slaby [this message]
2011-01-06 16:38                     ` Rafael J. Wysocki
2011-01-06 16:38                     ` Rafael J. Wysocki
2011-01-06 21:01                       ` Len Brown
2011-01-06 21:01                       ` Len Brown
2011-01-06  9:24               ` suspend hangs at platform phase [was: mmotm 2010-12-23-16-58 uploaded] Jiri Slaby
2011-01-06  9:24               ` Jiri Slaby
2011-01-06 15:45                 ` Rafael J. Wysocki
2011-01-06 15:45                 ` Rafael J. Wysocki
2011-01-05 22:39         ` Rafael J. Wysocki
2011-01-06  8:27     ` ia64 build broken " Jiri Slaby
2011-01-06  8:31       ` [PATCH 1/1] ia64: fix build of ioremap_cache Jiri Slaby
2011-01-06 16:03         ` Len Brown
2011-01-06 16:21           ` Jiri Slaby
2011-01-06  8:27     ` ia64 build broken [was: mmotm 2010-12-23-16-58 uploaded] Jiri Slaby
2011-01-04 13:40 ` suspend hangs at platform phase " Jiri Slaby

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=4D25EE4A.9010602@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=lenb@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.