All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	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: Wed, 8 Feb 2023 04:13:10 +0200	[thread overview]
Message-ID: <Y+MFNvr2deX7+Mxa@kernel.org> (raw)
In-Reply-To: <8a7775912f31394944b43db12adc78efd84b1fad.camel@HansenPartnership.com>

On Thu, Feb 02, 2023 at 07:57:37AM -0500, James Bottomley wrote:
> 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
> 

And e.g. I do not have a Ryzen CPU so pretty hard to answer such question.

BR, Jarkko

  reply	other threads:[~2023-02-08  2:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 10:28 [regression] Bug 216989 - since 6.1 systems with AMD Ryzen stutter when fTPM is enabled Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-02 12:57 ` James Bottomley
2023-02-08  2:13   ` Jarkko Sakkinen [this message]
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=Y+MFNvr2deX7+Mxa@kernel.org \
    --to=jarkko@kernel.org \
    --cc=1138267643@qq.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Jason@zx2c4.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.