From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Peter Huewe <peterhuewe@gmx.de>,
Jarkko Sakkinen <jarkko@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-integrity@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
reach622@mailcuk.com, 1138267643@qq.com,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: [regression] Bug 216989 - since 6.1 systems with AMD Ryzen stutter when fTPM is enabled
Date: Thu, 02 Feb 2023 07:57:37 -0500 [thread overview]
Message-ID: <8a7775912f31394944b43db12adc78efd84b1fad.camel@HansenPartnership.com> (raw)
In-Reply-To: <3a196414-68d8-29c9-24cc-2b8cb4c9d358@leemhuis.info>
On Thu, 2023-02-02 at 11:28 +0100, Linux kernel regression tracking
(Thorsten Leemhuis) wrote:
[...]
> So it's a firmware problem, but apparently one that Linux only
> triggers since 6.1.
>
> Jason, could the hwrng changes have anything to do with this?
>
> A bisection really would be helpful, but I guess that is not easy as
> the problem apparently only shows up after some time...
the problem description says the fTPM causes system stutter when it
writes to NVRAM. Since an fTPM is a proprietary implementation, we
don't know what it does. The ms TPM implementation definitely doesn't
trigger NV writes on rng requests, but it is plausible this fTPM does
... particularly if they have a time based input to the DRNG. Even if
this speculation is true, there's not much we can do about it, since
it's a firmware bug and AMD should have delivered the BIOS update that
fixes it.
The way to test this would be to set the config option
CONFIG_HW_RANDOM_TPM=n
and see if the stutter goes away. I suppose if someone could quantify
the bad bioses, we could warn, but that's about it.
James
next prev parent reply other threads:[~2023-02-02 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 10:28 Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-02 12:57 ` James Bottomley [this message]
2023-02-08 2:13 ` Jarkko Sakkinen
2023-02-08 2:13 ` Jarkko Sakkinen
2023-02-08 2:31 ` Jason A. Donenfeld
2023-02-08 2:52 ` Jarkko Sakkinen
2023-02-05 17:38 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-07 22:13 ` Jason A. Donenfeld
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=8a7775912f31394944b43db12adc78efd84b1fad.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=1138267643@qq.com \
--cc=Jason@zx2c4.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=reach622@mailcuk.com \
--cc=regressions@lists.linux.dev \
/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®