View Single Post
Old 2019-04-25, 05:51   #5
pepi37
 
pepi37's Avatar
 
Dec 2011
After milion nines:)

2·19·37 Posts
Default

Quote:
Originally Posted by Prime95 View Post
I tried to replicate the problem on my quad core Win10 machine but I was not successful.

This won't help but will provide me some extra assurance that prime95 is calling hwloc's set_affinity routine properly. In prime.txt set AffinityVerbosity=2 and restart. As before, post the picture of prime95 starting up.

One other user reported a nearly identical problem several months ago (or is this your second bug report?). At this point, I'm stumped.

Quote:
[Apr 25 07:49:48] Worker starting
[Apr 25 07:49:48] Setting affinity to run worker on logical CPUs 1 (zero-based)
[Apr 25 07:49:48] Affinity set to cpuset 0x00000002
[Apr 25 07:49:48] Setting affinity to run helper thread 1 on logical CPUs 2 (zero-based)
[Apr 25 07:49:48] Affinity set to cpuset 0x00000004
[Apr 25 07:49:48] Setting affinity to run helper thread 2 on logical CPUs 3 (zero-based)
[Apr 25 07:49:48] Affinity set to cpuset 0x00000008
[Apr 25 07:50:03] Resuming PRP test of 95*10^1593538-1 using FMA3 FFT length 384K, Pass1=384, Pass2=1K, clm=4, 3 threads
[Apr 25 07:50:03] Iteration: 2326703 / 5293625 [43.95%].

As you say it doesnot help but seems Prime95 cal hwloc's set_affinity routine properly
pepi37 is online now   Reply With Quote