This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
SIGILL on some XEON CPU caused by prebuilt bin in Docker container #470
Comments
Another CPU where this happens, as reported by a different user.
|
Another user report
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
The Ursa process finishes with exit code 132 (interrupted by signal 4: SIGILL) on some XEON CPUs.
A Docker image is provided, prebuilt on an x86_64 DigitalOcean Intel vCPU machine, which is not supported by some Intel processors that VPS providers might supply.
A few examples of CPU are:
Here are a few examples of VPS provider's client VPS where this was observed:
As a temporary solution, the user is asked to build the image instead of accepting the recommended "latest" or "nightly". This means that
cargo build
enables or disables some CPU features by considering the native CPU in which thebuild
is launched.Environment
Demo
As discussed and observed in: https://discord.com/channels/965698989464887386/1047823650541277194/1090335532669735053
Another user:
https://discord.com/channels/965698989464887386/1047823650541277194/1090966733130580008
For clarity, this has nothing to do with Docker. Here we see a binary built natively DO Intel Ubuntu latest x86_64, attempt run on the XEON E5 VPS:
Notes
Debugging details
Asssembly
A
mulx
described here https://docs.oracle.com/cd/E37838_01/html/E61064/gnyak.html seems to be a CPU feature not available on older intel CPU such like the XEON E5 family above.Obs: A cargo build with target
x86_64-unknown-linux-gnu
was attempted, but that seems to be used by default when no--target
is specified. This was tested in a Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz VPS shared by a community member " LinKong| Sui Global" (on Discord).Checklist
The text was updated successfully, but these errors were encountered: