linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Doug Smythies <dsmythies@telus.net>
Cc: "'Rafael J. Wysocki'" <rafael@kernel.org>,
	'kernel list' <linux-kernel@vger.kernel.org>,
	'ACPI Devel Maling List' <linux-acpi@vger.kernel.org>,
	"'Zhang, Rui'" <rui.zhang@intel.com>,
	"'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
	'Viresh Kumar' <viresh.kumar@linaro.org>,
	'Linux PM' <linux-pm@vger.kernel.org>,
	'Thomas Gleixner' <tglx@linutronix.de>,
	'Ingo Molnar' <mingo@redhat.com>,
	'Borislav Petkov' <bp@alien8.de>,
	"'H. Peter Anvin'" <hpa@zytor.com>,
	'the arch/x86 maintainers' <x86@kernel.org>
Subject: Re: 5.2-rc2: low framerate in flightgear, cpu not running at full speed, thermal related?
Date: Tue, 18 Jun 2019 10:34:50 +0200	[thread overview]
Message-ID: <20190618083449.GA4541@amd> (raw)
In-Reply-To: <002601d525ae$a2c00c90$e84025b0$@net>

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

On Tue 2019-06-18 01:20:01, Doug Smythies wrote:
> On 2019.06.13 01:53 Rafael J. Wysocki wrote:
> 
> > I personally doubt that any thermal throttling is involved here.
> 
> In earlier e-mails on this thread, Pavel showed his core and package
> temperatures as 97 and 98 degrees. If thermal throttling is not
> involved, it should be. The description of the observed CPU
> frequencies also matched my experiences with thermal throttling
> for the intel-pstate/powersave example. Myself, I can not determine
> if throttling is involved for the acpi-cpufreq/ondemand
> case, just from the clock frequencies, because,
> at least on my system, it uses the kidle_inject method
> instead of the pstate method.

Yes, I'm pretty sure it is thermal throttling. System is running >
3GHz when cold, and going below 2GHz when hot...

And I'm pretty sure the throttling works, too, because temperature
goes to ~98C quickly, and stays there.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2019-06-18  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 11:17 5.2-rc2: low framerate in flightgear, cpu not running at full speed, thermal related? Pavel Machek
2019-06-09 11:23 ` Pavel Machek
2019-06-09 12:12   ` Pavel Machek
2019-06-09 13:55     ` Daniel Lezcano
2019-06-09 14:13     ` Zhang Rui
2019-06-11 10:12       ` Pavel Machek
2019-06-11 10:15         ` Viresh Kumar
2019-06-12  2:37 ` Doug Smythies
2019-06-12 21:44   ` Rafael J. Wysocki
2019-06-12 23:39     ` Doug Smythies
2019-06-13  8:11       ` Pavel Machek
2019-06-13  9:00         ` Rafael J. Wysocki
2019-06-13  8:52       ` Rafael J. Wysocki
2019-06-18  8:20         ` Doug Smythies
2019-06-18  8:34           ` Pavel Machek [this message]

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=20190618083449.GA4541@amd \
    --to=pavel@ucw.cz \
    --cc=bp@alien8.de \
    --cc=dsmythies@telus.net \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@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).