Message from syslogd appear in console

[ihrsetrdr]

I just installed Debian 2.6.18-6-amd64 on a Q6600 rig, did the usual setup & downloaded the 6.02 beta1 client. Getting the following messages in the client console:



Message from syslogd@debian-DS3-5 at Fri May 30 21:46:49 2008 ...
debian-DS3-5 kernel: CPU0: Temperature above threshold, cpu clock throttled
[04:47:38] Writing local files
[04:47:39] Completed 600000 out of 5000000 steps (12 percent)

Message from syslogd@debian-DS3-5 at Fri May 30 21:51:49 2008 ...
debian-DS3-5 kernel: CPU0: Temperature above threshold, cpu clock throttled

Message from syslogd@debian-DS3-5 at Fri May 30 21:51:49 2008 ...
debian-DS3-5 kernel: CPU1: Temperature/speed normal
[04:56:26] Writing local files
[04:56:26] Completed 650000 out of 5000000 steps (13 percent)

Message from syslogd@debian-DS3-5 at Fri May 30 21:56:49 2008 ...
debian-DS3-5 kernel: CPU1: Temperature/speed normal

Message from syslogd@debian-DS3-5 at Fri May 30 21:56:49 2008 ...
debian-DS3-5 kernel: CPU0: Temperature/speed normal

I believe I ran into this same occurrence at sometime in the past, but don't recall what the cause was, or how to resolve it. Weird thing is- the syslogd messages only show in the console, but are not written to the log txt file.

No BIOS settings were changed, no actual temperature problem exists and as far as I can tell, there's no performance problem with the running WU.

Any ideas?

[ihrsetrdr]

Long story-short: Voltages in BIOS somehow got on "Auto", Vcore setting was un-necessarily high. Dropped vcore down to 1.3v and messages ceased to appear in console. This in turn prompted me to check my other machines, a couple of which were running over 70C; adjusted the vcore on them accordingly and are now in more 'comfortable' temp range.

[Adak]

That's as odd an error as ever I've heard of. Congrats on fixing it! :clap:

[harlam357]

Sometimes Optimized Defaults aren't so Optimized. :D

[ihrsetrdr]

That's as odd an error as ever I've heard of. Congrats on fixing it! :clap:

Yea, as I mentioned I had ran into this problem before, but don't recall the solution.


I was looking at this occurrence as:

>folding problem, or
>Linux o/s misconfiguration, but


turned out to be an old fashioned BIOS settings problem. It pays to listen to when a machine is crying out for help! :o