From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Larry Finger <Larry.Finger@lwfinger.net>,
Zhang Rui <rui.zhang@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Doug Smythies <dsmythies@telus.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: Thu, 29 Sep 2016 08:56:16 -0700 [thread overview]
Message-ID: <1475164576.5547.10.camel@linux.intel.com> (raw)
In-Reply-To: <16590757.26uEfRfeet@vostro.rjw.lan>
On Thu, 2016-09-29 at 14:19 +0200, Rafael J. Wysocki wrote:
[...]
> > My laptop was inadvertently put to sleep while I was gone. I forgot
> > to leave a
> > note for my wife and she quieted the noisy cpu fan. :)
> It looks like in 4.8-rc we made a change that caused the "high" trip
> point to
> be acted on.
This high trip point we don't expose in thermal subsystem (the thermal
zone dump didn't show this anywhere as a trip). This is exposed by
core-dts driver only. This is the point BIOS is supposed to act, I
guess that's why you are seeing 50% clock modulation.
Are you running thermald
What is?
# ps -e | grep thermald
>
> Srinivas, Rui, do you recall what that can be?
>
> One more question (I think I asked it previously): In the failing
> case
> (4.8-rc1 and later), when the frequency drops down to the 400 MHz,
> does it
> ever go back higher or is it stuck at that level forever?
>
> In any case, it may help to file a bug at bugzilla.kernel.org against
> CPU/thermal or similar and let me know the bug number. We'll need to
> collect some tracepoint data to debug this and some place to put them
> into for easy reference.
Yes, this is good idea.
Thanks,
Srinivas
next prev parent reply other threads:[~2016-09-29 15:59 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
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 [this message]
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=1475164576.5547.10.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dsmythies@telus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@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