From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jeff Chua <jeff.chua.linux@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Linux ALSA Subsystem Development <alsa-devel@alsa-project.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: linux-6.4 alsa sound broken
Date: Mon, 1 May 2023 11:36:49 +0700 [thread overview]
Message-ID: <ZE9B4avbDtIXOu4O@debian.me> (raw)
In-Reply-To: <CAAJw_ZsbTVd3Es373x_wTNDF7RknGhCD0r+NKUSwAO7HpLAkYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Mon, May 01, 2023 at 11:59:12AM +0800, Jeff Chua wrote:
> Latest git pull from Linus's tree ... playing a simple sound file will
> resulted in a lot of echo.
>
> Running on Lenovo X1 with ..
> 00:1f.3 Audio device: Intel Corporation Alder Lake PCH-P High
> Definition Audio Controller (rev 01)
>
> I've bisected and reverted the following patch fixed the problem.
>
> commit 9f656705c5faa18afb26d922cfc64f9fd103c38d
Thanks for the regression report. However, where is your dmesg and/or ALSA log
when the regression occurs? What is the playback test file?
FYI, 9f656705c5faa1 ("ALSA: pcm: rewrite snd_pcm_playback_silence()") is
originated as [1/2] of patch series that pokes around the auto-silencer. The
other patch ([2/2]) got NAKed since autofilling buffer should have been done in
alsa-lib (still to be discussed) [1].
Anyway, I'm adding this to regzbot:
#regzbot ^introduced 9f656705c5faa1
#regzbot title Much echoing when playing sound files on Intel Alder Lake PCH-P Audio Controller
Thanks.
[1]: https://lore.kernel.org/all/bb342e84-b468-8adc-6688-88da2c857da1@perex.cz/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-01 4:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 3:59 linux-6.4 alsa sound broken Jeff Chua
2023-05-01 4:36 ` Bagas Sanjaya [this message]
2023-05-01 6:35 ` Takashi Iwai
2023-05-01 13:16 ` Jeff Chua
2023-05-01 14:52 ` Takashi Iwai
2023-05-01 15:03 ` Jeff Chua
2023-05-03 4:40 ` Bagas Sanjaya
2023-05-03 5:42 ` Jeff Chua
2023-05-01 13:08 ` Jeff Chua
2023-05-01 7:17 ` Oswald Buddenhagen
2023-05-01 15:05 ` Jeff Chua
2023-05-03 4:34 ` Bagas Sanjaya
2023-05-03 4:37 ` Bagas Sanjaya
2023-05-03 6:06 ` Takashi Iwai
2023-05-03 12:19 ` Jeff Chua
2023-05-03 13:44 ` Takashi Iwai
2023-05-03 15:06 ` Jeff Chua
2023-05-03 15:47 ` Takashi Iwai
2023-05-03 16:10 ` Takashi Iwai
2023-05-03 19:32 ` Jaroslav Kysela
2023-05-03 20:00 ` Oswald Buddenhagen
2023-05-03 20:17 ` Jaroslav Kysela
2023-05-04 6:15 ` Takashi Iwai
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=ZE9B4avbDtIXOu4O@debian.me \
--to=bagasdotme@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oswald.buddenhagen@gmx.de \
--cc=perex@perex.cz \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.de \
/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