[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1250217283.2987.16.camel@minggr.sh.intel.com>
Date: Fri, 14 Aug 2009 10:34:43 +0800
From: Lin Ming <ming.m.lin@...el.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Len Brown <lenb@...nel.org>, "Brown, Len" <len.brown@...el.com>,
"Moore, Robert" <robert.moore@...el.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: acpi_ex_system_memory_space_handler oops
On Thu, 2009-08-13 at 20:46 +0800, Sergey Senozhatsky wrote:
> > Looks like regression is in the current RC.
>
> Looks like it isn't. On 17th reboot rc5-git0 crashed.
> (I'll recompile and try more.)
> I think bisecting here is kind of senseless. You never know how much reboots you need.
> Simple delay (like vga=791) - and everything is ok. We need to come up with something
> more clever, I guess.
>
> Any thougths?
Hi, Sergey
Could you please help to locate the line of code that causes oops, as
below?
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>
Thanks,
Lin Ming
>
> Sergey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists