Posts by kmanley57
log in
1) Message boards : Windows : CPU workunit availability (Message 16667)
Posted 1696 days ago by Profile kmanley57
Thank you! You made my day with getting new work.
2) Message boards : News : Collatz 4.xx Applications Released for Linux (Message 16149)
Posted 1757 days ago by Profile kmanley57
They are taking a long time to run! 6+ hours for a mini-collatz. I look forward to seeing the results of the change over. I hope there is a change I can do to get them to run faster for sure!!!
3) Message boards : Windows : CUDA WU's errors (Message 13779)
Posted 2108 days ago by Profile kmanley57
I am not sure it makes any difference, I use a 'dummy plug' which makes it think there is a monitor but there really isn't. Here is a link to make your own if you need it: http://www.overclock.net/t/384733/the-30-second-dummy-plug


No, I have a dummy plug on the one unused video connector. But by extending the desktop on to the other monitors resolved the cards/monitor going to sleep or whatever was done to them.

The other GPU projects I run did not need me to do this, but ?????
4) Message boards : Windows : CUDA WU's errors (Message 13770)
Posted 2109 days ago by Profile kmanley57
I have enabled the monitors in M.S. I will see if that makes any difference.
5) Message boards : Windows : CUDA WU's errors (Message 13768)
Posted 2109 days ago by Profile kmanley57
Did those 'fixes' several weeks ago before I start running any Wu from Collatz. So am hoping that is not it. I have a GPU monitoring program(EVGA PrecisionX) running on it so I can watch the usage drop off, then I go to my monitoring machine running BoincTasks and suspend and resume from it.

I had had a number of failed results on other projects that had me add the loopback connectors, which did not do anything anyway. This is the only project that has been giving this result of just stopping the WU. I may have to splurge and get an ATI card to place in there and run both types to see if it does it also.

On a side note one of the two cards does have monitors connected to both video connectors. I do not use them, so M.S. turns them off! But they are connected.
6) Message boards : Windows : CUDA WU's errors (Message 13765)
Posted 2109 days ago by Profile kmanley57
I have noticed ALL my cuda23 WU's seem to stop processing after about an hour, but suspending then resuming the task after boinc has started another WU, I then come back and resume the hung WU later when the new cuda23 WU stops processing.

Both installed cards do the same thing.

Processor: 4 AuthenticAMD AMD FX(tm)-4100 Quad-Core Processor [Family 21 Model 1 Stepping 2]
Processor: 2.00 MB cache
Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 cx16 sse4_1 sse4_2 syscall nx lm svm sse4a osvw ibs xop skinit wdt lwp fma4 page1gb rdtscp
OS: Microsoft Windows Vista: Ultimate x86 Edition, Service Pack 2, (06.00.6002.00)
Memory: 2.99 GB physical, 6.17 GB virtual
Disk: 76.69 GB total, 15.69 GB free
Local time is UTC -6 hours
NVIDIA GPU 0: GeForce 9800 GT (driver version 296.10, CUDA version 4.20, compute capability 1.1, 1024MB, 976MB available, 504 GFLOPS peak)
NVIDIA GPU 1: GeForce GTS 450 (driver version 296.10, CUDA version 4.20, compute capability 2.1, 2048MB, 1954MB available, 601 GFLOPS peak)
OpenCL: NVIDIA GPU 0 (not used): GeForce 9800 GT (driver version 296.10, device version OpenCL 1.0 CUDA, 1024MB, 976MB available)
OpenCL: NVIDIA GPU 1 (not used): GeForce GTS 450 (driver version 296.10, device version OpenCL 1.1 CUDA, 2048MB, 1954MB available)

Paste of WU that I had to suspend, then restart to get to complete:

Collatz Conjecture 2.03 collatz (cuda23) collatz_2374834517528311212392_824633720832_1 02:20:44 (00:08:43) 4/12/2012 10:36:12 AM 4/12/2012 10:38:16 AM 0.01C + 1 NVIDIA GPU (d1) Reported: OK * MegaMan

Task 113014382 Workunit 49474699

STDERR report attached to task:

<core_client_version>7.0.25</core_client_version>
<![CDATA[
<stderr_txt>
Running Collatz Conjecture (3x+1) CUDA GPU application v2.01
based on version 1.2 by Gipsel
instructed by BOINC client to use device 1
Reading input file ... done.
Checking 824633720832 numbers starting with 2374834517528311212392
No checkpoint data found.
Running Collatz Conjecture (3x+1) CUDA GPU application v2.01
based on version 1.2 by Gipsel
instructed by BOINC client to use device 0
Reading input file ... done.
Checking 824633720832 numbers starting with 2374834517528311212392
Resuming from checkpoint ... done
needed 1759 steps for 2374834517679537690358
444630872738552 total executed steps for 824633720832 numbers

WU completed.
GPU time: 3771.35 seconds
Elapsed time: 3776.15
called boinc_finish

</stderr_txt>
]]>

I had one WU before I upgraded to the latest version of Boinc, and it also hung/stopped.

Task 112735111 Workunit 49376680

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<stderr_txt>
Running Collatz Conjecture (3x+1) CUDA GPU application v2.01
based on version 1.2 by Gipsel
instructed by BOINC client to use device 0
Reading input file ... done.
Checking 824633720832 numbers starting with 2374796169998708222312
No checkpoint data found.
Running Collatz Conjecture (3x+1) CUDA GPU application v2.01
based on version 1.2 by Gipsel
instructed by BOINC client to use device 1
Reading input file ... done.
Checking 824633720832 numbers starting with 2374796169998708222312
Resuming from checkpoint ... done
needed 1661 steps for 2374796170036590065311
422192759689365 total executed steps for 824633720832 numbers

WU completed.
GPU time: 4408.63 seconds
Elapsed time: 4434.02
called boinc_finish

</stderr_txt>
]]>




Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.