You are not logged in.
After upgrading to kernel 6.17.8-arch1-1, I now get an error message right before fsck that says simply the following:
RDSEED32 is broken. Disabling the corresponding CPUID bit.After checking kernel bug reports, I see that this is an issue with amd-ucode and that it's been addressed on Nov 3, but it's unclear whether it's available on the latest amd-ucode-20251111-1. My other AMD systems run fine. I understand that this affects only certain AMD CPUs, so here are my specs:
Operating System: Arch Linux
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Memory: 64 GiB of RAM (62.1 GiB usable)
Graphics Processor 1: AMD Radeon 890M Graphics
Graphics Processor 2: NVIDIA GeForce RTX 5070 Laptop GPUI should say that this laptop has worked flawlessly (and continues to, despite this latest message) since I got it. I just want to make sure that it's not having any issues because of ucode bugs.
Offline
I get the same error with a 9700x. So far no issues.
Offline
I get the same error
```
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × AMD Ryzen AI 9 H 365 w/ Radeon 880M
Memory: 32 GiB of RAM (27.2 GiB usable)
Graphics Processor: AMD Radeon 890M Graphics
Manufacturer: LENOVO
Product Name: 21Q5
System Version: ThinkBook 16 G7+ ASP
```
Offline
Offline
So if I understand the reports correctly:
- People figured out that on AMD CPUs, the RDSEED32 register is not as random as it should be.
- As a stopgap measure, kernel folks have reconfigured the CPU for now so the CPUID instruction tells userspace programs they shouldn’t be using RDSEED32.
- In the meantime, AMD has published a microcode update to fix RDSEED32. The fix has only just landed in the main branch of `linux-firmware`.
- However, `linux-firmware` hasn’t had an upstream release yet since 2025-11-14. Once it does, it will include the microcode fix and can land on Arch.
- In the meantime, the CPUID workaround has now landed in Arch’s kernel packages, which explains why we suddenly see the message during startup.
Feel free to correct me if I’m wrong.
Offline
There was a firmware update today, in fact: version 20251125-1; along with amd-ucode, as well. The RDSEED32 message persists. Just thought people should be aware. This problem hasn't gone away, yet.
Offline
There was a firmware update today, in fact: version 20251125-1; along with amd-ucode, as well. The RDSEED32 message persists. Just thought people should be aware. This problem hasn't gone away, yet.
This update fixed the issue for me (9700x). So I guess the fix is being released incrementally to more CPUs.
Offline
I am running Kernel 6.17.9-zen1-1-zen on a Ryzen 9950x.
I updated the firmware and AMD ucode, but I still see the message.
Just an FYI.
Offline
I am running Kernel 6.17.9-arch1-1 on a Ryzen 9950x3D.
After updating firmware, AMD ucode and rebuilding my UKI, everything was fixed. No more RDSEED32 messages.
Offline
Updated linux-firmware today and now I'm getting
"Microcode: CPU0: Update failed for patch_Level0x0b40435"
I do love me some arch whackiness. Hopefully something will fix it eventually.
Offline
I was also seeing this, and at the same time the amd-ucode stopped loading. I reported the microcode problem https://gitlab.archlinux.org/archlinux/ … /issues/34. Updating the firmware / BIOS for the motherboard to the latest fixed the RDSEED32 message and the amd-ucode problem.
Offline
As of kernel 6.18.1, this RDSEED32 issue persists. This should not require a BIOS update. I've rebuilt my UKI and it still persists with the latest amd-ucode. I thought the patch was put in place for this kernel.
Last edited by haigioli (2025-12-17 14:17:29)
Offline
Take a look at the gitlab issue I linked in post #11. It details why the BIOS firmware must be updated. The method for loading microcode was changed to resolve a security issue.
Offline
@debo, I see your point. I've sent an email to my vendor to see if they have a BIOS update.
Offline
Apparently the fix for the security issue renders the later microcode updates unable to be loaded by the older firmware.
Offline