linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 173361] Under heavy load, the CPU speed suddenly and irreversibly drops from 3500 to 400 MHz
Date: Thu, 29 Sep 2016 16:40:29 +0000	[thread overview]
Message-ID: <bug-173361-137361-df12pSOD59@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-173361-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=173361

Doug Smythies <dsmythies@telus.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dsmythies@telus.net

--- Comment #1 from Doug Smythies <dsmythies@telus.net> ---
For what it is worth, some data from my computer:

. I get the exact same steady state temperature and package power under full
load with both kernel 4.7 and 4.8-rc8.

. I messed with the cooling so that it could exceed the high limit, and when it
did nothing tripped (as expected):

doug@s15:~/temp2$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +81.0°C  (high = +80.0°C, crit = +98.0°C)
Core 0:         +77.0°C  (high = +80.0°C, crit = +98.0°C)
Core 1:         +81.0°C  (high = +80.0°C, crit = +98.0°C)
Core 2:         +77.0°C  (high = +80.0°C, crit = +98.0°C)
Core 3:         +78.0°C  (high = +80.0°C, crit = +98.0°C)

For this comment from the e-mail thread: "Hmm, I would not expect the CPU to
drop from 80 to 40 degrees in a few seconds if the fan is not spinning.  I
wouldn't even expect it if the fan was spinning.  I would think at least 30 to
60 seconds if not more."

I from a steady state, full load, temperature of 78 degrees C to 0 load I see:
15 degrees drop in 1 second; 18 degrees drop in 2 seconds; 22 degrees drop in
10 seconds; 25 degrees droop in 20 seconds.

For the original post comment: "In that case, the bug would be that the
frequency is never restored."
It isn't supposed to restore. I do not know why in this case it is kicking in
at 50%, usually it is less. Regardless, the current control algorithm in the
intel_pstate driver is fundamentally incompatible with clock modulation, and
will always drive the CPU down to the minimum * the modulation %, regardless of
load. Other drivers typically drive the CPU frequency to what would normally be
desired * modulation % (and for the most part users don't even notice).

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2016-09-29 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 14:57 [Bug 173361] New: Under heavy load, the CPU speed suddenly and irreversibly drops from 3500 to 400 MHz bugzilla-daemon
2016-09-29 16:40 ` bugzilla-daemon [this message]
2016-09-29 17:18 ` [Bug 173361] " bugzilla-daemon
2016-09-29 18:28 ` bugzilla-daemon
2016-09-29 19:29 ` bugzilla-daemon
2016-09-29 21:32 ` bugzilla-daemon

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=bug-173361-137361-df12pSOD59@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pm@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).