cross-posted from: https://lemmy.world/post/2852886

For those out of the loop, some AMD users have been suffering from stuttering issues caused by the AMD fTPM random number generator. A firmware/BIOS update appears to fix the issue for some users, but not others, leading to more bug reports being sent in. Last week, Linus Torvalds said “let’s just disable the stupid fTPM hwrnd thing”, and, as of today the Linux kernel has gone ahead and blanket disabled RNG use for all current AMD fTPMs.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    30
    ·
    1 year ago

    This is the best summary I could come up with:


    As a follow-up to the first-on-Phoronix article last month that highlighted Linus Torvalds’ frustrated views on the AMD fTPM random number generator continuing to cause problems for users even with updated firmware/BIOS, as of today the Linux kernel has gone ahead and blanket disabled RNG use for all current AMD fTPMs.

    Mario summed up in that commit: tpm: Disable RNG for all AMD fTPMs

    The TPM RNG functionality was previously disabled on a subset of AMD fTPM series, but reports continue to show problems on some systems causing stutter root caused to TPM RNG functionality.

    Expand disabling TPM RNG use for all AMD fTPMs whether they have versions that claim to have fixed or not.

    Thus over the next few days this change in behavior for modern AMD Ryzen systems will be rolling out in the next set of stable kernel point releases.

    Hopefully this will lay to rest the various AMD stutter issues that continue to be reported by Linux users on recent kernel versions.


    I’m a bot and I’m open source!

    • Avid Amoeba@lemmy.caOP
      link
      fedilink
      arrow-up
      4
      ·
      1 year ago

      I assume there’s a kernel boot param that allows for disabling it if you get affected in a kernel older than the one they’ll be disabling this.

  • potemkinhr@lemmy.ml
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    Just to add a perspective from the other side of the fence, I have a gaming laptop running Windows 11 (yes I know) where this (or a very similar) issue has been plaguing Ryzen users for at least a year and a half. The issue is that TPM per se is not causing issues if turned on, but if BitLocker encryption is on it will cause occasional audio stutters and intermittent complete system halts. The only thing that reliably helps is completely turning off Bitlocker, the TPM chip can stay on and is of course needed for W11. OEMs and AMD have been digging their heads in the sand like ostritches and they have released the odd fix that does nothing to fix the underlying issue. I can’t see MS doing anything to reverse course on requirements and am getting a bit fed up with their BS lately, browsing what distro might suit me best and might pull the trigger and finally switch…

    • Kogasa@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year ago

      TPM is not necessary for Windows 11.

      I have a Windows 11 partition and fTPM is disabled in UEFI. Windows complains that “My computer doesn’t meet the requirements to update to Windows 11” on the update menu, but there’s no issue.

      • potemkinhr@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Thanks for the heads up, I’m distro hopping these days and looking for options on where to settle

    • Avid Amoeba@lemmy.caOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      You’ll need to use a bleeding edge kernel to get this patch unless it’s backported to older kernels by your distro’s maintainers. I doubt this will happen for say Debian or Ubuntu. Instead, you’d have to wait for a new HWE that has this new kernel or whatever the equivalent in Debian is.

      • argv_minus_one@beehaw.org
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        You can also solve this problem by disabling the TPM in the BIOS settings, assuming your motherboard has such a setting. No TPM, no problem.

          • argv_minus_one@beehaw.org
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 year ago

            This is the way. Besides these stuttering issues, the TPM is owner-disobedient (there is no way for the owner to extract keys stored in it) and an unnecessary attack surface (which, if breached, gives the attacker unfettered, persistent, and irrevocable access to the entire machine).