From: "Doug Smythies" <dsmythies@telus.net>
To: 'Viresh Kumar' <viresh.kumar@linaro.org>,
'Andy Tang' <andy.tang@nxp.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org
Subject: RE: Ask for help on governor
Date: Tue, 12 Dec 2017 08:18:19 -0800 [thread overview]
Message-ID: <000801d37364$d48f6ed0$7dae4c70$@net> (raw)
In-Reply-To: Of1qe6hVbC2CsOf1seMkbL
On 2017.12.11 23:31 Viresh Kumar wrote:
> On 12-12-17, 02:46, Andy Tang wrote:
>> Hi,
>>
>> I run into a question that conservative governor can't work while ondemand governor works well.
>> When cpu load gets higher, if ondemand governor is used, cpu frequency can get higher and higher.
>> But if I use conservative governor, cpu frequency stays on lowest frequency no matter what cpu load is.
>>
>> This issue was found on kernel 4.14.0, on kernel 4.9 kernel. It acts well.
>
> You mean to say that the problem exists on 4.14 but not on 4.9?
>
> Strange, as we haven't seen any such reports from anyone else.
Well, it is easy enough for us to check.
Indeed, it is broken in kernel 4.14-rc1, but O.K. in kernel 4.13.
It remains broken in kernel 4.15-rc1 (I am not on -rc3 yet).
Because it was easier for me to do so, I used intel_cpufreq (i.e. intel_pstate in passive mode).
>
>> I think it may related to cpufreq framework, not driver itself. Could you guys give me some clues on how to debug it?
>> I don't expect a direct answer; any suggestions are welcome.
>
> Please provide output of below:
>
> grep . /sys/devices/system/cpu/cpufreq/policy*/*
>
> And then you may need to bisect the problem as well by going to kernel version
> in between 4.9 and 4.14.
@Andy: Have you started bisecting the kernel yet? I suppose I could if you haven't,
or if you do not know how.
... Doug
next prev parent reply other threads:[~2017-12-12 16:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR0402MB282866171A847AE244A9F76CF3340@HE1PR0402MB2828.eurprd04.prod.outlook.com>
2017-12-12 7:30 ` Ask for help on governor Viresh Kumar
2017-12-12 16:18 ` Doug Smythies [this message]
2017-12-12 16:51 ` Rafael J. Wysocki
2017-12-13 3:10 ` Doug Smythies
2017-12-13 6:17 ` Viresh Kumar
2017-12-13 6:22 ` Andy Tang
2017-12-13 6:55 ` Viresh Kumar
2017-12-13 16:13 ` Doug Smythies
2017-12-14 1:21 ` Doug Smythies
2017-12-14 2:42 ` Andy Tang
2017-12-14 18:25 ` Stratos Karafotis
2017-12-15 1:29 ` Doug Smythies
2017-12-15 1:30 ` Doug Smythies
2017-12-15 1:56 ` Andy Tang
2017-12-15 7:37 ` Doug Smythies
2017-12-15 9:00 ` Andy Tang
2017-12-15 14:26 ` Rafael J. Wysocki
2017-12-15 15:53 ` Rafael J. Wysocki
2017-12-15 18:27 ` Doug Smythies
2017-12-15 23:53 ` Rafael J. Wysocki
2017-12-18 1:15 ` [PATCH] cpufreq: governor: Ensure sufficiently large sampling intervals Rafael J. Wysocki
2017-12-18 2:59 ` Andy Tang
2017-12-18 4:38 ` Viresh Kumar
2017-12-18 16:11 ` Doug Smythies
2017-12-18 17:42 ` Rafael J. Wysocki
2017-12-13 16:13 ` Ask for help on governor Doug Smythies
2017-12-13 16:49 ` Doug Smythies
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='000801d37364$d48f6ed0$7dae4c70$@net' \
--to=dsmythies@telus.net \
--cc=andy.tang@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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