All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Psyborg <pozega.tomislav@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	lm-sensors@vger.kernel.org
Subject: Re: [RFC] why do sensors break CPU scaling
Date: Sat, 1 Feb 2020 01:16:47 +0100	[thread overview]
Message-ID: <CAKR_QVLKtkfVy5AAKj+ay0cQ2NPWrW7CPb8SGF6urD2ooM=VXQ@mail.gmail.com> (raw)
In-Reply-To: <20200131223547.GA7334@amd>

On 31/01/2020, Pavel Machek <pavel@ucw.cz> wrote:
> On Wed 2019-11-20 21:42:12, Tom Psyborg wrote:
>> Hi
>>
>> Recently I've needed to set lowest CPU scaling profile, running ubuntu
>> 16.04.06 I used standard approach - echoing powersave to
>> /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor.
>> This did not work as the
>> /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq kept returning
>> max scaling freq.
>
> Noone noticed, right?
>
> If you still believe that's problem, you may want to look at
> MAINTAINERS file, and put sensors maintainers in the Cc list.
>
> Best regards,
> 									Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>

it is definitely a problem. i've installed radeon-profile and can
monitor both CPU and GPU temps from there without CPU scaling
breakage. CCing related list

WARNING: multiple messages have this Message-ID (diff)
From: Tom Psyborg <pozega.tomislav@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	lm-sensors@vger.kernel.org
Subject: Re: [RFC] why do sensors break CPU scaling
Date: Sat, 01 Feb 2020 00:16:47 +0000	[thread overview]
Message-ID: <CAKR_QVLKtkfVy5AAKj+ay0cQ2NPWrW7CPb8SGF6urD2ooM=VXQ@mail.gmail.com> (raw)
In-Reply-To: <20200131223547.GA7334@amd>

On 31/01/2020, Pavel Machek <pavel@ucw.cz> wrote:
> On Wed 2019-11-20 21:42:12, Tom Psyborg wrote:
>> Hi
>>
>> Recently I've needed to set lowest CPU scaling profile, running ubuntu
>> 16.04.06 I used standard approach - echoing powersave to
>> /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor.
>> This did not work as the
>> /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq kept returning
>> max scaling freq.
>
> Noone noticed, right?
>
> If you still believe that's problem, you may want to look at
> MAINTAINERS file, and put sensors maintainers in the Cc list.
>
> Best regards,
> 									Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
>

it is definitely a problem. i've installed radeon-profile and can
monitor both CPU and GPU temps from there without CPU scaling
breakage. CCing related list

  reply	other threads:[~2020-02-01  0:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 20:42 [RFC] why do sensors break CPU scaling Tom Psyborg
2019-11-21  1:51 ` David Niklas
2019-11-23 13:44   ` Tom Psyborg
2020-01-31 22:35 ` Pavel Machek
2020-02-01  0:16   ` Tom Psyborg [this message]
2020-02-01  0:16     ` Tom Psyborg

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='CAKR_QVLKtkfVy5AAKj+ay0cQ2NPWrW7CPb8SGF6urD2ooM=VXQ@mail.gmail.com' \
    --to=pozega.tomislav@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.