Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934884AbcKDOHg (ORCPT ); Fri, 4 Nov 2016 10:07:36 -0400 Received: from mga02.intel.com ([134.134.136.20]:60834 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934836AbcKDOHe (ORCPT ); Fri, 4 Nov 2016 10:07:34 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,443,1473145200"; d="scan'208";a="1055201393" From: "Pandruvada, Srinivas" To: "linux-kernel@vger.kernel.org" , "pavel@ucw.cz" , "viresh.kumar@linaro.org" , "linux-pm@vger.kernel.org" , "rjw@rjwysocki.net" CC: "Zhang, Rui" , "linux-acpi@vger.kernel.org" Subject: Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build Thread-Topic: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build Thread-Index: AQHSNqR6E9PvsljNE0SLAUXkZpyWbA== Date: Fri, 4 Nov 2016 14:05:20 +0000 Message-ID: <1478268311.26953.17.camel@intel.com> References: <20161104083849.GA32688@amd> <20161104085830.GA4089@amd> In-Reply-To: <20161104085830.GA4089@amd> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.168.45] Content-Type: text/plain; charset="utf-8" Content-ID: MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id uA4E7dok021813 Content-Length: 2779 Lines: 80 On Fri, 2016-11-04 at 09:58 +0100, Pavel Machek wrote: > On Fri 2016-11-04 09:38:49, Pavel Machek wrote: > > > > [...] > > What is worse, they go to low frequency even with "performance" > governor on v4.8-rc1?! > > pavel@duo:/sys/devices/system/cpu/cpu0/cpufreq$ sudo cat > /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq ; sudo cat > /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq  ; sudo cat > /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq ; sudo cat > /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq  ; sudo cat > /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq  ; sudo cat > /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq > 1000000 > 1000000 > 1000000 > 1000000 > 1833000 > 1833000 > 1000000 > 1000000 > 1833000 > 1833000 > 1000000 > 1000000 > pavel@duo:/sys/devices/system/cpu/cpu0/cpufreq$ grep -i > . /sys/devices/system/cpu/cpu0/cpufreq/* > /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 > /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1000000 You are having thermal issue, so the BIOS is forcing to lowest possible freq. Just for a test only, boot by adding to your kernel command line during boot  processor.ignore_ppc=1  > grep: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: > Permission denied > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1833000 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:1000000 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:10000 > /sys/devices/system/cpu/cpu0/cpufreq/freqdomain_cpus:0 1 > /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:18 > 33000 > 1333000 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:cons > ervative > powersave schedutil ondemand performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:acpi-cpufreq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed: > grep: /sys/devices/system/cpu/cpu0/cpufreq/stats: Is a directory > pavel@duo:/sys/devices/system/cpu/cpu0/cpufreq$ > > Let me try v4.9-rc2... that works ok (cpus at the high frequency > during the kernel build). Unfortunately that sends my cpus to 99C > temperature range (and eventually forces emergency shutdown). This we have to debug. Do you see same line like  " /sys/devices/system/cpu/cpu0/cpufreq/bios_limit:1000000 " If not we need to find out why. I suggest enter kernel bugzilla. I will add couple of more suggestion to debug. Thanks, Srinivas