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: Thu, 27 Aug 2009 15:59:54 +0800 [thread overview]
Message-ID: <1251359994.3282.11.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <20090827075253.GB3536@localdomain.by>
On Thu, 2009-08-27 at 15:52 +0800, Sergey Senozhatsky wrote:
> On (08/18/09 15:18), Lin Ming wrote:
>
> Hello Lin,
>
> rc7-git5 (patched)
>
> [ 0.178628] ACPI: EC: Look up EC in DSDT
> [ 0.196480] ACPI: Interpreter enabled
> [ 0.196575] ACPI: (supports S0 S1 S3 S4 S5)
> [ 0.197184] ACPI: Using IOAPIC for interrupt routing
> [ 0.197352] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
> [ 0.203511] ACPI Error (dswload-0790): [PCFG] Namespace lookup failure, AE_ALREADY_EXISTS
> [ 0.203738] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog 20090521 psloop-227
> [ 0.203964] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.RBPE] (Node f7017678), AE_ALREADY_EXISTS
> [ 0.204256] ACPI: Marking method RBPE as Serialized because of AE_ALREADY_EXISTS error
> [ 0.204510] ACPI Error (psparse-0537): Method parse/execution failed [\_GPE._L01] (Node f701d198), AE_ALREADY_EXISTS
> [ 0.204803] ACPI: Marking method _L01 as Serialized because of AE_ALREADY_EXISTS error
> [ 0.205063] ACPI Exception: AE_ALREADY_EXISTS, while evaluating GPE method [_L01] 20090521 evgpe-568
Do you mean rc7-git5 sometime boot fails even with the patch applied?
>
>
> [...]
> + if (!(region_obj->region.node->flags & ANOBJ_TEMPORARY)) {
> + acpi_ex_exit_interpreter();
> + }
> [...]
> Does it explain successful boot with delay (vga=791, prink delay, etc.)?
Sorry, could you explain the question a bit more?
Lin Ming
>
>
> > And would you please test the region-debug.patch multiple times to
> > verify if it really fixes the bug?
> >
> rc7-git5 (nopatch)
> + -
>
> rc7-git5 (patched)
> 20+ reboots
>
> Sergey
next prev parent reply other threads:[~2009-08-27 8:04 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
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 [this message]
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=1251359994.3282.11.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