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, Len Brown <len.brown@intel.com>
Subject: Re: Fwd: [Bug 92111] Power regression from 3.17 to 3.18 and 3.19
Date: Wed, 11 Feb 2015 02:05:05 +0000 [thread overview]
Message-ID: <20150211020505.GA16398@srcf.ucam.org> (raw)
In-Reply-To: <1910334.cCyQdZ49eW@vostro.rjw.lan>
On Wed, Feb 11, 2015 at 03:26:35AM +0100, Rafael J. Wysocki wrote:
> In order to "identify the root cause" it is pretty much necessary to know
> what _OSI("Darwin") causes the firmware to actually do and the only party
> knowing that is Apple. The only question I can ask hardware people is what
> it *theoretically* may be doing to trigger the observed behavior and
> honestly I doubt I'll get a useful answer to that.
The hardware has a fixed set of inputs that influence whether it enters
PC6. If we know what those are then we can identify which is actually at
play here, which gives us a high probability of identifying the root
cause.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2015-02-11 2:05 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
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 [this message]
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=20150211020505.GA16398@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=andreas.noever@gmail.com \
--cc=attila.jakosa@gmail.com \
--cc=len.brown@intel.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.