Forum > Linux

SETI MB CUDA for Linux

<< < (40/162) > >>

Raistmer:
In windows the difference in first and second PCI-E slots (if first has motitor attached and second not) is:
GPU that used by Windows for video output will subject of 3 or 2 seconds timeout, but secong GPU will not.
Don't know if this relevant to Linux though.

sunu:

--- Quote from: Raistmer on 12 Jul 2009, 07:01:59 am ---GPU that used by Windows for video output will subject of 3 or 2 seconds timeout, but secong GPU will not.
Don't know if this relevant to Linux though.

--- End quote ---

Well, if it is because of the first gpu also drawing the screen then it will probably also exist in linux. We don't have a big sample of seti cuda users with multi gpus in linux. Actually the sample is non-existent  :D

What Tye describes might be some faulty config, strange driver behavior, or some weird motherboard-gpu-gpu hardware incompatibility.

Raistmer:
Not sure it exist in linux. It's not GPU feature, it's windows feature - it will kill driver (Vista) with more than 2 secs of "no answer" from it.
Don't know if Linux kerner implements such watchdog machanism or not.
GPUs that don't output video don't subject of this "driver hung" check and can run long kernels. That's why surely not all that work OK on Tesla will work OK on user's GPUs (even if newly GPUs slightly faster than first released Teslas IMHO)

b0b3r:
Hello everyone


--- Quote from: Richard Haselgrove on 11 Jul 2009, 01:44:56 pm ---Came across an interesting error message in task 1294937260 while researching something else.


--- Quote ---SETI@home MB CUDA 608 Linux 64bit SM 1.0 - r06 by Crunch3r :p

Error: API mismatch: the NVIDIA kernel module has version 180.29,
but this NVIDIA driver component has version 180.60. 
...
--- End quote ---

Something to watch for when fiddling about with Linux drivers and modules.

The anonymous owner of host 5011059 seems to be having a real problem getting his or her GTX 295 running under gentoo.

--- End quote ---

With this host I don't have any problems. It just happen during system upgrade.

I have a real problem with host 5018683. I don't have any idea what's wrong. It isn't over clocked, or overheating. GPU-s have about 75C~77C at full load (~52C idle). And other CUDA programs are working fine, but with SETI almost all end with:

cufft: ERROR: /root/cuda-stuff/sw/rel/gpgpu/toolkit/r2.2/cufft/src/execute.cu, line 1070
cufft: ERROR: CUFFT_EXEC_FAILED
cufft: ERROR: /root/cuda-stuff/sw/rel/gpgpu/toolkit/r2.2/cufft/src/execute.cu, line 1070
cufft: ERROR: CUFFT_EXEC_FAILED
cufft: ERROR: /root/cuda-stuff/sw/rel/gpgpu/toolkit/r2.2/cufft/src/cufft.cu, line 147
cufft: ERROR: CUFFT_EXEC_FAILED
Cuda error 'cufftExecC2C' in file './cudaAcc_fft.cu' in line 63 : unspecified launch failure.
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file './cudaAcc_PowerSpectrum.cu' in line 56 : unspecified launch failure.
Cuda error 'cudaAcc_GetPowerSpectrum_kernel' in file './cudaAcc_PowerSpectrum.cu' in line 56 : unspecified launch failure.
Cuda error 'cudaAcc_summax32_kernel' in file './cudaAcc_summax.cu' in line 148 : unspecified launch failure.
Cuda error 'cudaAcc_summax32_kernel' in file './cudaAcc_summax.cu' in line 148 : unspecified launch failure.
Cuda error 'cudaMemcpy(PowerSpectrumSumMax, dev_PowerSpectrumSumMax, cudaAcc_NumDataPoints / fftlen * sizeof(*dev_PowerSpectrumSumMax), cudaMemcpyDeviceToHost)' in file './cudaAcc_summax.cu' in line 161 : unspecified launch failure.

I will be thankful for any idea what's wrong and how to solve it.

Raistmer:
FFT lib kernel launch failed, most probably incompatibility between CUDA RT and video driver used.

Navigation

[0] Message Index

[#] Next page

[*] Previous page