You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dpctl built with latest oneapi releases (2023.0.0, libsycl 6) fail to submit jobs to cpu #1023
@fcharras It would be useful to know whether the compiler/tbb from oneAPI are activated (if so what is the output of sycl-ls), and what version of dpctl are you using (0.13.0 from Intel channel, or 0.14.0dev1 from dppy/label/dev)?
What is the output of python -c "import dpctl; dpctl.lsplatform(verbosity=2)"?
The issue is that DPC++ 2023 runtime is trying to submit a kernel to queue targeting CPU SYCL device built for DPC++ 2022 toolchain, the one with "2022.14.8.0.04_160000".
The DPC++ RT most likely picks it up from ICD files in /etc/OpenCL/vendors. If my hunch is correct, cat /etc/OpenCL/vendors/intel64.icd would show a path into /opt/intel/oneapi/compiler/2022.*.
There are several solutions, other directly choose CPU device with driver version "2022.15.12.0.01_081451", or find a way to hide CPU/FPGA-emu drivers from 2022 installation (say uninstall older compiler).
sudo apt list --installed | grep oneapi-dpcpp-cpp | grep 2022
I don't think I have older compilers installed (since the docker image is rebuilt from scratch after all bumps), and the issue persists when specifically selecting the cpu with the good driver version.
I'll try setting up a minimal reproducer to understand what specifically triggers kernel rejection. It seems to be related to work_group_size: the test pipeline seems to hint that for cpu kernels submitted with a group size equal to max_work_group_size are rejected.
Activity
oleksandr-pavlyk commentedon Dec 28, 2022
@fcharras It would be useful to know whether the compiler/tbb from oneAPI are activated (if so what is the output of
sycl-ls), and what version of dpctl are you using (0.13.0 from Intel channel, or 0.14.0dev1 from dppy/label/dev)?What is the output of
python -c "import dpctl; dpctl.lsplatform(verbosity=2)"?fcharras commentedon Dec 28, 2022
This build used to work only relying on python libraries such as
dpcpp-cpp-rtandmkl-dpcpp+ addingbin-llvmfolder from the oneapi basekit toPATH.Those packages are correctly bumped
I tried activating entirely the
oneapi basekitsource setvars.shbut then get the same results.
fcharras commentedon Dec 28, 2022
oneapi basekit is also bumped accordingly
fcharras commentedon Dec 28, 2022
The version of
dpctlis0.14.0dev1, built from source. Maybe the build instructions changed recently ?I'll try a conda install to compare the results.
oleksandr-pavlyk commentedon Dec 28, 2022
The issue is that DPC++ 2023 runtime is trying to submit a kernel to queue targeting CPU SYCL device built for DPC++ 2022 toolchain, the one with "2022.14.8.0.04_160000".
The DPC++ RT most likely picks it up from ICD files in
/etc/OpenCL/vendors. If my hunch is correct,cat /etc/OpenCL/vendors/intel64.icdwould show a path into/opt/intel/oneapi/compiler/2022.*.There are several solutions, other directly choose CPU device with driver version "2022.15.12.0.01_081451", or find a way to hide CPU/FPGA-emu drivers from 2022 installation (say uninstall older compiler).
and then
sudo apt removethose listed.fcharras commentedon Jan 7, 2023
I don't think I have older compilers installed (since the docker image is rebuilt from scratch after all bumps), and the issue persists when specifically selecting the cpu with the good driver version.
Also, some kernels continues running fine. (see https://github.com/soda-inria/sklearn-numba-dpex/actions/runs/3733104423/jobs/6333449877 )
I'll try setting up a minimal reproducer to understand what specifically triggers kernel rejection. It seems to be related to
work_group_size: the test pipeline seems to hint that forcpukernels submitted with a group size equal tomax_work_group_sizeare rejected.fcharras commentedon Jan 11, 2023
Remaining errors encountered are detailed in IntelPython/numba-dpex#868 IntelPython/numba-dpex#867 and IntelPython/numba-dpex#865 with workarounds.
Unless you want to keep track of it here I think we can close this issue.
oleksandr-pavlyk commentedon Jan 11, 2023
Thanks you @fcharras, closing