Or a bug in the GPU driver. Either way I agree boinc shouldn't try to "support" that nasty situation of the device becoming *unusable* until a reboot.
What if the user tries to run a CUDA-enabled video encoder after SETI temporarily blocked up the GPU? El 03/06/2010, a las 17:59, David Anderson <[email protected]> escribió: > I don't think BOINC can or should solve this problem; > it's a problem with the s...@home CUDA app. > Eric, are you aware of this? > -- David > > Raistmer wrote: >> One more example when 2 overflows suppressed single non-overflowed >> (and much >> probably valid) result and passed through Validator into database. >> These >> CUDA-induced overflows can pollute SETI's database. >> http://setiathome.berkeley.edu/workunit.php?wuid=618018953 > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
