I recently bought a Macbook Pro 13" Early 2015. I was successful in installing Linux Mint 18.1 Sarah and everything worked fine but the Macbook Pro started overheating. Idle CPU temperature was around 67-70 degrees Celsius. I tried running a simple python script which printed numbers from 0 to 1 million and saw the temperatures hovering at around 90 degrees Celsius which in my opinion is very hot for a simple program. I thought it has something to do with Linux Mint and tried installing Ubuntu 16.04 which is the base for Linux Mint and still had the same heat issues. I tried Fedora and RHEL, same heat issues. I have an Asus ROG gaming laptop which is running Windows and Linux Mint on dual boot and Linux Mint runs around 70 degrees even under heavy load. I installed macfanctld and it does nothing except run fast for like 10 seconds after boot and then nothing. My question is, why does Linux run so hot on Apple hardware which has an Intel i5 processor with lower TDP than the Intel i7 on the Asus which has higher TDP rating? I really would love to use Linux on the Macbook Pro without the heat issues. **[Edit]** This is my output of lspci -k | grep -EA2 'VGA|3D': `00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) Subsystem: Apple Inc. Broadwell-U Integrated Graphics Kernel driver in use: i915 `

I utilize Mate's Hardware Sensor Monitor, and it shows the following for my device: What does each label refer to? What temperatures are considered dangerous?

I have a Samsung laptop and installed Archlinux on it. At first everything was fine, I was even surprised at how nice everything was, no driver problems, everything went smooth. I could watch videos and it would barely get hot. But after an update (with "pacman -Syu"), it started overheating (and getting slower as it starts to overheat). I'm not sure about what update was because I didn't notice it right away. I notice it the most when I'm watching videos but it is always hot and I can't really watch videos anymore because then it gets really slow. I also installed flash, I'm not sure which one worked, I think it was "chromium-pepper-flash". But I also have "flashplugin" installed. I don't think CPU frequency scaling utilities are the right solution because it was working before. What are my options? How do I detect what caused the problem? ___________________ Edit: Added some stats Running chrome with 8 text/js tabs opened (Amazon, stackexchange, wired, ...): Average temperature: 75 Celsius degrees Average %CPU: 10% Average memory: 43% _______ Same as above but with a Youtube video in fullscreen: Average temperature: 93+ Celsius degrees (had to stop before it crashed) Average %CPU: 80% Average Memory: 47% Does this mean the problem is with the GPU driver?

What is the best way to get the CPU temperature on Linux from the command line? On one small portable system, I was able to get the CPU temperature from here:

/sys/class/thermal/thermal_zone0/temp

or here:

/sys/class/thermal/thermal_zone1/temp

However some people say to look for the "coretemp" value, which doesn't seem to exist on my system. Is there an official best practice for getting CPU temperature?

What are the commands to find out fan speed and cpu temp in linux (I know lm-sensor can do the task). Is there any alternative for that?

Dell Latitude E5550 sometimes reboots without no reason. I made a script that run sensors once per second, and it contained lines like Ambient: +39.0°C Ambient: +38.0°C Ambient: +44.0°C Ambient: +38.0°C Ambient: N/A Ambient: +127.0°C Ambient: +127.0°C Ambient: +38.0°C so quite clearly one thermal sensor is failing. (CPU temp sensor seems to work.) First, why sensors show for example dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 0 RPM CPU: +46.0°C Ambient: +47.0°C SODIMM: +34.0°C Other: +30.0°C coretemp-isa-0000 Adapter: ISA adapter Package id 0: +52.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +51.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +52.0°C (high = +105.0°C, crit = +105.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +25.0°C (crit = +107.0°C) temp2: +27.8°C (crit = +105.0°C) temp3: +29.8°C (crit = +105.0°C) i.e. what are all those temperatures? Second, can I disable shutdown from the ambient thermal sensor?

This doesn't happen every time, but sometimes when watching a video, my computer seems to (almost) freeze. The screen changes every few seconds or so. Rebooting fixes the issue until the next time it happens. I noticed that the logs contain the same line every 2 seconds.

Feb 07 09:50:47 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:44 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:42 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:40 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot
Feb 07 09:50:38 spoon kernel: xhci_hcd 0000:c1:00.3: Refused to change power state from D0 to D3hot

This makes me think it's something to do with overheating, but the computer doesn't even feel warm. On boot, I see the following logs:

Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: No valid trip points!
Feb 07 09:28:21 spoon kernel: ACPI: thermal: [Firmware Bug]: Invalid critical threshold (-274000)

Not sure if this is related to the issue. My computer is new, so it shouldn't be because of old parts. Any advice on how I can further debug this? Thanks in advance!

**Edit:** The original question of this post was regarding the "average" cpu MHz as obtained via conky builtins and the command line. A further question was regarding temperatures as reported by conky vs temperatures obtained via the command line. A tertiary question was regarding per core MHz as reported by both methods. 1. The "average" MHz question has been rendered superfluous by my discovery that I'd messed up my conkey.conf file a very long time ago. There is no average cpu MHz variable in the current version of conky, and there might not have ever been. In addition. it's such a transitory measurement, I'm not sure it's actually useful at all - at least for me. 2. @terdon requested a minimal conkyrc file so other people could try to reproduce what I said I was experiencing. So I created one. I'll include it below. But creating it allowed me to see I was seeing what I expected to see - not what was actually there. It turns out that the command I had been using to get the cpu temp - ${hwmon 1 temp 3}, actually is the cpu die teperature plus the Tctl offset for fan control. The actual cpu temp can be obtained with this command: ${exec sensors -f k10temp-pci-00c3 | grep Tccd1 | cut -b 15-21}F. I don't see a way to get the actual cpu temp through conky's builtins. 3. The per core MHz question as reported by conky's builtins, and the command line. This question is still out there, but I think I know whats going, I just haven't proved it yet. At least to myself. I created the requested conky.conf - I don't use a conkyrc file. And running it next to my actual conky was giving me really interesting results. So I created another version, identical to the other, but one being aligned to the middle_left, and the other being aligned to the middle_middle. In these conky.conf files, I'm using both the builtins, and getting the stats from an exec command. Interestingly, all 4 sets of data from these two conky instances will often align very well. Sometimes almost perfectly! That was actually surprising. And the data being reported from my actual conky was almost always in the 3-4 GHz range, while the two test conky's was almost always in the 2 GHz range... So, what I think is going on is my 'production' conky.conf is rather large - with lots and lots going on. and it kicks up the cpu frequency while it's running. And then when the test conky.confs are running, they show lower GHz because they're actually being less demanding. Does this sound reasonable? Here's the test conky.conf: conky.config = { alignment = 'middle_left', background = false, update_interval = 1.5, cpu_avg_samples = 2, out_to_console = false, override_utf8_locale = true, double_buffer = true, text_buffer_size = 8192, own_window = true, own_window_transparent = true, own_window_argb_visual = true, own_window_type = 'normal', own_window_argb_value = 0, own_window_hints = 'undecorated,below,sticky,skip_taskbar,skip_pager', border_inner_margin = 20, border_outer_margin = 0, font = 'monospace:size=10', gap_x = 350, gap_y = 0, minimum_width = 450, minimum_height = 450, draw_borders = false, use_xft = true, xftalpha = 0.8, uppercase = false, maximum_width = 1024, temperature_unit = "fahrenheit", } conky.text = [[ CPU Temp: Conky Builtin 1 3: ${hwmon 1 temp 3}°F Using hwmon: ${exec awk '{print ((($0 / 1000)*1.8)+32) }' < /sys/class/hwmon/hwmon1/temp3_input }°F # Temp of the die plus the Tctl offset for fan control Using sensors Tctl : ${exec sensors -f k10temp-pci-00c3 | grep Tctl | cut -b 15-21}F # Temp of the die itself Using sensors Tccd1: ${exec sensors -f k10temp-pci-00c3 | grep Tccd1 | cut -b 15-21}F Average CPU Frequency: ${exec cat /proc/cpuinfo |grep "cpu MHz"| awk '{sum+=$4;} END{printf "%2.2f", (sum/12)/1000;}'} GHz CPU1: ${freq_g 1} GHz ${goto 170}CPU1: ${exec awk '{printf "%2.2f", ($0)/1000000;}' conky to gather, and display my Linux system stats for a long time. I noticed over a decade ago that the 'average' cpu MHz just copies the first core, it isn't an average of all cores. The command to get the average cpu frequency in conky is: ${freq_g 0}. To get the cores individually, you just use ${freq_g 1} - ${freq_g 12}. In other words, 0 is supposed to be the average, not the first core, and individually, you start counting at 1, through how many cores you have. But 0 and 1 both always display the exact same thing. Checking in bash, I run this command: grep "cpu MHz" corectrl to control the cpu governor, and control the gpu. When I set the cpu to 'performance mode', the frequency of the cpu jumps up accordingly - from the low 2 GHz range, to the low 4 GHz range, as reported by conky. But when I check the output with the above grep command, all the cores are showing that they're running in the low to mid 3 GHz range. I'm not really expecting precision numbers here, just pretty close ballpark numbers. Or, in other words, I expect precision numbers, but they're going to change so many time per second that I expect them to be reported differently. The biggest problem I'm having is that my grep command rarely shows the cpu frequency going above 4 GHz, while conky rarely shows it below 4 GHz - in performance mode. Should I just display the outputs from my grep command in conky, and just accept the two outputs aren't going to jive? ---- I'm having a very similar issue with conky's built in cpu temperature detection. I can display what conky's builtin is reporting, and the results using sensors, and hwmon. The conky builtin is almost always showing the lowest temperature. The other two methods bounce around a lot more, and usually show higher temperatures then conky's builtin. And I mean they might show a ten degree difference, or more, for a long time.

I use thermald to prevent my Surface Pro 7 from overheating, using the intel powercap rapl driver (rapl_controller in thermald). I would also like to use the same rapl driver to reduce power consumption when on battery, but I can't find a way to do that aside from copying and pasting into the terminal each time: sudo systemctl stop thermald && sudo powercap-set intel-rapl -z 0 -c 0 -l 5000000 -s 12000000 && sudo powercap-set intel-rapl-mmio -z 0 -c 0 -l 5000000 -s 12000000 Is there a way to get **thermald** to change the TargetState for the rapl_controller to 5000000 when on battery? Here is my current thermal-conf.xml for reference:

Surface Pro Intel Thermal Workaround
        *
        QUIET
        
                16750 
                4000
                12000 
                12000
        
        
                
                        cpu
                        
                                
                                        x86_pkg_temp
                                        67000 
                                        passive
                                        SEQUENTIAL
                                        
                                                1
                                                rapl_controller
                                                1
                                                12750000

EDIT: I ended up creating a systemd service to check the battery status every minute and run the relevant command. I'd still be interested to know if it's possible through thermald.

I have Ubuntu 14.04. I am using the i3 window manager and want to display CPU temperature in the i3-statusbar. Folder /sys/devices/platform/coretemp.0 does not exists and neither does /proc/acpi/thermal_zone. What should I do? I do not want to use lm-sensors or similar.

I'm trying to enable sysstat to take temperature readings, so that I have past temperature information to diagnose host failures in the future. I tried this command to get temperature information:

$ sar -m TEMP
Requested activities not available in file /var/log/sysstat/sa22

Here's what the sar man page has to say about this:

-m { keyword [,...] | ALL }
       Report power management statistics.  Note that these statistics depend on sadc's option "-S  POWER"  to
       be collected.

       Possible keywords are CPU, FAN, FREQ, IN, TEMP and USB.

       [...]

       With  the  TEMP  keyword,  statistics about devices temperature are reported.  The following values are
       displayed:

According to this, power management information (which temperature is a subset of) is not logged by default. So, I changed the file /etc/sysstat/sysstat to enable it. I changed this:

# Parameters for the system activity data collector (see sadc(8) manual page)
# which are used for the generation of log files.
# By default contains the `-S DISK' option responsible for generating disk
# statisitcs. Use `-S XALL' to collect all available statistics.
SADC_OPTIONS="-S DISK"

into this:

SADC_OPTIONS="-S DISK,POWER"

Another issue on the [sysstat issue tracker](https://github.com/sysstat/sysstat/issues/156) said that sysstat requires lm-sensors to function, so I installed that package too. Here's the output of sensors:

$ sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +119.0°C)
temp2:        +29.8°C  (crit = +119.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +89.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +86.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +88.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +89.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +89.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +88.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +87.0°C  (high = +82.0°C, crit = +100.0°C)

nvme-pci-0800
Adapter: PCI adapter
Composite:    +38.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +38.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +37.9°C  (low  = -273.1°C, high = +65261.8°C)

So this does seem to correctly detect my temperature sensors. I also tried waiting ten minutes for another collection to happen. (My system is configured to log every ten minutes, at :05, :15, :25, etc.) Unfortunately, after all that, I still get the same error:

$ sar -m TEMP
Requested activities not available in file /var/log/sysstat/sa22

Opening the following page on my browser rises my CPU temperature to over 85ºC (and continues that way as long as the page is open): https://mathoverflow.net/questions/382270/reflection-principle-vs-universes . I am using void linux, and tested this both on firefox and on chromium. My friend using windows also noticed a high amount of CPU usage when visiting that page. What could be the cause of this?

I have a fresh install of Manjaro running on a server i have built. I have an AMD Genoa 9334 ES. On windows I can detect the correct core temperature (see attached images). On the linux OS (Ubuntu 24.04, Debian Bookworm latest + Manjaro) lm-sensors is not detecting the thermal sensors in the CPU core. The K10temp is giving the Package temperature on the motherboard sensors rather than the core. The fact this is an ES should not come into play. As it works on Windows I know its not a BIOS issue. I am running the latest kernel (6.8.8-2-MANJARO). Linux temperatures: Windows temperatures: Some extra information: (output of pwmconfig + sensors-detect CPU) # pwmconfig version 3.6.0+git This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. /usr/bin/pwmconfig: There are no pwm-capable sensor modules installed Output of sensors detect: # sensors-detect version 3.6.0+git # System: Supermicro Super Server # Board: Supermicro H13SSL-NT # Kernel: 6.8.8-2-MANJARO x86_64 # Processor: AMD Eng Sample: 100-000000897-03 (25/17/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... NoVIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No AMD Family 19h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No *IMPORTANT FOR ANYONE HAVING THE SAME ISSUE* Ubuntu and Debian did not have support for AMD 19h when I ran sensors-detect (unsure of the kernel I was using) but Manjaro does here. The Genoa 9334 is zen 4 which as far as im aware is I think it should be detecting AMD Family 19h thermal sensors here. My question is simple, how can I force it to install the module for this even though its not detecting it? I know the sensor exists and can be accessed. Any help is appriciated but please don't tell me to run sensors-detect or that k10temp showing the packages it the best we can do because that is not the case. I am ready to cry and pull my hair out even my eyebrows.

I've got a USB enclosure for five 3.5" drives, but not only is the fan very loud, it also cools idle drives down to under 30°C, which according to data floating around the Internet increases chances for drive failure. Is it possible to turn this fan off and on? Then I could write a script to keep drives in a safe range of temperatures. More details on the enclosure: * 9558U3 from Orico * USB3.0, JBOD * IEC (power) connector

This is a follow-up question to *https://unix.stackexchange.com/questions/148731/how-to-reduce-temperature-on-a-dell-xps-l502x* . After reading the answer, I noticed that my harddrive is spinning constantly, even when running TLP in bat-mode (mostly default settings, laptop-mode=5). **What I already do** * /tmp is mounted as a tmpfs. AFAIK this is not recommended for /var/tmp, is it? * TLP is running with this configuration * / and /boot are ext4 mounted with commit=15,noatime * / is mounted from a LUKS partition, is this a problem? **What I am searching for** I guess that constant disk access is the major cause of my disk spinning all the time. Are there any other ways to reduce disk access and/or ways to allow the disk to spin down?

I'm on a Dell laptop with Sandy Bridge Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz CPU running a 5.15.0-100-generic Linux kernel. The CPU goes up to 3.4GHz (as both the MATE CPU Frequency Monitor applet shows and as /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq shows) and it seems to get stuck at a lower frequency whenever the temperatures reach a certain threshold. Then it won't go up to 3.4GHz again unless both the temperature decreases (putting the laptop in the freezer for a bit helps in that regard) and the computer is rebooted. Is there any way to force it back up without at least the reboot step? I have my MATE CPU Frequency Monitor set to Performance and I've tried sudo cpufreq-set -g performance, and writing 3400000 to /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_min_freq (seemed like it could do it) but none work other than both decreasing the temperature (that alone won't make the frequency go back up) and rebooting (that alone doesn't work either unless the temperature is low at the time of reboot). I care because the lower frequenciese mess up my microbenchmarks.

Sometimes, my laptop with Intel Core i3 is overheating. For example today. $ sensors radeon-pci-0300 Adapter: PCI adapter temp1: +59.0°C (crit = +120.0°C, hyst = +90.0°C) coretemp-isa-0000 Adapter: ISA adapter Package id 0: +58.0°C (high = +100.0°C, crit = +100.0°C) Core 0: +57.0°C (high = +100.0°C, crit = +100.0°C) Core 1: +55.0°C (high = +100.0°C, crit = +100.0°C) BAT0-acpi-0 Adapter: ACPI interface in0: 15.30 V How to use thermald to fix it? The file /etc/thermald/thermal-conf.xml is missing. Should I create one? How would it look like?

I have ran sensors-detect and lm_sensors still returns the following. radeon-pci-0100 Adapter: PCI adapter temp1: +511.0°C (crit = +120.0°C, hyst = +90.0°C) coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +47.0°C (high = +87.0°C, crit = +105.0°C) Core 0: +46.0°C (high = +87.0°C, crit = +105.0°C) Core 1: +47.0°C (high = +87.0°C, crit = +105.0°C)

I'm running Ubuntu 20.04 on a Thinkpad T14s. When I push the CPUs hard, i.e. with stress-ng --cpu 8 --tz -t 60, I watch the core temps spike to 90°C before I panic and stop the stress test. The fan will start eventually, but not nearly soon enough, and from experiments with lesser stress levels it doesn't seem that the fan will be able to dump enough heat anyway. I have had some good luck using thinkfan to make the fan more responsive, and that buys me some nice wiggle room at medium-high temps, but it doesn't make enough of a difference at those high spikes. I also installed cpupower-gui. It shows me that my system is already running in the powersave mode, with a max CPU speed of 4900 MHz. If I bring down the CPUs to around 3400 MHz, the system seems to stabilize quite nicely at about 70°-75° at full load with or without thinkfan. (It's a little warmer without thinkfan.) So, I've got a solution, but I'm unhappy with it; it seems that just permanently capping my CPUs isn't supposed to be the right answer. It is my very limited understanding that the intel_pstate driver is supposed to be implementing thermal control. I don't know how to verify if it is doing its job or not; from a functional practical perspective, it doesn't seem to be. My questions: is there a better solution than pegging the CPU speed as I've done? And am I better off running with more aggressive fans via thinkfan, or should I drop the CPU power further and stick with the built-in auto fan curve?

I have bought a fanless PC, and it is really important for me to have some form of power management for this PC, because currently I don't under Qubes, and the result is that if I do something that puts a lot of load on the CPU like playing a full-screen video in Firefox, the CPU overheats and the system (firmware?) automatically goes into emergency power-saving mode, which involves making the CPU go really slow. I have transferred responsibility to the Linux kernel for power management by adding cpufreq=dom0-kernel to the Xen command line. This doesn't help. I have then tried to switch from the intel pstate driver (which doesn't work with my Rocket Lake CPU, an Intel® Core™ i7-11700) to the acpi-cpufreq driver by adding intel_pstate=disable. This also doesn't help - sudo cpupower frequency-info shows "no or unknown cpufreq driver is active on this CPU". I then installed the latest version of thermald on my dom0 domain, but thermald is not able to find any temperature sensors:

[WARN]Thermal DTS: No coretemp sysfs found

I have ran sudo sensors-detect, but that didn't help. I have then ran modprobe processor_thermal_rapl and modprobe processor_thermal_device and restarted thermald, but it still showed the same errors. My motherboard is an Asus TUF GAMING B560M-PLUS WIFI. Please help me to enable some form of thermal throttling / frequency governor on this PC, other than the firmware's emergency thermal throttling.