Messages in this thread Patch in this message | | | Date | Wed, 24 Aug 2011 12:16:15 +0800 | From | Huang Ying <> | Subject | Re: kernel oops and panic in acpi_atomic_read under 2.6.39.3. call trace included |
| |
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
--- drivers/acpi/apei/ghes.c | 6 ++++++ 1 file changed, 6 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, 0x%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_info(GHES_PFX "gar accessed: %d, 0x%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()) | |