From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 173361] Under heavy load, the CPU speed suddenly and irreversibly drops from 3500 to 400 MHz
Date: Thu, 29 Sep 2016 18:28:04 +0000 [thread overview]
Message-ID: <bug-173361-137361-RbdcSor3ZC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-173361-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=173361
--- Comment #3 from Doug Smythies <dsmythies@telus.net> ---
Created attachment 240221
--> https://bugzilla.kernel.org/attachment.cgi?id=240221&action=edit
Script to continuously monitor package temperature
I guess the point is that one can not come after the event trigger and obtain
anything close to related temperatures. Perhaps the attached script could be
used to monitor package temperature from well before to well after the event.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-09-29 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 14:57 [Bug 173361] New: Under heavy load, the CPU speed suddenly and irreversibly drops from 3500 to 400 MHz bugzilla-daemon
2016-09-29 16:40 ` [Bug 173361] " bugzilla-daemon
2016-09-29 17:18 ` bugzilla-daemon
2016-09-29 18:28 ` bugzilla-daemon [this message]
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-RbdcSor3ZC@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).