From: Huang Ying <ying.huang@intel.com>
To: "rick@microway.com" <rick@microway.com>
Cc: Don Zickus <dzickus@redhat.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Houghton <rhoughton@microway.com>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: kernel oops and panic in acpi_atomic_read under 2.6.39.3. call trace included
Date: Mon, 05 Sep 2011 10:50:04 +0800 [thread overview]
Message-ID: <4E6438DC.4010007@intel.com> (raw)
In-Reply-To: <50815a5ec08cdb713de8eaa92ad6e8b3.squirrel@www.microway.com>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
On 09/03/2011 07:32 AM, rick@microway.com wrote:
> Hi Huang,
>
> Sorry for the delay in my response. Hurricane Irene delayed our testing a
> bit.
>
> I had to switch the 5620 CPUS I had for 5670s. After 4 days of running
> (it was usually about 2 before) I finally got this output in dmesg:
>
> [337296.365930] GHES: gar accessed: 0, 0xbf7b9370
> [337296.365936] ACPI atomic read mem: addr 0xbf7b9370 mapped to
> ffffc90013ee8370
>
> It is not mapped to 0 as expected, but it didn't crash now!
But I don't think this patch fixed the issue. Maybe just hided the
issue. Do you have time to try the new patch attached?
Best Regards,
Huang Ying
[-- Attachment #2: dbg_ghes.patch --]
[-- Type: text/x-patch, Size: 1213 bytes --]
---
drivers/acpi/apei/ghes.c | 6 ++++++
drivers/acpi/atomicio.c | 2 ++
2 files changed, 8 insertions(+)
--- a/drivers/acpi/apei/ghes.c
+++ b/drivers/acpi/apei/ghes.c
@@ -299,6 +299,9 @@ static struct ghes *ghes_new(struct acpi
return ERR_PTR(-ENOMEM);
ghes->generic = generic;
rc = acpi_pre_map_gar(&generic->error_status_address);
+ pr_info(GHES_PFX "gar mapped: %d, %#llx\n",
+ generic->error_status_address.space_id,
+ generic->error_status_address.address);
if (rc)
goto err_free;
error_block_length = generic->error_block_length;
@@ -398,6 +401,9 @@ static int ghes_read_estatus(struct ghes
u32 len;
int rc;
+ pr_err(GHES_PFX "gar accessed: %d, %#llx\n",
+ g->error_status_address.space_id,
+ g->error_status_address.address);
rc = acpi_atomic_read(&buf_paddr, &g->error_status_address);
if (rc) {
if (!silent && printk_ratelimit())
--- a/drivers/acpi/atomicio.c
+++ b/drivers/acpi/atomicio.c
@@ -270,6 +270,8 @@ static int acpi_atomic_read_mem(u64 padd
rcu_read_lock();
addr = __acpi_ioremap_fast(paddr, width);
+ if (!addr)
+ panic("ACPI atomic read mem: addr %#llx is not mapped!\n", paddr);
switch (width) {
case 8:
*val = readb(addr);
next prev parent reply other threads:[~2011-09-05 2:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 21:51 kernel oops and panic in acpi_atomic_read under 2.6.39.3. call trace included Rick Warner
2011-08-18 7:47 ` Rafael J. Wysocki
2011-08-18 21:43 ` Rafael J. Wysocki
2011-08-22 14:42 ` rick
2011-08-22 18:47 ` Rafael J. Wysocki
2011-08-22 20:51 ` Rick Warner
2011-08-22 21:13 ` Rafael J. Wysocki
2011-08-23 17:16 ` rick
2011-08-23 17:14 ` Don Zickus
2011-08-23 17:24 ` rick
2011-08-24 4:16 ` Huang Ying
2011-08-24 22:18 ` rick
2011-08-25 15:47 ` rick
2011-08-26 0:34 ` Huang Ying
2011-09-02 23:32 ` rick
2011-09-05 2:50 ` Huang Ying [this message]
2011-09-15 18:35 ` rick
2011-09-16 0:20 ` 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=4E6438DC.4010007@intel.com \
--to=ying.huang@intel.com \
--cc=dzickus@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rhoughton@microway.com \
--cc=rick@microway.com \
--cc=rjw@sisk.pl \
/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