public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Christian Heusel" <christian@heusel.eu>,
	"Peter Huewe" <peterhuewe@gmx.de>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"James Bottomley" <James.Bottomley@hansenpartnership.com>
Cc: <linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<regressions@lists.linux.dev>
Subject: Re: [REGRESSION][BISECTED] tpm: Popping noise in USB headphones since 1b6d7f9eb150
Date: Fri, 25 Oct 2024 17:47:36 +0300	[thread overview]
Message-ID: <D54YWMOV7KOO.2X0N035UHEFBD@kernel.org> (raw)
In-Reply-To: <7d052744-4bfa-40bc-ba06-1b4c47a5eb87@heusel.eu>

Yeah, this is on the list.

See: https://bugzilla.kernel.org/show_bug.cgi?id=219383#c5

I had a fix for the AMD boot-time issue already over a month ago
but unfortunately took time to get enough feedback.

BR, Jarkko

On Fri Oct 25, 2024 at 3:11 AM EEST, Christian Heusel wrote:
> Hello everyone,
>
> Adam reports that since switching to the 6.10 kernel they have a popping
> sound from time to time (roughly every 10 minues) on their headphones
> which are connected via a [UGREEN's 5-in-1 USB-C Hub][0].
>
> We have then done a [lengthy bisection][1] on the mainline kernel which
> came to the conclusion that the following commit is the culprit of the
> issue:
>
>     1b6d7f9eb150 ("tpm: add session encryption protection to tpm2_get_random()")
>
> Since I thought that these results are likely not correct Adam has
> verified our results again by re-testing the bisection steps and again
> came to the same conclusion. Additionally I have shot the same question
> [at Jarkko on Mastodon] to find out if it's possible that changes in the
> TPM subsystem can have such an effect.. Without knowing the exact commit
> we had bisected to he pointed to the same functionality:
>
> > Jarkko Sakkinen (@jarkko@social.kernel.org):
> >
> > @gromit i might actually might have hunch for this but have been
> > unmotivated to move forward before these patches are merged. One thing
> > at a time IMHO, especially with performance fixes.
> > NOTE: this is a hyphothesis.
> >
> > tpm2_get_random() needs to be reconsidered with encryption as hwrng
> > calls it often enough and there's now more overhead.
> >
> > It pulls entropy in small chunks subtracting the length in the look
> > like you would use read() syscall from user space. This is not right.
> > This leads to small and variable size exchanges and yeah generally
> > that equates to an inefficient implemenation with bad latency
> > properties.
>
> If there are any patches to test or if further input is needed from the
> initial reporter on our Bugtracker we can do that!
>
> Thank you all for your hard work on the kernel!
>
> Cheers,
> Chris
>
>
> [0]: https://uk.ugreen.com/collections/hubs-1/products/ugreen-5-in-1-4k-hdmi-usb-c-hub
> [1]: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/79#note_210599
> [2]: https://chaos.social/@gromit/113345582873908273
>
> ---
> #regzbot introduced: 1b6d7f9eb150 
> #regzbot link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/79
> #regzbot link: https://chaos.social/@gromit/113345582873908273
> #regzbot title: tpm: popping sound in headphones connected via USB-C


  reply	other threads:[~2024-10-25 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  0:11 [REGRESSION][BISECTED] tpm: Popping noise in USB headphones since 1b6d7f9eb150 Christian Heusel
2024-10-25 14:47 ` Jarkko Sakkinen [this message]
2024-11-26 11:42   ` Christian Heusel
2024-11-30  2:44     ` Jarkko Sakkinen
2024-12-02 22:15       ` Stefan Berger
2024-12-03  6:38         ` Jarkko Sakkinen
2024-12-09 12:58         ` Jarkko Sakkinen

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=D54YWMOV7KOO.2X0N035UHEFBD@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=christian@heusel.eu \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --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