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