LinuxQuestions.org - [SOLVED] Linux: Overheating issue?

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Linux: Overheating issue? (https://www.linuxquestions.org/questions/linux-newbie-8/linux-overheating-issue-4175630273/)

Linux: Overheating issue?

Hello, LQ members!
I'm new to this forum (and to Slackware, actually). This is my second post (the first one was a tiny self-introduction).
This is my question: does Linux have overheating issues?
My previous computer was an old Macbook Pro with Mac OS X and Devuan installed in dual boot. With the former I had no problems at all, with the latter, the machine turned really HOT and the fan got really LOUD, especially in summer. It was really annoying for the people around me and I was really afraid to burn the machine, so I changed it.
Now I'm using a Thinkpad X220 with Windows 10 and Slackware in dual boot. With Windows no problem; with Slack sometimes no problem, sometimes, especially when slackbuilding, the machine turns quite hot the fan gets really fast and doesn't stop, even after the program is installed, and I need to shut down the machine in order to stop it.

What's the problem here?
Is there a solution?

Thank you very much.
Greetings,
Matteo

Quote:

Originally Posted by mathieu pretre (Post 5858216)

Well, you've jumped into the deep end starting with Slackware!

Anyhow, I do have a very similar problem myself when I use ffmpeg to convert videos. In that: it only happens when I am actually doing that, but not otherwise. It sounds (like with my heating issues) like your machine doesn't have good enough cooling and it's clearly a over-heating issue that's your problem here.

It does seem a little strange to me that Windows has no issue, but Linux does. It may well be a clue. I'd think it would be the other way around if anything. I would suggest upgrading cooling, but I'm not sure how you could do that given the machine we are talking about. I can't say I'm that familiar with Slackware, although it's still Linux as much as the distribution I use (which is not Slackware Linux).

I just wonder if you're getting any MCE (Machine Check Event) warnings/errors in your kernel log, try the following command when it's fan starts spinning really fast:

Code:

dmesg | grep -i mce

This might help pin point the problem or at least confirm it's actually over-heating. There's also the sensors program you can also use to check bad temperatures.

Is this a desktop or laptop system?

Quote:

Originally Posted by AwesomeMachine (Post 5858423)

Is this a desktop or laptop system?

I *think* the OP's talking about this sucker. :)

But I could be wrong...

Windows tends to throttle the cpu almost all the time, which extends battery life and makes the system run cooler, at the expense of performance! But that's OK, because you'll want to buy another faster system sooner! Linux throttles the cpu wide open when necessary, so the battery runs out faster and the system runs hotter, but you get the performance you paid for!

Slackware includes a command line tool called "sensors." You can use it to check the temperature (I learned that thanks to your question--I was looking for lm-sensors).

Code:

$ sensors

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +33.0°C  (high = +80.0°C, crit = +100.0°C)

Core 0:        +30.0°C  (high = +80.0°C, crit = +100.0°C)

Core 1:        +29.0°C  (high = +80.0°C, crit = +100.0°C)

Make sure that the air vents are clean and free of dust. Dust build-up is insidious and harmful.

By the by, I started with Slackware (v. 10 it was), and I'm glad I did. Slackware teaches you to understand Linux.

Quote:

Windows tends to throttle the cpu almost all the time,

No it doesn't.
Overheating has nothing to do with the OS you are running, but the TASK you are running under it.
CPU throttling because the temperature is getting too high is done by the BIOS, not the OS.

Quote:

Originally Posted by frankbell (Post 5858542)

Slackware includes a command line tool called "sensors." You can use it to check the temperature (I learned that thanks to your question--I was looking for lm-sensors).

Code:

$ sensors

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +33.0°C  (high = +80.0°C, crit = +100.0°C)

Core 0:        +30.0°C  (high = +80.0°C, crit = +100.0°C)

Core 1:        +29.0°C  (high = +80.0°C, crit = +100.0°C)

Thank you very much!
I figured out some possible solutions with the help of some useful tools:
1. xfce4-cpufreq-plugin helps you to figure out what the frequency of your CPU is (downloaded from SlackBuild.org)
2.

Code:

$ top

shows you the processes currently running on your computer and the usage of your CPU in percentage (if you want a graphical tool, you can also use System Monitor). Just to experiment a little, I slackbuilt qt5. I realized that the compiler (cc1plus) used 100% of my CPU. At that point I downloaded and slackbuilt another tool:
3. cpulimit: this little application allows you to decide how much of the CPU you want every process to use. In my case, I decided that the compiler should not exceed the 50% of the CPU:

Code:

# cpulimit --limit=50 --exe=cc1plus

that affected the performances, but also the temperature: the CPU never exceeded 70°C during the slackbuild
4.

Code:

$ sensors

Sounds good?

PS: yes, Slackware is a fantastic distro. Some people find it difficult. I actually find it easier and leaner than other distributions...

And you're welcome, given that I had mentioned the "sensors" program in post #2.

Quote:

Originally Posted by dave@burn-it.co.uk (Post 5858711)

If the os doesn't throttle the cpu in time, the BIOS will. And if even the BIOS fails, the cpu will shut itself down. But the os is able to throttle the cpu. Overheating has nothing to do with the os, but how hot the system runs within safe boundaries is up to the os.

Isn't it amazing how you manage to argue and make out I am wrong and yet still agree at the same time???