I started two more separation runs listed:

ps_p_82_1s_dr8_4
de_p_82_1s_dr8_4

Let me know if you have problems with them specifically.



Jeff Thompson

Hey
Whats sup ==== not getting any new WU's as of right now ???


Regards

john g

same here...

---

The work generator for separation seems to be down. I'm on it.

stream_fit_work_generator: not running

---

Looks like the work generator is back up now. Some of the runs didn't have the correct file permissions, and so they were crashing the stream fit work generator when it tried to access those files.

I killed all of the offending runs, and started some new ones:

de_separation_12_3s_sscon_2
de_separation_13_3s_sscon_2

These runs are resuming with updated permissions

under the names

ps_p_82_1s_dr8_4_2

de_p_82_1s_dr8_4_2



Jeff

just started getting new work...way to stay on top of it guys!

---

24 of those last night:

de_separation_13_3s_sscon_2

An output buffer would exceed CL_DEVICE_MAX_MEM_ALLOC_SIZE
Capability check failed for cut 0
Failed to calculate likelihood

Confirm previous post.. Still receiving ATI WUs with errors:

de_separation_13_3s_sscon_2

An output buffer would exceed CL_DEVICE_MAX_MEM_ALLOC_SIZE
Capability check failed for cut 0
Failed to calculate likelihood

However, I am also receiving the de_p_82_1s_dr8_4_2 ATI WUs , which are completing without any issue...

DrNoCDN

de_separation_12_3s_sscon_2

with the same error

de_separation_12_3s_sscon_2

with the same error

Looking at the error logs, it looks like your BOINC client may be out of date. The error that you received is typical when running an outdated BOINC client, an outdated Milkyway@home app, or an old (or buggy) GPU driver. Try making sure all of those are up to date and see if you still get errors.

The overall error rates are currently low, so I think the new runs are doing well.

de_separation_12_3s_sscon_2

with the same error

Looking at the error logs, it looks like your BOINC client may be out of date. The error that you received is typical when running an outdated BOINC client, an outdated Milkyway@home app, or an old (or buggy) GPU driver. Try making sure all of those are up to date and see if you still get errors.

The overall error rates are currently low, so I think the new runs are doing well.

You must have looked into different error logs than I did.
I am talking about errors of WU type
de_separation_12_3s_sscon_2 and
de_separation_13_3s_sscon_2.
Those are the only WUs that I see in my error list.

1) The error comes from out of the mw app (see setup_cl.c, separationCheckCutMemory), not from the BOINC client.
2) I am running milkyway_separation_1.02_windows_intelx86__opencl_amd_ati.exe (with app_info to use the command line params). If you have a newer internal version that I could try, I am willing to.
3) cat 12.1 (on Win XP) has never been a problem with every WU before and after
de_separation_12_3s_sscon_2 and
de_separation_13_3s_sscon_2

4) DrNoCDN gets the same error with those runs on Linux with BOINC 7 client, a newer cat version and the linux app.

There must be something special in those runs, making them error out on some systems but not on others.
My best guess for now is a WU paramter too close to the limit to work on all systems.

Sorry, I am not going to mess with a stable system because of 2 runs and an unknown cause of those errors. Sitting them out and live with the 2s per WU error is the better choice for the moment.

I am talking about errors of WU type
de_separation_12_3s_sscon_2 and
de_separation_13_3s_sscon_2.
Those are the only WUs that I see in my error list.

I am having the same problems with these 2 running amd on boinc client on win7.
I even installed new client 7.0.64 clean ... same problems. I'm using an ATI Radeon HD 4800 Series GPU with newest driver.

I have too a problem on hd 4850 with this series of wus.

---

DSKAG Austria Research Team: http://www.research.dskag.at

Multiple errors for : de_separation_13_3s_sscon_2.
[edit]
also de_separation_12_3s_sscon_2.

Win xp and hd5850

---

OWN every thing I need
EARN.. enough to live !!!
WANT a solar array on the roof so I can run a BOINC farm( DREAM on!!)
NO wife
NO kids
NO troubles

Have some issues with *separation_12_3s_sscon_2* and *separation_13_3s_sscon_2* too.

Not with errors or validation, but some of them make my system unusable and take over 4600 seconds instead of the expected ~800 with 80-85% GPU load instead of the usual 99% I have (and no performance issues with that 99%). That's over 1 hour for a task, which should be completed in 12-13 minutes and all that time my computer is almost unusable.

Most of them are OK, but the performance issues are really annoying.

My system:
- Win7 with BOINC 6.12.34
- ATI HD3850, 0.82 CAL application (no OpenCL support on that GPU), running 2 WUs at once

All other WUs run fine.

---

Ya, I'm still throwing computation errors on anything that is de_separation_12_3s_sscon_2... on a Win7x64 box and a Linux box

Both are running Radeon 4800 series GPUs and Boinc 7.0.28

Running de_separation_09_3s_sscon_1 and de_separation_11_3s_sscon_1 tasks no problem on the same boxes

Hmm... The only thing that seems to be different between the "12/13" and "11" runs is that I bumped up the step sizes a bit on one of the integrals. I'm not sure why these runs are failing for you, but my best guess is that the slightly higher step sizes were just enough to overflow the memory in your GPUs - which might explain why most users are not having the same issue.

I've stopped the "de_separation_12_3s_sscon_2" and "de_separation_13_3s_sscon_2" runs and restarted them with "3" at the end instead of "2", this time with integral sizes that are the same as the "11" runs. If the restarted runs run fine for you, then I guess the step sizes were the culprit. Let me know how they go for you.

I can confirm the

de_separation_12_3s_sscon_2 workunits continue to fail

while

de_separation_12_3s_sscon_3 workunits process correctly

i7:920 + hd4850 +winxp

---

OWN every thing I need
EARN.. enough to live !!!
WANT a solar array on the roof so I can run a BOINC farm( DREAM on!!)
NO wife
NO kids
NO troubles