Is there a thread at Beta for reporting hosts with high numbers of invalids and errors?

I happened to notice http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=64599 with a lot. (The same box at Seti main only has one task, an AP that will time out in under 12 hours from now.)

---

David
signature sent back to alpha testing

Is there a thread at Beta for reporting hosts with high numbers of invalids and errors?

I happened to notice http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=64599 with a lot. (The same box at Seti main only has one task, an AP that will time out in under 12 hours from now.)

It could be that this guy's problem fits some other thread. The WU that caught my attention is, for him, an openCL on Intel graphics.

---

David
signature sent back to alpha testing

As we're doing Beta testing, hosts which reveal a problem are perhaps more valuable than those which don't.

host 64599 does seem very prone to creating false Autocorr signals with high peak powers, and is running Intel's OpenCL 1.1 drivers. I don't know if all hosts running those drivers are suffering the same, though, nor whether Raistmer will be able to diagnose and find a workaround. Potentially, a release to the main project might have to require Intel's OpenCL 1.2 drivers.

                                                                   Joe

I would say that host requires reboot first. And only if it will not help, then driver upgrade. I had such state on own PC once, with OpenCL 1.2 drivers installed.
I'm afraid not much to diagnose here besides some similarity in reported overflows to teach app to recognise wrong apps and throw clean error instead of false overflow. User intervention required (well, maybe worth to reboot such host programmatically from app, but I'm afraid some users could upset ;) )

I have the same issue, with OpenCL 1.1 and an Intel(R) HD Graphics 4000 card.

I would say that host requires reboot first.

That does not help at all.

Potentially, a release to the main project might have to require Intel's OpenCL 1.2 drivers.

I agree. As you can see here, all S@H tasks produce lots of autocorr and finally

SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected equals the storage space allocated.

The host mentioned in the above post is now using OpenCL 1.2 drivers on the same GPU and gets valid results.

I also noticed that AP workunits also fail (seems to, at the time of this writing neither of my AP workunits are marked as invalid, but they will be, for sure)

Well, current Intel drivers support OpenCL 1.2 so no probs with that.

I just wanted to suggest that the server should not give out any intel_gpu work units if OpenCL < 1.2