Re: APEI: ERST table in ACPI NVS not supported

[Chen Gong <gong.chen@linux.intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On Tue, Jan 29, 2013 at 10:08:11AM -0800, Max Asbock wrote:
> Date: Tue, 29 Jan 2013 10:08:11 -0800
> From: Max Asbock <masbock@linux.vnet.ibm.com>
> To: gong.chen@linux.intel.com, ying.huang@intel.com
> CC: linux-acpi@vger.kernel.org, masbock@linux.vnet.ibm.com
> Subject: APEI: ERST table in ACPI NVS not supported
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130108
>  Thunderbird/10.0.12
> 
> Hi,
> 
> 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?

> thanks,
> Max
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]