AMD Ryzen 3000 series fails to boot

The attachment "Rebase of https://github.com/systemd/systemd/pull/12536" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

A systemd package with this patch applied is building here:

- amd64 - https://launchpad.net/~system76/+archive/ubuntu/proposed/+build/17236776
- i386 - https://launchpad.net/~system76/+archive/ubuntu/proposed/+build/17236777

I have tested the patch posted, and it produces a bootable system with 19.04. We will be releasing the patched version of systemd in the following PPAs:

Pop!_OS - https://launchpad.net/~system76/+archive/ubuntu/pop
Ubuntu support for System76 computers - https://launchpad.net/~system76-dev/+archive/ubuntu/stable

Please let me know what needs to happen to get this patch into Ubuntu 19.04

Thanks for your bug report & patch!

I'm subscribing ubuntu-sponsors which is what is needed for the bug to get on the sponsoring queue (http://reqorts.qa.ubuntu.com/reports/sponsoring/index.html)

I'm also tagging the bug rls-dd-incoming and rls-ee-incoming so it gets on the list of targetted to review which should help visibility

Good findings!

Thank you so much for testing the rdrand theory.

I guess a read fix would require a new ISO, which could easily be made as a dot release (19.04.1).

Regards,
Eric

Sebastien, thanks for getting eyes on it!

Éric, these systems will not boot the 19.04 ISO without either new firmware fixing the rdrand instruction, or a new ISO updating systemd with this patch.

FWIW, I think not booting a 19.04 ISO is probably fine, and it's not worth spinning a point release for this. "I can't install a 9mo release on this hardware" is unforunate, but not world-ending.

However, we should definitely SRU this for people who are likely to take their EXISTING 19.04 system with a Ryzen 1xxx/2xxx and drop in a 3xxx and find it doesn't boot anymore. Also, obviously, we should make sure it's fixed for 19.10.

Status changed to 'Confirmed' because the bug affects multiple users.

Hello Jeremy, or anyone else affected,

Accepted systemd into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/240-6ubuntu5.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Note that the fix is committed to git for eoan, but not uploaded as systemd currently fails its testsuite on eoan. This needs investigation.

Thanks, I will get it tested soon

All autopkgtests for the newly accepted systemd (240-6ubuntu5.2) for disco have finished running.
There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures.

https://people.canonical.com/~ubuntu-archive/pending-sru.html#disco

I tested 240-6ubuntu5.2, it fixes the issue on Ubuntu 19.04

>> FWIW, I think not booting a 19.04 ISO is probably fine,

Unless like me, you have just upgraded your hardware to a Ryzen 3600x and find you have to downgrade from the version you are using on your old machine to use the new machine you just purchased.....

@matthew-sleeper & All,

The current options workaround options are installing 18.04/18.10, then upgrading to 19.04.
Using the netboot installer to install 19.04 on AMD 3000 series machines may also work after the fix for this but gets released to -updates:
http://cdimage.ubuntu.com/netboot/disco/

I personally believe that this bug would warrant at least spinning a half-official installer for amd64, but @adconrad can make this call, not me.

Hi, could you confirm that this bug is regarding all 3 gen Ryzen processors? I mean that 3400G (with integrated GPU) processor has Zen+ architecture but others have Zen2. Thanks.

Hi, I can confirm now that newly installed 19.04 on 3400G is booting without any problems.

AMD released a BIOS fix: https://www.phoronix.com/scan.php?page=news_item&px=AMD-Releases-Linux-Zen2-Fix&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Phoronix+%28Phoronix%29

This bug was fixed in the package systemd - 240-6ubuntu5.2

---------------
systemd (240-6ubuntu5.2) disco; urgency=medium

  [ Jeremy Soller ]
  * random-util: eat up bad RDRAND values seen on AMD CPUs.
    This fixes AMD Ryzen 3000 series failing to boot (LP: #1835809)

 -- Balint Reczey <email address hidden> Tue, 09 Jul 2019 11:52:55 +0200

The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

AMD has pulled back their first BIOS/Microcode fix due to problems with some boards switching down from PCI 4.0 to PCI 2.0 - the release seemingly only went as far as the big board vendors. the board vendors got order to not re-distribute that version in any form. sounds reasonable to me. indeed its already indicated that AMD still hopes to provide a solution in a near time frame.

Maybe unrelated (but those communications channel might be worth watching for related news):
Robert Hallock of AMD has announced a new beta driver for the chipset that is/was available via google drive. It is said this fixes something relevant for at least the game Destiny 2. As the test phase was closed already a quick follow up in about 1 day was promised.
https://www.reddit.com/r/Amd/comments/ciajef/placeholder_update_on_whea_warnings_destiny_2_and/evayush/
https://drive.google.com/file/d/1mojPNWcOuuhxvdBkYJlkLbsDXwGLImGp/view

A bunch of updates went public - the AGESA component update is still due as its pushed to the end user via the integration and qualification pipeline of the board vendors. It got said this will take several weeks.
https://community.amd.com/community/gaming/blog/2019/07/30/community-update-5-let-s-talk-clocks-voltages-and-destiny-2

Does anyone here have a work around to install Ubuntu 19.04 without upgrading from a previous version?

@g.grazios, please see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/comments/16

Today in IRC we were asked if the ficed package is in the 19.04 ISOs. It isn't so they will fail to boot on AMD Ryzen 3000 CPUs.

Is there a plan to re-build the 19.04 ISOs? If not there ought to at least be a prominent addition to the 19.04 release notes.

IS this fix now implemented to the latest ISO available for download?

This bug was fixed in the package systemd - 240-6ubuntu13

---------------
systemd (240-6ubuntu13) eoan; urgency=medium

  * Drop s390x seccomp fix causing regression on s390x
    Files:
    - debian/patches/src-shared-seccomp-util.c-Add-mmap-definitions-for-s390.patch
    https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=da95e1d022e94a4d3ce0b69bd6eb398c95d09f24

 -- Balint Reczey <email address hidden> Mon, 26 Aug 2019 17:02:54 +0200