-
Notifications
You must be signed in to change notification settings - Fork 11.7k
Misc. bug: llama-bench SEGFAULTS w/ SYCL/HIP backend, however llama-cli seems to work #10850
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
Comments
This probably helps:
Also, I don't know if its related or a separate issue, but when I run
|
It seems it is failing in gemm_batch when calculating context and not in rmsnorm. Can you try running It is also failing at model warmup (again while calculating context) edit: gemm_batch uses MKL |
@qnixsynapse for |
hmm. I figured that out. llama-cli test completion passes because it doesn't use MKL's gemm_batch |
Based on the results of This of course is a bit of a niche of a niche. I've submitted a PR w/ some fixes so people can properly build SYCL for AMD GPUs but I can understand if it's not digging too deep on. |
I think we have to make MKL select the AMD backend, probably rocblas? I think adding compile_definition |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Name and Version
❯ build/bin/llama-cli --version
ggml_sycl_init: GGML_SYCL_FORCE_MMQ: no
ggml_sycl_init: SYCL_USE_XMX: yes
ggml_sycl_init: found 1 SYCL devices:
version: 4334 (4ddd199)
built with Intel(R) oneAPI DPC++/C++ Compiler 2025.0.0 (2025.0.0.20241008) for x86_64-unknown-linux-gnu
Operating systems
Linux
Which llama.cpp modules do you know to be affected?
llama-bench
Problem description & steps to reproduce
I have built with the SYCL backend w/ AMD HIP support using (mostly) the build docs (PR coming for some fixes).
When I try to run
llama-bench
I get a segfault after callingggml_sycl_rms_norm
:Note, when I run
llama-cli
it runs, so the build is at least somewhat working:First Bad Commit
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: