[QUOTE=Prime95;573558]Build 30.5 build 1 is available. It fixes the PRP problem described here: [url]https://www.mersenneforum.org/showthread.php?p=573197#post573197[/url][/QUOTE]

There is no prime95.exe in the windows folders.

Oops. Fixed.

OK.
Restarted with 30.5.1 a session initiated with 30.4.9, and had the following message:

[code]
Worker #1 Mar 13 13:46] Worker starting
[Worker #1 Mar 13 13:46] Setting affinity to run worker on CPU core #1
[Worker #2 Mar 13 13:46] Waiting 5 seconds to stagger worker starts.
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 1 on CPU core #1
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 4 on CPU core #3
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 5 on CPU core #3
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 6 on CPU core #4
[Worker #1 Mar 13 13:46] Resuming trial factoring of M216166681 to 2^74
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 3 on CPU core #2
[Worker #1 Mar 13 13:46] Trial factoring M216166681 to 2^74 is 24.56% complete.
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 2 on CPU core #2
[Worker #1 Mar 13 13:46] Setting affinity to run helper thread 7 on CPU core #4
[Worker #2 Mar 13 13:46] Worker starting
[Worker #2 Mar 13 13:46] Setting affinity to run worker on CPU core #5
[Worker #2 Mar 13 13:46] Setting affinity to run helper thread 1 on CPU core #6
[Worker #2 Mar 13 13:46] Setting affinity to run helper thread 3 on CPU core #8
[/code]

while with version 30.4.9 I had the following allorment for the CPUs:

[code]
[Worker #1 Mar 13 13:47] Worker starting
[Worker #1 Mar 13 13:47] Setting affinity to run worker on CPU core #1
[Worker #2 Mar 13 13:47] Waiting 5 seconds to stagger worker starts.
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 1 on CPU core #1
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 5 on CPU core #3
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 6 on CPU core #4
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 3 on CPU core #2
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 4 on CPU core #3
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 7 on CPU core #4
[Worker #1 Mar 13 13:47] Resuming trial factoring of M216166681 to 2^74
[Worker #1 Mar 13 13:47] Setting affinity to run helper thread 2 on CPU core #2
[Worker #1 Mar 13 13:47] Trial factoring M216166681 to 2^74 is 24.56% complete.
[Worker #2 Mar 13 13:47] Worker starting
[Worker #2 Mar 13 13:47] Setting affinity to run worker on CPU core #5
[Worker #2 Mar 13 13:47] Setting affinity to run helper thread 1 on CPU core #6
[Worker #2 Mar 13 13:47] Setting affinity to run helper thread 2 on CPU core #7
[Worker #2 Mar 13 13:47] Setting affinity to run helper thread 3 on CPU core #8
[Worker #2 Mar 13 13:47]
[/code]

Something went wrong with the assignatio of the CPUs at the worker threads...? or maybe it's just me.

Luigi

[QUOTE=ET_;573572]OK.
Restarted with 30.5.1 a session initiated with 30.4.9, and had the following message:

[code]
[...]
[Worker #1 Mar 13 13:46] Resuming trial factoring of M216166681 to 2^74
[...]
[Worker #2 Mar 13 13:46] Setting affinity to run worker on CPU core #5
[Worker #2 Mar 13 13:46] Setting affinity to run helper thread 1 on CPU core #6
[Worker #2 Mar 13 13:46] Setting affinity to run helper thread 3 on CPU core #8
[/code]

while with version 30.4.9 I had the following allorment for the CPUs:

[code]
[...]
[Worker #1 Mar 13 13:47] Resuming trial factoring of M216166681 to 2^74
[...]
[Worker #2 Mar 13 13:47] Setting affinity to run worker on CPU core #5
[Worker #2 Mar 13 13:47] Setting affinity to run helper thread 1 on CPU core #6
[Worker #2 Mar 13 13:47] Setting affinity to run helper thread 2 on CPU core #7
[Worker #2 Mar 13 13:47] Setting affinity to run helper thread 3 on CPU core #8
[Worker #2 Mar 13 13:47]
[/code]

Something went wrong with the assignatio of the CPUs at the worker threads...? or maybe it's just me.[/QUOTE]

The only difference I can see (apart from the line ordering) is that 30.5 is missing helper thread 2 on worker #2 (which I've clipped your log to in the quote). And of course there's the obligatory question of why you're doing TF on a CPU.

[QUOTE=Happy5214;573576]And of course there's the obligatory question of why you're doing TF on a CPU.[/QUOTE]

Because the PRP-CF-DC category is getting TF assignments right now when there are no DCs.

[QUOTE=ATH;573583]Because the PRP-CF-DC category is getting TF assignments right now when there are no DCs.[/QUOTE]
Still? I thought George fixed that. I've been following since my computers run that work type and received TFs as well, but they were queued far enough in advance that I still have a couple of days worth of PRPs before I run out.

[QUOTE=Happy5214;573587]Still? I thought George fixed that. I've been following since my computers run that work type and received TFs as well, but they were queued far enough in advance that I still have a couple of days worth of PRPs before I run out.[/QUOTE]

I usually get 3 days of work in advance, that's why there was that single TF range on my worktodo :smile:

[QUOTE=ET_;573598]I usually get 3 days of work in advance, that's why there was that single TF range on my worktodo :smile:[/QUOTE]
I cut mine back to 1 day ahead and released the TFs. Two of the machines were only attached to GIMPS for the PRP-CF-DC backlog clearing push. They normally run clients for my personal PRPNet servers, and they're slated to resume that work once their queues dry up. I haven't decided what I'll do with the third (by far the most powerful). I have a few backlogged P-1 and ECM exponents to run, but I don't know if I'll do first-time PRP-CF or start BOINC work after that (which was the original plan post-clearing).

[QUOTE=Happy5214;573587]Still? I thought George fixed that. I've been following since my computers run that work type and received TFs as well, but they were queued far enough in advance that I still have a couple of days worth of PRPs before I run out.[/QUOTE]

Fix is not working, I'm still getting TF just now.

On a completely unrelated note, my PRP-CF-DC test of [M]10841147[/M] somehow ran without even attempting to generate a proof. It's not a big deal, since it was a DC and the residues matched, but this is the first time I recall this happening since I switched to 30.3 (of which I was an early adopter). I don't know if the worktodo line was wrong (it's complete, so the line is gone), but I didn't see anything unusual in the log files. But it didn't even attempt to create a residue file at the beginning of the test, and it sent periodic residues like in the pre-proof era. Actually, looking at the console printouts again, it didn't use Gerbicz on it either. I upgraded from 30.4 to 30.5 midway, but I don't think that had an impact, since 30.4 had already decided the test type (though strangely it did lower the FFT lengths back to 560K from 576K on those tests).

Edit: From my laptop, here's the printout line:
[code][Worker #1 Mar 13 02:16] Starting PRP test of M10841147/24023981753 using FMA3 FFT length 576K, Pass1=384, Pass2=1536, clm=2, 2 threads[/code]

Edit 2: Oh, now I see what happened. Some clown did the first-time test as a type-1 instead of a type-5. Would I get first-time or DC credit if I redid that as a type-5 with proof?

[QUOTE=Happy5214;573602]Edit 2: Oh, now I see what happened. Some clown did the first-time test as a type-1 instead of a type-5. Would I get first-time or DC credit if I redid that as a type-5 with proof?[/QUOTE]

I think you would get a credit.