From patchwork Mon Aug 29 01:15:26 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Huang, Ying" X-Patchwork-Id: 1106002 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter2.kernel.org (8.14.4/8.14.4) with ESMTP id p7T1Fe0s011042 for ; Mon, 29 Aug 2011 01:15:40 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751502Ab1H2BP3 (ORCPT ); Sun, 28 Aug 2011 21:15:29 -0400 Received: from mga01.intel.com ([192.55.52.88]:63557 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750951Ab1H2BP2 (ORCPT ); Sun, 28 Aug 2011 21:15:28 -0400 Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 28 Aug 2011 18:15:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.68,294,1312182000"; d="scan'208";a="45804801" Received: from yhuang-dev.sh.intel.com (HELO [10.239.13.105]) ([10.239.13.105]) by fmsmga002.fm.intel.com with ESMTP; 28 Aug 2011 18:15:27 -0700 Message-ID: <4E5AE82E.6000807@intel.com> Date: Mon, 29 Aug 2011 09:15:26 +0800 From: Huang Ying User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110820 Iceowl/1.0b2 Icedove/3.1.12 MIME-Version: 1.0 To: Pavel Ivanov CC: Bjorn Helgaas , linux-kernel , "linux-acpi@vger.kernel.org" Subject: Re: APEI: Can not request iomem region for GARs References: <4E520149.3010802@intel.com> <4E571D66.1070302@intel.com> In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.6 (demeter2.kernel.org [140.211.167.43]); Mon, 29 Aug 2011 01:15:40 +0000 (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 --- 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);