Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hangs on Intel #9

Open
dca00 opened this issue Jul 14, 2024 · 8 comments
Open

Hangs on Intel #9

dca00 opened this issue Jul 14, 2024 · 8 comments

Comments

@dca00
Copy link

dca00 commented Jul 14, 2024

Hi,

Is it normal and expected that the EXE hangs on Intel i3 Sandy Bridge? It shows nothing after the banner and pins the CPU at 100%.
It also crashes on i7 Sandy Bridge.

@ProjectPhysX
Copy link
Owner

Hi @dca00,

that should not happen. Is that with the Intel CPU Runtime for OpenCL, or with PoCL?
Can you please share the full console output up to the point where it hangs, for both CPUs?

Kind regards,
Moritz

@dca00
Copy link
Author

dca00 commented Jul 15, 2024

wrapper_2120

It sits like this for some time, then I kill it with Ctrl-C. Maybe I do not wait long enough. How long is it supposed to take?

@ProjectPhysX
Copy link
Owner

What seems to happen here is that the OpenCL Runtime compiler gets stuck.

Did you install the Intel CPU Runtime for OpenCL yourself on the system? This looks like an ancient version. Try with latest version.

@dca00
Copy link
Author

dca00 commented Jul 17, 2024

Updated the runtime. Now, this is the output:
image
Other than the output and that the CPU is pinned to 37%, the behavior hasn't changed.

@ProjectPhysX
Copy link
Owner

Ok you have the CPU showing up 3 times now, lets get to the bottom of it. By default Device ID 1 is selected. Try manually selecting Device ID 2. For this, change this line in src/main.cppto:

	Device device(select_device_with_id(2));

and compile+run it and post the output here. Try also with ID 0.

@dca00
Copy link
Author

dca00 commented Jul 18, 2024

First, this message shows:
image
And then:
image
And then I can kill it with Ctrl-C

@ProjectPhysX
Copy link
Owner

This is the full expected output. The OpenCL kernel runs correctly.

To fix this weird error, try uninstalling the old version of the OpenCL CPU Runtime you have installed (twice?) to get rid of broken device ID listings 0 and 1.

@dca00
Copy link
Author

dca00 commented Jul 19, 2024

It wasn't installed twice: the machine was reimaged clean and new runtime installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants