Posts by tpl
log in
1) Message boards : Number crunching : Solo_collatz wus waiting for validation (Message 17656)
Posted 1556 days ago by Profile tpl
Down to 250 pending Solo-collatz....
2) Message boards : Number crunching : Solo_collatz wus waiting for validation (Message 17654)
Posted 1557 days ago by Profile tpl
1220 Pending Solo-Collatz here at the moment....
3) Message boards : News : Badges? We need stinkin' badges! (Message 17614)
Posted 1565 days ago by Profile tpl
We will see whats coming.... :-)
4) Message boards : News : Badges? We need stinkin' badges! (Message 17596)
Posted 1568 days ago by Profile tpl
Emerald...Allready done....what is the next goal :-))
5) Message boards : Number crunching : How to: reduce CPU usage while running on Intel GPU (Message 17031)
Posted 1662 days ago by Profile tpl
hi,
when i start crunching with Intel GPU..... 1 Core from
my 7990 crunching with half power....
2 WU's per core>>>8 WU's with the ati's and 2 WU's
with the Intel GPU at the same time.
When i disable the Intel GPU all ATI cores running
normal with the same speed.


Win7, aktual boinc,
2x ATI 7990
1x Intel Hd 4000
6) Message boards : News : v4.07 Released for Windows (Message 16551)
Posted 1701 days ago by Profile tpl
When i only use the HD4000 for a Monitor boinc find the Intel GPU....
The Problem...my ati´s run with 2 WU´s for 1 GPU and now the Intel GPU
does the same....thats very slow..
I became some error Messages on the Intel WU:
<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -16777217 (0xfeffffff)
</message>
<stderr_txt>
Collatz Conjecture v4.05 x86_64 for OpenCL 1.0 or later
Based on the AMD Brook+ kernels by Gipsel
Suspending...

Resuming at 2379563904726125488488
At offset 83342020355 got 1599 from the GPU when expecting 627
Error: GPU steps do not match CPU steps. Workunit processing has been aborted.
14:22:46 (3736): called boinc_finish

</stderr_txt>
]]>

and the other message:

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<stderr_txt>
Collatz Conjecture v4.05 x86_64 for OpenCL 1.0 or later
Based on the AMD Brook+ kernels by Gipsel
12:08:36 (3568): Can't acquire lockfile (32) - waiting 35s
12:09:11 (3568): Can't acquire lockfile (32) - exiting
12:09:11 (3568): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
12:15:44 (3260): Can't acquire lockfile (32) - waiting 35s
12:16:19 (3260): Can't acquire lockfile (32) - exiting
12:16:19 (3260): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
13:40:28 (1392): Can't acquire lockfile (32) - waiting 35s
13:41:03 (1392): Can't acquire lockfile (32) - exiting
13:41:03 (1392): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
14:23:24 (5488): Can't acquire lockfile (32) - waiting 35s
14:23:59 (5488): Can't acquire lockfile (32) - exiting
14:23:59 (5488): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
14:42:15 (2908): Can't acquire lockfile (32) - waiting 35s
14:42:50 (2908): Can't acquire lockfile (32) - exiting
14:42:50 (2908): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
15:25:35 (6096): Can't acquire lockfile (32) - waiting 35s
15:26:10 (6096): Can't acquire lockfile (32) - exiting
15:26:10 (6096): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
15:44:23 (6460): Can't acquire lockfile (32) - waiting 35s
15:44:58 (6460): Can't acquire lockfile (32) - exiting
15:44:58 (6460): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
16:27:23 (4352): Can't acquire lockfile (32) - waiting 35s
16:27:58 (4352): Can't acquire lockfile (32) - exiting
16:27:58 (4352): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
16:45:48 (3716): Can't acquire lockfile (32) - waiting 35s
16:46:23 (3716): Can't acquire lockfile (32) - exiting
16:46:23 (3716): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
17:29:07 (7872): Can't acquire lockfile (32) - waiting 35s
17:29:42 (7872): Can't acquire lockfile (32) - exiting
17:29:42 (7872): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
17:47:31 (8060): Can't acquire lockfile (32) - waiting 35s
17:48:06 (8060): Can't acquire lockfile (32) - exiting
17:48:06 (8060): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
18:31:18 (8932): Can't acquire lockfile (32) - waiting 35s
18:31:53 (8932): Can't acquire lockfile (32) - exiting
18:31:53 (8932): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
18:49:09 (8964): Can't acquire lockfile (32) - waiting 35s
18:49:44 (8964): Can't acquire lockfile (32) - exiting
18:49:44 (8964): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
19:32:53 (5952): Can't acquire lockfile (32) - waiting 35s
19:33:28 (5952): Can't acquire lockfile (32) - exiting
19:33:28 (5952): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
19:51:09 (996): Can't acquire lockfile (32) - waiting 35s
19:51:44 (996): Can't acquire lockfile (32) - exiting
19:51:44 (996): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
20:34:53 (3548): Can't acquire lockfile (32) - waiting 35s
20:35:28 (3548): Can't acquire lockfile (32) - exiting
20:35:28 (3548): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
20:52:48 (6184): Can't acquire lockfile (32) - waiting 35s
20:53:23 (6184): Can't acquire lockfile (32) - exiting
20:53:23 (6184): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
21:36:29 (7444): Can't acquire lockfile (32) - waiting 35s
21:37:04 (7444): Can't acquire lockfile (32) - exiting
21:37:04 (7444): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)
21:54:55 (8712): Can't acquire lockfile (32) - waiting 35s
21:55:30 (8712): Can't acquire lockfile (32) - exiting
21:55:30 (8712): Error: Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

(0x20)

Resuming at
checkpoint data not consistent! Starting from scratch.

Highest Steps 1966 for 2379563904426547183950
Total Steps 418500978346474
Avg Steps 507
CPU time 36902.5 seconds
Total time 37666.7 seconds
09:05:02 (4216): called boinc_finish

</stderr_txt>
]]>

7) Message boards : News : v4.07 Released for Windows (Message 16540)
Posted 1702 days ago by Profile tpl
4.07 running without Problems on my 7990
Running 2 Units on each gpu with98-99%
i need 1900-2250 sec for a solo wu and (i don´t know
why) nearly the same time for the Collatz wu´s?!?
Win 7-64 Ati 12.1 Driver, Boinc 7.0.64
Boinc don´t want to use the Intel HD4000
8) Message boards : Number crunching : How long should 3.13 with cuda 4.2 take? (Message 15966)
Posted 1814 days ago by Profile tpl
I see such a problem at my gtx 560 ti 2 win dual GPU....
1 GPU running with normal speed the second need 3 time longer for a WU.
with evga Percussion i see that the second GPU running with 425 instead
of 850 MHz.... I must restart the pc and after restart the two GPUs running
with 850....
i don't know why but after restart 2 days ago the GPUs running
with the normal speed...
9) Message boards : Number crunching : No work available for the applications you have selected (Message 15813)
Posted 1845 days ago by Profile tpl
Is 7.0.35/42 beta....maybe they will fix it
befor became oficial status...
10) Message boards : Number crunching : GPU Stops crunching (Message 15812)
Posted 1845 days ago by Profile tpl
So much ideas....wow
11) Message boards : Number crunching : Challenge (Message 15769)
Posted 1847 days ago by Profile tpl
Hihi, yes....especially when we are in Front :-)
12) Message boards : Number crunching : GPU Stops crunching (Message 15764)
Posted 1848 days ago by Profile tpl
For example:

Name collatz_2377879015644520491368_824633720832_0
Arbeitspaket 57246525
Erstellt 24 Dec 2012 14:01:37 UTC
Gesendet 24 Dec 2012 14:18:06 UTC
Empfangen 26 Dec 2012 20:04:15 UTC
Serverstatus Abgeschloßen
Resultat Erfolgreich
Clientstatus Fertig
Exit status 0 (0x0)
Computer ID 118368
Ablaufdatum 31 Dec 2012 14:18:06 UTC
Laufzeit 14,015.70
CPU Zeit 252.27
Prüfungsstatus gestartet
Punkte 0.00
Anwendungsversion collatz v2.03 (cuda23)
Stderr output

<core_client_version>7.0.28</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 2377879015644520491368
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 2377879015644520491368
Resuming from checkpoint ... done
needed 1785 steps for 2377879015914387721287
427602391386580 total executed steps for 824633720832 numbers

WU completed.
GPU time: 3591.04 seconds
Elapsed time: 3585.33
called boinc_finish

</stderr_txt>
]]>

Look here:
Laufzeit 14,015.70
GPU time: 3591.04 seconds
13) Message boards : Number crunching : GPU Stops crunching (Message 15759)
Posted 1848 days ago by Profile tpl
Hi,
we have a problem with stock app...
GPU Stops crunching but the time goes on...
After restart the PC all running normal...
The same on NVIDIA 560ti, gtx 295, gtx 470
Can somebody help?
14) Message boards : Number crunching : Challenge (Message 15692)
Posted 1852 days ago by Profile tpl
hallo friends of collatz conjekture....
We have a smal challenge..

http://boincstats.com/en/stats/challenge/team/chat/299

Have a nice fight...
tpl/GPUUG
15) Message boards : Number crunching : cuda50/4.2 error on gtx9800 (Message 15664)
Posted 1856 days ago by Profile tpl
Hi,
my old NVIDIA (9800gt, 9800gtx, 9800gx2) don't
running with cuda50/4.2 optimized apps 3.17...
WU's finished very fast without error but also
without some steps...
16) Message boards : Number crunching : Upload.... (Message 15586)
Posted 1869 days ago by Profile tpl
My proxy was the problem...
17) Message boards : Number crunching : Upload.... (Message 15556)
Posted 1873 days ago by Profile tpl
Can't upload at the moment...
18) Message boards : Number crunching : Where's the Beef !? (Message 15534)
Posted 1879 days ago by Profile tpl
FYI, the CUDA 4.2 and CUDA 5 apps have been working very well, so I plan to make them standard apps very soon. With the new .config files, they are even easier to optimize as they don't require an app_info.xml.


don´t running with 9800, 9800 gtx+ and 9800 gx2...
maybe i make some mistake...who knows...

BTW 3,4mio pending
19) Message boards : Number crunching : Where's the Beef !? (Message 15523)
Posted 1882 days ago by Profile tpl
Hi,
i crunch collatz normaly with some ATI GPUs....
Now i switch some NVIDIA GPUs from seti...
I use the optimizet app's for my 200-600 series....
Which app is the best for my old 9800 GPUs?

BTW. have 2,6 mio pendings now...




Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.