linux-kernel - 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")

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3cc1eca2-0278-4b90-9cc6-e5c75ed4327d@leemhuis.info>
Date: Sun, 29 Sep 2024 08:41:26 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@...mhuis.info>
To: Salvatore Bonaccorso <carnil@...ian.org>, Takashi Iwai <tiwai@...e.de>,
 Jaroslav Kysela <perex@...ex.cz>, linux-sound@...r.kernel.org
Cc: Eric Degenetais <eric.4.debian@...batoulnz.fr>,
 linux-kernel@...r.kernel.org, stable <stable@...r.kernel.org>,
 regressions@...ts.linux.dev, Sasha Levin <sashal@...nel.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.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")

Hi! On 28.09.24 15:19, Salvatore Bonaccorso wrote:
> 
> 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?

Just "the usual", which is not widely known, so allow me to explain.

Please in situations like this *always* try to test a recent mainline
kernel. Given the timing, it's best to test 6.12-rc1 once it out later
today.

That's because it's unclear if this is something the regular maintainers
or the stable team/the one that asked for the backport has to handle.
Some developers do not care, but often it's required, as otherwise
nobody will take a close look -- especially when it comes to longterm
kernels. That's because participation in stable/longterm maintenance is
entirely optional for mainline developers (e.g. the author of the
culprit). This page
https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
has a few points that explain the problem in more detail.

HTH, Ciao, Thorsten