It just consumes full CPU core under CodeXL GPU profiler and makes no progress. Even stderr.txt didn't created. will leave it running through nigh but most probably no profile results will be gathered.
Well, yes, of course :-) That's why I mentioned it earlier. Thanks Richard for stepping in!
Quote:
Thanks, command line was crucial for success.
So you can confirm you could run it from start to finish on the machine you're going to use for profiling? stderr.txt and results.cand* do exist at the end of the run?
Quote:
It just consumes full CPU core under CodeXL GPU profiler and makes no progress.
Hm, not sure how CodeXL instruments an app in order to profile it...
[19:54:38][3092][ERROR] Error in OpenCL context: Out of device memory.
[19:54:38][3092][ERROR] Error in OpenCL context: Out of device memory.
(and is still running). Pretty much the same as the live result for task 406867971.
Now that's an interesting feature: the was an error but the app finished anyway? Do you see these regularly and, if so, do the affected tasks validate?
Update: this "error" is thrown by the OpenCL runtime (via a callback) during context creation. Interestingly enough though, the call to create the context itself doesn't return an error. Doesn't seem to matter...
[19:54:38][3092][ERROR] Error in OpenCL context: Out of device memory.
[19:54:38][3092][ERROR] Error in OpenCL context: Out of device memory.
(and is still running). Pretty much the same as the live result for task 406867971.
Now that's an interesting feature: the was an error but the app finished anyway? Do you see these regularly and, if so, do the affected tasks validate?
Update: this "error" is thrown by the OpenCL runtime (via a callback) during context creation. Interestingly enough though, the call to create the context itself doesn't return an error. Doesn't seem to matter...
The OpenCL error is reported in every task I've looked at, but the overall failure rate (either error or invalid) is extraordinarily low - in fact, the Haswell (8864187) is showing no failures at all - the overclocked i7 is a little more temperamental.
[19:54:38][3092][ERROR] Error in OpenCL context: Out of device memory.
[19:54:38][3092][ERROR] Error in OpenCL context: Out of device memory.
The first mention of this OpenCL error was during testing over at Albert@home in this message by Bikeman. It was in response to me posting a stderr.txt from the first test of the app outside the lab. So it's been there from the start.
So you can confirm you could run it from start to finish on the machine you're going to use for profiling? stderr.txt and results.cand* do exist at the end of the run?
Hm, not sure how CodeXL instruments an app in order to profile it...
Oliver
1) didn't run it from start to finish, just checked that it starts OK and writes into stderr.txt about it.
Running under profiler didn't result even in creating stderr.txt at all.
2) No additional instrumentation on compilation/linkage stages required.
So I used stock binary downloaded from project.
PS. Here is thread on AMD CodeXL forum about this issue, for reference. http://devgurus.amd.com/thread/167648
There are similar issues in other threads on that forum too. I found no solution so far.
Funny, I know Gergely and could ask him whether he could solve his issue. Are the symptoms the same in your case or did you indeed just list "similar" ones...?
Just a rough guess, but maybe CodeXL can't handle cross-compiled MinGW binaries and expects MS builds...?
Oliver
Viable guess. I had issues with AMD profilers (non-solvable) when used ICC for MultiBeam ATi GPU app building. So far only MSVC-compiled binary was able to be profiled...
Thanks, command line was
)
Thanks, command line was crucial for success.
Now will try to run under profiler.
It just consumes full CPU
)
It just consumes full CPU core under CodeXL GPU profiler and makes no progress. Even stderr.txt didn't created. will leave it running through nigh but most probably no profile results will be gathered.
RE: Can't run offline, app
)
Well, yes, of course :-) That's why I mentioned it earlier. Thanks Richard for stepping in!
So you can confirm you could run it from start to finish on the machine you're going to use for profiling? stderr.txt and results.cand* do exist at the end of the run?
Hm, not sure how CodeXL instruments an app in order to profile it...
Oliver
Einstein@Home Project
RE: [19:54:38][3092][ERROR
)
Now that's an interesting feature: the was an error but the app finished anyway? Do you see these regularly and, if so, do the affected tasks validate?
Update: this "error" is thrown by the OpenCL runtime (via a callback) during context creation. Interestingly enough though, the call to create the context itself doesn't return an error. Doesn't seem to matter...
Best,
Oliver
Einstein@Home Project
RE: RE: [19:54:38][3092][
)
Yes, spot-check any you like from
Valid tasks for computer 5744895
Valid tasks for computer 8864187
The OpenCL error is reported in every task I've looked at, but the overall failure rate (either error or invalid) is extraordinarily low - in fact, the Haswell (8864187) is showing no failures at all - the overclocked i7 is a little more temperamental.
RE: [19:54:38][3092][ERROR]
)
The first mention of this OpenCL error was during testing over at Albert@home in this message by Bikeman. It was in response to me posting a stderr.txt from the first test of the app outside the lab. So it's been there from the start.
RE: So you can confirm you
)
1) didn't run it from start to finish, just checked that it starts OK and writes into stderr.txt about it.
Running under profiler didn't result even in creating stderr.txt at all.
2) No additional instrumentation on compilation/linkage stages required.
So I used stock binary downloaded from project.
PS. Here is thread on AMD CodeXL forum about this issue, for reference.
http://devgurus.amd.com/thread/167648
There are similar issues in other threads on that forum too. I found no solution so far.
PPS: threads with similar issues (app hangs on start):
http://devgurus.amd.com/message/1300495#1300495
http://devgurus.amd.com/message/1295856#1295856
http://devgurus.amd.com/message/1287984#1287984
Last one looks especially similar, some conversation with AMD staff... but no useful answer still.
Just a rough guess, but maybe
)
Just a rough guess, but maybe CodeXL can't handle cross-compiled MinGW binaries and expects MS builds...?
Oliver
Einstein@Home Project
RE: http://devgurus.amd.com
)
Funny, I know Gergely and could ask him whether he could solve his issue. Are the symptoms the same in your case or did you indeed just list "similar" ones...?
Einstein@Home Project
RE: Just a rough guess, but
)
Viable guess. I had issues with AMD profilers (non-solvable) when used ICC for MultiBeam ATi GPU app building. So far only MSVC-compiled binary was able to be profiled...