topic Re: Runtime Error: zeKernelSetIndirectAccess not found in GPU Compute Software

Runtime Error: zeKernelSetIndirectAccess not found

dobbsy — Tue, 29 Sep 2020 18:55:40 GMT

Hi,

I hope this is the right board to post this issue to. Since the Beta 9 update i get the following error message when running a DPC++ program (I translated this from German, so the exact wording might be different in the English error message): 'The entry point for the procedure "zeKernelSetIndirectAccess" not found in DLL "[path_to_onenapi_root_dir]\windows\bin\pi_level_zero.dll" '.

The DPC++ programs actually run fine once i acknowledge the error by pressing "OK", but I'd still like to find out what the problem is with my setup.

To produce this error message, a creation of a queue-object is sufficient, so the minimal working example is very short:

#include <CL/sycl.hpp> int main(int argc, char** argv) { cl::sycl::queue q; }

Environment:

Windows 10 Home (version 2004)
Intel oneAPI Base Toolkit 2021.1 beta 9
Visual Studio 2019 Community Edition (The DPC++ projects have all been created using the Intel Extension for VS)

Thanks in advance for your help!

Re:Runtime Error: zeKernelSetIndirectAccess not found

RahulV_intel — Wed, 30 Sep 2020 06:15:55 GMT

Hi,

The issue is reproducible with level0 back-end. Nevertheless, you can still run it on OpenCL back-end by setting the environment variable SYCL_BE=PI_OPENCL.

On windows CMD, despite the error message, I can still run it on OpenCL back-end even without setting SYCL_BE.

I've let the concerned team know about this issue. Thanks for reporting.

Regards,

Rahul

Re:Runtime Error: zeKernelSetIndirectAccess not found

Subarnarek_G_Intel — Thu, 01 Oct 2020 18:29:05 GMT

This case is already escalated to the Engineering. Can you check where the driver got installed in your system?

Betreff: Re:Runtime Error: zeKernelSetIndirectAccess not found

dobbsy — Fri, 02 Oct 2020 11:58:03 GMT

I'm sorry, which driver are you talking about exactly? In case you mean the pi_level_zero library, its full path is "C:\Program Files (x86)\Intel\oneAPI\compiler\2021.1-beta09\windows\bin" on my machine. I noticed I left out some subdirectories in my original post, sorry for that.

Re: Runtime Error: zeKernelSetIndirectAccess not found

JamesReinders — Tue, 29 Dec 2020 23:35:35 GMT

I'm seeing the SAME error on both my systems. I installed four of the oneAPI *GOLD* toolkits - Base, HPC, IoT, and Render. One of my systems has Windows 10 Pro, the other runs Windows 10 Home. One has a DG1 which is *not* being detected properly, and the other has an Iris Xe (i7-1165G7). All have up-to-date Windows drivers installed. SYCL/DPC++ can enumerate the devices, and my DPC++ programs run correctly - but this POP-UP occurs with ALL runs of ALL my simple DPC++ programs (from our DPC++ book).

Please advise why this DLL is causing issues, and how to fix it.

Re: Runtime Error: zeKernelSetIndirectAccess not found

isilin1 — Wed, 30 Dec 2020 15:51:25 GMT

I'm having the same issue. Using the latest Win10 Pro, latest drivers, OneAPI Base + HPC packs, Microsoft Visual Studio 2019 or OneAPI Command Prompt. All code samples crash with the message "zeKernelSetIndirectAccess could not be located in pi_level_zero.dll".

Re: Runtime Error: zeKernelSetIndirectAccess not found

JamesR — Wed, 06 Jan 2021 23:01:30 GMT

Here is the FIX. Let me know if it does not work for you.

The fix is simple: update to the latest Intel graphics drivers by visiting https://downloadcenter.intel.com/product/80939/Graphics and using the "Get Started" button, or manually downloading and installing the latest drivers for your machine. Along the way - ignore the advice to use the OEM's drivers or use Intel's drivers for testing only.

Do this even though Windows may say you have the latest and greatest driver installed.

Once you do that - the pop-up goes away. It fixed both my machines.

This is a symptom of evolving support for oneAPI (DPC++ etc.) in the graphics drivers, and they take some time to propagated to be automatically updated by Windows.

I'll help Intel see if the install and tools can do better to analyze what is installed, and give better diagnostics or advice when there is a driver mismatch. The pop-up was WAY to cryptic.

With the current drivers, I found things were working GREAT!

If you haven't looked at our book on DPC++ - considering reading it... it can be downloaded (PDF) for free from https://www.apress.com/us/book/9781484255735 or a print copy can be purchased.

Re: Runtime Error: zeKernelSetIndirectAccess not found

isilin1 — Thu, 07 Jan 2021 03:17:06 GMT

Thanks, that worked.

Re: Runtime Error: zeKernelSetIndirectAccess not found

SUKLA — Mon, 18 Jan 2021 07:05:26 GMT

I downloaded Gaphics driver but it did not fix the problem.

Dilip

Re:Runtime Error: zeKernelSetIndirectAccess not found

Subarnarek_G_Intel — Mon, 01 Feb 2021 06:09:29 GMT

After installing the latest driver did you follow James' instructions? And is it still failing?

Re:Runtime Error: zeKernelSetIndirectAccess not found

Subarnarek_G_Intel — Mon, 01 Feb 2021 14:08:27 GMT

The error is not reproducible at my end. It got resolved after upgrading the driver in the same timeframe when the case was initially released. Can you let me know the driver version that you have?

Re:Runtime Error: zeKernelSetIndirectAccess not found

Subarnarek_G_Intel — Wed, 17 Feb 2021 05:27:52 GMT

Based on our internal verification, the issue is resolved with driver version 27.20.100.9168, that can be downloaded from https://downloadcenter.intel.com/product/126790/Intel-UHD-Graphics-630. If you are using any of the OEM machines (Lenovo, Dell, HP, etc.), the OEM may restrict installation of this driver directly from the above link. In that case its recommended to download this version (or any higher version) directly from the OEM website. Please let us know if this information is helpful and if it resolves the issue under discussion.

Re:Runtime Error: zeKernelSetIndirectAccess not found

Subarnarek_G_Intel — Fri, 19 Mar 2021 12:16:18 GMT

Closing the case as there was no response from the customer.

This issue has been resolved and we will no longer respond to this thread. If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only