It appears a large number of the older machines are having a problem with the new cal_ati app. I also had a problem with the cal_ati app with the 13.1 Legacy driver. There are a few others, but a large number are using that one driver. The app seems to work fine with the older driver 11.12. Interesting...

Oh dear, that looks like the new Brook app is having problems. One for Raistmer.

I fear that changing the scheduler so that it spreads problematic units across different platforms requires a fair bit of coding on David's part. Not something easily set in motion.
____________
A person who won't read has no advantage over one who can't read. (Mark Twain)

This would be the same as the issue where a CPU task it processed & uploaded. The wingmate is a nvidia GPU that trashes a workunit recording 30 spikes and flagging it with -9 overflow. Then it gets sent to a 3rd host on a nvidia GPU that proceeds to do the same thing. So the two nvidia results matched up and the one good CPU result is flagged as invalid.

When this was first noticed, a few years ago iirc, there was a suggestion that something be implemented so specific hardware/software would get flagged and the task sent to something different. So that valid science data could be collected instead of tossed into the bin.
However that would add a lot of complexity to the server backend. Which is already rather complex.
____________
SETI@home classic workunits: 93,865 CPU time: 863,447 hoursJoin the BP6/VP6 User Group today!

Even thought the advertising says it's for accelerating retries that doesn't mean it needs to be used for that. Setting the avg turnaround time to something high and delay bound multiplier to 1.0 wouldn't exclude any good hosts from getting work but it would prevent bad hosts from trashing workunits.

I don't think it would increase server load much (no promises!) so the only question is do we have enough reliable hosts.

I just contacted Eric and he says that the cal_ati app has been deprecated and is not currently active or being distributed.

Which means the hosts that have been using it will crunch up whatever work they have cached, but the servers will no longer send any new work for that application.

I assume that it may be brought back after bugfix and further testing, but Eric did not specifically say that.

He seemed to be rather frustrated with driver version detection issues in BOINC over on beta. So it could be a bit before we see this all released again. If it was due to that kind of issue anyway.
____________
SETI@home classic workunits: 93,865 CPU time: 863,447 hoursJoin the BP6/VP6 User Group today!

These two hosts listed above are running Cat 10.5 (CAL 1.4.636) and Cat 9.7 (CAL 1.4.344), they need at least Cat 11.1 (CAL 1.4.900) for OpenCL support to be included,
but since you can't tell that apart from Cat 10.12 where OpenCL support was only available with the APP edition, and not the Normal edition,
then the minimum needs to be Cat 11.2 (CAL 1.4.1016), and possibly later than that.
(and even that doesn't guarantee that it'll work when sent to every host since you could at the time download the bare driver without Catalyst Control Centre,
and without the OpenCL driver, the OpenCL driver being a smallish additional download)