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
Date: Tue, 29 Jan 2013 10:08:11 -0800 [thread overview]
Message-ID: <5108100B.9040907@linux.vnet.ibm.com> (raw)
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?
thanks,
Max
next reply other threads:[~2013-01-29 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:08 Max Asbock [this message]
2013-02-04 9:20 ` APEI: ERST table in ACPI NVS not supported Chen Gong
2013-02-04 17:06 ` Max Asbock
2013-02-05 1:56 ` Chen Gong
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=5108100B.9040907@linux.vnet.ibm.com \
--to=masbock@linux.vnet.ibm.com \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).