From: Huang Ying <ying.huang@intel.com>
To: Pavel Ivanov <paivanof@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.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, 05 Sep 2011 10:05:42 +0800 [thread overview]
Message-ID: <4E642E76.4010309@intel.com> (raw)
In-Reply-To: <CAG1a4rtXhK-TtgayUDBK34kB2rEHUSN_6ZEX2B6Zg2-GprwCEA@mail.gmail.com>
On 09/03/2011 10:44 AM, Pavel Ivanov wrote:
> On Mon, Aug 29, 2011 at 1:37 AM, Huang Ying <ying.huang@intel.com> wrote:
>> On 08/27/2011 11:28 AM, Pavel Ivanov wrote:
>>> Also I noticed there's another suspicious message in dmesg and it was
>>> there earlier too (although it's not shown on console):
>>>
>>> GHES: Failed to enable APEI firmware first mode
>>>
>>> Is it bad? What does it mean?
>>
>> Maybe this has been fixed, please this patch,
>>
>> https://lkml.org/lkml/2011/8/11/297
>
> Yes, this patch indeed fixed this failure message. It's now replaced by
>
> GHES: APEI firmware first mode is enabled by WHEA _OSC.
>
> Can I ask you another question: what does the following message mean?
>
> [Firmware Warn]: GHES: Poll interval is 0 for generic hardware error
> source: 1, disabled.
This means:
The generic hardware error source with ID 1 is notified by poll, that
is, Linux should poll the specified address to check whether there is
hardware error report from hardware. But the poll interval specified by
firmware is "0". I think this should be a firmware error, and disabled
it. I think maybe you can contact firmware vendor to fix this.
Best Regards,
Huang Ying
prev parent reply other threads:[~2011-09-05 2:05 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
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 [this message]
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=4E642E76.4010309@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