Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755256AbcKEOTS (ORCPT ); Sat, 5 Nov 2016 10:19:18 -0400 Received: from mga06.intel.com ([134.134.136.31]:57963 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754498AbcKEOTQ (ORCPT ); Sat, 5 Nov 2016 10:19:16 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,597,1473145200"; d="scan'208";a="782869960" From: "Pandruvada, Srinivas" To: "pavel@ucw.cz" CC: "linux-kernel@vger.kernel.org" , "Zhang, Rui" , "linux-pm@vger.kernel.org" , "platform-driver-x86@vger.kernel.org" , "rjw@rjwysocki.net" , "viresh.kumar@linaro.org" , "ibm-acpi-devel@lists.sourceforge.net" , "ibm-acpi@hmh.eng.br" , "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: AQHSNqR6E9PvsljNE0SLAUXkZpyWbKDJwJWAgAAZhgCAABIcgIAA6rGAgAADagCAAAWkgIAAAywAgAAEDoA= Date: Sat, 5 Nov 2016 14:19:13 +0000 Message-ID: <1478355545.22182.1.camel@intel.com> References: <20161104083849.GA32688@amd> <20161104085830.GA4089@amd> <1478268311.26953.17.camel@intel.com> <20161104204439.GA2581@amd> <20161104221600.GA7007@amd> <1478301649.7947.3.camel@intel.com> <20161105132049.GC10310@amd> <1478352782.19557.7.camel@intel.com> <20161105135313.GB3933@amd> <20161105140434.GA3755@amd> In-Reply-To: <20161105140434.GA3755@amd> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.157.235] Content-Type: text/plain; charset="utf-8" Content-ID: <90D3E5104A78D041A7DBAED7458C83B0@intel.com> 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 uA5EJc8i025657 Content-Length: 1592 Lines: 54 On Sat, 2016-11-05 at 15:04 +0100, Pavel Machek wrote: > On Sat 2016-11-05 14:53:13, Pavel Machek wrote: > > > > Hi! > > > > > > > > > > > > > Ok, can do, let me recompile and reboot. > > > > > > > > > > > > > > > > > > > When temperature limit is > > > > > reached acpi_processor_ppc_notifier() > > > > > should > > > > > be called. > > > > > > > > No, that's not correct for ACPI passive trip points, is it? If > > > > I > > > > recall correctly, those should be monitored even when > > > > temperature is > > > > below them so that it does not reach them...? > > > No if BIOS is sending PPC, it will be called. You can try first > > > in 4.8. > > > > > > Also try > > > > > > Don't run workload, just on an idle system. > > > > > > # echo 1 > /sys/class/thermal/cooling_device2/cur_state > > > monitor the scaling_max_freq, it should reduce > > > > > > # echo 2 > /sys/class/thermal/cooling_device2/cur_state > > > monitor the scaling_max_freq, it should reduce > > > > Yes, this seems to work. scaling_max goes to 1.5, then 1.1. Also > > under > > load, scaling_max_freq changes. But at that point, we are already > > around 98C... and bios_limit stays the same all the time in v4.9. > > ...while in v4.8-rc1, bios limit goes to 1.0 GHz at 90C, and > temperature just doesn't go above that. > > Does it make sense to try with v4.8-final? I sent some suggestion to try in previous email to add more prints and enable debug in acpi-cpufreq. Let's try that first. We need to fix anyway even if 4.8-final has this issue. Thanks, Srinivas > > Best regards, > Pavel