CUDALucas (a.k.a. MaclucasFFTW/CUDA 2.3/CUFFTW)

[mognuts]

Originally Posted by owftheevil

Crashes how?

This is the console output:

C:\Users\John\Desktop\cudalucas>CUDALucas_205Beta_x64_r52 -cufftbench 2048 1 5
 ------- DEVICE 0 -------
name                GeForce GTX 460
Compatibility       2.1
clockRate (MHz)     1430
memClockRate (MHz)  1800
totalGlobalMem      1073741824
totalConstMem       65536
l2CacheSize         524288
sharedMemPerBlock   49152
regsPerBlock        32768
warpSize            32
memPitch            2147483647
maxThreadsPerBlock  1024
maxThreadsPerMP     1536
multiProcessorCount 7
maxThreadsDim[3]    1024,1024,64
maxGridSize[3]      65535,65535,65535
textureAlignment    512
deviceOverlap       1
 Thread bench, testing various thread sizes for ffts 1K to 2048K, doing 5 passes.
fft size = 1K, ave time = 6.5100 msec, Norm1 threads 32, Norm2 threads 32
fft size = 1K, ave time = 6.5094 msec, Norm1 threads 32, Norm2 threads 64
fft size = 1K, ave time = 6.5098 msec, Norm1 threads 32, Norm2 threads 128
fft size = 1K, ave time = 6.5084 msec, Norm1 threads 32, Norm2 threads 256
fft size = 1K, ave time = 6.5089 msec, Norm1 threads 32, Norm2 threads 512
fft size = 1K, ave time = 6.5085 msec, Norm1 threads 32, Norm2 threads 1024
fft size = 1K, ave time = 6.5084 msec, Norm1 threads 64, Norm2 threads 32
fft size = 1K, ave time = 6.5088 msec, Norm1 threads 64, Norm2 threads 64
fft size = 1K, ave time = 6.5085 msec, Norm1 threads 64, Norm2 threads 128
fft size = 1K, ave time = 6.5087 msec, Norm1 threads 64, Norm2 threads 256
fft size = 1K, ave time = 6.5080 msec, Norm1 threads 64, Norm2 threads 512
fft size = 1K, ave time = 6.5087 msec, Norm1 threads 64, Norm2 threads 1024
fft size = 1K, ave time = 6.5084 msec, Norm1 threads 128, Norm2 threads 32
fft size = 1K, ave time = 6.5080 msec, Norm1 threads 128, Norm2 threads 64
fft size = 1K, ave time = 6.5082 msec, Norm1 threads 128, Norm2 threads 128
fft size = 1K, ave time = 6.5079 msec, Norm1 threads 128, Norm2 threads 256
fft size = 1K, ave time = 6.5082 msec, Norm1 threads 128, Norm2 threads 512
fft size = 1K, ave time = 6.5072 msec, Norm1 threads 128, Norm2 threads 1024
fft size = 1K, ave time = 6.5090 msec, Norm1 threads 256, Norm2 threads 32
fft size = 1K, ave time = 6.5091 msec, Norm1 threads 256, Norm2 threads 64
fft size = 1K, ave time = 6.5085 msec, Norm1 threads 256, Norm2 threads 128
fft size = 1K, ave time = 6.5088 msec, Norm1 threads 256, Norm2 threads 256
fft size = 1K, ave time = 6.5078 msec, Norm1 threads 256, Norm2 threads 512
fft size = 1K, ave time = 6.5085 msec, Norm1 threads 256, Norm2 threads 1024
fft size = 1K, ave time = 6.5099 msec, Norm1 threads 512, Norm2 threads 32
fft size = 1K, ave time = 6.5098 msec, Norm1 threads 512, Norm2 threads 64
fft size = 1K, ave time = 6.5093 msec, Norm1 threads 512, Norm2 threads 128
fft size = 1K, ave time = 6.5098 msec, Norm1 threads 512, Norm2 threads 256
fft size = 1K, ave time = 6.5096 msec, Norm1 threads 512, Norm2 threads 512
fft size = 1K, ave time = 6.5099 msec, Norm1 threads 512, Norm2 threads 1024
fft size = 1K, ave time = 5.9309 msec, Norm1 threads 128, Mult threads 32, Norm2 threads 1024
fft size = 1K, ave time = 5.9307 msec, Norm1 threads 128, Mult threads 64, Norm2 threads 1024
fft size = 1K, ave time = 5.9311 msec, Norm1 threads 128, Mult threads 128, Norm2 threads 1024
fft size = 1K, ave time = 5.9318 msec, Norm1 threads 128, Mult threads 256, Norm2 threads 1024
Best time for fft = 1K, time: 5.9307, t0 = 128, t1 = 64, t2 = 1024

Followed by a dialogue box containing the following text:

CUDALucas_205Beta_x64_r52.exe has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

This happens regardless of the parameters used for -cufftbench.

[mognuts]

On a more positive note, r52 correctly found 3 known primes.

M( 11213 )P, n = 1K, CUDALucas v2.05 Beta
M( 1257787 )P, n = 64K, CUDALucas v2.05 Beta
M( 2976221 )P, n = 256K, CUDALucas v2.05 Beta

[owftheevil]

R53 is up, fixing the sparse <gpu> fft.txt file issue, the uninitialized pointer causing mismatched residues in the self-test, an incorrect fft length in the threads bench and a bad bounday case condition in the fft initialization.

@mognuts: I could not get the behaviour your 460 showed to happen, so I don't know if the problem is fixed or not.

Windows version is not up yet.

[ET_]

Originally Posted by owftheevil

R53 is up, fixing the sparse <gpu> fft.txt file issue, the uninitialized pointer causing mismatched residues in the self-test, an incorrect fft length in the threads bench and a bad bounday case condition in the fft initialization.

@mognuts: I could not get the behaviour your 460 showed to happen, so I don't know if the problem is fixed or not.

Windows version is not up yet.

You are referring to CUDALucas, not CUDAPm1 issues, aren't you?

Luigi

[flashjh]

r53 is on SourceForge.

.ini file is updated, please re-download.

Formatting output can be customized now.

Please run the tests in this post and continute to post any issues or bugs.

Thanks!

Originally Posted by ET_

You are referring to CUDALucas, not CUDAPm1 issues, aren't you?

Luigi

Yes

[flashjh]

Posted Win32 .exe files on SourceForge - first time I've built Win32 with 2.05 Beta, please test accordingly.

[flashjh]

Successful test of Win32 version of r53

I am now able to build CUDA version 4.0 and up, 64 bit only, if anyone needs a version, let me know.

[flashjh]

SorceForge updated with latest commit, currently r55. Minor formatting changes and updated makefile.win file to allow for Win32 or x64 compiles with CUDA 4.0 up to 5.5.

If anyone wants help compiling with make or in MSVS, let me know.

Had another successful DC with Win32 version. With the help of petrw1 I have 23/24 good DCs. The bad one was probably caused by all my stopping/starting while compiling, etc. None the less, that's why we DC.

[flashjh]

Originally Posted by mognuts

This is the console output:

<snip>

Followed by a dialogue box containing the following text:

CUDALucas_205Beta_x64_r52.exe has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

This happens regardless of the parameters used for -cufftbench.

I am running tests to cause the NVIDIA Windows Kernel Mode Driver failure. Testing all versions of NVidia WHQL drivers since 296.10. Those results later...

@mognuts, I was able to (accidentally) reproduce the results you experienced.

@owftheevil

-Anytime I run -cufftbench fft# smallerfft# 1 it causes CUDALucas to crash like mognuts experienced
-When I run -cufftbench fft# fft# any# it skips some of the fft tests completely

See the attached file for screenshot and bench.txt output for the skipped tests. I included the .exe file I'm using for testing. I'm currently on 314.22, but it doesn't seem to matter what driver I use.

[owftheevil]

I'll take a look.

New commit r56, fixes a regression concerning command line input. Try to specify a nonstandard fft like 3150k and you'll see what I'm talking about.

[flashjh]

Windows r56 executables posted to SourceForge