From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755590AbcKEOEl (ORCPT ); Sat, 5 Nov 2016 10:04:41 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:36847 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754215AbcKEOEj (ORCPT ); Sat, 5 Nov 2016 10:04:39 -0400 Date: Sat, 5 Nov 2016 15:04:34 +0100 From: Pavel Machek To: "Pandruvada, Srinivas" 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 Message-ID: <20161105140434.GA3755@amd> 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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <20161105135313.GB3933@amd> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat 2016-11-05 14:53:13, Pavel Machek wrote: > Hi! >=20 > > > Ok, can do, let me recompile and reboot. > > >=20 > > > >=20 > > > > When temperature limit is reached=A0acpi_processor_ppc_notifier() > > > > should > > > > be called. > > >=20 > > > 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. > >=20 > > Also try > >=20 > > Don't run workload, just on an idle system. > >=20 > > # echo 1 > /sys/class/thermal/cooling_device2/cur_state > > monitor the scaling_max_freq, it should reduce > >=20 > > # echo 2 > /sys/class/thermal/cooling_device2/cur_state > > monitor the scaling_max_freq, it should reduce >=20 > 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. =2E..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? Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgd5vIACgkQMOfwapXb+vLCKwCgmZHxamvsCLOBcG6b3dk2kmwL xaUAoLPm/uX2MiwGP10ZVn91H7Xz+9Ht =n3aK -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF--