[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled"



Hi l0f4r0,

Reply follows inline.

<l0f4r0@tuta.io> writes:

> Hi team,
>
> Multiple times per hour (despite no notable CPU-consuming activity), I
> get something like the following journalctl crit/2 entry:
>
> kernel: CPUX: Package temperature above threshold, cpu clock throttled
> (total events = Y) where X=[0-7] (I have a quad-core i7 with
> hyperthreading activated) and Y is generally a 4-digit number.
>

While I'm very much a junior member of the team, I have noted similar
behaviour on a laptop as old as an X220 and wonder if it might be due to
Spectre mitigations.  I have not noticed such log entries after
disabling hyperthreading.  FYI, as someone who works with realtime audio
I've found that hyperthreading is detrimental to worst-case latency.
eg: after many hours trying to workaround troublesome unpredictable
latency spikes the solution to disable hyperthreading emerged as the
simplest solution.

> There are different threads about it on the Internet. Some seem to
> indicate a kernel issue, others says it's sensors or CPU paste fault
> and others don't explain anything and recommend to change the
> threshold or deactivate the alerts themselves (!).
>

Yeah, you're right, that seems ill-advised, even if one can depend on
the EC to shut down the laptop in case of thermal overload.  Have you
tried disabling CPU freq boost?  When the ambient temperature is above
27°C my X220 and X230 need to have boost disabled to avoid
overheating/throttling.

> Are you aware of anything Debian-kernel-related please (I didn't see
> any such bug at
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=linux-image-4.19.0-6-amd64
> though) that could help me regarding that matter, considering the fact
> I'm on Debian 10 (kernel 4.19.67-2+deb10u2) with an amd64 Lenovo
> ThinkPad X390?  NB: My laptop is brand new, so I'm not really
> convinced of an hardware issue at this stage (it cannot be totally
> excluded though).
>

Sorry, I'm not aware of any, but someone else might be!

> Thank you in advance and Happy GNU Year! :)
> Best regards,
> l0f4r0

Thanks, you too! :-)


Best,
Nicholas

Attachment: signature.asc
Description: PGP signature


Reply to: