-
Notifications
You must be signed in to change notification settings - Fork 54
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
Crash with Intel driver when default device is AMD #10
Comments
It crashes at this line: I'm not sure whether it is acceptable for you, but try to deinstall the Intel driver and use the AMD driver for CPU. Even if you are not going to stay with this in a long run - the result of this experiment is important for other users (wil publish it on the Deployment page (once back from vacation at the end of the week)). |
Hi @Ristovski, Thanks. |
Dear comrade @Ristovski ;) do you experience this issue with the Intel 14.2 runtime? We got reports that everything works fine with that version. Thanks. |
Hello @AvtechScientific ! I must deeply apologize for my absence as I have been busy! (sad embarrased emoticon here) I must say that I am impressed of your dedication towards issue reports! 😃 You are truly doing excellent work! Keep it up and all of you have a nice weekend! --Ristovski PS: 'Comrade' was a nice touch! :3 |
The "known" bug that causes a segfault when used with the Intel driver WITH Intel graphics - seems to happen even while the default device/platform is the dedicated GPU (AMD Radeon HD 8850M) running xf86-video-ati/mesa-cl. Even when the user adds --platform and --device arguments, it still accesses the Intel GPU opencl (checked by doing strace):
access("/opt/intel/opencl-sdk/lib64/clbltfnl9_img_cbk.o", F_OK) = 0
open("/opt/intel/opencl-sdk/lib64/clbltfnl9_img_cbk.o", O_RDONLY) = 3
The cause of the segfault is the same as the one in the "known issue" page.
The text was updated successfully, but these errors were encountered: