public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Doug Smythies" <dsmythies@telus.net>
To: "'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
	"'Larry Finger'" <Larry.Finger@lwfinger.net>,
	"'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	"'LKML'" <linux-kernel@vger.kernel.org>,
	"'Linux PM list'" <linux-pm@vger.kernel.org>
Subject: RE: Regression in 4.8 - CPU speed set very low
Date: Mon, 26 Sep 2016 20:12:38 -0700	[thread overview]
Message-ID: <003001d2186d$02c34820$0849d860$@net> (raw)
In-Reply-To: ohH4bKxaUa8e7ohH5blnhh

On 2016.09.26 18:31 Srinivas Pandruvada wrote:
> On Mon, 2016-09-26 at 19:48 -0500, Larry Finger wrote:
>> On 09/26/2016 07:21 PM, Rafael J. Wysocki wrote: 
>>> On Tue, Sep 27, 2016 at 1:53 AM, Larry Finger wrote:
>>> But for both we need a reproducer anyway.
>> I do not have a reliable reproducer. The condition has always
>> happened when 
>> running a high-compute job such as a 'make -j8' on the kernel, or
>> building the 
>> RPM for openSUSE's implementation of VirtualBox. The latter is what
>> I'm using 
>> for most of my testing.

Run some CPU stressor and get all your CPU's going at 100% load.
And watch your core temperatures while you do so.

> 
>>> It also would be good to rule out the thermal throttling (as per
>>> the Srinivas' comments).

It is almost certainly thermal throttling, or similar causing
Clock modulation, of it seems 50%.

>>> 
>>> For now, please tell me what's in
>>> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
>> 800000
> Your effective freq is lower than 800MHz. One of the possible reason is
> thermal throttling.
>
> What distro you are using?

And what make and model of LapTop?

  parent reply	other threads:[~2016-09-27  3:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 17:39 Regression in 4.8 - CPU speed set very low Larry Finger
2016-09-14 16:00 ` Larry Finger
2016-09-19  2:54   ` Larry Finger
2016-09-24  2:45     ` Larry Finger
2016-09-26 11:37       ` Rafael J. Wysocki
2016-09-26 16:15         ` Larry Finger
2016-09-26 21:06           ` Rafael J. Wysocki
2016-09-26 21:26             ` Srinivas Pandruvada
2016-09-26 21:30               ` Rafael J. Wysocki
2016-09-26 21:41                 ` Srinivas Pandruvada
2016-09-26 21:46                   ` Rafael J. Wysocki
2016-09-26 21:28             ` Larry Finger
2016-09-26 21:37               ` Rafael J. Wysocki
2016-09-26 21:46                 ` Srinivas Pandruvada
2016-09-26 22:15                   ` Larry Finger
2016-09-26 22:09                 ` Larry Finger
2016-09-26 22:16                   ` Rafael J. Wysocki
2016-09-26 23:53                     ` Larry Finger
2016-09-27  0:21                       ` Rafael J. Wysocki
2016-09-27  0:48                         ` Larry Finger
2016-09-27  1:30                           ` Srinivas Pandruvada
2016-09-27  2:53                             ` Larry Finger
2016-09-27  3:12                           ` Doug Smythies [this message]
2016-09-27  8:48                             ` Larry Finger
2016-09-27 11:46                               ` Rafael J. Wysocki
2016-09-29  2:22                                 ` Larry Finger
2016-09-29 12:19                                   ` Rafael J. Wysocki
2016-09-29 15:09                                     ` Larry Finger
2016-09-29 15:56                                     ` Srinivas Pandruvada
2016-09-29 16:24                                       ` Larry Finger
2016-09-29 20:52                                       ` Rafael J. Wysocki
2016-09-30 21:52                                       ` Larry Finger
2016-09-27 14:51               ` Lennart Sorensen
2016-09-29  2:26                 ` Larry Finger
2016-09-29 14:17                   ` Lennart Sorensen

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='003001d2186d$02c34820$0849d860$@net' \
    --to=dsmythies@telus.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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