[Letux-kernel] thermal madness

[Andreas Kemnade]

Hi,

On Sat, 14 Sep 2019 12:28:06 +0200
"H. Nikolaus Schaller" <hns at goldelico.com> wrote:

> > Am 14.09.2019 um 12:23 schrieb Andreas Kemnade <andreas at kemnade.info>:
> > 
> > On Fri, 13 Sep 2019 22:27:11 +0200
> > Andreas Kemnade <andreas at kemnade.info> wrote:
> >   
> >> some more testing here:
> >> root@(none):/# cpufreq-info 
> >> cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
> >> Report errors and bugs to cpufreq at vger.kernel.org, please.
> >> analyzing CPU 0:
> >>  driver: cpufreq-dt
> >>  CPUs which run at the same hardware frequency: 0
> >>  CPUs which need to have their frequency coordinated by software: 0
> >>  maximum transition latency: 300 us.
> >>  hardware limits: 300 MHz - 1000 MHz
> >>  available frequency steps: 300 MHz, 600 MHz, 800 MHz, 1000 MHz
> >>  available cpufreq governors: conservative, userspace, powersave, ondemand, performance
> >>  current policy: frequency should be within 300 MHz and 1000 MHz.
> >>                  The governor "ondemand" may decide which speed to use
> >>                  within this range.
> >>  current CPU frequency is 600 MHz (asserted by call to hardware).
> >>  cpufreq stats: 300 MHz:94.86%, 600 MHz:2.49%, 800 MHz:0.92%, 1000 MHz:1.73%  (51)  
> > 
> > should this be 1000Mhz: 0%? If not enabled the boost switch.  
> 
> I had it enabled... 
> 
> And we can remove the turbo-mode; tag anyways as soon as thermal throttling works.
> 
I am not sure about that. How do we test that 1Ghz works well? I
remember hw troubles not showing up in memtest but in gcc giving
internal errors and corrupted filesystems. So maybe compiling the
kernel in 1Ghz would be a good test. Or compiling anything with a
reproducable build infrastructure. Debian pbuild system e.g. should
give the same build results everywhere.

Regards,
Andreas