Had to remove SETI due to errors


log in

Advanced search

Message boards : Number crunching : Had to remove SETI due to errors

Author Message
Profile mitrichr
Avatar
Send message
Joined: 23 May 07
Posts: 32
Credit: 1,720,566
RAC: 0
Message 1312286 - Posted: 7 Dec 2012, 20:20:38 UTC

I had SETI installed for CPU and GPU on a computer. I needed to remove it because it loaded a huge number of GPU tasks of very short duration which erred one after another, but tied up the GPU preventing three other GPU projects from running any tasks.

I am still running SETI for CPU only on four other machines.
____________
>>RSM
http://sciencesprings.wordpress.com
http://twitter.com/sciencesprings

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 3965
Credit: 31,930,168
RAC: 12,987
United Kingdom
Message 1312287 - Posted: 7 Dec 2012, 20:31:04 UTC - in response to Message 1312286.

Keplar GPUs with recent drivers error all their Cuda_fermi Wu's, to fix it, do the environment variable fix in this thread:

NVidia driver problems which cause computation errors

Claggy

Profile mitrichr
Avatar
Send message
Joined: 23 May 07
Posts: 32
Credit: 1,720,566
RAC: 0
Message 1312323 - Posted: 7 Dec 2012, 22:49:37 UTC

I got some help and re-installed 301.42, which I had in the past. This is a new machine so the drivers were the "latest and greatest". But I had 301.42 on GTX 670's before.
____________
>>RSM
http://sciencesprings.wordpress.com
http://twitter.com/sciencesprings

Ianab
Volunteer tester
Send message
Joined: 11 Jun 08
Posts: 622
Credit: 11,040,156
RAC: 3,990
New Zealand
Message 1312419 - Posted: 8 Dec 2012, 5:42:12 UTC - in response to Message 1312323.

I seem to remember reading that there might also be issues when running other projects as well as SETI / CUDA. Either project runs OK alone, but when you are switching between them weird things seem to happen?

Someone else may remember more info about this?

Ian

Profile mitrichr
Avatar
Send message
Joined: 23 May 07
Posts: 32
Credit: 1,720,566
RAC: 0
Message 1312584 - Posted: 8 Dec 2012, 14:50:30 UTC

I have been running SET@home on GPU on one machine (along with CPU on four other machines) along with Einstein and GPUGrid without any problems.

In fact, the other projects were fine with the new driver.

I am just glad to be able to do for SET@home whatever I can, to respect its position as the "mother" of all BOINC.
____________
>>RSM
http://sciencesprings.wordpress.com
http://twitter.com/sciencesprings

Claggy
Volunteer tester
Send message
Joined: 5 Jul 99
Posts: 3965
Credit: 31,930,168
RAC: 12,987
United Kingdom
Message 1312628 - Posted: 8 Dec 2012, 16:29:35 UTC - in response to Message 1312419.

I seem to remember reading that there might also be issues when running other projects as well as SETI / CUDA. Either project runs OK alone, but when you are switching between them weird things seem to happen?

Someone else may remember more info about this?

Ian

Not all Cuda projects have thread safe Cuda apps, 270.xx drivers and later react badly to terminating processes mid kernel execution,
and with recent Boinc versions, one project's Cuda app can be pre-empted so another can run, which can cause driver restarts and downclocking:

Recent Driver Cuda-safe Project List

Claggy

Message boards : Number crunching : Had to remove SETI due to errors

Copyright © 2014 University of California