All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: 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 18:30:46 -0700	[thread overview]
Message-ID: <1474939846.4669.96.camel@linux.intel.com> (raw)
In-Reply-To: <2326a7dd-675f-752b-f100-5dce6e4c93fd@lwfinger.net>

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 <Larry.Finger@lwfinge
> > r.net> wrote:
> > > 
> > > On 09/26/2016 05:16 PM, Rafael J. Wysocki wrote:
> > > > 
> > > > 
> > > > On Tue, Sep 27, 2016 at 12:09 AM, Larry Finger
> > > <Larry.Finger@lwfinger.net> wrote:
> > > > 
> > > > 
> > > > 
> > > > Maybe it's better to try diagnose the problem instead of
> > > > spending more
> > > > time on bisection.
> > > 
> > > In my original post, I asked for such help, but nothing until
> > > today. I had
> > > no idea what to check, but now I have a better idea.
> > > 
> > > > 
> > > > I'd like to know whether or not 4.7 was definitely good,
> > > > though.
> > > 
> > > I never saw this problem with 4.7, but given the difficulty in
> > > triggering
> > > the problem, my tests may not have been definitive.
> > > > 
> > > > 
> > > > 
> > > > > 
> > > > > If it is one of them, it may be a while before I dare call
> > > > > this one
> > > > > "good".
> > > > > In one respect, that is good as I will be traveling tomorrow
> > > > > and
> > > > > Wednesday.
> > > > 
> > > > What does "cat
> > > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver" say?
> > > 
> > > intel_pstate
> > You probably don't need to worry about all of the cpufreq changes
> > in
> > 4.8-rc, then.  Only a few of them affect intel_pstate and I don't
> > see
> > how any of them may lead to the observed symptoms.
> > 
> > First off, if you have a reproducer, please run it on 4.7 and see
> > if
> > you can trigger the issue in there.
> I'm running 4.8-rc7 at the moment hoping to trigger the problem and
> get the data 
> requested by Srinivas. Once I get that, I will try 4.7 again.
> > 
> > 
> > Second, it would be good to have a look at the output from the
> > cpu_frequency and pstate_sample tracepoints around when the issue
> > triggers.  The pstate_sample one would be more interesting.
> > 
> > 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.
> 
> > 
> > It also would be good to rule out the thermal throttling (as per
> > the
> > Srinivas' comments).
> > 
> > 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?


Thanks,
Srinivas


  reply	other threads:[~2016-09-27  1:33 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 [this message]
2016-09-27  2:53                             ` Larry Finger
2016-09-27  3:12                           ` Doug Smythies
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=1474939846.4669.96.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --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 \
    /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.