Device 'gfx906:sramecc+:xnack-' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU)
Board: Vega 20
Driver version:      3241.0 (HSA1.1,LC)
Version:             OpenCL 2.0 
Compute capability:  0.0
Max compute units:   60
Clock frequency:     1725 Mhz
Global mem size:     34342961152
Local mem size:      65536
Max const buf size:  29191516976
Double extension:    cl_khr_fp64

In some cases the stderr from BOINC is truncated or missing completely. I think I mostly fixed the problem for future updates

<core_client_version>6.10.60</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>

<core_client_version>6.10.60</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkywayathome_client separation 0.62 Windows x86 double CAL++ </search_application>
Found 1 CAL devices
Chose device 0

Device target:         CAL_TARGET_CAYMAN
Revision:              1
CAL Version:           1.4.900
Engine clock:          810 Mhz
Memory clock:          1100 Mhz
GPU RAM:               2048
Wavefront size:        64
Double precision:      CAL_TRUE
Compute shader:        CAL_TRUE
Number SIMD:           22
Number shader engines: 2
Pitch alignment:       256
Surface alignment:     4096
Max size 2D:           { 16384, 16384 }

Estimated iteration time 119.647166 ms
Target frequency 30.000000 Hz, polling mode 1, using responsiveness factor of 1.000000
Dividing into 4 chunks
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using { 1, 4 } chunk(s) of size { 1400, 400 }
Integration time = 82.015017 s, average per iteration = 128.148464 ms
Integral 0 time = 83.759557 s
Estimated iteration time 29.911792 ms
Target frequency 30.000000 Hz, polling mode 1, using responsiveness factor of 1.000000
Dividing into 1 chunks
Integration range: { nu_steps = 640, mu_steps = 400, r_steps = 1400 }
Using { 1, 1 } chunk(s) of size { 1400, 400 }
Integration time = 20.501572 s, average per iteration = 32.033706 ms
Integral 1 time = 20.980437 s
Likelihood time = 6.569375 s
Non-finite result
Failed to calculate likelihood
<background_integral> 0.000972832098789 </background_integral>
<stream_integral>  27.656173175642195  1183.863218271929800  -0.138228459499025 </stream_integral>
<background_likelihood> -2.983789565586555 </background_likelihood>
<stream_only_likelihood>  -58.146684859558270  -7.945487711078723  -1.#IND00000000000 </stream_only_likelihood>
<search_likelihood> -1.#IND00000000000 </search_likelihood>
18:19:23 (2796): called boinc_finish

</stderr_txt>

CAL Runtime: 1.4.1016
Found 2 CAL devices

Device 0: ATI Radeon HD5800 series (Cypress) 1024 MB local RAM (remote 2047 MB cached + 2047 MB uncached)
GPU core clock: 1000 MHz, memory clock: 1500 MHz
1600 shader units organized in 20 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

Device 1: ATI Radeon HD5800 series (Cypress) 1024 MB local RAM (remote 2047 MB cached + 2047 MB uncached)
GPU core clock: 1000 MHz, memory clock: 1500 MHz
1600 shader units organized in 20 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

...

WU completed.
CPU time: 26.5358 seconds,  GPU time: 92.3703 seconds,  wall clock time: 94.065 seconds,  CPU frequency: 2.80643 GHz

...

Validate state	Valid
Claimed credit	0.154616492621667
Granted credit	213.756235697696
application version	MilkyWay@Home v0.23 (ati13ati)

1/14/2010 11:58:10 AM	Milkyway@home	Message from server: No work sent
1/14/2010 11:58:10 AM	Milkyway@home	Message from server: ATI Catalyst 9.2+ needed to use GPU
1/14/2010 11:58:10 AM	Milkyway@home	Message from server: Your computer has no NVIDIA GPU

DA decided that GPU work should be done in strict FIFO order ... that means that if you want to run MW mostly you need to trim your queue to try to avoid large chunks of Collatz being DL. Of course, the issue here is that you have network drops and lowering the queue means you will run out of work ...

In that this would not solve your problem ... you need to complain on the alpha mailing list ... I have, but so far to silence ... What you really want is to have Collatz on hand and only run it if you cannot get MW work ... or you run dry because of a network outage ...

Theory says that Resource Share will be respected over time ... but I cannot prove that ... in that the debt calculations seem to have been bent for some time my suspicion is that this is also not true ...

I run with a one day something cache and right now my ATI system seems to run a day on MW if it can get work, then it will DL 90 or so Collatz and spend a day running them off ... then again, I also run with 100/100 share allocation so I am not quite in your situation...

Anyway, your problem is that you are running into one of the later brainstorms of UCB... oh, alternative, downlevel your installation and use app info to make it work (of course you may not be able to run CPU of MW and Collatz) ...