AK V8 + CUDA MB team work mod

[Raistmer]

Stock app should experience the same difficulties with server installation. So if stock works the reason in something else.

What driver do you use? 180.x required. I looked on yor link to result - "invalid device symbol" there.
This one: http://setiathome.berkeley.edu/result.php?resultid=1140067400

[Richard Haselgrove]

Yes, this is known inherently error of CUDA MB (but was unknown if this bug still with us or not).
Probably you can do nothing to avoid it, just kepp crunching - I hope this error prety rare. Thanks for report (I passed bug report to developer).

I have had two of these recently (with stock v6.08) - one already purged, the other
http://setiathome.berkeley.edu/result.php?resultid=1137771930

[P51 Mustang]

Stock app should experience the same difficulties with server installation. So if stock works the reason in something else.

What driver do you use? 180.x required. I looked on yor link to result - "invalid device symbol" there.
This one: http://setiathome.berkeley.edu/result.php?resultid=1140067400

Traced it down to the wrong video drivers.  Version 178.24 was installed Jan 7th 2009.  It has now been upgraded to version 181.22

[YukonTrooper]

I'm getting lots of computation errors.  Cuda app running fine + 4x AK V8 running fine, but fifth AK V8 will start and stop at 8-9 seconds with computation error.  Fifth AK V8 starts again and repeats.  Computation errors stack up quick!  I'm doing SETI and SETI Beta, but only installed package to setiathome.berkeley.edu folder not setiathome.berkeley.edu_beta folder.

Specs:

i7 920
GTX 260 216SP w/178.xx

Could you provide link on that host, please?
5th AK v8 (first one, actually) shouldn't take 8-9 seconds. It should take 0 seconds to pass control to CUDA MB....

http://setiathome.berkeley.edu/result.php?resultid=1140502904

Ok, 180.xx drivers are required.

Hmmm, but GPU WU's aren't the problem, it's the AK V8 WU's. 

[Raistmer]

I'm getting lots of computation errors.  Cuda app running fine + 4x AK V8 running fine, but fifth AK V8 will start and stop at 8-9 seconds with computation error.  Fifth AK V8 starts again and repeats.  Computation errors stack up quick!  I'm doing SETI and SETI Beta, but only installed package to setiathome.berkeley.edu folder not setiathome.berkeley.edu_beta folder.

Specs:

i7 920
GTX 260 216SP w/178.xx

Could you provide link on that host, please?
5th AK v8 (first one, actually) shouldn't take 8-9 seconds. It should take 0 seconds to pass control to CUDA MB....

http://setiathome.berkeley.edu/result.php?resultid=1140502904

Ok, 180.xx drivers are required.

Hmmm, but GPU WU's aren't the problem, it's the AK V8 WU's. 

Look at link you provided. It points on CUDA processed task.
ADDON: form stderr of your result:
Cuda error 'cudaMemcpyToSymbol(cudaAcc_GaussFit_settings, (void*) &settings, sizeof(settings))' in file 'd:/BTR/seticuda/seti_boinc/client/cuda/cudaAcc_gaussfit.cu' in line 454 : invalid device symbol.

The answer is the same - update to 18x.xx drivers.

[wickedguy]

Working very Great on my Amd X2 5000+ with an old 8800 Gs Card!

But I cant use my SLI 9800Gtx+ on my Q6600.

[Raistmer]

Working very Great on my Amd X2 5000+ with an old 8800 Gs Card!

But I cant use my SLI 9800Gtx+ on my Q6600.

SLI is not supported by CUDA. It will see cards in SLI mode as one device (if will work at all).

[wickedguy]

Working very Great on my Amd X2 5000+ with an old 8800 Gs Card!

But I cant use my SLI 9800Gtx+ on my Q6600.

SLI is not supported by CUDA. It will see cards in SLI mode as one device (if will work at all).

My bad, i means my 2 x 9800gtx. Of course I disabled SLI. But your package doesnt use my second card at all

[Raistmer]

Yes, it shouldn't, read again first post.
For dual GPU configs V7x of combo is more suitable, V8x for single GPU only.

[wickedguy]

Yes, it shouldn't, read again first post.
For dual GPU configs V7x of combo is more suitable, V8x for single GPU only.

Yup I read it, and i used it! But I cant get any more AP Wu since the last 3-4days, So i switched to V8x for that reason 

[Raistmer]

Yes, it shouldn't, read again first post.
For dual GPU configs V7x of combo is more suitable, V8x for single GPU only.

Yup I read it, and i used it! But I cant get any more AP Wu since the last 3-4days, So i switched to V8x for that reason 

Yeah, unfortunately both approaches have their own flaws. Hope sooner or later BOINC will do shceduling work by itself as it should be.
For now I can recommend switching to V7x combo while doing another CPU-based project like Einstein. That way you will use both GPU cards and do good things with your CPU also.
AP work is now ceased cause new AP version in testing...

[YukonTrooper]

Look at link you provided. It points on CUDA processed task.
ADDON: form stderr of your result:
Cuda error 'cudaMemcpyToSymbol(cudaAcc_GaussFit_settings, (void*) &settings, sizeof(settings))' in file 'd:/BTR/seticuda/seti_boinc/client/cuda/cudaAcc_gaussfit.cu' in line 454 : invalid device symbol.

The answer is the same - update to 18x.xx drivers.

I noticed that, but I didn't think anything of it because it was the AK V8 processes failing; however, I updated to 180.xx and I now see how everything works.  MB works but CUDA doesn't show up in Boinc Manager.  This is normal, correct?  Can I suspend CUDA without suspending anything else for when I play games, or do I have to cancel the whole project?

[Josef W. Segur]

...
AP work is now ceased cause new AP version in testing...

The ap_splitters at main finished splitting all the data the project had on hand, a hoped-for shipment from Arecibo didn't arrive Friday, and the HPSS which has the reserve stock of unsplit data was being upgraded so Matt couldn't get more data. If they've also decided to not split AP work when there's some available, that's good too.
                                                                                   Joe

[Raistmer]

...
AP work is now ceased cause new AP version in testing...

The ap_splitters at main finished splitting all the data the project had on hand, a hoped-for shipment from Arecibo didn't arrive Friday, and the HPSS which has the reserve stock of unsplit data was being upgraded so Matt couldn't get more data. If they've also decided to not split AP work when there's some available, that's good too.
                                                                                   Joe

It's offtopic to current thread but too curious not to ask
Is data set that possible to process with AP so smaller than MB one ?? We do MB many years already - do that huge data array not suitable for AP ?

[Raistmer]

I noticed that, but I didn't think anything of it because it was the AK V8 processes failing; however, I updated to 180.xx and I now see how everything works.  MB works but CUDA doesn't show up in Boinc Manager.  This is normal, correct?  Can I suspend CUDA without suspending anything else for when I play games, or do I have to cancel the whole project?

Reread first post once more
There is NO separate CUDA app from BOINC point of view. BOINC doesn't know anything about this CUDA app. It's modified AK_v8 who will call CUDA and who will fail for BOINC if CUDA fails.