> ... 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 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
