From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-integrity@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
reach622@mailcuk.com, 1138267643@qq.com,
Jarkko Sakkinen <jarkko@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [regression] Bug 216989 - since 6.1 systems with AMD Ryzen stutter when fTPM is enabled
Date: Tue, 7 Feb 2023 19:13:46 -0300 [thread overview]
Message-ID: <Y+LNGrA5llMxJNCU@zx2c4.com> (raw)
In-Reply-To: <1c04756b-574b-210d-9580-a4de2aa16a20@leemhuis.info>
On Sun, Feb 05, 2023 at 06:38:16PM +0100, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> [ccing Dominik (who authored the culprit) and Herbert (who merged it)]
>
> On 02.02.23 11:28, Linux kernel regression tracking (Thorsten Leemhuis)
> wrote:
> >
> > I noticed a regression report in bugzilla.kernel.org. As many (most?)
> > kernel developer don't keep an eye on it, I decided to forward it by
> > mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216989 :
>
> Turns out according to a bisection from one of the reporters that
> b006c439d58d ("hwrng: core - start hwrng kthread also for untrusted
> sources") (merged for 6.1) apparently makes this hardware issue occur
> quicker/more frequently a lot quicker on any board that didn't get the
> firmware update yet. So it could be argued that from the point of the
> kernel it *might* be considered a regression.
Finally replying without HTML, now that I'm at my laptop.
This isn't a bug with the commit you mentioned. Rather, this is a bug in
the TPM hardware and/or in the TPM driver. Probably the TPM driver
should quirk around the faulty BIOS to disable whatever functionality is
broken, or it should notice these latency spikes and warn, or something.
But I'll leave that to James; that's his wheelhouse.
Jason
prev parent reply other threads:[~2023-02-07 22: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
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 [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=Y+LNGrA5llMxJNCU@zx2c4.com \
--to=jason@zx2c4.com \
--cc=1138267643@qq.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--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