All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Jaroslav Kysela <perex@perex.cz>,
	linux-sound@vger.kernel.org,
	Eric Degenetais <eric.4.debian@grabatoulnz.fr>,
	linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>,
	regressions@lists.linux.dev, Sasha Levin <sashal@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [regression] Regular "cracks" in HDMI sound during playback since backport to 6.1.y for 92afcc310038 ("ALSA: hda: Conditionally use snooping for AMD HDMI")
Date: Wed, 02 Oct 2024 17:59:27 +0200	[thread overview]
Message-ID: <87a5fmlcm8.wl-tiwai@suse.de> (raw)
In-Reply-To: <87ed51ig23.wl-tiwai@suse.de>

On Mon, 30 Sep 2024 12:36:36 +0200,
Takashi Iwai wrote:
> 
> On Sat, 28 Sep 2024 15:19:49 +0200,
> Salvatore Bonaccorso wrote:
> > 
> > Hi
> > 
> > In downstream Debian we got a report from  Eric Degenetais, in
> > https://bugs.debian.org/1081833 that after the update to the 6.1.106
> > based version, there were regular cracks in HDMI sound during
> > playback.
> > 
> > Eric was able to bisec the issue down to
> > 92afcc310038ebe5d66c689bb0bf418f5451201c in the v6.1.y series which
> > got applied in 6.1.104.
> > 
> > Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081833#47
> > 
> > #regzbot introduced: 92afcc310038ebe5d66c689bb0bf418f5451201c
> > #regzbot link: https://bugs.debian.org/1081833
> > 
> > It should be noted that Eric as well tried more recent stable series
> > as well, in particular did test as well 6.10.6 based version back on
> > 20th september, and the issue was reproducible there as well.
> > 
> > Is there anything else we can try to provide?
> 
> Could you check 6.12-rc1 kernel whether the problem still appears?
> If yes, check with snd_hda_intel.snoop=0 boot option. 
> 
> I guess we should revert the patch in anyway; for 6.12, it's no longer
> correct to check with get_dma_ops(), and if this causes a problem on
> the older releases, the assumption isn't correct, either.

I decided to revert the commit.  Will submit the patch now.


Takashi

      reply	other threads:[~2024-10-02 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28 13:19 [regression] Regular "cracks" in HDMI sound during playback since backport to 6.1.y for 92afcc310038 ("ALSA: hda: Conditionally use snooping for AMD HDMI") Salvatore Bonaccorso
2024-09-29  6:41 ` Linux regression tracking (Thorsten Leemhuis)
2024-09-30 10:36 ` Takashi Iwai
2024-10-02 15:59   ` Takashi Iwai [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=87a5fmlcm8.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=carnil@debian.org \
    --cc=eric.4.debian@grabatoulnz.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@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 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.