From: "Doug Smythies" <dsmythies@telus.net>
To: sedat.dilek@gmail.com
Cc: "'Srinivas Pandruvada'" <srinivas.pandruvada@linux.intel.com>,
"'Rafael J. Wysocki'" <rafael.j.wysocki@intel.com>,
"'Jörg Otte'" <jrg.otte@gmail.com>,
linux-pm@vger.kernel.org, 'LKML' <linux-kernel@vger.kernel.org>
Subject: RE: [intel-pstate driver regression] processor frequency very high even if in idle
Date: Thu, 31 Mar 2016 07:30:04 -0700 [thread overview]
Message-ID: <002301d18b59$d208fe50$761afaf0$@net> (raw)
In-Reply-To: <CA+icZUXaoeQz5vMzPxjOaAzbzdQ4D1MV2dG5EvXAM54k6EOz1g@mail.gmail.com>
On 2016.03.31 01:11 Sedat Dilek wrote:
> On Thu, Mar 31, 2016 at 12:50 AM, Doug Smythies <dsmythies@telus.net> wrote:
>> On 2106.03.30 15:19 Srinivas Pandruvada wrote:
>>>>
>>>> Please see attached files.
>>>>
>>> Thanks. Your logs make sense. You have config set to performance mode
>>> by default (Which I believe default in all kernel Ubuntu).
>>
>> Yes, but via a startup script, by default Ubuntu sets the governor
>> to powersave 1 minute after boot (or ondemand if acpi-cpufreq).
>>
>
> Can you give more and precise informations on this?
> script-name etc.
The script is /etc/init.d/ondemand
It sleeps for 1 minute and then sets the scaling
governor, based on availability, in the following order:
interactive
ondemand
powersave
See also:
$ ls -l /etc/rc?.d/S06ondemand
lrwxrwxrwx 1 root root 18 Mar 8 09:51 /etc/rc2.d/S06ondemand -> ../init.d/ondemand
lrwxrwxrwx 1 root root 18 Mar 8 09:51 /etc/rc3.d/S06ondemand -> ../init.d/ondemand
lrwxrwxrwx 1 root root 18 Mar 8 09:51 /etc/rc4.d/S06ondemand -> ../init.d/ondemand
lrwxrwxrwx 1 root root 18 Mar 8 09:51 /etc/rc5.d/S06ondemand -> ../init.d/ondemand
>From your other e-mail:
> is somehow showing higher
> values than TSC_MHz.
> Not sure if this really make sense if TSC_MHz is a max-value (which I
> don't know it is).
That is normal, and is turbo mode. Example:
$ sudo turbostat -i 3 --msr=0x199
CPU Avg_MHz %Busy Bzy_MHz TSC_MHz MSR 0x199
- 478 12.53 3798 3413 0x00000000
0 3 0.09 3595 3413 0x00002500
4 1 0.03 3568 3413 0x00001000
1 4 0.11 3649 3413 0x00001200
5 2 0.07 3592 3413 0x00001000
2 3 0.08 3628 3413 0x00001000
6 1 0.03 3546 3413 0x00001000
3 1 0.02 3733 3413 0x00001000
7 3808 99.91 3799 3411 0x00002600
... Doug
next prev parent reply other threads:[~2016-03-31 14:30 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUVGq+rmnyGSbyNEfWJ+LsNg6j6daPPwoZM1zUp4WCJFGQ@mail.gmail.com>
2016-03-30 21:58 ` [intel-pstate driver regression] processor frequency very high even if in idle Rafael J. Wysocki
2016-03-30 22:23 ` Sedat Dilek
2016-03-30 22:29 ` Rafael J. Wysocki
[not found] ` <1459376311.13525.108.camel@linux.intel.com>
2016-03-30 22:25 ` Rafael J. Wysocki
2016-03-30 22:46 ` Srinivas Pandruvada
2016-03-30 23:17 ` Pandruvada, Srinivas
2016-03-30 23:25 ` Sedat Dilek
2016-03-30 23:28 ` Rafael J. Wysocki
2016-03-30 23:32 ` Sedat Dilek
2016-03-30 23:41 ` Rafael J. Wysocki
2016-03-31 6:38 ` Sedat Dilek
2016-03-31 7:45 ` Sedat Dilek
[not found] ` <CAA=4085Mmv7gRpJid8UGQ4ti6c1HhaENnogd8aPrg6E-w68QWg@mail.gmail.com>
2016-03-31 7:28 ` Navin P.S
[not found] ` <003b01d18ad6$831941c0$894bc540$@net>
[not found] ` <CA+icZUXaoeQz5vMzPxjOaAzbzdQ4D1MV2dG5EvXAM54k6EOz1g@mail.gmail.com>
2016-03-31 14:30 ` Doug Smythies [this message]
2016-04-02 6:12 ` Sedat Dilek
[not found] ` <CA+icZUVHyq7dOh457rYv+2nmNxPevY0ZcqxhQVhYG4Z1D-NaDA@mail.gmail.com>
2016-04-02 15:28 ` Srinivas Pandruvada
2016-04-02 17:19 ` Jörg Otte
2016-04-02 18:20 ` Sedat Dilek
2016-04-03 18:59 ` Doug Smythies
2016-04-04 5:13 ` Sedat Dilek
2016-04-04 6:14 ` Doug Smythies
2016-04-04 14:12 ` Sedat Dilek
[not found] <CADDKRnD81Hmf+JnG6NEpQWKiKE6_mqet5yRpLJ5K_0U1GtfahQ@mail.gmail.com>
[not found] ` <CADDKRnCH3yCut7A4Gvk3gHw4OpOYXoG0VQRe5mh2nTjptYU0gw@mail.gmail.com>
2016-03-29 21:34 ` Rafael J. Wysocki
2016-03-30 10:17 ` Jörg Otte
2016-03-30 11:05 ` Rafael J. Wysocki
2016-03-30 15:29 ` Jörg Otte
2016-03-30 18:39 ` Rafael J. Wysocki
2016-03-31 9:05 ` Jörg Otte
2016-03-31 11:42 ` Rafael J. Wysocki
2016-03-31 15:25 ` Jörg Otte
2016-03-31 15:43 ` Rafael J. Wysocki
2016-03-31 16:10 ` Srinivas Pandruvada
2016-03-31 17:27 ` Jörg Otte
2016-03-31 17:55 ` Srinivas Pandruvada
2016-04-01 0:08 ` Rafael J. Wysocki
2016-04-01 9:42 ` Jörg Otte
2016-04-01 15:05 ` Srinivas Pandruvada
2016-04-01 20:24 ` Rafael J. Wysocki
2016-04-01 9:20 ` Jörg Otte
2016-04-01 12:40 ` Rafael J. Wysocki
2016-04-01 14:06 ` Jörg Otte
2016-04-01 17:44 ` Srinivas Pandruvada
2016-04-01 18:31 ` Doug Smythies
2016-04-01 18:41 ` Srinivas Pandruvada
2016-04-01 19:54 ` Rafael J. Wysocki
2016-04-01 23:36 ` Doug Smythies
2016-04-02 0:28 ` Rafael J. Wysocki
2016-04-01 20:28 ` Rafael J. Wysocki
2016-04-02 22:50 ` Rafael J. Wysocki
2016-04-01 15:20 ` Doug Smythies
2016-04-01 16:46 ` Jörg Otte
2016-04-01 17:34 ` Jörg Otte
2016-03-30 15:33 ` Pandruvada, Srinivas
2016-03-30 15:51 ` Jörg Otte
2016-03-30 18:50 ` Doug Smythies
2016-03-30 18:58 ` Srinivas Pandruvada
2016-03-30 20:12 ` Rafael J. Wysocki
2016-03-30 20:26 ` Srinivas Pandruvada
2016-03-31 9:23 ` Jörg Otte
2016-03-31 14:39 ` Doug Smythies
2016-03-31 15:06 ` Srinivas Pandruvada
2016-03-31 15:32 ` Jörg Otte
2016-03-31 15:10 ` Doug Smythies
2016-04-01 7:20 ` 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='002301d18b59$d208fe50$761afaf0$@net' \
--to=dsmythies@telus.net \
--cc=jrg.otte@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sedat.dilek@gmail.com \
--cc=srinivas.pandruvada@linux.intel.com \
/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).