RDSEED32 is broken on startup

On startup I get this message now: RDSEED32 is broken it goes by very fast on the top so I can’t get all of the error typed. It seems like everything is working normally but I’m still a bit paranoid since I updated my computer after 3 months due to medical issues.

Is it all good? Or do I need to manually fix anything?

Does journalctl -b -p err show anything concerning?

Jan 18 12:54:19 Mechagodzilla kernel: **RDSEED32 is broken. Disabling the corresponding CPUID bit.**
Jan 18 12:54:31 Mechagodzilla wpa_supplicant\[1020\]: **bgscan simple: Failed to enable signal strength monitoring**
Jan 18 12:54:33 Mechagodzilla kernel: **Bluetooth: hci0: Execution of wmt command timed out**
Jan 18 12:54:33 Mechagodzilla kernel: **Bluetooth: hci0: Failed to send wmt func ctrl (-110)**
Jan 18 12:54:33 Mechagodzilla kded6\[1410\]: **Couldn’t find QML Decoration  “”**
Jan 18 12:54:38 Mechagodzilla wpa_supplicant\[1020\]: **bgscan simple: Failed to enable signal strength monitoring**
Jan 18 13:04:03 Mechagodzilla systemd-coredump\[5528\]: \[🡕\] **Process 5521 (minecraft-launc) of user 1000 dumped core.**

Here’s everything it showed. I apologize for just giving all of it, I’m not sure which is important to worry about or not.

It looks like this message is letting you know it is disabling this functionality due to an issue some AMD CPUs. See more information here.

If you want that message to go away, it seems like you need both the latest firmware/ucode and to update your BIOS to the latest revision. If you are updating the system, you should already have the latest firmware/ucode. So you may want to look and see if there is a fix for the issue in a recent BIOS update for your motherboard.

I’ll have to fix this some other time then, don’t have enough time to do this currently. Thank you for the help.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.