I have compiled this test using the latest 2.1 CUDA. Reinstalled the driver just to be sure. (I complained elsewhere about instability - since no one else complained similarly, I did a fresh reinstall and 2.1 seems to work o.k.)
For me, on my Suse 10.3 linux system with its single gtx260 the test seems to immediately fail after the screen blinks a bit. I “init 3” to get out of X to run the test. The usual calculations I run on this seem to work o.k.
So:
What does failing the test mean?
How can I “fix” my system so that it passes this test?
How worried should I be that it doesn’t pass this burn in test?
Thx,
B.C.
ADDED LATER: Ah! I have it! Not only does X have to be turned off, but also the linux framebuffer has to be turned off as well. Like Lady Galadriel, my gtx 260 passes the test. Although I don’t think my gtx 260 will pass into the west.
For reference:
[codebox]
./deviceQuery
There is 1 device supporting CUDA
Device 0: “GeForce GTX 260”
Major revision number: 1
Minor revision number: 3
Total amount of global memory: 939196416 bytes
Number of multiprocessors: 24
Number of cores: 192
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 16384 bytes
Total number of registers available per block: 16384
Warp size: 32
Maximum number of threads per block: 512
Maximum sizes of each dimension of a block: 512 x 512 x 64
Maximum sizes of each dimension of a grid: 65535 x 65535 x 1
Maximum memory pitch: 262144 bytes
Texture alignment: 256 bytes
Clock rate: 1.30 GHz
Concurrent copy and execution: Yes
Test PASSED
[/codebox]