Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #66678
| From | l0f4r0@tuta.io |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" |
| Date | 2020-04-02 15:30 +0200 |
| Message-ID | <zR84W-7bo-7@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <zlslj-F6-1@gated-at.bofh.it> <zqnuF-nF-3@gated-at.bofh.it> <zIbY5-74w-5@gated-at.bofh.it> <zQUbD-6VZ-3@gated-at.bofh.it> <zQUbD-6VZ-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi again, 2 avr. 2020 à 00:30 de l0f4r0@tuta.io: > => From now on, it seems I have 2 workarounds: turbo boost deactivation and Debian thermald. > I guess I should do some A/B testing... > I've just uninstalled thermald manually built from 01.org, and installed the official Debian package as suggested instead. I've adopted a zero-configuration approach. Here is my situation by default: systemctl status thermald.service thermald.service - Thermal Daemon Service Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-04-01 23:59:38 CEST; 15h ago Main PID: 30158 (thermald) Tasks: 2 (limit: 4915) Memory: 2.3M CGroup: /system.slice/thermald.service <http://system.slice/thermald.service> └─30158 /usr/sbin/thermald --no-daemon --dbus-enable avril 01 23:59:38 thermald[30158]: sensor id 10 : No temp sysfs for reading raw temp avril 01 23:59:38 thermald[30158]: sensor id 10 : No temp sysfs for reading raw temp avril 01 23:59:38 thermald[30158]: sensor id 10 : No temp sysfs for reading raw temp avril 01 23:59:38 thermald[30158]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml" avril 01 23:59:38 thermald[30158]: error: could not parse file /etc/thermald/thermal-conf.xml avril 01 23:59:38 thermald[30158]: sysfs open failed avril 01 23:59:38 thermald[30158]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml" avril 01 23:59:38 thermald[30158]: error: could not parse file /etc/thermald/thermal-conf.xml avril 01 23:59:38 thermald[30158]: I/O warning : failed to load external entity "/etc/thermald/thermal-conf.xml" avril 01 23:59:38 thermald[30158]: error: could not parse file /etc/thermald/thermal-conf.xml NB : indeed I don't have /etc/thermald/thermal-conf.xml but it seems that thermald can work without it (https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811788). grep -i pstate /boot/config-$(uname -r) CONFIG_X86_INTEL_PSTATE=y cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver intel_pstate intel_pstate intel_pstate intel_pstate intel_pstate intel_pstate intel_pstate intel_pstate cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.60 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 887 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes Logs "CPUX: Package temperature above threshold, cpu clock throttled (total events = XXX)" are still present in journalctl :( Do you still think thermald can help me? If so what would you try/configure please? Maybe there is simply something required by thermald I haven't installed yet? Thank you for your appreciated help :) Best regards, l0f4r0
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Recurrent alerts "Package temperature above threshold, cpu clock throttled" <l0f4r0@tuta.io> - 2020-01-05 19:10 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" Nicholas D Steeves <nsteeves@gmail.com> - 2020-01-06 05:40 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" <l0f4r0@tuta.io> - 2020-01-19 19:30 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" Nicholas D Steeves <nsteeves@gmail.com> - 2020-01-20 22:30 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" Ben Hutchings <ben@decadent.org.uk> - 2020-03-09 02:20 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" l0f4r0@tuta.io - 2020-03-08 22:50 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" Ben Hutchings <ben@decadent.org.uk> - 2020-03-09 02:20 +0100
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" l0f4r0@tuta.io - 2020-04-02 00:40 +0200
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" l0f4r0@tuta.io - 2020-04-02 15:30 +0200
Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled" <l0f4r0@tuta.io> - 2020-01-20 00:30 +0100
csiph-web