From: Takashi Iwai <tiwai@suse.de>
To: Evgeny Kapun <abacabadabacaba@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Linux Sound Mailing List <linux-sound@vger.kernel.org>,
Kailang Yang <kailang@realtek.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions Mailing List <regressions@lists.linux.dev>,
Linux Stable Mailing List <stable@vger.kernel.org>
Subject: Re: [REGRESSION] Distorted sound on Acer Aspire A115-31 laptop
Date: Sun, 22 Dec 2024 09:27:17 +0100 [thread overview]
Message-ID: <87ldw89l7e.wl-tiwai@suse.de> (raw)
In-Reply-To: <57883f2e-49cd-4aa4-9879-7dcdf7fec6df@gmail.com>
On Sun, 22 Dec 2024 08:37:27 +0100,
Evgeny Kapun wrote:
>
> On 12/19/24 18:38, Takashi Iwai wrote:
> > Could you give alsa-info.sh output with broken and working (reverted)
> > states? Run the script with --no-upload option and attach the
> > outputs.
>
> Hi,
>
> I already posted alsa-info output in a previous message:
>
> Broken, kernel version 6.12.5:
> https://lore.kernel.org/linux-sound/0625722b-5404-406a-b571-ff79693fe980@gmail.com/3-alsa-info-6.12.5.txt
> Working, kernel version 6.7.11:
> https://lore.kernel.org/linux-sound/0625722b-5404-406a-b571-ff79693fe980@gmail.com/2-alsa-info-6.7.11.txt
>
> Or do you need alsa-info with a new kernel, but with the offending
> commit reverted?
Yes, that'll be the best for eliminating other possible artifacts.
thanks,
Takashi
next prev parent reply other threads:[~2024-12-22 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 13:06 [REGRESSION] Distorted sound on Acer Aspire A115-31 laptop Evgeny Kapun
2024-12-16 2:07 ` Kailang
2024-12-18 20:33 ` Evgeny Kapun
2024-12-19 2:05 ` Kailang
2024-12-22 7:26 ` Evgeny Kapun
2024-12-19 3:19 ` Kailang
2024-12-16 9:35 ` Kailang
2024-12-19 16:38 ` Takashi Iwai
2024-12-22 7:37 ` Evgeny Kapun
2024-12-22 8:27 ` Takashi Iwai [this message]
2024-12-23 13:29 ` Evgeny Kapun
2024-12-24 2:54 ` Kailang
2025-01-11 15:00 ` Evgeny Kapun
2025-01-16 14:26 ` Takashi Iwai
2025-01-17 7:48 ` Kailang
2025-01-17 10:06 ` 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=87ldw89l7e.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=abacabadabacaba@gmail.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--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