From: rick@microway.com
To: "Huang Ying" <ying.huang@intel.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: Wed, 24 Aug 2011 18:18:33 -0400 [thread overview]
Message-ID: <cf5a31c38191654364bd281df6cb81e0.squirrel@www.microway.com> (raw)
In-Reply-To: <4E547B0F.6000001@intel.com>
Hi Huang,
The original system needs to ship to our customer ASAP. Disabling ghes is
sufficient for the time being for that. As such, I have set up an
identical system as a temporary master for another cluster to continue
this testing.
I have applied your patch. Here is the output of dmesg | grep GHES so far:
[ 9.272198] GHES: gar mapped: 0, 0xbf7b5ff0
[ 9.280782] GHES: gar mapped: 0, 0xbf7b6200
[ 9.285102] [Firmware Warn]: GHES: Poll interval is 0 for generic
hardware error source: 1, disabled.
I have the serial console activated and stress tests started back up.
I'll reply with the output once I get another panic.
Thanks!
Rick
> Hi, Rick,
>
> It appears that panic occurs in acpi_atomic_read. I think the most
> likely cause is that the acpi_generic_address is not pre-mapped. Can
> you try the patch attached?
>
> It will print registers mapped and accessed. To use it, run the
> following command line before workload.
>
> dmesg | grep GHES
>
> Then try to find something like
>
> GHES: gar accessed: x, xxxx
>
> in kernel log when panic occurs.
>
> Best Regards,
> Huang Ying
>
>
next prev parent reply other threads:[~2011-08-24 22:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 21:51 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 [this message]
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
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=cf5a31c38191654364bd281df6cb81e0.squirrel@www.microway.com \
--to=rick@microway.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=rjw@sisk.pl \
--cc=ying.huang@intel.com \
/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
all inboxes | Powered by JetHome®