From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Andreas Noever <andreas.noever@gmail.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
attila.jakosa@gmail.com
Subject: Re: Fwd: [Bug 92111] Power regression from 3.17 to 3.18 and 3.19
Date: Wed, 11 Feb 2015 00:33:18 +0000 [thread overview]
Message-ID: <20150211003318.GA13680@srcf.ucam.org> (raw)
In-Reply-To: <1721194.3W9qJruT3Q@vostro.rjw.lan>
On Wed, Feb 11, 2015 at 01:53:26AM +0100, Rafael J. Wysocki wrote:
> On Wednesday, February 11, 2015 12:26:02 AM Matthew Garrett wrote:
> > Hm. It's not clear to me what the bug is describing. If we're not waking
> > up more frequently, why aren't we entering PC6?
>
> Good question. :-)
>
> The bug is saying, pretty much, that after a positive _OSI response to "Darwin"
> we cannot enter PC6 any more on that machine all other things being equal.
We're using intel_idle, so we should be making idle state determination
regardless of what ACPI tells us. So is Darwin mode influencing the
state of some MSR that controls whether PC6 can be entered? Is the GPU
blocking it because of some configuration difference? I don't know
enough about how the chip decides to enter PC6 to be able to tell.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2015-02-11 0:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 0:29 Fwd: [Bug 92111] Power regression from 3.17 to 3.18 and 3.19 Rafael J. Wysocki
2015-02-11 0:26 ` Matthew Garrett
2015-02-11 0:53 ` Rafael J. Wysocki
2015-02-11 0:33 ` Matthew Garrett [this message]
2015-02-11 1:02 ` Rafael J. Wysocki
2015-02-11 0:42 ` Matthew Garrett
2015-02-11 1:09 ` Rafael J. Wysocki
2015-02-11 0:48 ` Matthew Garrett
2015-02-11 1:14 ` Rafael J. Wysocki
2015-02-11 0:53 ` Matthew Garrett
2015-02-11 1:20 ` Rafael J. Wysocki
2015-02-11 1:01 ` Matthew Garrett
2015-02-11 1:57 ` Rafael J. Wysocki
2015-02-11 1:43 ` Matthew Garrett
2015-02-11 2:26 ` Rafael J. Wysocki
2015-02-11 2:05 ` Matthew Garrett
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=20150211003318.GA13680@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=andreas.noever@gmail.com \
--cc=attila.jakosa@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.