Skip to content
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

provided PTX was compiled with an unsupported toolchain #122

Open
thangld201 opened this issue Jan 16, 2024 · 1 comment
Open

provided PTX was compiled with an unsupported toolchain #122

thangld201 opened this issue Jan 16, 2024 · 1 comment

Comments

@thangld201
Copy link

thangld201 commented Jan 16, 2024

./build/bin/main -m /tmp/ReluLLaMA-7B-PowerInfer-GGUF/llama-7b-relu.powerinfer.gguf -n 128 -t 8 --vram-budget 40 -p "Hi. How are you ?"
Log start
main: build = 1560 (2217e7f)
main: built with cc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0 for x86_64-linux-gnu
main: seed  = 1705391051
ggml_init_cublas: GGML_CUDA_FORCE_MMQ:   no
ggml_init_cublas: CUDA_USE_TENSOR_CORES: yes
ggml_init_cublas: found 1 CUDA devices:
  Device 0: A100-SXM4-40GB, compute capability 8.0

CUDA error 222 at /py_lib/PowerInfer/ggml-cuda.cu:6466: the provided PTX was compiled with an unsupported toolchain.
current device: 0

I'm having the above error. Could you take a look ? @hodlen I used gpu with llama.cpp normally so this error should be from PowerInfer.

Similar issue with llama-cpp-python was raised here.

@hodlen
Copy link
Collaborator

hodlen commented Jan 22, 2024

Hi @thangld201, can I confirm that you compiled the code using the latest main branch, and encountered the error at this line?

The error might indicate that the PTX was generated by a compiler newer than what is supported by the CUDA driver and PTX JIT compiler. This line of code is involved in initializing the CUDA backend and is the same as in llama.cpp. Therefore, I suspect the issue may stem from your running environment.

I suggest trying again after updating the CUDA toolkit and ensuring that the compiler and driver versions match, as a similar issue was resolved in this way. Please feel free to provide more details if the error persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants