Are you saying that only about 10% of computers are experiencing issues? It is strange because there was a performance drop by 70% during last month: http://universeathome.pl/universe/history.php

Because is no new tasks really since then.

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Please help me understand this.

I have a Universe@Home task with the following properties:
App: Universe BHspin v2 0.01
Task: universe_bh2_160803_107_1_20000_1-999999_940000_1
URL: http://universeathome.pl/universe/result.php?resultid=21698177
Elapsed: 11:32:39
CPU Time: 17:42:40
CPU Time since checkpoint: 17:10:42
Estimated time remaining: 1d 00:00:32
Status: Will not suspend correctly, and looks like it'll never complete.

Questions:
1) Does this task look like it is a "problem" task that will never complete?
2) What information can I get you to help you solve the problem? Note: I copied the slot and project folder, so I might be able to run it outside of BOINC (if you give me instructions how), if that helps.
3) Is any progress being made to fix this issue?

Setting "No New Tasks" again ... :/

You're still trying Jacob. Fair enough. I don't crunch here anymore, his attitude is damaging to the entire BOINC environment. It is a real shame.

Maybe just lucky here, but no problems since I resumed on 27 April, and almost 300 validated by now. That includes mainly Universe BHspin v2 v0.01 but also some Universe Ultraviolet reionization v0.05. And I just started my first Universe QuarkStars v0.03 for a while, and they may have had problems before but I don't quite recall what, so we will see.
http://universeathome.pl/universe/results.php?hostid=68706

But I run Linux on that machine 24/7 and don't reboot, which may help.

If there is anything you'd like me to test or try, tell me what to do and I'll do it. I want it solved, and am willing to try things for you.

Unfortunately, I can't as I can't send source code.
The problem is the code compiles correctly without BOINC libraries, but with them not.
What makes situation strange, BOINC code in sources didn't change for almost a year, so it is well tested by us (all of us).
We make checks nearly every day trying to find wrong part, but this is going part by part in above 20k of source code lines.

With the current app - I can't identify problem as it exists only on some computers in very rare conditions and doesn't replicate on my development computers (two of them).

i have a feeling that defined library calls or something could be the cause of your problem....

#define Jippers=Nod24
#call Blender.Jazz

ill defined and so redefined .... in code without clear.


*****

AMD Platform Optimization - please read for all developers

https://community.amd.com/thread/213045

http://32ipi028l5q82yhj72224m8j.wpengine.netdna-cdn.com/wp-content/uploads/2017/03/GDC2017-Optimizing-For-AMD-Ryzen.pdf

http://www.agner.org/optimize/

http://www.agner.org

for example : 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 fma cx16 sse4_1 sse4_2 popcnt aes f16c syscall nx lm avx sse4a osvw xop wdt fma4 topx page1gb rdtscp bmi1

---

http://esa-space.blogspot.com/

boinc optimization > http://esa-space.blogspot.rs/2017/04/boinc.html

T/C/RNG/Entropy Drivers and sources > http://esa-space.blogspot.ru/2017/04/rng-and-random-web.html

Please help me understand this.

I have a Universe@Home task with the following properties:
App: Universe BHspin v2 0.01
Task: universe_bh2_160803_107_1_20000_1-999999_940000_1
URL: http://universeathome.pl/universe/result.php?resultid=21698177
Elapsed: 11:32:39
CPU Time: 17:42:40
CPU Time since checkpoint: 17:10:42
Estimated time remaining: 1d 00:00:32
Status: Will not suspend correctly, and looks like it'll never complete.

Questions:
1) Does this task look like it is a "problem" task that will never complete?
2) What information can I get you to help you solve the problem? Note: I copied the slot and project folder, so I might be able to run it outside of BOINC (if you give me instructions how), if that helps.
3) Is any progress being made to fix this issue?

Setting "No New Tasks" again ... :/

For BHspin for last 45k units I found 4 with "EXIT_TIME_LIMIT_EXCEEDED" and some with "Unknown error number" (about a 100 work units).
To start outside BOINC client just simply start executable file in command line.
But if tasks are not make checkpoints I strongly suspect that is frozen...

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

If I try to run the
BHspin2_1_windows_intelx86.exe
... from an Admin Command Prompt, it runs for a couple seconds, then quits, and this is in the stderr.txt:

13:11:18 (12760): BOINC client no longer exists - exiting
13:11:18 (12760): timer handler: client dead, exiting

Should I try anything else?

More importantly:
Is any progress being made to fix this issue?

Delete all files except param.in and executable file from folder then run it again.

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Alright. I now have 2 standalone instances of the exe running:

1) "From beginning": Started with a folder that only had BHspin2_1_windows_intelx86.exe and param.in
2) "From checkpoint": Started with a folder that had everything the BOINC slots folder had, except I removed: boinc_lockfile, boinc_task_state.xml, init_data.xml, job.xml

We'll see how long each takes... and see if the "From checkpoint" one gets stuck in an infinite loop. If so, I could send you a .zip of the files, for you to try.

I feel like I'm trying to solve this problem alone, sometimes.

How long is this task supposed to run?
So far, it has run for 15.6 hours, even from a fresh standalone folder outside of BOINC, which only had the .exe and the param.in file... and is still running.
How long should I let it continue, for it to be useful for us to diagnose the issue?

OS: Windows 10 Pro x64, Insider Fast Ring, Build 16184

CPU: Intel i7-5960X

Executable: BHspin2_1_windows_intelx86.exe (Executed from an Admin Command Prompt)

param.in:

BHspin2 v:160803
SET num_tested 20000
SET hub_val 1000
SET idum -940000
SET OUTPUT 3
SET Mmina 5.0
SET Mminb 3.0
SET golambda 1
SET Beta 0.5
SET Fa 1.0
SET Sigma3 265
SET Sal -2.3
SET SS 0
SET ZZ 0.0001

error.dat:

error: in Renv_con() unknown Ka type: 1, iidd_old: 757382error: in Menv_con() unknown Ka type: 1, iidd_old: 757382

checkpoint.dat:

6000 703458 0 1 2

log.txt:

00:00:00 00:00:00 PROGRAM START: Tue May 02 22:52:30 2017
00:00:00 00:00:00 no checkpoint.dat file found00:00:00 00:00:00 cleaning checkpoints
00:00:00 00:00:00 gw_cpfile: source file "data0.dat2" not present
00:00:00 00:00:00 gw_cpfile: source file "data1.dat2" not present
00:00:00 00:00:00 gw_cpfile: source file "data2.dat2" not present
00:00:00 00:00:00 gw_cpfile: source file "error.dat2" not present
00:00:00 00:00:00 reading checkpoint: istart: -1; pp: 0; n: -1
00:00:00 00:00:00 checkpoint read
00:00:00 00:00:00 default values set
00:00:00 00:00:00 Reading param.in file
00:00:00 00:00:00 PARAMIN: num_tested = 20000
00:00:00 00:00:00 PARAMIN: hub_val = 1000
00:00:00 00:00:00 PARAMIN: idum = -940000
00:00:00 00:00:00 PARAMIN: OUTPUT = 3
00:00:00 00:00:00 PARAMIN: Mmina = 5.0
00:00:00 00:00:00 PARAMIN: Mminb = 3.0
00:00:00 00:00:00 PARAMIN: golambda = 1
00:00:00 00:00:00 PARAMIN: Beta = 0.5
00:00:00 00:00:00 PARAMIN: Fa = 1.0
00:00:00 00:00:00 PARAMIN: Sigma3 = 265
00:00:00 00:00:00 PARAMIN: Sal = -2.3
00:00:00 00:00:00 PARAMIN: SS = 0
00:00:00 00:00:00 PARAMIN unknown parameter: name: SS; value: 0
00:00:00 00:00:00 PARAMIN: ZZ = 0.0001
00:00:00 00:00:00 param.in file read
00:00:00 00:00:00 idum: -940000; num_tested: 20000
00:03:54 00:03:54 making checkpoint: j: 1000; iidd: 119575
00:03:54 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:03:54 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:03:54 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:03:54 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:03:54 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:03:54 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:03:54 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:03:54 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:09:12 00:05:18 making checkpoint: j: 2000; iidd: 241537
00:09:12 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:09:12 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:09:12 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:09:12 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:09:12 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:09:12 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:09:12 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:09:12 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:14:35 00:05:23 making checkpoint: j: 3000; iidd: 360794
00:14:35 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:14:35 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:14:35 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:14:35 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:14:35 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:14:35 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:14:35 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:14:35 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:20:19 00:05:44 making checkpoint: j: 4000; iidd: 477940
00:20:19 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:20:19 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:20:19 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:20:19 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:20:19 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:20:19 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:20:19 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:20:19 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:25:39 00:05:20 making checkpoint: j: 5000; iidd: 594193
00:25:39 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:25:39 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:25:39 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:25:39 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:25:39 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:25:39 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:25:39 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:25:39 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:31:26 00:05:47 making checkpoint: j: 6000; iidd: 703458
00:31:26 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:31:26 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:31:26 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:31:26 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:31:26 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:31:26 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:31:26 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:31:26 00:00:00 gw_cpfile: error.dat appended to error.dat3

@Jacob Klein
Please, stop it at all, please send zipped folder to me (krzyszp @ interia . pl), because it shows that particular function have problem.

Also, if you experience long delay in checkpoints, please before you cancel it send mi whole folder to email provided above (if you just cancel it I don't have possibility to read files).

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Email sent. I hope that it helps you!
Question: You said "if you experience long delay in checkpoints" ...... but I need more info.
For a task that is working correctly: What is the longest amount of expected CPU Time between 2 checkpoints?

I think if time between two checkpoint is above two hours it is enough...
I suspect - because it this application relay on some random factors.

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Okay. If CPU Time between checkpoints is > 2 hours, it is a problem.
Do examples (like the one I emailed to you), help you to solve the problem??

Definatelly, because I get proper data to find source of the problem...

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

Okay. If CPU Time between checkpoints is > 2 hours, it is a problem.
Do examples (like the one I emailed to you), help you to solve the problem??

Definatelly, because I get proper data to find source of the problem...

Have you learned anything new, using the example that I sent to you?
I put forth effort to test it for hours, and then to get it to you, was hoping you would have replied by now.

Just a note I had 3 BHSpin together with this issue. I aborted two yesterday and the third one today after letting it run (it was still early in the crunching).

I don't remember if there were others as I recently realized I hadn't turned Universe back on and didn't really pay attention other than to note I had Ultraviolet and Quarkstars too (which is good to see :) ).

~Y

Okay. If CPU Time between checkpoints is > 2 hours, it is a problem.
Do examples (like the one I emailed to you), help you to solve the problem??

Definatelly, because I get proper data to find source of the problem...

Have you learned anything new, using the example that I sent to you?
I put forth effort to test it for hours, and then to get it to you, was hoping you would have replied by now.

Hello? Progress?

This is still an issue! :(

Can you PLEASE put more effort to STOP WASTING OUR CPU RESOURCES on this bug?? FIX IT!
I'm now PERMANENTLY setting "No New Tasks" for your project, because it ABUSES my resources!

I Just had another task, where it wasn't responding to suspend, and wasn't checkpointing, despite running for many hours. I confirmed that running it standalone exhibited the same problematic behavior. I aborted it. Details below.

OS: Windows 10 Pro x64, Insider Fast Ring, Build 16232
CPU: Intel i7-5960X
Executable: BHspin2_1_windows_intelx86.exe (Executed from an Admin Command Prompt)

param.in:

BHspin2 v:160803
SET num_tested 20000
SET hub_val 1000
SET idum -10000
SET OUTPUT 3
SET Mmina 5.0
SET Mminb 3.0
SET golambda 10
SET Beta 1.0
SET Fa 1.0
SET Sigma3 130
SET Sal -2.3
SET SS 0
SET ZZ 0.0001

error.dat:

error: in Renv_con() unknown Ka type: 1, iidd_old: 687281error: in Menv_con() unknown Ka type: 1, iidd_old: 687281

error.dat2

warning: derivative from dlnRdt() not accurate, error: 1e+030, K: 8, 291867
warning: derivative from dlnRdlnM() not accurate, error: 1e+030, K: 8, 291867
warning: derivative from dlnRdt() not accurate, error: 1e+030, K: 8, 512091
warning: derivative from dlnRdlnM() not accurate, error: 1e+030, K: 8, 512091

error.dat3

warning: derivative from dlnRdt() not accurate, error: 1e+030, K: 8, 291867
warning: derivative from dlnRdlnM() not accurate, error: 1e+030, K: 8, 291867
warning: derivative from dlnRdt() not accurate, error: 1e+030, K: 8, 512091
warning: derivative from dlnRdlnM() not accurate, error: 1e+030, K: 8, 512091

checkpoint.dat:

5000 600133 0 1 2

log.txt:

00:00:00 00:00:00 PROGRAM START: Fri Jun 30 09:49:13 2017
00:00:00 00:00:00 no checkpoint.dat file found00:00:00 00:00:00 cleaning checkpoints
00:00:00 00:00:00 gw_cpfile: source file "data0.dat2" not present
00:00:00 00:00:00 gw_cpfile: source file "data1.dat2" not present
00:00:00 00:00:00 gw_cpfile: source file "data2.dat2" not present
00:00:00 00:00:00 gw_cpfile: source file "error.dat2" not present
00:00:00 00:00:00 reading checkpoint: istart: -1; pp: 0; n: -1
00:00:00 00:00:00 checkpoint read
00:00:00 00:00:00 default values set
00:00:00 00:00:00 Reading param.in file
00:00:00 00:00:00 PARAMIN: num_tested = 20000
00:00:00 00:00:00 PARAMIN: hub_val = 1000
00:00:00 00:00:00 PARAMIN: idum = -10000
00:00:00 00:00:00 PARAMIN: OUTPUT = 3
00:00:00 00:00:00 PARAMIN: Mmina = 5.0
00:00:00 00:00:00 PARAMIN: Mminb = 3.0
00:00:00 00:00:00 PARAMIN: golambda = 10
00:00:00 00:00:00 PARAMIN: Beta = 1.0
00:00:00 00:00:00 PARAMIN: Fa = 1.0
00:00:00 00:00:00 PARAMIN: Sigma3 = 130
00:00:00 00:00:00 PARAMIN: Sal = -2.3
00:00:00 00:00:00 PARAMIN: SS = 0
00:00:00 00:00:00 PARAMIN unknown parameter: name: SS; value: 0
00:00:00 00:00:00 PARAMIN: ZZ = 0.0001
00:00:00 00:00:00 param.in file read
00:00:00 00:00:00 idum: -10000; num_tested: 20000
00:08:46 00:08:46 making checkpoint: j: 1000; iidd: 116149
00:08:46 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:08:46 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:08:46 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:08:46 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:08:46 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:08:46 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:08:46 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:08:46 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:20:05 00:11:19 making checkpoint: j: 2000; iidd: 234065
00:20:05 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:20:05 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:20:05 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:20:05 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:20:05 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:20:05 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:20:05 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:20:05 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:31:17 00:11:12 making checkpoint: j: 3000; iidd: 355368
00:31:17 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:31:17 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:31:17 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:31:17 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:31:17 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:31:17 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:31:17 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:31:17 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:41:49 00:10:32 making checkpoint: j: 4000; iidd: 481406
00:41:49 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:41:49 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:41:49 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:41:49 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:41:49 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:41:49 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:41:49 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:41:49 00:00:00 gw_cpfile: error.dat appended to error.dat3
00:51:08 00:09:19 making checkpoint: j: 5000; iidd: 600133
00:51:08 00:00:00 gw_cpfile: data0.dat appended to data0.dat2
00:51:08 00:00:00 gw_cpfile: data1.dat appended to data1.dat2
00:51:08 00:00:00 gw_cpfile: data2.dat appended to data2.dat2
00:51:08 00:00:00 gw_cpfile: error.dat appended to error.dat2
00:51:08 00:00:00 gw_cpfile: data0.dat appended to data0.dat3
00:51:08 00:00:00 gw_cpfile: data1.dat appended to data1.dat3
00:51:08 00:00:00 gw_cpfile: data2.dat appended to data2.dat3
00:51:08 00:00:00 gw_cpfile: error.dat appended to error.dat3