All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.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:34:43 +0800	[thread overview]
Message-ID: <1250217283.2987.16.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20090813124647.GA19195@localdomain.by>

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


  reply	other threads:[~2009-08-14  2:38 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 [this message]
2009-08-14  7:40       ` Sergey Senozhatsky
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=1250217283.2987.16.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.moore@intel.com \
    --cc=sergey.senozhatsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.