Thread: Let's make a list of all the fun ways AMD's Zen 2 RdRand failure has messed up this Fedora 30 system. The instruction reports success (CF=1) but returns 0xFFFFFFFFFFFFFFFF (almost?) every time.
4. Run grub2-mkconfig > grub.cfg add that nordrand arg. Bad move. That probes LVM devices which also uses RdRand. System gets unresponsive (all the blocked kworkers?) and I reboot, but now grub.cfg is empty so grub doesn't know how to load anything. No backup copy.
-
-
4b. Try to rebuild grub.cfg from the Fedora 29 USB. Nope, that uses RdRand too. It's a complex config and typing in commands at the grub prompt fails. Hours later, piece together a working cfg from the raw /boot/efi partition. Booted with nordrand, grub2-mkconfig works again.
Show this thread -
That was 4 days ago and it hasn't broken again yet. AMD released new microcode and then pulled it due to other bugs, so no real fix yet. Applications can still call RdRand from userspace so who knows what else will break.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

