Separation Runs ps_p_82_1s_dr8_4 and de_p_82_1s_dr8_4 Started
log in

Advanced search

Message boards : News : Separation Runs ps_p_82_1s_dr8_4 and de_p_82_1s_dr8_4 Started

1 · 2 · Next
Author Message
Jeffery M. Thompson
Volunteer moderator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 23 Sep 12
Posts: 145
Credit: 10,781,192
RAC: 6,350

Message 57964 - Posted: 22 Apr 2013, 19:07:39 UTC


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

John G
Send message
Joined: 1 Apr 10
Posts: 49
Credit: 171,863,025
RAC: 66

Message 57965 - Posted: 22 Apr 2013, 19:54:58 UTC

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


Regards

john g

Sunny129
Avatar
Send message
Joined: 25 Jan 11
Posts: 271
Credit: 346,072,284
RAC: 0

Message 57966 - Posted: 22 Apr 2013, 20:29:56 UTC

same here...
____________

Matthew
Volunteer moderator
Project developer
Project scientist
Send message
Joined: 6 May 09
Posts: 217
Credit: 6,856,375
RAC: 0

Message 57967 - Posted: 22 Apr 2013, 20:39:34 UTC

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

Link
Avatar
Send message
Joined: 19 Jul 10
Posts: 327
Credit: 16,283,020
RAC: 0

Message 57968 - Posted: 22 Apr 2013, 20:39:46 UTC

stream_fit_work_generator: not running
____________
.

Matthew
Volunteer moderator
Project developer
Project scientist
Send message
Joined: 6 May 09
Posts: 217
Credit: 6,856,375
RAC: 0

Message 57969 - Posted: 22 Apr 2013, 21:01:26 UTC

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

Jeffery M. Thompson
Volunteer moderator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 23 Sep 12
Posts: 145
Credit: 10,781,192
RAC: 6,350

Message 57970 - Posted: 22 Apr 2013, 21:32:56 UTC

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

Sunny129
Avatar
Send message
Joined: 25 Jan 11
Posts: 271
Credit: 346,072,284
RAC: 0

Message 57971 - Posted: 22 Apr 2013, 21:42:20 UTC

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

Len LE/GE
Send message
Joined: 8 Feb 08
Posts: 261
Credit: 104,050,322
RAC: 0

Message 57975 - Posted: 23 Apr 2013, 10:26:10 UTC

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

DrNoCDN
Send message
Joined: 24 Dec 09
Posts: 2
Credit: 10,708,491
RAC: 0

Message 57979 - Posted: 23 Apr 2013, 13:34:33 UTC

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

Len LE/GE
Send message
Joined: 8 Feb 08
Posts: 261
Credit: 104,050,322
RAC: 0

Message 57984 - Posted: 23 Apr 2013, 19:28:26 UTC

de_separation_12_3s_sscon_2

with the same error

Matthew
Volunteer moderator
Project developer
Project scientist
Send message
Joined: 6 May 09
Posts: 217
Credit: 6,856,375
RAC: 0

Message 57985 - Posted: 23 Apr 2013, 19:41:09 UTC - in response to Message 57984.

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.

Len LE/GE
Send message
Joined: 8 Feb 08
Posts: 261
Credit: 104,050,322
RAC: 0

Message 57988 - Posted: 24 Apr 2013, 0:09:47 UTC - in response to Message 57985.

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.

Profile JumpinJohnny
Send message
Joined: 29 Mar 13
Posts: 5
Credit: 31,192,336
RAC: 0

Message 57991 - Posted: 24 Apr 2013, 4:15:08 UTC - in response to Message 57988.


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.

Profile dskagcommunity
Avatar
Send message
Joined: 26 Feb 11
Posts: 170
Credit: 183,085,176
RAC: 0

Message 57992 - Posted: 24 Apr 2013, 5:36:57 UTC

I have too a problem on hd 4850 with this series of wus.
____________
DSKAG Austria Research Team: http://www.research.dskag.at



Profile RAMen
Avatar
Send message
Joined: 8 Apr 08
Posts: 45
Credit: 161,943,995
RAC: 0

Message 57993 - Posted: 24 Apr 2013, 7:27:33 UTC
Last modified: 24 Apr 2013, 7:32:28 UTC

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

Link
Avatar
Send message
Joined: 19 Jul 10
Posts: 327
Credit: 16,283,020
RAC: 0

Message 57998 - Posted: 24 Apr 2013, 15:12:32 UTC

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.
____________
.

DrNoCDN
Send message
Joined: 24 Dec 09
Posts: 2
Credit: 10,708,491
RAC: 0

Message 58001 - Posted: 24 Apr 2013, 21:11:28 UTC

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

Matthew
Volunteer moderator
Project developer
Project scientist
Send message
Joined: 6 May 09
Posts: 217
Credit: 6,856,375
RAC: 0

Message 58002 - Posted: 25 Apr 2013, 0:01:32 UTC

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.

Profile RAMen
Avatar
Send message
Joined: 8 Apr 08
Posts: 45
Credit: 161,943,995
RAC: 0

Message 58004 - Posted: 25 Apr 2013, 3:14:58 UTC
Last modified: 25 Apr 2013, 3:17:25 UTC

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

1 · 2 · Next
Post to thread

Message boards : News : Separation Runs ps_p_82_1s_dr8_4 and de_p_82_1s_dr8_4 Started


Main page · Your account · Message boards


Copyright © 2017 AstroInformatics Group