Forum > GPU crunching
CUDA MB V12b for multi-GPU multicore hosts.
Raistmer:
Nothing new, it's for multi-GPU hardware.
Pappa:
on the 8400GS host it had 3 errors not sure if it I have not rebooted in a couple fo days (memory corruption)
AR 2.0 error in pulsefind
http://setiathome.berkeley.edu/result.php?resultid=1460163970
http://setiathome.berkeley.edu/result.php?resultid=1460163968
http://setiathome.berkeley.edu/result.php?resultid=1460163895
switching back
Raistmer:
Wow, time exceeded in pulsefind. Resembles my own 9400GT experiments but I had unspecified error...
And do you never encountered same error for prev builds?
Pappa:
--- Quote from: Raistmer on 24 Dec 2009, 12:24:04 pm ---Wow, time exceeded in pulsefind. Resembles my own 9400GT experiments but I had unspecified error...
And do you never encountered same error for prev builds?
--- End quote ---
the 8400 was running the v12 nokill and wasdoing fine other than a few inconclusives.
the 9800GT has no problems.
Raistmer:
Hm... interesting... can't recall on whose PC last released V2 was built - mine or Jason's? And what CUDA version was used at build time... Currently I did build with 2.3 CUDA SDK installed.
It would be good to discriminate effect of building environment and priority/affinity changes itself.
Cause nothing in data-processing path was changed I see no other possible reasons for such change in behavior...
Ah, BTW, I did one more change in last build (this change reduced executable size against prev builds) - dropped Volkov's FFT sources from build cause they not used (it seems CUDA compiler embed kernel code into executable even if kernel doesn't in use in program). This surely changed alignment of CUDA kernels. Could it be reason of this timeout you've seen - no idea...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version