From: Sabrina Dubroca <sd@queasysnail.net>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: Lv Zheng <lv.zheng@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Bob Moore <robert.moore@intel.com>, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: ACPICA 20140214 auto-serialize weirds my machine...
Date: Fri, 14 Mar 2014 18:38:01 +0100 [thread overview]
Message-ID: <20140314173801.GA3755@kria> (raw)
In-Reply-To: <14866.1394813101@turing-police.cc.vt.edu>
Hi,
2014-03-14, 12:05:01 -0400, Valdis Kletnieks wrote:
> Surprisingly enough, this hasn't seemed to have bitten many Linux people yet,
> Google only finds a BSD thread (where the same ACPICA code is in use):
>
> http://comments.gmane.org/gmane.os.dragonfly-bsd.user/1817
I was about to report the same issue on a Dell Latitude D830. Boot
failure, flood of these messages:
ACPI Exception: AE_AML_MUTEX_ORDER, while evaluating GPE method [_L1C] (20140214/evgpe-580)
ACPI Error: Method parse/execution failed [\GPE._L1C] (Node f5e0c9a8), AE_AML_MUTEX_ORDER (20140214/psparse-536)
ACPI Error: Cannot acquire Mutex for method [SX30], current SyncLevel is too large (1) (20140214/dsmethod-362)
ACPI Exception: AE_AML_MUTEX_ORDER, while evaluating GPE method [_L1C] (20140214/evgpe-580)
With acpi_no_auto_serialize things look good.
Before I tried that option, a bisection led me to remove
"| AML_CREATE" from commit f56b05bd111b. That made the laptop boot,
things seemed okay, except for the battery not being detected: the
normal battery line was gone ("ACPI: Battery Slot [BAT0] (battery
present)") and there's this instead:
ACPI Error: Cannot acquire Mutex for method [SX45], current SyncLevel is too large (1) (20140214/dsmethod-362)
ACPI Error: Method parse/execution failed [\_SB_.BIF_] (Node f5c250d8), AE_AML_MUTEX_ORDER (20140214/psparse-536)
ACPI Error: Method parse/execution failed [\_SB_.BAT0._BIF] (Node f5c25168), AE_AML_MUTEX_ORDER (20140214/psparse-536)
ACPI Exception: AE_AML_MUTEX_ORDER, Evaluating _BIF (20140214/battery-416)
--
Sabrina
next prev parent reply other threads:[~2014-03-14 17:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 16:05 ACPICA 20140214 auto-serialize weirds my machine Valdis Kletnieks
2014-03-14 16:10 ` Rafael J. Wysocki
2014-03-14 17:24 ` Valdis.Kletnieks
2014-03-14 17:38 ` Sabrina Dubroca [this message]
2014-03-14 18:08 ` Sabrina Dubroca
2014-03-14 19:36 ` Moore, Robert
2014-03-14 20:04 ` Valdis.Kletnieks
2014-03-14 20:14 ` Moore, Robert
2014-03-14 21:02 ` Moore, Robert
2014-03-14 21:29 ` Moore, Robert
2014-03-17 1:18 ` Zheng, Lv
2014-03-17 4:13 ` [RFC PATCH 0/2] ACPICA: Updates for auto-serialization mechanism Lv Zheng
2014-03-17 4:14 ` [RFC PATCH 1/2] ACPICA: Dispatcher: Ignore SyncLevel " Lv Zheng
2014-03-18 0:50 ` Zheng, Lv
2014-03-18 22:58 ` Sabrina Dubroca
2014-03-17 4:14 ` [RFC PATCH 2/2] ACPI: Default disable auto-serialization Lv Zheng
2014-03-17 12:09 ` Rafael J. Wysocki
2014-03-18 0:31 ` Zheng, Lv
2014-03-18 1:13 ` Rafael J. Wysocki
2014-03-18 1:29 ` Zheng, Lv
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=20140314173801.GA3755@kria \
--to=sd@queasysnail.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.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