public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: "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: Tue, 18 Aug 2009 15:18:35 +0800	[thread overview]
Message-ID: <1250579915.13743.8.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20090818071359.GA3713@localdomain.by>

On Tue, 2009-08-18 at 15:13 +0800, Sergey Senozhatsky wrote:
> On (08/17/09 21:22), Lin Ming wrote:
> > > rc6-git2
> > > 25 successful reboots.
> > >
> > > I'll need some more time to test against rc5.
> > >
> > > /*should I also test DSDT in case region-debug.patch fixed the problem?*/
> > 
> > Yes, please also help to test the custome DSDT.
> > region-debug.patch is just a debug patch.
> > We need to root cause the problem clearly and then work out a clean solution.
> > 
> 
> Hi, Lin
> Looks like DSDT didn't solve the problem (oops on 4th reboot).
> 
> So:
> region-debug.patch	+
> DSDT			-
> 
> /* Is that possible? */

Yes, that is possible. 
The same aml method is re-entered when interpreter lock is released.
So you still see AE_ALREADY_EXISTS error with the custom DSDT, right?

Thanks for the info, I'll continue to look at this issue.
And would you please test the region-debug.patch multiple times to
verify if it really fixes the bug?

Thanks,
Lin Ming


  reply	other threads:[~2009-08-18  7:23 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
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 [this message]
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=1250579915.13743.8.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=len.brown@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox