I've been trying to isolate some problems I've seen in the last 2 weeks. Kale http://moowrap.net/show_host_detail.php?hostid=804, has been doing Moo! since May 14th with just a couple of invalids, but nothing to kill the computer. Kale is running Moo! exclusively on an HD 5770 GPU, and has other projects running on the CPU. It's running just great.

Tomato http://moowrap.net/show_host_detail.php?hostid=809 normally runs Milkyway on the GPU with other CPU projects. Moo! is a backup as is Collatz. Milkyway and Collatz have never had a problem working together. I "think" I'm seeing a problem when the GPU (HD 4770) changes projects. Moo! has always been running when a VPU reset occurred. This causes Moo! or the next project to fail (or hang). I've run Moo! by itself on Tomato for days and it does just fine. I'm guessing that project switching may be part of the problem.

If I was fortunate then I saw this quickly, rebooted Tomato, and everything continued just fine. If not, then carnage occurred until I finally noticed the problem making Moo! (one time stuck) and non-Moo! tasks invalid. I haven't seen enough of these "interesting" events to really know what's going on.

Both Kale and Tomato are running Cat 11.5.

I'm just reporting (not complaining) about what I have seen. It may be part of a known problem however. In any event I've taken the following advice:

Me: Doctor, it hurts when I do this.
Doctor: Then stop doing it.

I've removed Moo! from the backup list on Tomato except for when I want to try it again while I watch :)

Rick

The different projects cause different heat levels-maybe somehow a factor.....or memory settings?

Does the rig run fine with Moo exclusively?

---

Team Renegades
Forum

Tomato ran Moo! for 5 days exclusively with no problems. This was while Milkyway was down. Milkyway has been up and down for the past week so Tomato has been going to its backup projects off and on.

I'll never say that Tomato isn't at fault. Most of my problems are either me or the computer...sigh. In this case I think Moo! project switching is the prime candidate for my woes, but I could be wrong.

Try and focus on what the GPU settings are for the Projects that are switched to, or switched from.

Tomato ran well with MW and/or Moo from what you said. Both are low memory projects, and even GPU settings are similar for most people depending how much o/c they may or may not apply.

A Collatz switch to MW is a good example of what might be happening. Collatz running at high(ish) GPU, and certainly high memory gets switched to MW on backup (say). The machine is set for Collatz, so the higher Collatz settings may well, with most people, bring down the MW WUs when backup kicks in - solely depends on how close the card is tuned to the relevant Projects needs, which do differ.

In reverse, a machine crunching MW switching to Collatz would be fine, run slow for sure if MW low memory had been set (which would slow Collatz), but it would run and not fall over.

Regards
Zy