From: Takashi Iwai <tiwai@suse.de>
To: Mike Karcic <mikekarcic@protonmail.com>
Cc: Sean Rhodes <sean@starlabs.systems>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.de" <tiwai@suse.de>
Subject: Re: [REGRESSION] Speaker pop/chirp on Meteor Lake ALC287 (17aa:231e) -- 6.12.73 to 6.12.85
Date: Thu, 28 May 2026 08:08:01 +0200 [thread overview]
Message-ID: <87eciwukvy.wl-tiwai@suse.de> (raw)
In-Reply-To: <wZmYozyav1sNx53nFr4ShKmcdLFVJp5bdUOJgUq1I57MX6kgyq7n8XvH-MWG9Fi4q2x4CQqjEQ3Q8ok5MClut8hNixnhVmVtXkhcOzH1sw8=@protonmail.com>
On Thu, 28 May 2026 01:18:31 +0200,
Mike Karcic wrote:
>
> I tested both setups on top of Debian's 6.12.90 source tree.
>
> 1. I applied the 46c862f5419e patch, but the chirp was still there on every audio transition.
> 2. I did a full revert of 630fbc6e870e, and the chirp is completely gone.
There is a follow-up fix in the upstream, try to apply the commit
46c862f5419e ("ALSA: hda/realtek - fixed speaker no sound update").
thanks,
Takashi
>
> My hardware is a Lenovo ThinkPad (Meteor Lake), ALC287, subsystem 17aa:231e.
>
>
>
> Sent with Proton Mail secure email.
>
> On Wednesday, May 27th, 2026 at 3:44 PM, Sean Rhodes <sean@starlabs.systems> wrote:
>
> > What about 630fbc6e870e? If so, 46c862f5419e looks relevant.
> >
> > On Wed, 27 May 2026 at 15:25, Mike Karcic <mikekarcic@protonmail.com> wrote:
> > >
> > > Speaker pop/chirp regression on a Lenovo ThinkPad with Meteor Lake and
> > > Realtek ALC287 (subsystem ID 17aa:231e). The chirp occurs on speaker
> > > power state transitions when audio starts or stops. It is not present
> > > on kernel 6.12.73 and is present on 6.12.85. A desktop with ALC897
> > > (subsystem ID 1f660202) on kernel 6.19.14 is unaffected, so this is
> > > codec/fixup-specific.
> > >
> > > Tested on the same LMDE (Debian 13) installation with multiple kernels
> > > selectable from GRUB. All userspace, firmware, and configuration are
> > > identical between tests. Cold boot between kernel switches is required,
> > > as warm reboot can carry codec register state forward. The kernel is
> > > not tainted on any tested version.
> > >
> > > Bisection results (Debian package versions):
> > > 6.12.48 -- no chirp
> > > 6.12.73 -- no chirp
> > > 6.12.85 -- chirp present
> > > 6.12.86 -- chirp present
> > > 6.12.90 -- chirp present
> > >
> > > Also broken: 6.19.14-101.fc44.x86_64 (Fedora/Aurora 44)
> > >
> > > The regression window (6.12.73 to 6.12.85) includes two commits
> > > targeting speaker pop on the Star Labs StarFighter (ALC233, SSID
> > > 7017:2014) that touch patch_realtek.c:
> > >
> > > 1cb3c20688fc ("ALSA: hda/realtek: Fix speaker pop on Star Labs StarFighter")
> > > Fixes commit ("ALSA: hda/realtek: Sequence GPIO2 on Star Labs StarFighter")
> > >
> > > These are quirk-gated to SSID 7017:2014 and should not run on
> > > 17aa:231e, but they are the most prominent sound changes in the
> > > regression window. The actual culprit may be a different commit
> > > in the 6.12.74-6.12.85 range. I was unable to narrow further as
> > > Debian does not publish intermediate point-release packages.
> > >
> > > I can build and test vanilla kernels for a proper bisection if
> > > guided, and I can test proposed fixes.
> > >
> > > Hardware:
> > > Lenovo ThinkPad, Meteor Lake
> > > Codec: Realtek ALC287
> > > Subsystem ID: 17aa:231e
> > > PCI: 0000:00:1f.3
> > > Machine driver: skl_hda_dsp_generic
> > > Codec fixup: "ALC287: picked fixup for PCI SSID 17aa:231e"
> > >
> > > Unaffected hardware (same 6.19.14 kernel, no chirp):
> > > Desktop, Realtek ALC897, Subsystem ID: 1f660202
> > >
> > > Controlled variables (identical across all tested 6.12 kernels):
> > > SOF firmware: 2.12.0.1 (firmware-sof-signed 2025.01-1)
> > > Topology: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
> > > Topology ABI: 3:29:1 (Kernel ABI: 3:23:1 on all tested)
> > > ALSA UCM: alsa-ucm-conf 1.2.14-1
> > > PipeWire: 1.4.2, WirePlumber: 0.5.8
> > > power_save: 10, hda_model: (null)
> > > Desktop: KDE Plasma 6 (Wayland)
> > >
> > > Eliminated causes:
> > > - Topology files in sof-ipc4-tplg/ and sof-ace-tplg/ are
> > > byte-identical (confirmed via binary diff). Path irrelevant.
> > > - SOF firmware version (same 2.12.0.1 on all tested kernels).
> > > - Topology ABI mismatch (3:29:1 vs 3:23:1 present on working
> > > kernel too).
> > > - power_save (10 on all kernels).
> > > - PipeWire/WirePlumber (identical versions on all kernels).
> > > - Desktop environment (KDE on all; a KDE install triggered a
> > > kernel update which was the actual cause of the regression
> > > appearing).
> > >
> > > dmesg (6.12.48, working):
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1:
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Topology file: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.12.0.1
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
> > > snd_hda_codec_alc269 ehdaudio0D0: ALC287: picked fixup for PCI SSID 17aa:231e
> > > snd_hda_codec_alc269 ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
> > >
> > > dmesg (6.19.14, affected):
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: hda codecs found, mask 5
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1:
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Topology file: intel/sof-ipc4-tplg/sof-hda-generic-2ch.tplg
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.14.1.1
> > > sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1
> > > snd_hda_codec_alc269 ehdaudio0D0: ALC287: picked fixup for PCI SSID 17aa:231e
> > > snd_hda_codec_alc269 ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
> > >
> > > Note: The kernel is not tainted on any tested version.
> >
next prev parent reply other threads:[~2026-05-28 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 14:25 [REGRESSION] Speaker pop/chirp on Meteor Lake ALC287 (17aa:231e) -- 6.12.73 to 6.12.85 Mike Karcic
2026-05-27 19:43 ` Sean Rhodes
2026-05-27 23:18 ` Mike Karcic
2026-05-28 6:08 ` Takashi Iwai [this message]
2026-05-28 13:38 ` Mike Karcic
2026-05-28 14:07 ` Takashi Iwai
2026-05-28 18:27 ` Mike Karcic
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 14:21 Mike Karcic
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=87eciwukvy.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mikekarcic@protonmail.com \
--cc=regressions@lists.linux.dev \
--cc=sean@starlabs.systems \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox