diff mbox

APEI: Can not request iomem region for GARs

Message ID 4E5AE82E.6000807@intel.com (mailing list archive)
State New, archived
Headers show

Commit Message

Huang, Ying Aug. 29, 2011, 1:15 a.m. UTC 
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

Comments

Huang, Ying Aug. 29, 2011, 5:22 a.m. UTC | #1 
On 08/29/2011 12:10 PM, Pavel Ivanov wrote:
> On Sun, Aug 28, 2011 at 9:15 PM, Huang Ying <ying.huang@intel.com> wrote:
>> 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.
> 
> dmesg after the patch is in attachment.

-ENOENT is returned for apei_exec_run(, ACPI_ERST_GET_ERROR_RANGE).
That is there is no instructions for mandatory action
ACPI_ERST_GET_ERROR_RANGE.  It should be a firmware bug, try raise it to
firmware vendor?

Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Pavel Ivanov Aug. 29, 2011, 2:43 p.m. UTC | #2 
On Mon, Aug 29, 2011 at 1:22 AM, Huang Ying <ying.huang@intel.com> wrote:
> -ENOENT is returned for apei_exec_run(, ACPI_ERST_GET_ERROR_RANGE).
> That is there is no instructions for mandatory action
> ACPI_ERST_GET_ERROR_RANGE.  It should be a firmware bug, try raise it to
> firmware vendor?

Could you please advise me on how should I do that? Do I need to
report this issue to my motherboard vendor (which is Asus)? If yes
then should it be via the standard technical support channel (like
http://vip.asus.com/eservice/techserv.aspx) or something more special?


Thank you,
Pavel
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Huang, Ying Aug. 30, 2011, 12:55 a.m. UTC | #3 
On 08/29/2011 10:43 PM, Pavel Ivanov wrote:
> On Mon, Aug 29, 2011 at 1:22 AM, Huang Ying <ying.huang@intel.com> wrote:
>> -ENOENT is returned for apei_exec_run(, ACPI_ERST_GET_ERROR_RANGE).
>> That is there is no instructions for mandatory action
>> ACPI_ERST_GET_ERROR_RANGE.  It should be a firmware bug, try raise it to
>> firmware vendor?
> 
> Could you please advise me on how should I do that? Do I need to
> report this issue to my motherboard vendor (which is Asus)? If yes
> then should it be via the standard technical support channel (like
> http://vip.asus.com/eservice/techserv.aspx) or something more special?

Sorry, I don't know how to do that too.

Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

---
 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);