From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Len Brown <lenb@kernel.org>, "Brown, Len" <len.brown@intel.com>,
"Moore, Robert" <robert.moore@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: acpi_ex_system_memory_space_handler oops
Date: Fri, 14 Aug 2009 10:40:33 +0300 [thread overview]
Message-ID: <20090814074033.GA3046@localdomain.by> (raw)
In-Reply-To: <1250217283.2987.16.camel@minggr.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]
On (08/14/09 10:34), Lin Ming wrote:
> Hi, Sergey
>
Hi Lin,
> Could you please help to locate the line of code that causes oops, as
> below?
>
According to EIP, acpi_ex_system_memory_space_handler+0x75
0x0000023f <acpi_ex_system_memory_space_handler+94>: call 0x240 <acpi_ex_system_memory_space_handler+95>
0x00000244 <acpi_ex_system_memory_space_handler+99>: mov $0x3004,%eax
0x00000249 <acpi_ex_system_memory_space_handler+104>: add $0x10,%esp
0x0000024c <acpi_ex_system_memory_space_handler+107>: jmp 0x3f5 <acpi_ex_system_memory_space_handler+532>
0x00000251 <acpi_ex_system_memory_space_handler+112>: mov $0x1,%eax
0x00000256 <acpi_ex_system_memory_space_handler+117>: mov 0x8(%ebx),%edx <<
0x00000259 <acpi_ex_system_memory_space_handler+120>: mov %edx,-0x28(%ebp)
0x0000025c <acpi_ex_system_memory_space_handler+123>: cmp %edx,-0x14(%ebp)
which I belive is (marked with __):
/*
* Does the request fit into the cached memory mapping?
* Is 1) Address below the current mapping? OR
* 2) Address beyond the current mapping?
*/
if ((__ address __ < mem_info->mapped_physical_address) ||
(((acpi_integer) address + length) > ((acpi_integer)
mem_info->
mapped_physical_address +
mem_info->mapped_length))) {
> 1. Compile the kernel with debug info
> Kernel menuconfig -> Kernel hacking -> Compile the kernel with debug info
>
> 2. Retest until it oops, here you get the address of code that causes oops.
> addr2line -e vmlinux <the address>
>
Sure, will try.
Sergey
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]
next prev parent reply other threads:[~2009-08-14 7:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 20:10 acpi_ex_system_memory_space_handler oops Sergey Senozhatsky
2009-08-12 21:46 ` Rafael J. Wysocki
2009-08-13 0:18 ` Len Brown
2009-08-13 8:34 ` Sergey Senozhatsky
2009-08-13 9:53 ` Sergey Senozhatsky
2009-08-13 11:02 ` Sergey Senozhatsky
2009-08-13 12:46 ` Sergey Senozhatsky
2009-08-14 2:34 ` Lin Ming
2009-08-14 7:40 ` Sergey Senozhatsky [this message]
2009-08-14 7:53 ` Sergey Senozhatsky
2009-08-14 9:12 ` Sergey Senozhatsky
2009-08-14 9:38 ` Sergey Senozhatsky
2009-08-14 12:48 ` Sergey Senozhatsky
2009-08-13 13:43 ` Sergey Senozhatsky
2009-08-17 8:43 ` Lin Ming
2009-08-17 11:30 ` Sergey Senozhatsky
2009-08-17 13:22 ` Lin Ming
2009-08-18 7:13 ` Sergey Senozhatsky
2009-08-18 7:18 ` Lin Ming
2009-08-18 7:45 ` Sergey Senozhatsky
2009-08-18 8:00 ` Sergey Senozhatsky
2009-08-27 7:52 ` Sergey Senozhatsky
2009-08-27 7:59 ` Lin Ming
2009-08-27 8:29 ` Sergey Senozhatsky
2009-08-27 8:44 ` Lin Ming
2009-08-27 9:05 ` Sergey Senozhatsky
2009-08-31 21:12 ` Sergey Senozhatsky
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=20090814074033.GA3046@localdomain.by \
--to=sergey.senozhatsky@gmail.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@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