From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: 'Linux PM' <linux-pm@vger.kernel.org>
Subject: RE: CPUs do not go idle - excessive energy consumption
Date: Thu, 19 Oct 2017 17:16:00 -0700 [thread overview]
Message-ID: <000001d34938$9d012310$d7036930$@net> (raw)
In-Reply-To: 30gVe635D3OTt30gXeUUCy
On 2017.10.13 07:10 Doug Smythies wrote:
> On 2017.10.12 09:36 Doug Smythies wrote:
>> On 2017.10.12 08:53 Rafael J. Wysocki wrote:
>>> On Thu, Oct 12, 2017 at 5:28 PM, Doug Smythies <dsmythies@telus.net> wrote:
>>>>
>>>> I am observing higher than nominal processor package power consumption, under
>>>> some conditions. The worst case, so far, was an extra 6.3 watts or 25%, however
>>>> more typically it is between 0 and 4 watts (over 1 minute sampling intervals).
>>>>
>> ...[snip]...
>>
>>> For starters, you can try to apply this patch
>>> https://patchwork.kernel.org/patch/9866841/ and see if it makes any
>> difference.
>>
>> Oh darn, I missed the importance and relevance of that e-mail (but I did get it),
>> which might have saved me a lot of time.
>> It sounds like it is exactly the same issue.
>> I'll try it as soon as I can either resolve the conflicts, or go back
>> and apply it to whatever kernel version would result in no conflicts.
>>
>> I'll report back once I have some test results.
I'll report back by replying to the above referenced e-mail.
> The patch did not solve the problem.
The patch did not work as it was sent.
The changes I had to make will also be in the above mentioned reply.
The patch still doesn't solve this particular problem.
Merely disabling idle state 0 does solve the problem.
I have been trying to demonstrate a downside to disabling
idle state 0, and haven't found one. pipe-test is something we used
before, but I don't see any difference on my computer.
I have reviewed and reminded myself about the issues with the menu governor.
>
> Because the test results vary, and always have, it is hard to know for
> certain of there was some improvement, but I did have a couple of 10 minute
> tests with 0 occurrences (based on my arbitrary thresholds). A one hour
> test had 530 occurrences.
>
> ... Doug
prev parent reply other threads:[~2017-10-20 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 15:28 CPUs do not go idle - excessive energy consumption Doug Smythies
2017-10-12 15:52 ` Rafael J. Wysocki
2017-10-12 16:36 ` Doug Smythies
2017-10-13 14:10 ` Doug Smythies
2017-10-20 0:16 ` Doug Smythies [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='000001d34938$9d012310$d7036930$@net' \
--to=dsmythies@telus.net \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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).