Hi Travis,

I had it earlier I thins as was getting this error message:
Stderr output
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkywayathome_client separation 0.57 Windows x86 double CAL++ </search_application>
Failed to get CAL device attributes: Parameter passed in is invalid (CAL_RESULT_INVALID_PARAMETER)
Error getting device information: Parameter passed in is invalid (CAL_RESULT_INVALID_PARAMETER)
Failed to get CAL info: Parameter passed in is invalid (CAL_RESULT_INVALID_PARAMETER)
Failed to setup CAL
00:09:34 (5740): called boinc_finish

</stderr_txt>
]]>


--------------------------------------------------------------------------------
So there is nothing telling about not finding any file. Or do I mis read anything?

---

Greetings from,
TJ

The ATI app is using nearly a full cpu core per wu....ouch!

Not here, only 0.05CPU.

That's what it says, but it's busy waiting for the GPU to finish things which I thought I fixed months ago.

And it's ~25% slower compared to the old app... that sucks :(

What GPU? I was running it for a few days in the last week and it was pretty much the same for my 5870

Mine all crunched against 0.23 (appinfo was deleted at startup, but 0.23 was still in the dir as was the brook file. Seemed ok in spite of that, have not yet checked if they validated at the server end.

I had reset when I noticed 0.23 was active, but the reset did not download the new app. Want me to leave the setup as is for now for "tests" or should I try a detatch?

EDIT: They errored at server end, so validator did its thing. I'll do a detatch see if it downloads new app etc

Regards
Zy

I did notice that it seems to continue to run for about 5 secs when it's suppose to be finished.

The ATI app is using nearly a full cpu core per wu....ouch!

Not here, only 0.05CPU.

That's what it says, but it's busy waiting for the GPU to finish things which I thought I fixed months ago.

And it's ~25% slower compared to the old app... that sucks :(

What GPU? I was running it for a few days in the last week and it was pretty much the same for my 5870

on a 4850 @ 760MHz it takes 249 sec compared to 188 sec using the old app (same WUs of course).

On a 5870 @ 960MHz it takes 105 sec now, while the old app only took like 80 sec or so.

---

Join Support science! Joinc Team BOINC United now!

The ATI app is using nearly a full cpu core per wu....ouch!

Not here, only 0.05CPU.

That's what it says, but it's busy waiting for the GPU to finish things which I thought I fixed months ago.

And it's ~25% slower compared to the old app... that sucks :(

What GPU? I was running it for a few days in the last week and it was pretty much the same for my 5870

On my 5850 it's also slower.

The ATI app is using nearly a full cpu core per wu....ouch!

Not here, only 0.05CPU.

That's what it says, but it's busy waiting for the GPU to finish things which I thought I fixed months ago.

And it's ~25% slower compared to the old app... that sucks :(

What GPU? I was running it for a few days in the last week and it was pretty much the same for my 5870

on a 4850 @ 760MHz it takes 249 sec compared to 188 sec using the old app (same WUs of course).

On a 5870 @ 960MHz it takes 105 sec now, while the old app only took like 80 sec or so.

There are different sized tasks out there, so you need to be sure to compare ones from the same set of workunits. When I was using it there were some that were around ~80s and some ~110s for both.

Mine all crunched against 0.23 (appinfo was deleted at startup, but 0.23 was still in the dir as was the brook file. Seemed ok in spite of that, have not yet checked if they validated at the server end.

Regards
Zy

They are crunching but getting marked invalid.

am I the only one who have a problem with the cpu temperature after getting the new WUs ?

I reinstalled the project and will test it again when the next WUs are available ...

The ATI app is using nearly a full cpu core per wu....ouch!

Not here, only 0.05CPU.

That's what it says, but it's busy waiting for the GPU to finish things which I thought I fixed months ago.

And it's ~25% slower compared to the old app... that sucks :(

What GPU? I was running it for a few days in the last week and it was pretty much the same for my 5870

on a 4850 @ 760MHz it takes 249 sec compared to 188 sec using the old app (same WUs of course).

On a 5870 @ 960MHz it takes 105 sec now, while the old app only took like 80 sec or so.

There are different sized tasks out there, so you need to be sure to compare ones from the same set of workunits. When I was using it there were some that were around ~80s and some ~110s for both.

I know, that's why i posted "same WUs" (10_3s_fix20) those that grant 367 credits. It is definetely quite a bit slower.

EDIT:

Are you using the math functions included with cal++ (include\cal\il\math) or something else ?

---

Join Support science! Joinc Team BOINC United now!

Mine all crunched against 0.23 (appinfo was deleted at startup, but 0.23 was still in the dir as was the brook file. Seemed ok in spite of that, have not yet checked if they validated at the server end.

Regards
Zy

They are crunching but getting marked invalid.

Anything crunched with the 0.23 ATI application will be marked invalid -- as it doesn't write the fitness to standard error. I'm not sure if it will even calculate anything as I think it expects an input file for parameters as well. Same thing goes for older optimized applications for the CPU.

---

No dramas - the WUs "completed" but was picked up at server end and invalidated. So that angle is covered ok.

I did a detatch just now - no files came down, there was a claim of a master file download, but nothing appeared in the project directory, which is now totally empty. I had expected the relevant files to download, then stop as WUs not available. Could be all downloads of any nature on hold, fair enough, if not, then something lurketh.

Regards
Zy

No dramas - the WUs "completed" but was picked up at server end and invalidated. So that angle is covered ok.

I did a detatch just now - no files came down, there was a claim of a master file download, but nothing appeared in the project directory, which is now totally empty. I had expected the relevant files to download, then stop as WUs not available. Could be all downloads of any nature on hold, fair enough, if not, then something lurketh.

Regards
Zy

There aren't any workunits available because there's no working GPU limit in place. Somethings wrong with the scheduler and it's just sending out WUs happy-go-lucky to any GPU that asks. So since we don't want a repeat of what happened before, we're not going to be able to send out any work until that gets taken care of.

---

Fully understood re stop WUs, I was just posting the end result of a detatch a few minutes ago - a blank directory, despite claims it was downloading masterfile.

That may also be the result of the stop at server end, fair enough, but if the expectation is that I should have a full set of files downloaded on detatch (less WUs obviously), then somethings amiss, nothing came down.

Pure observation reporting something unusual, may or may not be connected with the current hassle/WU stop.

Regards
Zy

Anything crunched with the 0.23 ATI application will be marked invalid -- as it doesn't write the fitness to standard error. I'm not sure if it will even calculate anything as I think it expects an input file for parameters as well. Same thing goes for older optimized applications for the CPU.

0.23 was modified to accept both for input (file and params), so I thought to give it a try before switching to 0.57. Not really expecting them to end up as valid but worth a try if the output was modified too.

.....I did a detatch just now - no files came down, there was a claim of a master file download, but nothing appeared in the project directory, which is now totally empty. I had expected the relevant files to download, then stop as WUs not available.....

Yes I think no files download to the project directory until there are tasks available. Files such as "master_milkyway.cs.rpi.edu_milkyway.xml" probably download or are updated in the BOINC folder though when it says master file download. I am attached only to MilkyWay and DNA@Home in Windows. Both project directories are currently empty.

Can't let the CPU be idle, so eOn is running in a Dotsch/UX VirtualBox. It's so eerily quiet with no GPU crunching, I've been sleeping really well.

Is Matt going to release a 64-bit ATI version as well?

That might account for some of the speed difference that people are seeing.

---

..... Yes I think no files download to the project directory until there are tasks available. Files such as "master_milkyway.cs.rpi.edu_milkyway.xml" probably download or are updated in the BOINC folder though when it says master file download. I am attached only to MilkyWay and DNA@Home in Windows. Both project directories are currently empty...

Ah that explains it, thanks for that. I thought we got the lot, less a WU, on detatch and initialisation. Hence the blank directory had me scrating my head somewhat, when prior to the 'WU Stop' the schedular was chucking out WUs like drunks at closing time :)

No GPUs running .... weeell silver lining and all that .... few days more and you'll be able to go out for a meal on the proceeds, instead of giving it to the Power Company :)

Regards
Zy

I have been told to cross-post this error to this thread below because I am using stock applications. However, the task that got stuck has failed out by computation error, so I will update the post:

I noticed a large number of work units in my work queue whose names start with "de_separation_17_3s_fix_4_", and they seem to generate plenty of compute errors. Could someone look into these work units? I have noticed that all CPU and ATI GPU clients used by my computer and others trying to handle this work have all returned computation errors. I cannot include Nvidia clients because none of these work units have been sent to an Nvidia client yet.

Update: I am using Catalyst 11.3 on my reference Sapphire Radeon HD 6970. My OS is Windows 7 Ultimate 64-bit.

I just did 2 batches of 16. All errored immediately. HD 5970 Catalyst 10.4 on Xeon 3520 running Windows 7.

Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkywayathome_client separation 0.57 Windows x86 double CAL++ </search_application>
Failed to get CAL device attributes: Parameter passed in is invalid (CAL_RESULT_INVALID_PARAMETER)
Error getting device information: Parameter passed in is invalid (CAL_RESULT_INVALID_PARAMETER)
Failed to get CAL info: Parameter passed in is invalid (CAL_RESULT_INVALID_PARAMETER)
Failed to setup CAL
11:08:42 (1040): called boinc_finish