Forum > Linux
SETI MB CUDA for Linux
Lysia:
I'm also seeing this
Cuda error 'GaussFit_kernel' in file './cudaAcc_gaussfit.cu' in line 506 : invalid configuration argument.
Beginning of stderr.txt is
--- Code: ---SETI@home MB CUDA 608 Linux 32bit SM 1.0 - r06 by Crunch3r :p
setiathome_CUDA: Found 1 CUDA device(s):
Device 1 : GeForce 8800 GTS 512
totalGlobalMem = 536543232
sharedMemPerBlock = 16384
regsPerBlock = 8192
warpSize = 32
memPitch = 262144
maxThreadsPerBlock = 512
clockRate = 1620000
totalConstMem = 65536
major = 1
minor = 1
textureAlignment = 256
deviceOverlap = 1
multiProcessorCount = 16
setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce 8800 GTS 512 is okay
SETI@home using CUDA accelerated device GeForce 8800 GTS 512
setiathome_enhanced 6.01 Revision: 402 g++ (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
libboinc: BOINC 6.5.0
Work Unit Info:
...............
WU true angle range is : 0.447697
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled 626.74337 0.00000
sse1_ChirpData_ak 49414.78434 0.00098
v_vTranspose4 22247.17831 0.00000
BH SSE folding 9764.43373 0.00000
Cuda error 'GaussFit_kernel' in file './cudaAcc_gaussfit.cu' in line 506 : invalid configuration argument.
--- End code ---
I'm running BOINC 6.4.5, Ubuntu 8.04 (2.6.24-23) and have a 8800 GTS 512 (G92). http://setiathome.berkeley.edu/show_host_detail.php?hostid=4840816
Nvidia driver is 180.29, I have tried with CUDA Toolkit from Nvidia (the versions of the libs are 2.1) and the CUDA libs delivered with the S@H-client, with the same results.
The only thing I seem to have in common with all the other reports in this thread seems to be that I run a 32 bit Linux.
I have calculated some work units, most of them still need validation, two are in state "Completed, validation inconclusive", so I guess the results may be garbage.
And some work units just gave a "Compute Error" (http://setiathome.berkeley.edu/result.php?resultid=1185431682), is this normal?
By the way:
Is there any good reason, why libcufft.so.2 and libcudart.so.2 are mentioned in app_info.xml? That should be normal libraries, and I don't think boinc should need to know about them. I did not unpack them at the beginning (had installed CUDA Toolkit), and boinc tried to download these files (and failed) now I have them in projects/setiathome.berkeley.edu but I don't think they are used from there.
sunu:
Lysius, what kind of cuda client are you running? Those tasks marked "Error while computing" seem to have been killed with the VLAR autokill. As far as I know there hasn't been released a linux cuda client with a VLAR autokill function.
Lysia:
--- Quote from: sunu on 15 Mar 2009, 09:24:24 pm ---Lysius, what kind of cuda client are you running? Those tasks marked "Error while computing" seem to have been killed with the VLAR autokill. As far as I know there hasn't been released a linux cuda client with a VLAR autokill function.
--- End quote ---
I'm using the Download from the first post in this thread (i686), redownloaded and verrified that this is really what I have installed. Is there anything newer?
And where can I find the source?
Has anyone successfully used the 32-bit version or does everybody use 64-bit?
sunu:
Yes Lysius, there is something wrong with the 32bit app. I've found and downloaded one of the WUs that you've done ( http://setiathome.berkeley.edu/workunit.php?wuid=424266619 ). The 32bit app gives me the same errors, while the 64bit app is good. Worse still, the two results are weakly similar.
Note to Crunch3r: I've posted the two results in the development thread.
Lysia:
--- Quote from: sunu on 16 Mar 2009, 12:17:56 pm ---Yes Lysius, there is something wrong with the 32bit app. I've found and downloaded one of the WUs that you've done ( http://setiathome.berkeley.edu/workunit.php?wuid=424266619 ). The 32bit app gives me the same errors, while the 64bit app is good. Worse still, the two results are weakly similar.
--- End quote ---
Any news on this?
And is there a guide anywhere on how to test an app without using BOINC and reporting possible garbage?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version