Language server crashes with CRNGT failed / FIPS integrity test failed on AMD Zen+ (Fedora 43)

Google Antigravity
1

Environment:

  • OS: Fedora 43

  • CPU: AMD (Zen+ with recent firmware/microcode update)

  • Antigravity version: [your version]

Description: The Antigravity language server crashes immediately on startup with CRNGT failed. SIGABRT: abort due to BoringSSL’s Continuous Random Number Generator Test failing. This is caused by recent AMD firmware updates that cause RDRAND to return constant values while still reporting success, which triggers BoringSSL’s security abort.

Attempted workarounds:

  • OPENSSL_ia32cap="0:0" — ineffective, binary ignores it

  • update-crypto-policies --set LEGACY — ineffective

  • nordrand kernel boot flag — changes error to FIPS integrity test failed because the hardcoded FIPS checksum no longer matches, making the two bugs mutually exclusive

  • setenforce 0 — ineffective

Root cause: The language server binary (language_server_linux_x64) is statically linked with BoringSSL in FIPS mode and executes raw RDRAND assembly instructions, bypassing all kernel and environment-level workarounds. The FIPS integrity checksum is hardcoded, preventing any runtime patching.

Requested fix: Provide a non-FIPS build of the language server for Linux, or update BoringSSL to detect poisoned RDRAND output and fall back to software entropy gracefully without breaking the FIPS integrity check.