From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: Regression in 4.8 - CPU speed set very low
Date: Tue, 27 Sep 2016 10:51:14 -0400 [thread overview]
Message-ID: <20160927145114.GM14311@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1436996d-078b-aa51-4452-b6655d917135@lwfinger.net>
On Mon, Sep 26, 2016 at 04:28:29PM -0500, Larry Finger wrote:
> Mostly I use a KDE applet named "System load" and look at the "average
> clock", but the same info is also available in /proc/cpuinfo as "cpu MHz".
> When the bug triggers, the system gets very slow, and the cpu fan stops even
> though the cpu is still busy.
>
> Commit f7816ad, which had run for 7 days without showing the bug, failed
> after about 2 hours today. All my testing since Sept. 9 has been wasted. Oh
> well, that's the way it goes!
Is it possible there is no bug and instead you have a hardware problem?
What I am thinking:
CPU fan stops, then CPU gets busy, CPU overheats, thermal throtling
kicks in to protect CPU and it gets VERY slow.
So maybe you have a bad CPU fan that is getting stuck. Perhaps even if
you have a motherboard that varies the CPU fan depending on need and the
fan doesn't like the lowest speed and sometimes gets stuck when asked
to go slow.
Of course if the CPU fan is the problem that could explain why it takes
varying amounts of time to see the problem.
I suggest checking what the cpu temperature sensors are showing next
time it gets slow.
--
Len Sorensen
next prev parent reply other threads:[~2016-09-27 14:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f89dffb9-cc78-9849-9539-74ce89e773cd@lwfinger.net>
[not found] ` <28fa8706-4251-4d07-6a6a-4ee8d9d1267b@lwfinger.net>
[not found] ` <2be25c2e-8c10-e62a-3a66-19da8143f2b0@lwfinger.net>
2016-09-26 11:37 ` Regression in 4.8 - CPU speed set very low 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
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 [this message]
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=20160927145114.GM14311@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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;
as well as URLs for NNTP newsgroup(s).