All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Dean Matthew Menezes <dean.menezes@utexas.edu>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Linux Sound System <linux-sound@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: No sound on speakers X1 Carbon Gen 12
Date: Wed, 16 Oct 2024 11:21:24 +0200	[thread overview]
Message-ID: <87bjzktncb.wl-tiwai@suse.de> (raw)
In-Reply-To: <433b8579-e181-40e6-9eac-815d73993b23@leemhuis.info>

On Wed, 16 Oct 2024 07:56:09 +0200,
Linux regression tracking (Thorsten Leemhuis) wrote:
> 
> On 16.10.24 07:42, Greg KH wrote:
> > On Tue, Oct 15, 2024 at 07:47:22PM -0500, Dean Matthew Menezes wrote:
> >> I am not getting sound on the speakers on my Thinkpad X1 Carbon Gen 12
> >> with kernel 6.11.2  The sound is working in kernel 6.8
> > 
> > Can you use 'git bisect' to track down the offending change?
> 
> Yeah, that would help a lot.
> 
> But FWIW, I CCed the audio maintainers and the sound mailing list, with
> a bit of luck they might have an idea.
> 
> You might also want to publish your dmesg files from the latest working
> and the first broken kernel, that gives people a chance to spot obvious
> problems. Ohh, and runing alsa-info.sh and publishing the output could
> help, too.

Yes, alsa-info.sh outputs are really needed for debugging, especially
because Lenovo has (literally) hundreds of different models.

Please run the script with --no-upload option and attach the outputs
from both working and non-working cases.


thanks,

Takashi

  reply	other threads:[~2024-10-16  9:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  0:47 No sound on speakers X1 Carbon Gen 12 Dean Matthew Menezes
2024-10-16  5:42 ` Greg KH
2024-10-16  5:56   ` Linux regression tracking (Thorsten Leemhuis)
2024-10-16  9:21     ` Takashi Iwai [this message]
2024-10-16 21:18       ` Dean Matthew Menezes
2024-10-17  8:34         ` Takashi Iwai
2024-10-18 23:14           ` Dean Matthew Menezes
2024-10-19  8:12             ` Takashi Iwai
2024-10-19 23:11               ` Dean Matthew Menezes
2024-10-20  7:19                 ` Takashi Iwai
2024-10-20 14:54                   ` Dean Matthew Menezes
     [not found]                   ` <CAEkK70TWL_me58QZXeJSq+=Ry3jA+CgZJttsgAPz1wP7ywqj6A@mail.gmail.com>
2024-10-20 15:29                     ` Takashi Iwai
2024-10-20 15:33                       ` Takashi Iwai
2024-10-21  1:30                         ` Dean Matthew Menezes
2024-10-21  6:59                           ` Takashi Iwai
2024-10-21  7:56                             ` Kailang
2024-10-21  8:20                               ` Takashi Iwai
2024-10-21  8:19                             ` Kailang
2024-10-21  8:24                               ` Takashi Iwai
2024-10-21  8:38                                 ` Kailang
2024-10-21  8:56                                   ` Takashi Iwai
2024-10-21  8:59                                     ` Kailang
2024-10-25  1:22                                       ` Dean Matthew Menezes
2024-10-25  7:17                                         ` Takashi Iwai
2024-10-25  7:32                                           ` Kailang
2024-10-26  0:22                                           ` Dean Matthew Menezes
2024-11-08  2:58                                             ` Kailang
2024-11-11  6:57                                             ` Kailang
2024-11-12  3:17                                               ` Dean Matthew Menezes
2024-11-13  6:22                                                 ` Kailang
2024-11-13  6:43                                                   ` Takashi Iwai
2024-10-21  9:31                                     ` Kailang

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=87bjzktncb.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=dean.menezes@utexas.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.