-
Notifications
You must be signed in to change notification settings - Fork 7
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
Got "Illegal instruction" error while loading GGUF models after built #434 #2
Comments
Can you provide your hardware information? I'm wondering if it's related to avx Nevermind I see now it's in the printout, sec |
I tried to run with different flag combinations with |
If you're building it from the Dockerfile can you try adding ENV NOAVX2_BUILD=1 before make? |
The build failed with that ENV at this line https://github.com/LostRuins/koboldcpp/blob/2dc96687eb7c0fcacb2506e2fcf97dc909cc6cae/Makefile#L439: Logs:
|
To add: I even tried to build the Docker image inside the same k8s cluster (using Kaniko) to ensure the build environment is as close as possible (if not the same) to the running environment. However, the issue still occurs. |
@MichaelBui Could you try to replace the make on line 14 with:
that was able to compile for me, may work for you |
@noneabove1182 which branch is that? I've checked both |
@noneabove1182 this version (~2 months ago) doesn't support GGUF. |
That's just where it was committed |
i did mess up and i see what you're saying now, but also i think that that build option is irrelevant anyways sadly did you ever try building on that VM and running it with --noavx2 to see if it actually worked or if it's a hardware issue? |
Yes, I mentioned above:
I tried similar steps with oobabooga and succeeded without any errors. |
The app fails while loading models:
The build is successful (
DONE
without return code):Environment and Context
I've also reported here because I'm not sure if it's KoboldCPP related issue or Docker/Kubernetes related issue: LostRuins/koboldcpp#434
The text was updated successfully, but these errors were encountered: