You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Illegal instruction on stable-x86_64-unknown-linux-gnu #5160
rustup 1.29.2 (d8c92c676 2026-10-21)info: This is the version for the rustup toolchain manager, not the rustc compiler.info: the currently active `rustc` version is `rustc 1.99.1 (58cf8f9c3 2026-10-13)`
I'm not aware of any changes on our end that could have caused this.
This could possibly be an issue in rustc (though I somewhat doubt it) since one difference is that rustup was built with a newer rustc. More likely it's something that changed when building one of the C dependencies we use (e.g. a cryptography library).
Thread 1 "rustup-init" received signal SIGILL, Illegal instruction.
#0 0x0000555555ca3638 in core::core_arch::x86::sse41::_mm_extract_epi32::<1> ()
#1 0x0000555555ca3626 in <chacha20::ChaChaCore<chacha20::R12, chacha20::variants::Legacy> as rand_core::block::Generator>::generate ()
#2 0x0000555555ca26c9 in rustup::utils::raw::random_string ()
#3 0x0000555555ca4428 in <rustup::dist::temp::Context>::new_file_with_ext ()
#4 0x0000555555886f8c in <rustup::dist::download::DownloadCfg>::download_and_check::{closure#0} ()
#5 0x0000555555886356 in <rustup::dist::download::DownloadCfg>::dl_v2_manifest::{closure#0} ()
#6 0x000055555589b759 in rustup::dist::try_update_from_dist_::{closure#0} ()
#7 0x000055555585ab30 in <rustup::dist::DistOptions>::install_into::{closure#0}::{closure#0} ()
#8 0x0000555555854cd7 in <rustup::install::InstallMethod>::install::{closure#0}::{closure#0} ()
#9 0x0000555555885484 in <rustup::install::InstallMethod>::install::{closure#0} ()
#10 0x000055555585657c in <rustup::toolchain::distributable::DistributableToolchain>::install::{closure#0}::{closure#0} ()
#11 0x000055555588b80e in <rustup::toolchain::distributable::DistributableToolchain>::install::{closure#0} ()
#12 0x000055555585f7c6 in rustup::cli::setup_mode::main::{closure#0}::{closure#0} ()
#13 0x0000555555852075 in rustup_init::run_rustup_inner::{closure#0}::{closure#0} ()
#14 0x00005555558504e4 in rustup_init::run_rustup::{closure#0}::{closure#0} ()
#15 0x00005555558848a7 in rustup_init::main::{closure#0} ()
#16 0x000055555581a94d in <tokio::runtime::runtime::Runtime>::block_on::<rustup_init::main::{closure#0}> ()
#17 0x00005555558bc9a2 in rustup_init::main ()
#18 0x000055555583ef3b in std::sys::backtrace::__rust_begin_short_backtrace::<fn() -> core::result::Result<std::process::ExitCode, anyhow::Error>, core::result::Result<std::process::ExitCode, anyhow::Error>> ()
#19 0x00005555558e5f70 in main ()
Updating chacha20 from v0.10.1 (yanked) to v0.10.2 fixes the issue.
Activity
ChrisDenton commentedon Oct 24, 2026
I'm not aware of any changes on our end that could have caused this.
This could possibly be an issue in rustc (though I somewhat doubt it) since one difference is that rustup was built with a newer rustc. More likely it's something that changed when building one of the C dependencies we use (e.g. a cryptography library).
shoPanda commentedon Oct 24, 2026
I believe this is the issue: RustCrypto/stream-ciphers#579
Running on CPU with SSE2 but without SSE4.1:
Updating chacha20 from v0.10.1 (yanked) to v0.10.2 fixes the issue.
ChrisDenton commentedon Oct 24, 2026
Thanks! We'll need to do another release then.
rami3l commentedon Oct 25, 2026
Closed by #5162, thanks a lot @ChrisDenton! I'll handle the release when I get back later this week.
See #5166 for the release status.