By: name (email.delete@this.email.em), August 11, 2019 8:35 am
Room: Moderated Discussions
anonymou5 (no.delete@this.spam.com) on August 10, 2019 2:52 pm wrote:
> > Zen 2 with the rdrand bug
>
> Is Family 17h actually affected?
>
> Because https://bugzilla.kernel.org/show_bug.cgi?id=85911 suggests only 22 = 16h = not Zen1/Zen2.
>
> And https://github.com/systemd/systemd/pull/12536/commits/1c53d4a070edbec8ad2d384ba0014d0eb6bae077
> doesn't seem to terrible for a workaround.
Actually, the Ryzen 3000 (Zen2) series was/is affected. According to user reports (such as https://www.reddit.com/r/Amd/comments/cmza34/agesa_1003_abb_fixes_rdrandrdseed/) a new firmware fixes the issue.
It seems AMD's QA is not the best - 'let the early adopters beta test the stuff first'.
> > Zen 2 with the rdrand bug
>
> Is Family 17h actually affected?
>
> Because https://bugzilla.kernel.org/show_bug.cgi?id=85911 suggests only 22 = 16h = not Zen1/Zen2.
>
> And https://github.com/systemd/systemd/pull/12536/commits/1c53d4a070edbec8ad2d384ba0014d0eb6bae077
> doesn't seem to terrible for a workaround.
Actually, the Ryzen 3000 (Zen2) series was/is affected. According to user reports (such as https://www.reddit.com/r/Amd/comments/cmza34/agesa_1003_abb_fixes_rdrandrdseed/) a new firmware fixes the issue.
It seems AMD's QA is not the best - 'let the early adopters beta test the stuff first'.