mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: Diederik de Haas <didi.debian@cknow.org>,
	John Allen <john.allen@amd.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Non working HWRNG on AMD Ryzen 5 5500GT
Date: Thu, 15 Aug 2024 09:16:45 -0500	[thread overview]
Message-ID: <0561862d-99d9-ae72-49d0-9ad0639482ea@amd.com> (raw)
In-Reply-To: <D3GJCRNY4KDK.3SPJB5WP8Z7DK@cknow.org>

On 8/15/24 08:56, Diederik de Haas wrote:
> Hi,
> 
> I recently bought an Asus ROG STRIX B550-F GAMING MB with an
> AMD Ryzen 5 5500GT CPU (and installed the latest BIOS: 3607).
> I'm running Debian Testing/Sid on it with kernel 6.9 and now 6.10
> and it seems to work great.
> I've been doing some (unrelated) tests with `rngtest` from the
> `rng-tools5` package and wondered how it would fare on my AMD CPU.

I'm not very familiar with this test. What is the command line that you
are using to invoke it?

> 
> And I found out it doesn't work at all!
> But on another system I have (Asus ROG CROSSHAIR VII HERO MB +
> AMD Ryzen 1800X CPU) it works absolutely fine.
> 
> # dmesg | grep ccp
> [    5.399853] ccp 0000:07:00.2: ccp: unable to access the device: you might
> be running a broken BIOS.
> [    5.401031] ccp 0000:07:00.2: tee enabled
> [    5.401113] ccp 0000:07:00.2: psp enabled

Which system is this output from?

Can you provide the output from lspci -nn?

Thanks,
Tom

> 
> Found an article [1] which could be relevant and downloaded and ran the
> accompanying test program (written by Jason Donenfeld):
> # ./amd-rdrand-bug
> Your RDRAND() does not have the AMD bug.
> # ./test-rdrand
> RDRAND() =x47c993c0
> RDRAND() =xec7c697d
> ... (more seemingly random numbers)
> RDRAND() =xba858101
> 
> I tried it with the latest microcode dd 2024-07-10, but that didn't make
> a difference.
> 
> So I'd like to know if this may actually be a bug on the kernel side.
> 
> Happy to provide additional information or run tests or try patches.
> 
> Cheers,
>   Diederik
> 
> [1] https://arstechnica.com/gadgets/2019/10/how-a-months-old-amd-microcode-bug-destroyed-my-weekend/

  reply	other threads:[~2024-08-15 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 13:56 Diederik de Haas
2024-08-15 14:16 ` Tom Lendacky [this message]
2024-08-15 14:40   ` Diederik de Haas
2024-08-15 14:53     ` Tom Lendacky
2024-08-15 15:22       ` Diederik de Haas
2024-08-15 14:22 ` Jason A. Donenfeld
2024-08-15 14:56   ` Diederik de Haas

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=0561862d-99d9-ae72-49d0-9ad0639482ea@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=davem@davemloft.net \
    --cc=didi.debian@cknow.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=john.allen@amd.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®