From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: unlvsur unlvsur <unlvsur@live.com>
Cc: "unlvsur unlvsur via Libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: About amd ryzen 3000 bugs of rdseed and rdrand?
Date: Mon, 4 Oct 2021 10:24:51 +0100 [thread overview]
Message-ID: <CAH6eHdTMfY=_hcFRm1A87dZW85K34QTO_txq9t5C7JYtTL-C=Q@mail.gmail.com> (raw)
In-Reply-To: <DM6PR05MB469779B5C2983655A5CA3E7BD6AE9@DM6PR05MB4697.namprd05.prod.outlook.com>
On Mon, 4 Oct 2021 at 09:50, unlvsur unlvsur via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> My computer used to always return -1 for rdseed and rdrand for ryzen 3000.
>
> AMD Ryzen 3000 series CPUs can't do Random on boot causing Boot Failure on newer Linux distributions - LinuxReviews<https://linuxreviews.org/AMD_Ryzen_3000_series_CPUs_can%27t_do_Random_on_boot_causing_Boot_Failure_on_newer_Linux_distributions>
>
> [PATCH] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h (kernel.org)<https://lore.kernel.org/all/776cb5c2d33e7fd0d2893904724c0e52b394f24a.1565817448.git.thomas.lendacky@amd.com/T/#u>
>
> Libstdc++ uses rdseed and rdrand internally. Does it contain the rdseed bugs on ryzen 3000 cpu?
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100444
prev parent reply other threads:[~2021-10-04 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 8:47 unlvsur unlvsur
2021-10-04 9:24 ` Jonathan Wakely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdTMfY=_hcFRm1A87dZW85K34QTO_txq9t5C7JYtTL-C=Q@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=libstdc++@gcc.gnu.org \
--cc=unlvsur@live.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).