BRP4 Intel GPUs and validation
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250424982
RAC: 35300
31 Aug 2021 11:53:43 UTC
Topic 225940
(moderation:
We are aware that currently quite some results computed with various, particularly ARM-based devices "lose" validation when compared to that of the dominating Intel GPUs. We are still working on solving this in the application code, but due to various issues this will take some more time.
To improve the situation that is understandably frustrating for some of you, we are reviving the "BRP4G" application and will let the Intel GPUs run these, so the results will be validated only among those. The other devices will keep processing BRP4 work and validate only in that group.
BM
As the results from the
)
As the results from the current BETA applications are collected and it is determined that the application is in fact running at a low enough error rate to make the application version is safe to be run by everyone can the BETA status be removed so that main line users who have not agreed to run "TEST Applications" can receive the new versions of the Applications ?
Thanks
Bill F
Dallas TX
In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.
I'd be against doing that
)
I'd be against doing that just yet. I've been running these tasks on some sample machines since the BRP4G run was restarted. I'd say that my results on HD 4600 GPUs are OK, but anything later than that is still problematic.
Take these stats from an HD 530 (still over 5 years old - nowhere near the cutting edge):
Check those figures very carefully. The separate categories add up to 238, leaving 146 unaccounted for. They are all 'validation inconclusive' against the stock application. Coupled with the figure of 69 invalid, I'd say that's unacceptable from a quality control point of view. The machine is a Dell Optiplex 5040 desktop, with no overclocking or other stressors.
Bernd intimated to me privately - just before his holidays - that "... we finally have someone actively working on it now, so we're getting back to it. I'll take a look at this issue." I'm ready and willing to take part in that investigation whenever called upon: I have some some experience of tackling similar issues at SETI@Home.
Richard Haselgrove
)
I agree with Richard I too would like the apps to be pretty solid before the drop of BETA status. I was thinking more of the two BETA's that have release dates in 2019.
Bill F
In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.
Hello, I can no longer
)
Hello,
I can no longer receive BRP4(G) tasks for my Intel HD4000 GPU from my i7-3770T even though I have not changed any settings.
Is this normal?
I have the following error message:
{AF} fansyl wrote:I can no
)
I don't use Intel GPUs at all so don't have any experience but from the log excerpt you published, did you see the following line?
... driver version required max: 1018103906, supplied: 1018105161It looks like there is a maximum driver version limit being applied and it shows that your supplied version is higher than the allowed max value. Perhaps that's a recent change by the project, or perhaps your driver version was updated recently as part of normal system maintenance. They've been trying to cut down on validation issues by excluding known problematic driver versions, hence the setting of these limits.
You could try downgrading your driver to be at or below the limit stated.
Cheers,
Gary.
Not Intel GPU related, but I
)
Not Intel GPU related, but I see recently similar issue with the "v1.61 aarch64-unknown-linux-gnu" application.
Examples of aarch64 loosing against two Androids: WU 649167107 WU 650389871
Example of Android loosing against two aarch64: WU 649945764
.
Next example of Android
)
Next example of Android loosing against two aarch64: WU 655777188
Update 31.07., Android loosing against two aarch64: WU 659634571. Perhaps interesting: both aarch64 computers use ARM BCM2835 CPU.
.