From: Lekensteyn <lekensteyn@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: ACPI Error: [_T_1] Namespace lookup failure, AE_ALREADY_EXISTS
Date: Fri, 16 Nov 2012 17:32:14 +0100 [thread overview]
Message-ID: <1471550.uqjjeh6DEC@al> (raw)
Hi,
I have written a WMI module for my Clevo laptop [1] that can accept WMI
notifications. This module usually works without issues, but I have rare times
where I get weird ACPI warnings *during* suspend (not on resume):
[21546.880745] ACPI Error: [_T_1] Namespace lookup failure, AE_ALREADY_EXISTS (20120913/dswload2-330)
[21546.880748] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20120913/psloop-231)
[21546.880753] ACPI Error: Method parse/execution failed [\_SB_.WMI_.WMBB] (Node ffff880232456988), AE_ALREADY_EXISTS (20120913/psparse-536)
[21546.880756] clevo_wmi: Failed to execute function 0x1: AE_ALREADY_EXISTS
[21546.880757] clevo_wmi: Could not get WMI event number.
[21546.900438] PM: suspend of devices complete after 459.769 msecs
[21546.900558] PM: late suspend of devices complete after 0.118 msecs
[21546.916355] ACPI: Marking method WMBB as Serialized because of AE_ALREADY_EXISTS error
The module installs a WMI notifier when loaded. When the notifier callback is
called, it calls a WMI method (WMBB) to retrieve the last event number. This
last thing is failing as can be seen above. The WMBB method is defined in
DSDT which can be found on [2] along with an acpidump and an analysis of
WMI events/methods.
To me, it seems a locking issue as this issue rarely occurs (3 times in like 2
months). I wonder if I did something wrong?
Regards,
Peter
[1]: https://github.com/Lekensteyn/acpi-stuff/tree/master/clevo-wmi
[2]: https://github.com/Lekensteyn/acpi-stuff/tree/master/dsl/Clevo_B7130
reply other threads:[~2012-11-16 16:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1471550.uqjjeh6DEC@al \
--to=lekensteyn@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).