22 Jul
2004
22 Jul
'04
5:41 a.m.
Malcom,
As always, YMMV. I was able to bump my SuperMicro
FSB800 P4 servers from
3.2GHz to 3.4GHz, which passed by hardcore 7-day 100% CPU burn-in test
(which does md5sums of /dev/random filled memory) without any trouble.
Since the box lives in CPU Paradise [a datacentre, with 65F, 55% RH, and
lots of forced-air circulation, and not a trace of dust], it's quite happy.
You use this commercially? For "mission critical" stuff?
...
This message has been brought to you in part by a grant from Columba.
22 Jul
22 Jul
5:53 a.m.
New subject: [linux-audio-user] CPU clock - beware - Solved for now?
You use this commercially? For "mission
critical" stuff?
Yes. It passed all 100% CPU utilisation and md5-memory checksumming tests
without a single fault in its cabinet.
I was just idly curious about it... it's running as a backup server for
something else. It's going onto its 75th day of uptime, and no process has
even core-dumped on it. CPU Temperature is holding at 45 C, and these
SuperMicros have passive CPU cooling (albeit with four 12,000 RPM chassis
fans drawing air from the air towards the rear).
Go figure. I assumed it'd have crashed and burned during my burn-in test.
It performed flawlessly.
I did use good quality ECC DDR-400 matched RAMs.
=MB=
--
A focus on Quality.
7407
days inactive
7407
days old
linux-audio-user@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Malcolm Baldridge -
RickTaylor＠Speakeasy.Net