cudaPm1 Stage 2 does not start

[kriesel]

I don't see anything unusual in the headers of the files originally posted to Google drive, except that the fft length is a bit large, at 20480K. "N 20971520". FFT files I have here indicate it could be done in 18816K.

>perl cudapm1export.pl

CUDAPm1export for Windows V0.1 2018-08-15

Input file name received as c333898333s1.
Extracted exponent q 333898333 from filename
Opened file c333898333s1 for read
Length of input file data read is 41737392 bytes, 10434348 words.
Exported file's header will read as follows:

Format Mersenne Neutral Exchange V1.0
FileOrigin "CUDAPm1export for Windows" "V0.1 2018-08-15" c333898333s1 2019 Jul 31 22:42:11 UTC
Type P-1 stage 2
Exponent 333898333
Iteration 4515547
N 20971520
AccumulatedTime 100719
B1 3130000
Reserved6 0
Reserved7 0
Reserved8 0
Reserved9 0
B2 0
D 0
E 0
NRP 0
M 0
K 0
T 0
Midpasstransforms 0
Itran_done 0
PtrandonePlusNumtran 0
Itime 0
Ptime 0
Reserved22 0
Reserved23 0
Reserved24 0
DataFormat binary bytes
CRC32 0x53c404f5
DataBinaryByteCount 41737292
EndOfHeader 0x2e04cfbb

Exported file header has length 546 including record terminators.
Processing bulk binary data input without output to console, please wait until program indicates Done.

Res64 of binary form of data is: 0xea7d398e8effff52

Printing 41737292 bytes bulk binary data in binary form.
Done.


>perl cudapm1export.pl

CUDAPm1export for Windows V0.1 2018-08-15

Input file name received as t333898333s1.
Extracted exponent q 333898333 from filename
Opened file t333898333s1 for read
Length of input file data read is 41737392 bytes, 10434348 words.
Exported file's header will read as follows:

Format Mersenne Neutral Exchange V1.0
FileOrigin "CUDAPm1export for Windows" "V0.1 2018-08-15" t333898333s1 2019 Jul 31 22:45:14 UTC
Type P-1 stage 1
Exponent 333898333
Iteration 4515001
N 20971520
AccumulatedTime 100719
B1 3130000
Reserved6 0
Reserved7 0
Reserved8 0
Reserved9 0
DataFormat binary bytes
CRC32 0x24bdce34
DataBinaryByteCount 41737292
EndOfHeader 0xe45759b0

Exported file header has length 389 including record terminators.
Processing bulk binary data input without output to console, please wait until program indicates Done.

Res64 of binary form of data is: 0x2f8ad881eed5913c

Printing 41737292 bytes bulk binary data in binary form.
Done.

[dcheuk]

Originally Posted by kriesel

Quick death reproducible here, CUDAPm1 V0.20, GTX 1080 Ti.

batch wrapper reports (re)launch at Wed 07/31/2019 15:58:59.30 reset count 0 of max 3 
CUDAPm1 v0.20
------- DEVICE 0 -------
name                GeForce GTX 1080 Ti
Compatibility       6.1
clockRate (MHz)     1620
memClockRate (MHz)  5505
totalGlobalMem      zu
totalConstMem       zu
l2CacheSize         2883584
sharedMemPerBlock   zu
regsPerBlock        65536
warpSize            32
memPitch            zu
maxThreadsPerBlock  1024
maxThreadsPerMP     2048
multiProcessorCount 28
maxThreadsDim[3]    1024,1024,64
maxGridSize[3]      2147483647,65535,65535
textureAlignment    zu
deviceOverlap       1

CUDA reports 10988M of 11264M GPU memory free.
Using threads: norm1 32, mult 32, norm2 64.
No stage 2 checkpoint.
Using up to 5120M GPU memory.
Selected B1=2740000, B2=67130000, 3.71% chance of finding a factor
Using B1 = 3130000 from savefile.
Continuing stage 2 from a partial result of M333898333 fft length = 20480K
batch wrapper reports exit at Wed 07/31/2019 16:00:23.95

Will try a couple other things. Renamed c file out of the way, redoing s1 gcd from t file now. If it works, it will give bigger NRP, maybe larger e, on the 11GB.

Originally Posted by kriesel

I don't see anything unusual in the headers of the files originally posted to Google drive, except that the fft length is a bit large, at 20480K. "N 20971520". FFT files I have here indicate it could be done in 18816K.

I could be wrong, but I think the RTX does this faster on 20480K that's why it was chosen.

Yeah this is weird. Oh well