From: "Doug Smythies" <dsmythies@telus.net> To: "'Jörg Otte'" <jrg.otte@gmail.com>, "'Pandruvada, Srinivas'" <srinivas.pandruvada@intel.com> Cc: <rafael@kernel.org>, <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>, <rjw@rjwysocki.net> Subject: RE: [intel-pstate driver regression] processor frequency very high even if in idle Date: Wed, 30 Mar 2016 11:50:35 -0700 [thread overview] Message-ID: <002401d18ab5$0bf84a30$23e8de90$@net> (raw) In-Reply-To: <CADDKRnA5x9dK=6KZWijiP_ihrUA9Afpmqw8TSzYn9oaBeaOfKw@mail.gmail.com> On 2016.03.30 08:52 Jörg Otte wrote: > 2016-03-30 17:33 GMT+02:00 Pandruvada, Srinivas <srinivas.pandruvada@intel.com>: >> On Wed, 2016-03-30 at 13:05 +0200, Rafael J. Wysocki wrote: >>> On Wed, Mar 30, 2016 at 12:17 PM, Jörg Otte <jrg.otte@gmail.com> >>>>>> Now in v4.6-rc1 the characteristic has dramatically changed. >>>>>> If in idle the processor frequency is more or less a few >>>>>> MHz around 2500Mhz. >>>>>> I currently use acpi_cpufreq which works as usual. >>>>>> Processor: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz >>>>>> (family: 0x6, model: 0x3c, stepping: 0x3) >> I want to reproduce this if I can. Can you give us info about your >> setup (Linux distribution, laptop model etc.)? I would like to try to reproduce the issue also. > Distro: Ubuntu 14.04.4 LTS Note that with Ubuntu 14.04, I had issues where my CPU would lock at pstate 24 (not always 24, but usually), regardless of load. However, it was always after an S3 suspend, occurred 100% of the time, and was independent of intel_pstate or acpi-cpufreq CPU frequency scaling drivers. Since changing my test server to Ubuntu server edition 16.04 (development version), I have not had those issues. While I have no proof, I have assumed the issue elimination was somehow related to the change to systemd. It might be worth observing both what the intel_pstate is asking for and what the processor is actually doing. What is being asked for: # rdmsr --bitfield 15:8 -d -a 0x199 What is being given: # rdmsr --bitfield 15:8 -d -a 0x198 An old problematic example from an idle system (mine) Note, my minimum pstate is 16: What was being given: # rdmsr --bitfield 15:8 -d -a 0x198 24 24 24 24 24 24 24 24 What was being asked for: # rdmsr --bitfield 15:8 -d -a 0x199 16 16 16 16 16 16 16 16 To gain further insight, it might also be worth acquiring some trace data. On an otherwise idle system, do: # perf record -a --event=power:pstate_sample sleep 300 If pressed for time, your sleep time can be less than 5 minutes, but try to get at least 100 seconds. The resulting perf.data file will be too big to include as an on-list attachment, but send it (or them) to me off-list for post processing, and I'll report back. ... Doug
WARNING: multiple messages have this Message-ID (diff)
From: "Doug Smythies" <dsmythies@telus.net> To: "'Jörg Otte'" <jrg.otte@gmail.com>, "'Pandruvada, Srinivas'" <srinivas.pandruvada@intel.com> Cc: rafael@kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, rjw@rjwysocki.net Subject: RE: [intel-pstate driver regression] processor frequency very high even if in idle Date: Wed, 30 Mar 2016 11:50:35 -0700 [thread overview] Message-ID: <002401d18ab5$0bf84a30$23e8de90$@net> (raw) In-Reply-To: <CADDKRnA5x9dK=6KZWijiP_ihrUA9Afpmqw8TSzYn9oaBeaOfKw@mail.gmail.com> On 2016.03.30 08:52 Jörg Otte wrote: > 2016-03-30 17:33 GMT+02:00 Pandruvada, Srinivas <srinivas.pandruvada@intel.com>: >> On Wed, 2016-03-30 at 13:05 +0200, Rafael J. Wysocki wrote: >>> On Wed, Mar 30, 2016 at 12:17 PM, Jörg Otte <jrg.otte@gmail.com> >>>>>> Now in v4.6-rc1 the characteristic has dramatically changed. >>>>>> If in idle the processor frequency is more or less a few >>>>>> MHz around 2500Mhz. >>>>>> I currently use acpi_cpufreq which works as usual. >>>>>> Processor: Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz >>>>>> (family: 0x6, model: 0x3c, stepping: 0x3) >> I want to reproduce this if I can. Can you give us info about your >> setup (Linux distribution, laptop model etc.)? I would like to try to reproduce the issue also. > Distro: Ubuntu 14.04.4 LTS Note that with Ubuntu 14.04, I had issues where my CPU would lock at pstate 24 (not always 24, but usually), regardless of load. However, it was always after an S3 suspend, occurred 100% of the time, and was independent of intel_pstate or acpi-cpufreq CPU frequency scaling drivers. Since changing my test server to Ubuntu server edition 16.04 (development version), I have not had those issues. While I have no proof, I have assumed the issue elimination was somehow related to the change to systemd. It might be worth observing both what the intel_pstate is asking for and what the processor is actually doing. What is being asked for: # rdmsr --bitfield 15:8 -d -a 0x199 What is being given: # rdmsr --bitfield 15:8 -d -a 0x198 An old problematic example from an idle system (mine) Note, my minimum pstate is 16: What was being given: # rdmsr --bitfield 15:8 -d -a 0x198 24 24 24 24 24 24 24 24 What was being asked for: # rdmsr --bitfield 15:8 -d -a 0x199 16 16 16 16 16 16 16 16 To gain further insight, it might also be worth acquiring some trace data. On an otherwise idle system, do: # perf record -a --event=power:pstate_sample sleep 300 If pressed for time, your sleep time can be less than 5 minutes, but try to get at least 100 seconds. The resulting perf.data file will be too big to include as an on-list attachment, but send it (or them) to me off-list for post processing, and I'll report back. ... Doug
next prev parent reply other threads:[~2016-03-30 18:50 UTC|newest] Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-29 17:24 [intel-pstate driver regression] processor frequency very high even if in idle Jörg Otte 2016-03-29 17:32 ` Jörg Otte 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 [this message] 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 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-03-31 15:10 ` Doug Smythies 2016-04-01 7:20 ` Doug Smythies 2016-04-01 7:20 ` Doug Smythies 2016-03-30 21:41 Sedat Dilek 2016-03-30 21:58 ` Rafael J. Wysocki 2016-03-30 22:23 ` Sedat Dilek 2016-03-30 22:29 ` Rafael J. Wysocki 2016-03-30 22:18 ` Srinivas Pandruvada 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 2016-03-30 22:50 ` Doug Smythies 2016-03-30 23:12 ` Srinivas Pandruvada 2016-03-31 8:10 ` Sedat Dilek 2016-03-31 14:30 ` Doug Smythies 2016-03-31 14:30 ` Doug Smythies 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-03 18:59 ` Doug Smythies 2016-04-04 5:13 ` Sedat Dilek 2016-04-04 6:14 ` Doug Smythies 2016-04-04 6:14 ` Doug Smythies 2016-04-04 14:12 ` Sedat Dilek
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='002401d18ab5$0bf84a30$23e8de90$@net' \ --to=dsmythies@telus.net \ --cc=jrg.otte@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=rafael@kernel.org \ --cc=rjw@rjwysocki.net \ --cc=srinivas.pandruvada@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: linkBe 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.