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, 29 Aug 2011 09:15:26 +0800 [thread overview]
Message-ID: <4E5AE82E.6000807@intel.com> (raw)
In-Reply-To: <CAG1a4rtckCtpNjg9ApiLt4zQWArAu7N2ivoiMjueqYDRrr-G+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
Hi, Pavel,
On 08/27/2011 11:28 AM, Pavel Ivanov wrote:
> Huang,
>
> I can confirm that new patch got rid of the old error message but
> introduced a new one:
>
> ERST: Failed to get Error Log Address Range
Please try the attached patch to find why there is the error message.
> 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?
It means you may receive a unknown NMI without GHES error record for
some detected hardware error.
Best Regards,
Huang Ying
[-- Attachment #2: dbg_erst_erange.patch --]
[-- Type: text/x-patch, Size: 767 bytes --]
---
drivers/acpi/apei/erst.c | 3 +++
1 file changed, 3 insertions(+)
--- a/drivers/acpi/apei/erst.c
+++ b/drivers/acpi/apei/erst.c
@@ -387,14 +387,17 @@ static int erst_get_erange(struct erst_e
erst_exec_ctx_init(&ctx);
rc = apei_exec_run(&ctx, ACPI_ERST_GET_ERROR_RANGE);
+ pr_info(ERST_PFX "get erange: %d\n", rc);
if (rc)
return rc;
range->base = apei_exec_ctx_get_output(&ctx);
rc = apei_exec_run(&ctx, ACPI_ERST_GET_ERROR_LENGTH);
+ pr_info(ERST_PFX "get erange length: %d\n", rc);
if (rc)
return rc;
range->size = apei_exec_ctx_get_output(&ctx);
rc = apei_exec_run(&ctx, ACPI_ERST_GET_ERROR_ATTRIBUTES);
+ pr_info(ERST_PFX "get erange attributes: %d\n", rc);
if (rc)
return rc;
range->attr = apei_exec_ctx_get_output(&ctx);
next prev parent reply other threads:[~2011-08-29 1:15 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 [this message]
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=4E5AE82E.6000807@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