Posts by noderaser

21) Questions and Answers : Windows : All tasks failing on R9 280X (Message 6068) Posted 9 Aug 2014 by noderaser Post: I recently built a shiny new machine with a Radeon R9 280X, and thus far all of my GPU tasks have failed. Here's a sample from a recently failed task: dnetc v2.9109-518-CTR-10092921 for ATI Stream on Win32 (WindowsNT 6.1). Using email address (distributed.net ID) '<censored> ' [Aug 08 08:28:00 UTC] Automatic processor type detection found an unknown processor. [Aug 08 08:28:00 UTC] RC5-72: using core #0 (IL 4-pipe c). [Aug 08 08:28:00 UTC] RC5-72: Loaded D2:BCF0B300:00000000:642^32 [Aug 08 08:28:00 UTC] RC5-72: 11 packets (704.00 stats units) remain in in.r72 [Aug 08 08:28:00 UTC] RC5-72: 0 packets are in out.r72 [Aug 08 08:28:00 UTC] 1 cruncher has been started. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:00 UTC] Core compilation failed. Exiting. [Aug 08 08:28:01 UTC] Core compilation failed. Exiting. [Aug 08 08:28:01 UTC] Core compilation failed. Exiting. [Aug 08 08:28:01 UTC] Core compilation failed. Exiting. [Aug 08 08:28:01 UTC] Break* Shutting down... [Aug 08 08:28:01 UTC] Core compilation failed. Exiting. [Aug 08 08:28:01 UTC] RC5-72: Saved D2:BCF0B300:00000000:64*2^32 (0 keys done) 0.00:00:01.09 - [0 keys/s] [Aug 08 08:28:01 UTC] RC5-72: 12 packets (768.00 stats units) are in in.r72 [Aug 08 08:28:01 UTC] RC5-72: 0 packets are in out.r72 [Aug 08 08:28:01 UTC] Shutdown complete. 01:28:01 (6428): input buffer 12 packets (2144 bytes), checkpoint file 0 packets (32 bytes), output buffer 0 packets (0 bytes) 01:28:01 (6428): premature exit detected, app exit status: 0x1 01:28:01 (6428): no progress detected during last retry 01:28:01 (6428): too many retries (max 10), cancelling 01:28:01 (6428): called boinc_finish
22) Message boards : Number crunching : Huge Decrease in GPU Runtimes (Message 6017) Posted 21 Apr 2014 by noderaser Post: I should also point out, that Moo! does not seem to make full use of my GPU, it hovers around 90% +/- 5% utilization. I'm not saying that's a completely terrible thing, as it allows me to run GPU computation all the time without a lag in the UI, but perhaps it could be improved on so the project runs more efficiently?
23) Message boards : Number crunching : Huge Decrease in GPU Runtimes (Message 6005) Posted 16 Apr 2014 by noderaser Post: I've noticed that within the past few days, my average runtime for GPU units on my HD4670 has dropped from around 2 hours to 18 minutes. I'm not saying that's a bad thing, just curious as to why such a sudden and drastic change would crop up. I've noticed on the Server Status page, that there are workunits of varying sizes, is there info anywhere on what constitutes one size of workunit versus another? And, is there a way to determine which size a particular workunit is? Lastly, it would be great if I could get this project working on my Mac OS X clients; the GeForce 320M does nothing but error out and the HD6750M never gets any work.
24) Questions and Answers : Macintosh : CUDA tasks failing on MacBook Pro (Message 5804) Posted 2 Jan 2014 by noderaser Post: Haven't had a successful one yet on this host. No problems from my two AMD hosts, an iMac and Win7 machine. MacBook Pro, 13" Mid-2010 2.4 GHz C2D/4 GB RAM nVidia GeForce 320M 256 MB OS X 10.8.5 BOINC 7.2.33 Same host handles Collatz tasks without incident. Recently upgraded BOINC client, have two in the queue that have failed but not reported yet. From the last returned WU: <core_client_version>7.2.28</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> dyld: DYLD_ environment variables being ignored because main executable (/Library/Application Support/BOINC Data/slots/2/../../switcher/switcher) is setuid or setgid 00:30:42 (2877): wrapper: starting v1.3.9.7 00:30:42 (2877): device: 1 x GeForce 320M (driver version 5.5.28, CUDA version 5.50, compute capability 1.2, 253MB, 121MB available, 137 GFLOPS peak) 00:30:42 (2877): checkpoint interval: 15 min (task 56000 GFLOPS, 7 min) 00:30:42 (2877): wrapper: running dnetc518-macosx-x86-cuda31 (-ini dnetc.ini -runoffline -multiok=1) - attempt 1/10 dyld: Library not loaded: @rpath/libtlshook.dylib Referenced from: /Library/Application Support/BOINC Data/slots/2/libcudart.dylib Reason: image not found 00:30:45 (2877): app exit status: 0x5 00:30:45 (2877): called boinc_finish </stderr_txt> ]]>

Previous 20