[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50815a5ec08cdb713de8eaa92ad6e8b3.squirrel@www.microway.com>
Date: Fri, 2 Sep 2011 19:32:38 -0400
From: rick@...roway.com
To: "Huang Ying" <ying.huang@...el.com>
Cc: "Don Zickus" <dzickus@...hat.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Richard Houghton" <rhoughton@...roway.com>,
"ACPI Devel Mailing List" <linux-acpi@...r.kernel.org>,
"Len Brown" <lenb@...nel.org>,
"Matthew Garrett" <mjg59@...f.ucam.org>
Subject: Re: kernel oops and panic in acpi_atomic_read under 2.6.39.3. call
trace included
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!
Thanks,
Rick
> On 08/25/2011 11:47 PM, rick@...roway.com wrote:
>> Hi Huang,
>>
>> My new setup reproduced the panic. However I do not have any gar
>> accessed
>> messages on it. The gar mapped messages are in my previous email. Here
>> is the latest call trace. There is no GHES output prior to it:
>>
>
> That is wired. Can you try the patch attached? If my guessing is
> correct, there will be no panic, but something as follow will be in dmesg:
>
> ACPI atomic read mem: addr 0xxxxx mapped to 0
>
> Best Regards,
> Huang Ying
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists