From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Rick Warner <rick@microway.com>
Cc: 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, 22 Aug 2011 23:13:26 +0200 [thread overview]
Message-ID: <201108222313.26769.rjw@sisk.pl> (raw)
In-Reply-To: <201108221651.35654.rick@microway.com>
Hi,
On Monday, August 22, 2011, Rick Warner wrote:
...
> Hi Rafael,
>
> Thanks for the off-list help in getting you this info.
>
> I had already rebuilt the kernel using the change I mentioned earlier (test on
> !&g->error_status_address) since the call trace I got.
>
> I luckily still had a copy of the kernel and modules I built previously using
> just your patch, so I undid my change to the ghes.c source, leaving just your
> patch but not mine so it would match the ghes.ko module I ran on. This is the
> output of gdb on that ghes.ko now:
>
> (gdb) l *ghes_read_estatus+0x38
> 0x258 is in ghes_read_estatus (drivers/acpi/apei/ghes.c:296).
> warning: Source file is more recent than executable.
> 291 int rc;
> 292 if (!g)
> 293 return -EINVAL;
> 294
> 295 rc = acpi_atomic_read(&buf_paddr, &g->error_status_address);
> 296 if (rc) {
> 297 if (!silent && printk_ratelimit())
> 298 pr_warning(FW_WARN GHES_PFX
> 299 "Failed to read error status block address for hardware error source:
> %d.\n",
> 300 g->header.source_id);
>
> The warning about the source being newer is because of the reverted change in
> the ghes.c source mentioned above.
OK, since &buf_addr cannot be NULL, perhaps ghes is. Please check if the
appended patch makes a difference.
Thanks,
Rafael
---
drivers/acpi/apei/ghes.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
Index: linux/drivers/acpi/apei/ghes.c
===================================================================
--- linux.orig/drivers/acpi/apei/ghes.c
+++ linux/drivers/acpi/apei/ghes.c
@@ -393,11 +393,16 @@ static void ghes_copy_tofrom_phys(void *
static int ghes_read_estatus(struct ghes *ghes, int silent)
{
- struct acpi_hest_generic *g = ghes->generic;
+ struct acpi_hest_generic *g;
u64 buf_paddr;
u32 len;
int rc;
+ if (!ghes || !ghes->generic)
+ return -EINVAL;
+
+ g = ghes->generic;
+
rc = acpi_atomic_read(&buf_paddr, &g->error_status_address);
if (rc) {
if (!silent && printk_ratelimit())
next prev parent reply other threads:[~2011-08-22 21:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201108171751.51648.rick@microway.com>
2011-08-18 7:47 ` kernel oops and panic in acpi_atomic_read under 2.6.39.3. call trace included 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 [this message]
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
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=201108222313.26769.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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 \
/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