Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ever since i started using kernel 2.6, I keep getting messages saying my cpu temperature is above threshold and the system is running in modulated clock mode. This has happened with 2.6.3, .4, and .5. Any consoles I have open will give me this message several times a second.
This happens anytime I run a program that uses my 3d card (Radeon) such as tuxracer and some screensavers. It also happens during other intensive tasks, ie compiling a kernel.
I doubt that my temperature is really dangerously high since these are things I had done under kernel 2.4 with no problem.
Anybody else have this problem?
Is there a way to change the threshold, disable this feature, or otherwise solve this problem?
If you recompile, removing support for temperature sensors, then perhaps this may go away. A better thing to do would be to figure out IF your CPU is too hot, and if not, how to adjust the "Too Hot" temperature.
ok, installing a kernel module for my sensors (asb100 for ASUS motherboard) has allowed me to watch the cpu temp with gkrellm. As i compile a kernel, the 'temp2' reading progresses from about 36 degrees C to about 57, where it starts complaining.
Other readings, which remain steady are:
cpu speed: 1.6 ghz
temp1: 34 C
temp3: 125 C
temp4: -46 C
57 C sounds pretty hot. if it is actually that hot, i probably need a way to slow down more imperceptibly.
or are the readings wrong?
i opened up my box, and with the case open, i am actually able to get through a kernel compile..
i'm surprised it's getting so hot, its in a roomy aluminum case with good fans..
a lot of my normal desktop operations (opening apps and browsing filesystem) sped up significantly when i switched to the 2.6.x-1-686 kernel so i'd like to keep it, but this is a hassle..
anybody else's 2.6 kernel overheating their cpus?
maybe theres a way i can ask it to slow down sometimes?
Well, it soudns as if you Actually ARE having a heat problem. You may want to invest in either a better CPU fan/heatsink, or alot more fans. Is this an AMD, because AMDs actually (in my experiance, i have a 2400+) run hot. (mine is 50.. 53. Course, this is a win box. )
Well, it's an Intel P4.. I guess it's getting really hot.
I'm surprised I haven't seen anybody else have this problem (except laptop users) from searching help forums and google.
This suggests to me that it is, like you said, a matter of me not having enough fans or good heat sink.
But I'm still surprised that this computer has run about 20 hours a day for at least 2 years and never had a similar problem until I started using the 2.6 kernel. Does this mean that it is able to realize my processor's potential in ways previously impossible? who knows...
I've noticed that modulated clock mode isn't so bad. Mouse and windows are still responsive. Tuxracer stutters, but I'll be ok. The main noticeable effect is the infernal messages that are broadcast on any and all consoles I have open. I like knowing that my cpu temp is too high, but I don't want to know several times a second.. It is a dilemma I guess.
Anybody have a clue on how I might be able to stop these messages from being broadcast? Here is what one looks like:
Message from syslogd@wes at Thu Apr 15 20:12:15 2004 ...
wes kernel: CPU#0: Temperature above threshold
Intel tells me my P4 can run with a maximum case temperature of 75 C..
I guess maybe the cpu temperature given by my lm-sensors could mean a different thing than the 'case temperature'.
But it seems to me like they might be the same thing, in which case I could turn up my max heat from 57 C to 70 or even 75 C. Sounds hot to me, but the worst that can happen is I have to buy some new hardware, which can be fun from a non-economical standpoint.
So I guess I'll try and figure out how to increase my max temperature... unless somebody tells me that 70 C is way too hot and I would be crazy to do this.
Thanks geekzen for your replies, btw. I know this is not a fun problem to think about.
I'm hoping that if anybody else has this problem, this thread will make information easier to find for them than it originally was for me.
Course, this means that another Emergency wont be broadcast... not good.
Someone needs to help you here.... This post needs to be moved to hardware. I will do the report/modcall.
While searching for information on the problem I'm having with Fedora Core 2, I found this page. It describes myproblem exactly. I am running the Gimps client (not just stress testing - I participate), and after abot 15 minutes, I start getting the emergency messages to all my consoles... about 8 a second, to the point where I actually cannot type anything useful and kill the process (slightly different flavor with my problem - as a hyperthreaded processor, I have 2 CPUs screaming at me.
While it is a little hot, it is within the range the processor should be fine with (about 60 degrees) according to intel's website.
I don't want to just turn off logging the .emerg to the console... that would be wRong... It is also annoying that my messages file is getting HUGE. I would prefer to just turn off this particular warning, or (ideally) make the processor not complain until it is a little hotter (but I think the throttling back is hardware controlled).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.