From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 173361] New: Under heavy load, the CPU speed suddenly and irreversibly drops from 3500 to 400 MHz
Date: Thu, 29 Sep 2016 14:57:55 +0000 [thread overview]
Message-ID: <bug-173361-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=173361
Bug ID: 173361
Summary: Under heavy load, the CPU speed suddenly and
irreversibly drops from 3500 to 400 MHz
Product: Power Management
Version: 2.5
Kernel Version: 4.8-rc1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: Larry.Finger@lwfinger.net
Regression: No
My Toshiba Tecra A50-A laptop that a CPU described as 'Model: 6.60.3 "Intel(R)
Core(TM) i7-4600M CPU @ 2.90GHz"'. Under heavy load, this dual-core unit with
hyperthreading will suddenly drop from a frequency of 3500 to 410 MHz. The only
way to recover is to reboot. See
http://lkml.iu.edu/hypermail/linux/kernel/1609.3/00720.html for some details
and other discussion.
This bug is being filed under power management because the 'sensors' command
shows the following:
finger@linux-1t8h:~> sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +88.0°C (high = +84.0°C, crit = +100.0°C)
Core 0: +88.0°C (high = +84.0°C, crit = +100.0°C)
Core 1: +77.0°C (high = +84.0°C, crit = +100.0°C)
Routinely, at least one of the CPUs has a temperature higher than the "high"
value. As Rafael Wysocki states "It looks like in 4.8-rc we made a change that
caused the "high" trip point to be acted on." In that case, the bug would be
that the frequency is never restored.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2016-09-29 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 14:57 bugzilla-daemon [this message]
2016-09-29 16:40 ` [Bug 173361] Under heavy load, the CPU speed suddenly and irreversibly drops from 3500 to 400 MHz bugzilla-daemon
2016-09-29 17:18 ` 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@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).