David, Eric: I'm beginning to get worried that this may be happening because:
* Fermi cards are in the retail chain, in quantity, and * No Fermi compatible app has been installed on the main project yet We have at least one report (http://setiathome.berkeley.edu/forum_thread.php?id=60079#1000943) of a user who installed the card first, and asked questions afterwards: I haven't dared look to see how many more examples there are in Q & A. Perhaps people spotting and tempted to report this problem could check for the Fermi hardware / stock cuda23 application combo. Now we've got the DLL compatibility and application planning under control at SETI Beta, how close are we to declaring v6.10 "tested" and safe to install at the main SETI project? That would ease a lot of the problems, and nip this data pollution in the bud. ----- Original Message ----- From: "David Anderson" <[email protected]> To: "Raistmer" <[email protected]> Cc: <[email protected]> Sent: Thursday, June 03, 2010 9:59 PM Subject: Re: [boinc_dev] host punishment mechanism revisited >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.
