LKML Archive on
help / color / mirror / Atom feed
From: Alexey Starikovskiy <>
To: Meelis Roos <>
Cc: Linux Kernel list <>,
Subject: Re: 2.6.21-rc1: more ACPI errors (EC__)
Date: Sun, 04 Mar 2007 13:31:31 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.SOC.4.64.0702260842260.9705@math>

Meelis Roos wrote:
> I tested 2.6.21-rc1 on my laptop (IBM X20 with 440BX) and found two 
> problems:
> First, a seemingly harmless one - ACPI error messages during bootup:
> ACPI Exception (evregion-0420): AE_NOT_FOUND, Returned by Handler for [EmbeddedControl] [20070126]
> ACPI Exception (dswexec-0462): AE_NOT_FOUND, While resolving operands for [OpcodeName unavailable] [20070126]
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.ISA_.EC__.BAT0._STA] (Node d3c435e0), AE_NOT_FOUND
> ACPI Exception (evregion-0420): AE_NOT_FOUND, Returned by Handler for [EmbeddedControl] [20070126]
> ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.ISA_.EC__.AC__._PSR] (Node d3c43540), AE_NOT_FOUND
> ACPI Exception (ac-0095): AE_NOT_FOUND, Error reading AC Adapter state [20070126]
> And second, there were ACPI error messages about EC__ during shutdown. 
> These messages appeared, then the "acpi_power_off called" message 
> appeared, then it waited for about 5 seconds (this does not happen 
> normally) and then it succeeded shutting down. Captured a screenshot of 
> these messages, temporarily available at 
please take a look at 8066 bug and patches there.


  parent reply	other threads:[~2007-03-04 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 20:49 2.6.21-rc1: more ACPI errors (EC__) Meelis Roos
2007-02-28 22:14 ` Moore, Robert
2007-03-04 10:31 ` Alexey Starikovskiy [this message]
2007-03-08 15:48   ` Meelis Roos

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).