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:
signature.asc
Description: Digital signature
