From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Jörg Otte" <jrg.otte@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [v3.20]: Missing /sys/class/ACAD directory OR Cannot release Mutex
Date: Tue, 24 Feb 2015 00:24:16 +0100 [thread overview]
Message-ID: <1643186.zN49pcFPny@vostro.rjw.lan> (raw)
In-Reply-To: <CADDKRnDO7LAr5bg-5TJ-2=Va3kBw-cWqDvWoL3omWVJHUUd7tA@mail.gmail.com>
On Sunday, February 22, 2015 01:33:09 PM Jörg Otte wrote:
> Starting with kernel 3.19.0-05184-g18320f2, I often find my notebook
> running with 'powersave' policy even if it is on AC.
>
> It turned out that /sys/class/ACAD directory is missing and in the
> logs I see:
>
> ACPI Error: Cannot release Mutex [MUT0], not acquired (20150204/exmutex-376)
> ACPI Error: Method parse/execution failed [\_SB_.ACAD._PSR] (Node
> ffff880216028d48), AE_AML_MUTEX_NOT_ACQUIRED (20150204/psparse-536)
> ACPI Exception: AE_AML_MUTEX_NOT_ACQUIRED, Error reading AC Adapter
> state (20150204/ac-131)
>
> At the last 25 startups since 3.19.0-05184-g18320f2 it occured 13 times.
>
> It does not occur with kernels older than 3.19.0-05184-g18320f2.
Which mainline commit is that?
The only changes in 4.0-rc1 that can affect that are the ACPI EC updates IIRC.
Is there a chance to try the acpi-ec branch from linux-pm.git and see if the
problem is there?
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-23 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 12:33 [v3.20]: Missing /sys/class/ACAD directory OR Cannot release Mutex Jörg Otte
2015-02-23 23:24 ` Rafael J. Wysocki [this message]
2015-02-24 11:03 ` Jörg Otte
2015-02-24 13:29 ` Jörg Otte
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=1643186.zN49pcFPny@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=jrg.otte@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.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