On 02/04/2013 01:20 AM, Chen Gong wrote:
On Tue, Jan 29, 2013 at 10:08:11AM -0800, Max Asbock wrote:
we have systems that declare the memory range for ERST in ACPI NVS.
Because ACPI NVS is marked 'busy' by e820_reserve_resources() the
call to request_mem_region(erst_erange.base, erst_erange.size, "APEI
ERST") made from erst_init() fails and we get:
ERST: Can not request iomem region<0x 7e91f000-0x
7e920c00> for ERST.
I did notice that quite some effort was made to add code to avoid
resource conflicts between APEI and ACPI NVS. But ERST still goes
straight to request_mem_region() which is bound to fail. I am
assuming this should go through apei_resources_request() instead or
I am missing something?
If my understanding is right, after ERST resource is requested via
apei_resources_request and when requesting error log address range,
you meet an NVS conflict, right?
If so, NVS must be excluded. But I'm afraid if error range is
separated into two parts thus some errors will be lost. Would you
please paste errage address range and conflicted NVS range?
ACPI NVS is:
[ 0.000000] BIOS-e820: [mem 0x000000007e6a5000-0x000000007ebc5fff]
ACPI NVS
ERST erange is:
0x7e91f000-0x7e920c00
which is a single range entirely within ACPI NVS.
thanks,
Max
--
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
