[linux-audio-user] CPU clock - beware
chris.pickett at mail.mcgill.ca
Sat Jul 24 21:41:30 EDT 2004
tim hall wrote:
> Last Saturday 24 July 2004 13:40, robin fell was like:
>>On Sat, 2004-07-24 at 13:21, tim hall wrote:
>>>Well, I'm running at 100MHz x 6 right now.
>>>I take full responsibility for my actions.
>>>Are there any signs I should watch out for?
>>if at all possible, you should run memtest86 (or similar) for a few
>>hours to ensure the memory performance hasn't suffered. i keep a
>>memtest86 on my grub boot menu at all times.
>>the poor man's test would be to stress the hell outta your box with lots
>>of heavy lifting - perhaps recompiling the kernel over, and over, and
>>over again to see if strange gcc errors occur. such strange errors are
>>usually an indication of an unhappy cpu or memory.
> Well, memtest86 sounds easy enough.
cpuburn was also mentioned and it's easy too (and generally more
intensive than compiling a kernel).
More information about the Linux-audio-user