linux-kernel - Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 5 Nov 2016 15:04:34 +0100
From:   Pavel Machek <pavel@....cz>
To:     "Pandruvada, Srinivas" <srinivas.pandruvada@...el.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Zhang, Rui" <rui.zhang@...el.com>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        "rjw@...ysocki.net" <rjw@...ysocki.net>,
        "viresh.kumar@...aro.org" <viresh.kumar@...aro.org>,
        "ibm-acpi-devel@...ts.sourceforge.net" 
        <ibm-acpi-devel@...ts.sourceforge.net>,
        "ibm-acpi@....eng.br" <ibm-acpi@....eng.br>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: v4.8-rc1: thinkpad x60: running at low frequency even during
 kernel build

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?

Best regards,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)