From: Huang Ying <ying.huang@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Pavel Ivanov <paivanof@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: APEI: Can not request iomem region for GARs
Date: Mon, 22 Aug 2011 13:43:42 +0800 [thread overview]
Message-ID: <4E51EC8E.7040304@intel.com> (raw)
In-Reply-To: <CAErSpo4FfBoGDUquoLNsJ9=z-M-x6NQgP8xJL_VqEXpsL2H5PA@mail.gmail.com>
On 08/20/2011 05:48 AM, Bjorn Helgaas wrote:
> On Tue, Aug 16, 2011 at 9:43 PM, Pavel Ivanov <paivanof@gmail.com> wrote:
>> Ever since I switched from kernel 2.6.38 to 3.0 and later versions I
>> always get the following error message on each boot:
>>
>> [ 2.844242] APEI: Can not request iomem region
>> <00000000bf7b522a-00000000bf7b522c> for GARs.
>>
>> If it was only in dmesg I wouldn't even notice it. But it's always
>> printed on the console which is kind of annoying.
>> I don't quite understand what this message is about and couldn't find
>> anything on the internet. Does this message mean some error that I
>> could fix? If no, is there any way I can suppress it (besides lowering
>> the error level of messages printed on console, of course)?
>
> [+cc Huang Ying, APEI author]
>
> BIOS-e820: 00000000bf79e000 - 00000000bf7d0000 (ACPI NVS)
> APEI: Can not request iomem region <00000000bf7b522a-00000000bf7b522c> for GARs.
>
> This register is in the ACPI NVS region, which is type E820_NVS (not
> E820_RESERVED), so e820_reserve_resources() reserves it as
> IORESOURCE_BUSY. My guess is that Huang tested this on machines where
> the EINJ/ERST registers are in "reserved" regions, not ACPI NVS
> regions. The "reserved" regions are not marked IORESOURCE_BUSY.
>
> Huang, when you fix this, please include something like the following
> (mangled) patch so the error message is more consistent with other
> resource messages.
The patch looks good. Can you resubmit it with changelog?
> Could you also remove the ERST/EINJ/HEST "Table is not found"
> messages? As far as I can tell, these tables are optional, and
> printing the message is confusing to users, e.g.,
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/599715
Yes. This seems confusing to them. I will change this.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2011-08-22 5:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 3:43 APEI: Can not request iomem region for GARs Pavel Ivanov
2011-08-19 21:48 ` Bjorn Helgaas
2011-08-22 5:43 ` Huang Ying [this message]
2011-08-22 7:12 ` Huang Ying
2011-08-22 16:45 ` Bjorn Helgaas
2011-08-22 21:04 ` Yinghai Lu
2011-08-23 0:32 ` Huang Ying
2011-08-25 2:45 ` Pavel Ivanov
2011-08-26 4:13 ` Huang Ying
2011-08-26 13:43 ` Bjorn Helgaas
2011-08-29 1:27 ` Huang Ying
2011-08-29 14:48 ` Bjorn Helgaas
2011-08-30 0:57 ` Huang Ying
2011-08-27 3:28 ` Pavel Ivanov
2011-08-29 1:15 ` Huang Ying
2011-08-29 4:10 ` Pavel Ivanov
2011-08-29 5:22 ` Huang Ying
2011-08-29 14:43 ` Pavel Ivanov
2011-08-30 0:55 ` Huang Ying
2011-08-29 5:37 ` Huang Ying
2011-09-03 2:44 ` Pavel Ivanov
2011-09-05 2:05 ` Huang Ying
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=4E51EC8E.7040304@intel.com \
--to=ying.huang@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paivanof@gmail.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