Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757534AbcCaPKd (ORCPT ); Thu, 31 Mar 2016 11:10:33 -0400 Received: from cmta5.telus.net ([209.171.16.78]:49541 "EHLO cmta5.telus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757047AbcCaPKb convert rfc822-to-8bit (ORCPT ); Thu, 31 Mar 2016 11:10:31 -0400 X-Authority-Analysis: v=2.1 cv=QPGVPV/L c=1 sm=2 tr=0 a=zJWegnE7BH9C0Gl4FFgQyA==:117 a=zJWegnE7BH9C0Gl4FFgQyA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=Pyq9K9CWowscuQLKlpiwfMBGOR0=:19 a=IkcTkHD0fZMA:10 a=eVYlwL0TDKzaUm1s0t8A:9 a=QEXdDO2ut3YA:10 X-Telus-Outbound-IP: 173.180.45.4 From: "Doug Smythies" To: "=?utf-8?Q?'J=C3=B6rg_Otte'?=" Cc: "'Rafael J. Wysocki'" , "'Linux Kernel Mailing List'" , , "'Rafael J. Wysocki'" , "'Srinivas Pandruvada'" References: <4187911.uaFVupaTVL@vostro.rjw.lan> <1459352017.13525.45.camel@intel.com> <002401d18ab5$0bf84a30$23e8de90$@net> <1459364336.13525.69.camel@linux.intel.com> <1459369587.13525.75.camel@linux.intel.com> <002701d18b5b$22ea72d0$68bf5870$@net> In-Reply-To: <002701d18b5b$22ea72d0$68bf5870$@net> Subject: RE: [intel-pstate driver regression] processor frequency very high even if in idle Date: Thu, 31 Mar 2016 08:10:25 -0700 Message-ID: <003001d18b5f$748d3420$5da79c60$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8BIT X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdGLLv7MHgs7AILJQgirHrp+XHtjlAAKu6MgAAEsvcA= Content-Language: en-ca Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 855 Lines: 33 On 2016.03.31 07:40 Doug Smythies wrote: > On 2016.03.31 02:24 Jörg Otte wrote: >> >> jojo@fichte:/sys/devices/system/cpu/cpufreq/policy0$ cat scaling_governor >> powersave >> >> turbostat -i 1 --msr=0x199 >> CPUID(7): No-SGX ... [cut]... > Very Interesting. > > I would still like to get a trace sample to post process. > Copied from a previous e-mail: > > 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. Never mind. I had not seen some of the e-mails, in particular the one where Rafael had figured out the issue. ... Doug