-
Notifications
You must be signed in to change notification settings - Fork 658
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
2.1.0-rc.2 SIGILL on older CPU #11872
Comments
@evgenykuzyakov Well, it was discussed in this thread: #11711 (comment), and concluded with:
|
Let's add it to the release notes than and update docs |
Hi @evgenykuzyakov, the hardware requirements have always required SHA-NI. See the docs. We initially hoped that this will be an easy transition since it is specified in the requirements. You are right, it is worth adding it to the release notes to make it clear. |
I have updated the release notes. |
Describe the bug
Testnet RPC node crashes with
2.1.0-rc.2
release: https://gist.github.com/evgenykuzyakov/4d4bd4759f8ebee978ef7f2898200a06It has the following CPU: https://gist.github.com/evgenykuzyakov/0b54e1ec527a6bc1d7b0507e472dbca1
Seems like 2.1.0 release introduced
+sha
target in.cargo/config.toml
that is not available on some older CPUs.It also looks like
+sha
is just an optimization and is not a hard requirement for a node to function.To Reproduce
2.0.0-rc.5
to2.1.0-rc.2
.neard
on the x86 CPU withoutsha
flagExpected behavior
Either verify the CPU flag exists before compilation or make it an explicit requirement in the release.
Version (please complete the following information):
2.1.0-rc.2
Additional context
Verified that it runs when the flag is removed from the
.cargo/config.toml
The text was updated successfully, but these errors were encountered: