From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.223.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 512EC3FCB06 for ; Tue, 2 Jun 2026 17:45:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=195.135.223.130 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780422322; cv=none; b=r0xtuDvdIzB3YVbIIgl8XhvbILKIrpNvvgiCA95bzdGgLMalnTLTxYa+YFG81TiMIXF8N/A8wiI+LLJxWVu6ag8y/F57oOTs4652dWfyH+j2J4R6qI4RiK2H2PPlWsT9Sex4Qu2wGJlYmPRAZK5+HWlcDP3hQe3GxYTfsaI8mgQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780422322; c=relaxed/simple; bh=xts6qQ534694Mm/S4A1BHBCd21Jsj+ab9M4kr0sTKIY=; h=Date:Message-ID:From:To:Cc:Subject:In-Reply-To:References: MIME-Version:Content-Type; b=HgFiJTqHGoVqW2CswsNaNJcJ5LOlE0lsTOLW75XYREXVteGAewbKV71ONH3lgyDeyy51iDWkFhtgWFw17+LFim7ag8HmEl8j9F3u4vpsSaE6TygplDTcvrqBfpcxPCHknokOvrNvamSLHmItedsCdp217EVgQxtcc9WDGSudRGw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=suse.de; spf=pass smtp.mailfrom=suse.de; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b=EEyDlwlh; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b=qXhKCi2j; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b=Ze3PPXkR; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b=RUAAcjtK; arc=none smtp.client-ip=195.135.223.130 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=suse.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=suse.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b="EEyDlwlh"; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b="qXhKCi2j"; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b="Ze3PPXkR"; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b="RUAAcjtK" Received: from imap1.dmz-prg2.suse.org (unknown [10.150.64.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id EDA976C009; Tue, 2 Jun 2026 17:45:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1780422313; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lu4UfJ/uxJdMYzOhZ1NYp7qD1lKEW76JZx60l7/sK4s=; b=EEyDlwlhGRvG66ZJ+71nKOi4fgg53huF/vLT6gNAAJ6/urwXTSqlwy660R4bcirBOMIprx lt6Ksf9el5Khb4dr2lQA1/it5z/tpShIbiyjZO8CuXPe1MhJuP1eQRpM2X3M+pl7oMxuv2 ogtVGdh2xLJYkTq20JjXONNCFUPbPhM= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1780422313; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lu4UfJ/uxJdMYzOhZ1NYp7qD1lKEW76JZx60l7/sK4s=; b=qXhKCi2jM6o++1h7BocoQCByvoUy9F1tFVCrRhXE7nI89lVLSTm0Vyorx4cqUvnAQ2IvXs TZKbqGSTuh25IABQ== Authentication-Results: smtp-out1.suse.de; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1780422312; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lu4UfJ/uxJdMYzOhZ1NYp7qD1lKEW76JZx60l7/sK4s=; b=Ze3PPXkR6RVjekLzy+QxL15Rumtx/D5omtpOR/2evHMkXFf2EAOTZR9A/qw1MVlt1TG03A zQIxdwT0/f3/itVEeoXTT6c2dIN3ButzuktSZfKxEQFHE9b1e8Av9BkhzFBf/la4aFiTZc +ISCiIrhGA/dTrnigCC6D0jjRiUKeD0= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1780422312; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lu4UfJ/uxJdMYzOhZ1NYp7qD1lKEW76JZx60l7/sK4s=; b=RUAAcjtKnb3rnFMOUQSIkywATnSX0wnFlPLdmVVps312lJuVhQaQStWlKKctPoxWQarMrw slI6CphqsSdb2mAg== Received: from imap1.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap1.dmz-prg2.suse.org (Postfix) with ESMTPS id B306A779A7; Tue, 2 Jun 2026 17:45:12 +0000 (UTC) Received: from dovecot-director2.suse.de ([2a07:de40:b281:106:10:150:64:167]) by imap1.dmz-prg2.suse.org with ESMTPSA id 2hRlKqgWH2qiMgAAD6G6ig (envelope-from ); Tue, 02 Jun 2026 17:45:12 +0000 Date: Tue, 02 Jun 2026 19:45:12 +0200 Message-ID: <87wlwgygyf.wl-tiwai@suse.de> From: Takashi Iwai To: Kailang Cc: Takashi Iwai , Mike Karcic , Sean Rhodes , "stable@vger.kernel.org" , "regressions@lists.linux.dev" , "linux-sound@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [REGRESSION] Speaker pop/chirp on Meteor Lake ALC287 (17aa:231e) -- 6.12.73 to 6.12.85 In-Reply-To: <833d600fdebd4aaeab6706185ce854e6@realtek.com> References: <87eciwukvy.wl-tiwai@suse.de> <87mrxjsk52.wl-tiwai@suse.de> <87cxyfs2vm.wl-tiwai@suse.de> <833d600fdebd4aaeab6706185ce854e6@realtek.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/30.2 Mule/6.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Spam-Flag: NO X-Spam-Score: -3.30 X-Spamd-Result: default: False [-3.30 / 50.00]; BAYES_HAM(-3.00)[100.00%]; NEURAL_HAM_LONG(-1.00)[-1.000]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_SHORT(-0.20)[-1.000]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; FUZZY_RATELIMITED(0.00)[rspamd.com]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCPT_COUNT_SEVEN(0.00)[8]; FREEMAIL_ENVRCPT(0.00)[protonmail.com]; DKIM_SIGNED(0.00)[suse.de:s=susede2_rsa,suse.de:s=susede2_ed25519]; FROM_HAS_DN(0.00)[]; FREEMAIL_CC(0.00)[suse.de,protonmail.com,starlabs.systems,vger.kernel.org,lists.linux.dev]; TO_DN_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DBL_BLOCKED_OPENRESOLVER(0.00)[suse.de:email,suse.de:mid,protonmail.com:email,linux.dev:email,imap1.dmz-prg2.suse.org:helo] X-Spam-Level: On Tue, 02 Jun 2026 08:14:14 +0200, Kailang wrote: > > > There were the same SSID for two different symptoms. > But this project was from 2025. This machine maybe didn't in our site. Aha, that can explain the difference of the behavior, then. Do both of them have the same codec ID and SSID, too? Takashi > > -----Original Message----- > From: Takashi Iwai > Sent: Friday, May 29, 2026 4:20 AM > To: Mike Karcic > Cc: Kailang ; Takashi Iwai ; Sean Rhodes ; stable@vger.kernel.org; regressions@lists.linux.dev; linux-sound@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [REGRESSION] Speaker pop/chirp on Meteor Lake ALC287 (17aa:231e) -- 6.12.73 to 6.12.85 > > > External mail : This email originated from outside the organization. Do not reply, click links, or open attachments unless you recognize the sender and know the content is safe. > > > > On Thu, 28 May 2026 20:27:30 +0200, > Mike Karcic wrote: > > > > Yes, I can confirm the patched kernel is running, and commenting out that line fixes the problem completely. > > > > Below is output with the added debug lines as requested: > > > > $ uname -r > > 6.12.90-debug-no-discoefs > > > > $ sudo dmesg | grep -i "alc287_alc1318" > > [ 453.823528] snd_hda_codec_realtek ehdaudio0D0: > > alc287_alc1318_playback_pcm_hook called action=0 [ 453.871577] > > snd_hda_codec_realtek ehdaudio0D0: alc287_alc1318_playback_pcm_hook > > called action=1 [ 459.605379] snd_hda_codec_realtek ehdaudio0D0: > > alc287_alc1318_playback_pcm_hook called action=2 [ 459.605497] > > snd_hda_codec_realtek ehdaudio0D0: alc287_alc1318_playback_pcm_hook > > called action=3 > > > > $ grep -n -A5 -B2 "alc_process_coef_fw.*dis_coefs" sound/pci/hda/patch_realtek.c > > 7918- return; > > 7919- alc_update_coef_idx(codec, 0x10, 1<<11, 1<<11); > > 7920: /* alc_process_coef_fw(codec, dis_coefs); */ /* commented out for testing */ > > 7921- alc_process_coef_fw(codec, coefs); > > 7922- spec->power_hook = alc287_s4_power_gpio3_default; > > 7923- spec->gen.pcm_playback_hook = alc287_alc1318_playback_pcm_hook; > > 7924-} > > Hm, then the previous fix doesn't seem working, obviously. > Kailang, could you check this in your side? > > Maybe we should apply the AMP-silence-detection disablement conditionally to certain models? > > > thanks, > > Takashi > > > > > > > > > Sent with Proton Mail secure email. > > > > On Thursday, May 28th, 2026 at 10:07 AM, Takashi Iwai wrote: > > > > > On Thu, 28 May 2026 15:38:54 +0200, > > > Mike Karcic wrote: > > > > > > > > I did test 46c862f5419e on 6.12.90. Chirp still present. > > > > > > > > I'm also on a ThinkPad X1 Carbon Gen 12 with ALC287 (17aa:231e), > > > > same as the original reporter. The fix resolved it for them but > > > > not for me. > > > > > > > > Only a full revert of 630fbc6e870e resolves the issue. > > > > > > > > Verification on the running kernel: > > > > > > > > $ grep -c "dis_coefs" sound/pci/hda/patch_realtek.c > > > > 2 > > > > > > > > $ grep -c "en_coefs" sound/pci/hda/patch_realtek.c > > > > 0 > > > > > > > > $ sed -n '/alc287_alc1318_playback_pcm_hook/,/^}/p' sound/pci/hda/patch_realtek.c > > > > static void alc287_alc1318_playback_pcm_hook(struct hda_pcm_stream *hinfo, > > > > struct hda_codec *codec, > > > > struct snd_pcm_substream *substream, > > > > int action) > > > > { > > > > switch (action) { > > > > case HDA_GEN_PCM_ACT_OPEN: > > > > alc_write_coefex_idx(codec, 0x5a, 0x00, 0x954f); > > > > break; > > > > case HDA_GEN_PCM_ACT_CLOSE: > > > > alc_write_coefex_idx(codec, 0x5a, 0x00, 0x554f); > > > > break; > > > > } > > > > } > > > > > > > > Happy to test further patches. > > > > > > Just to be sure, could you verify that you've tested really the > > > patched kernel, e.g. by adding a debug print, etc? > > > If yes and the problem is seen even with the patch, try to comment out > > > alc_process_coef_fw(codec, dis_coefs); and confirm that this fixes > > > the problem. > > > > > > > > > Takashi > > >