Ryzen 3000: a known bug causes many Linux distributions to fail


When using the Ryzen processors random number generator, there is a problem with Linux, due to which many current Linux distributions do not start on the AMD Ryzen 3000 presented Sunday. The bug has long been known, but it is more evident in the new CPU family. The System and service manager Systemd gets so much out of phase that the system startup fails with the new Ryzen.

For many current Linux distributions, the system boot fails with the Ryzen 3000.

For many current Linux distributions, the system boot fails with the Ryzen 3000.

(Photo: c & # 39; t / Thorsten Leemhuis)

The problem occurs with Ubuntu 19.04, Fedora 30 or the current Manjaro, for example, with the versions installed and when the installation support is started. The version also released on the Debian 10 weekend and the old Ubuntu 18.04 and Fedora 29 distributions begin instead.

the The problem is known from the autumn of 2018: On some systems Ryzen 2 has arrived already the Systemd 240, 241 and the current version 242 from footballwhen the system is reactivated from suspend mode. On the other hand, everything went normal with older versions of Systemd, because only a code added to 240 triggers the problem, which gets random numbers directly from the processor via the RDRAND statement. The developers have This code was then adapted a few weeks ago into the developer branch againso that Systemd can detect the bad behavior on the CPUs involved; In this change, they have emphasized that in reality it is a kernel of bugs or BIOS that must be managed, because otherwise it can also affect other programs.

With AMD Ryzen 3000 the problem does not only arise when waking up from standby, but already starting the system: this was evident in the test lab, because Ubuntu 19.04, Fedora 30 or Manjaro do not start up on several motherboards with a Ryzen 3000. With a Ryzen 2000 it managed the cards but easily. We have therefore installed a Fedora 30 with such and provided the system version used there with the correction of the problem. So we could still use the Ryzen 3000 and here: The Linux distribution started normally.

Ubuntu 18.04 and Fedora 29 use an old system, so the problem does not appear there. Debian 10 would actually have been influenced by Macke, because it uses Systemd 241; The distribution is running, however, as the Debian developers are still correcting the problem shortly before the release integrated into your systemd package,

Also the creators of Fedora 30, Ubuntu 19.04 and Co. should be on this path. In order to install these distributions, developers should also provide new installation media. This effort is spared by the creators of the most preserved distributions. Presumably, they will address the problem only with the next one, expected in the autumn versions like Fedora 31 and Ubuntu 19.10, which should then get the bug fix with Systemd 243 or new house. It remains to be seen whether the Linux kernel or BIOS developers will include an alternative solution to identify the problem first and for all programs.


On the home page

. (tagsToTranslate) AMD Ryzen 3000 (t) Linux and Open Source (t) Systemd


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.