linux-kernel - Re: cpufreq/thermal regression in 6.10

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] [day] [month] [year] [list]

Date: Sat, 22 Jun 2024 14:14:00 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Jens Glathe <jens.glathe@...schoolsolutions.biz>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, Johan Hovold <johan@...nel.org>, 
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>, Daniel Lezcano <daniel.lezcano@...aro.org>, 
	Viresh Kumar <viresh.kumar@...aro.org>, Zhang Rui <rui.zhang@...el.com>, 
	Lukasz Luba <lukasz.luba@....com>, Steev Klimaszewski <steev@...i.org>, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org, regressions@...ts.linux.dev
Subject: Re: cpufreq/thermal regression in 6.10

On Fri, Jun 21, 2024 at 10:00 PM Jens Glathe
<jens.glathe@...schoolsolutions.biz> wrote:
>
> Hi there,
>
> thank you for the fast fix. Applied, built, installed. Test is
> successful, performance core scaling up to 2995200 comes back when skin
> temp drops below 55°C.
>
> Tested-by: Jens Glathe <jens.glathe@...schoolsolutions.biz>

Great, thanks for testing!

I'll submit the patch shortly and it would be good if the others
affected by this issue could try it to confirm that it doesn't regress
anything.


> On 6/21/24 18:41, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Fri, Jun 21, 2024 at 5:53 PM Jens Glathe
> > <jens.glathe@...schoolsolutions.biz> wrote:
> >> Hi there,
> >>
> >> unfortunately I experienced the issue with the fix applied. I had to
> >> revert this and  the original commit to get back to normal behaviour. My
> >> system (also Lenovo Thinkpad X13s) uses the schedutil governor, the
> >> behaviour is as described from Steev and Johan. The full throttling
> >> happened during a package build and left the performance cores at 940800.
> > So can you please test the attached patch, on top of the fix?
>