All WUs crunched & errored out
log in

Advanced search

Message boards : Number crunching : All WUs crunched & errored out

Author Message
John Clark
Send message
Joined: 4 Oct 08
Posts: 1635
Credit: 62,406,415
RAC: 7,582
Message 50254 - Posted: 19 Jul 2011, 21:08:47 UTC

Like I have seen a number of times in these threads, posters are saying their WUs are errored out with the statement - Error while computing

This happened on both my quads when crunching the stock GPU application (0.82) on an HD850 (one quad) and an HD5970 (other quad).

I am using AMD driver 11.3, with AP and OpenCL (according to GPU-Z) and still get the errors.

I have not been back to Milkyway for a while and did a Project reset to ensure I had the latest GPU client.

Suggestions please.
____________
Go away, I was asleep


Profile dnolan
Avatar
Send message
Joined: 26 Oct 09
Posts: 55
Credit: 351,754,052
RAC: 1,015
Message 50257 - Posted: 19 Jul 2011, 21:48:06 UTC

All the errors I see in your tasks relate to the problem in this thread

-Dave
____________

bob
Send message
Joined: 12 Apr 09
Posts: 12
Credit: 42,694,666
RAC: 77,910
Message 50527 - Posted: 4 Aug 2011, 7:28:27 UTC

I have not seen this before.

Task error out

<core_client_version>6.12.33</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Using SSE2 path
Found 2 CAL devices
Chose device 0

Device target: CAL_TARGET_770
Revision: 2
CAL Version: 1.4.1457
Engine clock: 625 Mhz
Memory clock: 993 Mhz
GPU RAM: 1024
Wavefront size: 64
Double precision: CAL_TRUE
Compute shader: CAL_TRUE
Number SIMD: 10
Number shader engines: 1
Pitch alignment: 256
Surface alignment: 256
Max size 2D: { 8192, 8192 }

Estimated iteration time 396.578000 ms
Target frequency 30.000000 Hz, polling mode 1
Dividing into 11 chunks, initially sleeping for 0 ms
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using 11 chunk(s) with sizes: 144 144 144 144 144 144 144 144 144 144 160
Integration time = 565.331039 s, average per iteration = 883.329749 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
Failed to map resource: Operational error (CAL_RESULT_ERROR)
Failed to release CAL resource
Integral 0 time = 568.351234 s
Failed to calculate integral 0
02:17:41 (26300): called boinc_finish

</stderr_txt>
]]>

Has any one else seen this. Just started after the most recent recovery.

dp
Send message
Joined: 23 Jan 08
Posts: 3
Credit: 25,498,484
RAC: 18,199
Message 50536 - Posted: 4 Aug 2011, 22:49:02 UTC

I seem to have way too many errors compared to actual results.
Have detached and restarted but to no avail.

Stderr output
<core_client_version>6.12.33</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
]]>

Is this an expected result?

Thanx
dp

Profile banditwolf
Avatar
Send message
Joined: 12 Nov 07
Posts: 2425
Credit: 295,133
RAC: 0
Message 50543 - Posted: 5 Aug 2011, 12:24:38 UTC - in response to Message 50536.

Some wu's have been running too long, look for a thread on that. Looking at your results you do seem to be running ok now.
____________
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.


Post to thread

Message boards : Number crunching : All WUs crunched & errored out


Main page · Your account · Message boards


Copyright © 2013 AstroInformatics Group