[[APi]TheMan]

I've been noticing lately that one of my Xserves has been getting a lot of EARLY UNIT END errors:

Code:
[admin@server: ~/Library/Folding@home]:$ cat FAHlog-Prev.txt | grep EARLY | wc -l
      16

My desktop and laptop machines don't do this... should I experiment with not using -advmethods and -forceasm?

[reader50]

That CPU is running a little warm, making errors now and then. Yes, back off the -advmethods. Backing off the -forceasm won't make a difference unless the Xserve crashes.

This will probably get you a bunch of Tinker units. Less production, but the CPUs will run cooler.

You might want to look over the ventilation for that Xserve, see if the air grilles have dusted up. This symptom happens with overclocking, or if there is insufficient cooling.

[[APi]TheMan]

Originally posted by reader50:
That CPU is running a little warm, making errors now and then. Yes, back off the -advmethods. Backing off the -forceasm won't make a difference unless the Xserve crashes.

This will probably get you a bunch of Tinker units. Less production, but the CPUs will run cooler.

You might want to look over the ventilation for that Xserve, see if the air grilles have dusted up. This symptom happens with overclocking, or if there is insufficient cooling.

Bummer, my Xserves have a rather nice closed rack that they hang out in, I guess I'll have to play with the cooling some.

My laptop doesn't give these errors, and it's running MUCH hotter than any of my crunching Xserves, so hot that I worry sometimes, maybe I should experiment with losing the -advmethods for my AlBook too.

Thanks