-
Notifications
You must be signed in to change notification settings - Fork 311
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
SYCL Intel UHD 770 segfault #405
Comments
Could you run it inside gdb and give us the stacktrace?
and hit r+enter. |
You might also try pulling a more up-to-date ggml. There are always advancements and fixes happening upstream. |
Sadly debuginfod did not retrieve the symbols for libze_intel_gpu.so.1:
stable-diffusion.cpp was cloned with --recursive, head of ggml was detached at 21d3a30 (11 days) despite fresh
it was fast-forwarded to the current fbac47b This resulted in build errors due to disabled now gdb returns
So it crashes way earlier. |
I guess sd.cpp's type list is out of date, bc that is very wrong. |
it seemed fine before updating ggml:
|
Yea, updating ggml might be more work than I thought. Instead, can you try applying some patches manually, and see what happens? |
It would also help if you could build in Debug mode, so we have line numbers :) |
so after
I applied llama.cpp 2a358fb. and rebuilt with debugging.
And the same as initial behavior. |
Hi,
trying to use SYCL on the 12600K's iGPU UHD 770, I've ran into the following issue:
OS: Manjaro
to install oneAPI:
(despite-dependencies because of blender)
and
from https://archlinux.org/packages/extra/x86_64/intel-oneapi-basekit/
instead of a simple
pacman -S --needed intel-oneapi-basekit
as the current repo package appears broken.Then installing dnn and the driver with
sudo pacman -S --needed onednn onetbb intel-compute-runtime
.I've built it like this:
F16 on or off makes no difference, the same result:
I can see the iGPU being used at 100% for render/3D by sd executable, visible in intel_gpu_top of intel-gpu-tools package on the line
for approx. 20 seconds, then it proceeds to
RAM is 80GB, didn't run out.
The text was updated successfully, but these errors were encountered: