-
Notifications
You must be signed in to change notification settings - Fork 234
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
Gemini Lake clpeak fails on Ubuntu 22.04 latest kernel #679
Comments
I have the same problem on both Celeron J4125 and N4000. terminate called after throwing an instance of 'InferenceEngine::GeneralError'
what(): [ GENERAL_ERROR ] Check 'false' failed at src/plugins/intel_gpu/src/plugin/program.cpp:401:
GPU program build failed!
[GPU] clWaitForEvents, error code: -14 Note that Linux kernel 5.15 does not have the problem. |
I heard about this issue a year ago but I no longer have a GLK device now. @looi @Ar-Ray-code |
I don't think this is necessarily a kernel regression, because as I have stated above, vulkan compute works fine. Personally, I have switched to using vulkan. The performance is comparable (especially making proper use of vulkan subgroups), but more importantly, it seems to be much more stable on both Windows and Linux. Intel Compute Runtime / OpenCL has weird issues like this one. Vulkan also seems to work much better on non-intel GPUs, especially nvidia, where they refuse to support basic features like subgroups and half-precision floats in OpenCL. So I feel like vulkan is the future and OpenCL is dying anyways. |
Your input suggests this is a kernel regression. The only difference between whether it works or not is the kernel version, bisect the commit between the two should find the culprit. This isn't the first time I've seen i915 regression, last time it even broke both the Vulkan compute and OpenCL. |
I agree that a kernel change broke Intel Compute Runtime. I guess whether or not it's a kernel regression is a subjective question depending on what exactly caused the breakage. Maybe Intel Compute Runtime is making incorrect assumptions about i915 or relying on undefined behavior, in which case it would not be a kernel regression. Given that vulkan compute still works, I think it is a likely possibility. |
any news on this one? same issue |
@JablonskiMateusz any chance you could take a look? thank you |
I have the same issue with J5005 Gemini Lake and Proxmox 8.2.7 running kernel 6.8.12-2-pve and the most recent Intel Compute Runtime 24.35.30872.22 Old kernel 5.15.108-1-pve works out of the box. |
I am also having the same issue on my J5005 running Ubuntu 24 LTS with kernel 6.8.0-48 with the updated OpenVINO runtime. Not able to use the GPU for acceleration. This was working fine on older kernels. @looi can you provide insturctions on how you are setting the |
System: Dell Wyse 5070 Intel Celeron J4105 (Gemini Lake)
Intel Compute Runtime 23.30.26918.9 installed with official instructions.
What works
i915.enable_hangcheck=0 i915.request_timeout_ms=100000
, see Broadwell iGPU hangs running clpeak with 5.13+ kernels #497What doesn't work
i915.enable_hangcheck=0 i915.request_timeout_ms=100000
) or increasing to 200000 doesn't appear to help.The text was updated successfully, but these errors were encountered: