Message boards :
News :
testing work generation with 'ps_separation_14_2s_null_3'
Message board moderation
Previous · 1 · 2 · 3 · 4 · Next
Author | Message |
---|---|
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
GPU-only tasks tested ... Very strange, it looks like they ran successfully. I have no clue why the client would have marked them as errors. Send Matt A. a message so hopefully he'll know what the issue is. |
Send message Joined: 5 Nov 10 Posts: 69 Credit: 15,064,831 RAC: 0 |
To be clear:- PC #A is 446288 (all but one old WU consistently fail, post-e.g., 1st June, 22:00 UTC). PC #B is 231173 (all old tasks complete OK, no new tasks for days as switched off). Can you point me to where you see PC #A (446288, post- 1st June, about 22:00 UTC) succeed processing any but that one [old] GPU task? Apologies if I've got any of this wrong. I'm not an expert, just a cruncher. |
Send message Joined: 29 Nov 10 Posts: 4 Credit: 4,783,425 RAC: 0 |
Just had 6 wus abort with computation error, all were ps separation null3 v4 units. This machine has had zero problems with any wus prior to today |
Send message Joined: 5 Sep 08 Posts: 28 Credit: 245,585,043 RAC: 0 |
Same here ... all errored out. I will leave a couple of cards here in case you need some testers. Good luck! |
Send message Joined: 22 Oct 11 Posts: 23 Credit: 71,023,220 RAC: 0 |
My systems are not able to get new work units to even check and see if and when things are fixed. ^..^~~ |
Send message Joined: 25 May 11 Posts: 3 Credit: 299,588 RAC: 0 |
all 4 WUs with errors - cannot get new tasks |
Send message Joined: 22 Oct 11 Posts: 23 Credit: 71,023,220 RAC: 0 |
I'd say "the pooch got screwed" with this update! Ha! Too funny! ^..^~~ |
Send message Joined: 5 Sep 08 Posts: 28 Credit: 245,585,043 RAC: 0 |
Just a personal request but if you can turn on that which is necessary for us to upload completed wu's and errors it would be most helpful. I was running quite a number of cards when the problems occured. When I look at my master console with BoincTasks, all those red lines give me heart palpatations. Hahaha No worries if that is not feasible. Have a good weekend. |
Send message Joined: 1 Sep 08 Posts: 520 Credit: 302,525,188 RAC: 0 |
I just did the suspend thing. Once we 'return to the future' here I'll likely do product resets or detach and rejoins just to clear out the cobwebs. Perhaps some information might be useful though. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
GPU-only tasks tested ... So Matt A. says this is most likely a problem with using an older version of the ATI application. |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
Just a personal request but if you can turn on that which is necessary for us to upload completed wu's and errors it would be most helpful. I was running quite a number of cards when the problems occured. When I look at my master console with BoincTasks, all those red lines give me heart palpatations. Hahaha Thinks are back on, hopefully I get some more information about why some clients are erroring out on the workunits. |
Send message Joined: 25 Jan 11 Posts: 271 Credit: 346,072,284 RAC: 0 |
i've run ~10 tasks since the server went back up, and only one errored out (a null_3 task). my first de_separation task crunched without error though. |
Send message Joined: 9 May 12 Posts: 12 Credit: 10,339,447 RAC: 0 |
We have run over 80 on AMD GPU today (No errors) At least a hundred or more went thru yesterday and the only errors were a couple _v2 that sneaked in. ;-) Even ran 8 thru my much slower nvidia GPU. (No errors) |
Send message Joined: 9 May 12 Posts: 12 Credit: 10,339,447 RAC: 0 |
Going good today but... another _v2 just slipped through and as before (Computation error) right at the end. [stars file] Too bad they don't error at the start... Mine only took (40.35) GPU , but wingman took (28,298.82)on CPU. Ouch ! http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=178264077 Can't these _v2 be weeded out rather than just sending more copies ? |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
Done, they shouldn't be getting sent out anymore. |
Send message Joined: 5 Nov 10 Posts: 69 Credit: 15,064,831 RAC: 0 |
Nope:- still erroring, details below ... Task 225600128 Ray_GTI-R | log out Name ps_separation_14_2s_null_3_v4_1338660883_41090_1 Workunit 178349109 Created 2 Jun 2012 | 20:15:08 UTC Sent 2 Jun 2012 | 20:15:53 UTC Received 2 Jun 2012 | 20:32:07 UTC Server state Over Outcome Computation error Client state Compute error Exit status 1 (0x1) Unknown error number Computer ID 231173 Report deadline 14 Jun 2012 | 20:15:53 UTC Run time 448.03 CPU time 4.86 Validate state Invalid Credit 0.00 Application version MilkyWay@Home v0.82 (ati14) Stderr output <core_client_version>6.12.34</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> Using SSE2 path Found 1 CAL devices Chose device 0 Device target: CAL_TARGET_670 Revision: 41 CAL Version: 1.4.1523 Engine clock: 668 Mhz Memory clock: 828 Mhz GPU RAM: 512 Wavefront size: 64 Double precision: CAL_TRUE Compute shader: CAL_FALSE Number SIMD: 4 Number shader engines: 1 Pitch alignment: 256 Surface alignment: 256 Max size 2D: { 8192, 8192 } Estimated iteration time 660.343376 ms Target frequency 30.000000 Hz, polling mode 1 Dividing into 19 chunks, initially sleeping for 0 ms Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 } Using 19 chunk(s) with sizes: 80 80 80 96 80 80 80 96 80 80 80 96 80 80 96 80 80 80 96 Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Integration time = 442.362278 s, average per iteration = 691.191059 ms Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Failed to map resource: Operational error (CAL_RESULT_ERROR) Failed to release CAL resource Integral 0 time = 446.066926 s Failed to calculate integral 0 21:31:13 (2680): called boinc_finish </stderr_txt> ]]> -------------------------------------------------------------------------------- |
Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0 |
Nope:- still erroring, details below ... Matt A. says it's because of the old version of your ATI application. |
Send message Joined: 19 Jul 10 Posts: 627 Credit: 19,304,927 RAC: 860 |
Matt A. says it's because of the old version of your ATI application. Does that basically mean, that the new tasks are incompatible with HD38x0 cards? |
Send message Joined: 19 Jul 10 Posts: 627 Credit: 19,304,927 RAC: 860 |
OK, they all error out, however I get as stderr that: <core_client_version>6.12.34</core_client_version> so it looks quite normal, only <search_application> milkywayathome_client separation 0.82 Windows x86_64 double CAL++ </search_application> is missing after "</search_likelihood>". EDIT: OK, I suspended the rest of those tasks for now and will crunch Collatz again until you (hopefully) fix that. Is generating few more of those errors with the rest of WUs, that I have here, of any use for you to find the problem, or shall I just abort them? |
Send message Joined: 5 Nov 10 Posts: 69 Credit: 15,064,831 RAC: 0 |
To recap:- on my PCs ... The current batch(es) of GPU WUs fail. The previous batches ran sucessfully. Others report the same issue. There has been no ATI application/driver change at this end. I thought the only change was to create new work i.e., I'm testing work generation right now, there should be workunits available to download now. Let me know how these workunits are crunching! Matt A. says it's because of the old version of your ATI application. Has there been an unannounced update to MW@H crunching requirement(s)? |
©2024 Astroinformatics Group