Thank you so much for this info.

I'll look into disabling lm_sensors (either uninstall or modprobe -r coretemp). Crossing my fingers.

Is there any way to monitor temps without taking control of the fans? I guess I need to look into more of what the lm_sensors package actually does.

I wrote a script that is logging the temps every 10 secs with alerts for "warm, hot, and critical." So far it has only hit warm (65 deg C -- 84 is critical) for no more than 4 inconsecutive times. I put a line that also logs the top processor utilizers to see if I could see what was doing it. Did have about 80 percent total processor utilization at those 4 separate times.

Thanks again for these tips.

I'll post back here with the results (but I won't be able to monitor the temps anymore).

Yours,
Narnie

PS

The logging was from /var/log/kern.log

---------- Post updated 06-19-10 at 08:26 AM ---------- Previous update was 06-18-10 at 11:35 PM ----------

For anyone reading this thread having the same problem as I, lm_sensors is a service and can be diabled with :

Code:

sudo /etc/init.d/lm-sensors stop

I'm not sure if this is sufficient or of removing the module it loads is sufficient (in my case, the module was coretemp).

---------- Post updated at 08:35 AM ---------- Previous update was at 08:26 AM ----------

OK, this is strange.

It shut down last night with the last temp reading of 49 deg C.

Strange.

After booting back up, I wsa running nothing windowed but a terminal. I was checking some things when I just happened to check my temps manually.

The temps were at 82 deg C. Huh??? I did a quick

Code:

top

and found that gnome-do was using 200% of my CPU (double-huh???).

I quickly pkilled it and watched as the temp came back down to where I'm used to seeing it. It seems, gnome-do on my system does some run-away things. Bad gnome-do.

Then after i uninstalled lm-sensors and removed the coretemp module, I stressed the CPU. I am using the generic ati drivers as the proprietary is too buggy for me, so I fired up 5 instances of glxgears and watched the temp go up. With coretemp removed, only another temp sensor worked (still called CPU, but called virtual--another huh?). It's critical max is listed at 104 deg C.

It normally is in the upper 60s/low 70s. With this CPU rendering stress, it went up to 89 deg C, but no higher.

Unless there is an answer to this posting to tell me otherwise, I'm going to try to reenable coretemp and see if all is well under this CPU stress and see if just the lm-sensors service is the culprit.

Narnie