stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasa Ostrouska <casaxa@gmail.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
	"Jason Montleon" <jmontleo@redhat.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	lma@semihalf.com,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	stable@vger.kernel.org, "Takashi Iwai" <tiwai@suse.de>,
	"amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Mon, 30 Jan 2023 13:22:30 +0100	[thread overview]
Message-ID: <CALFERdw=GwNYafR3q=5=k=H_jrzTZMyDBQLouFGV0JGu8i9sCg@mail.gmail.com> (raw)
In-Reply-To: <288d7ff4-75aa-7ad1-c49c-579373cab3ed@intel.com>

On Mon, Jan 30, 2023 at 1:15 PM Cezary Rojewski
<cezary.rojewski@intel.com> wrote:
>
> On 2023-01-30 12:27 PM, Linux kernel regression tracking (Thorsten
> Leemhuis) wrote:
> > On 30.01.23 07:33, Jason Montleon wrote:
> >> I ran a bisect back further while patching in
> >> f2bd1c5ae2cb0cf9525c9bffc0038c12dd7e1338.
> >
> > Cezary Rojewski, you authored this change which appears to cause a
> > regression. Do you maybe have an idea what's wrong here?
>
>
> Hello,
>
> Sitting with Lukasz and debugging this.
>
> Please note that messages seen in the logs:
> [    8.538645] snd_soc_skl 0000:00:1f.3: ASoC: no sink widget found for
> AEC Capture
> [    8.538654] snd_soc_skl 0000:00:1f.3: ASoC: Failed to add route
> echo_ref_out cpr 7 -> direct -> AEC Capture
>
> and:
> [    8.614993] rt5663 i2c-10EC5663:00: sysclk < 384 x fs, disable i2s asrc
> [    8.617460] HDMI HDA Codec ehdaudio0D2: hdac_hdmi_present_sense:
> disconnect for pin:port 5:0
> [    8.617581] HDMI HDA Codec ehdaudio0D2: hdac_hdmi_present_sense:
> disconnect for pin:port 6:0
> [    8.617712] HDMI HDA Codec ehdaudio0D2: hdac_hdmi_present_sense:
> disconnect for pin:port 7:0
>
> seem to be just noise, these are present even in working configuration.
> Looks like topology and AudioDSP firmware loads fine. However, one or
> more of sound cards component is deferred when probing what results in
> no error in the logs but still lack of audio.
>
> We managed to reproduce the problem on Lukasz' Eve machine. If hardware
> cooperates, we should be able to narrow down the problem quickly from
> here. Our suspect - something (a patch or two) is missing in sound/soc
> in Fedora tree. Our CI which also covers upstream skylake-driver with
> HDAudio (e.g.: rt274/rt286/rt298) and I2S (same examples) configurations
> show no signs of regression. Thus, this is probably Chromebook-specific.
>
> My opinion stands at - none of the patches mentioned during the
> discussion is the real problem. All of these were in fact addressing
> real problems with audio stack stability/reloading.
>
> Will reply once more is known.
>
>
> Kind regards,
> Czarek

Dear Czarek, many thanks for the answer and taking care of it. If
needed something from my side please jest let me know
and I will try to do it.

Rgds
Sasa

  reply	other threads:[~2023-01-30 12:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 17:09 Google Pixelbook EVE, no sound in kernel 6.1.x Jason Montleon
2023-01-28 17:52 ` Greg KH
2023-01-29  0:23   ` Jason Montleon
2023-01-30  6:33     ` Jason Montleon
2023-01-30 11:27       ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-30 12:15         ` Cezary Rojewski
2023-01-30 12:22           ` Sasa Ostrouska [this message]
2023-01-31 12:36             ` Cezary Rojewski
2023-01-31 14:58               ` Sasa Ostrouska
2023-01-31 15:48                 ` Cezary Rojewski
2023-01-31 16:02                   ` Sasa Ostrouska
2023-01-31 15:16               ` Jason Montleon
2023-01-31 15:46                 ` Cezary Rojewski
2023-02-01 11:05                 ` Amadeusz Sławiński
2023-02-01 14:33                   ` Jason Montleon
2023-02-04 15:16                     ` Jason Montleon
2023-02-06  9:03                       ` Amadeusz Sławiński
2023-02-06 13:51                         ` Jason Montleon
2023-02-06 19:57                           ` Jason Montleon
2023-02-06 21:15                             ` Sasa Ostrouska
2023-02-09 16:13                             ` Jason Montleon
2023-02-09 19:22                               ` Jason Montleon
2023-02-10 13:09                               ` Cezary Rojewski
2023-02-10 14:56                                 ` Jason Montleon
2023-02-10 17:15                                   ` Sasa Ostrouska
2023-01-30 11:23 ` Linux kernel regression tracking (#update)
  -- strict thread matches above, loose matches on Subject: below --
2023-01-23 20:44 Sasa Ostrouska
2023-01-24  5:09 ` Greg KH
2023-01-24 10:18   ` Lukasz Majczak
2023-01-24 11:34     ` Sasa Ostrouska
2023-01-24 12:11       ` Lukasz Majczak
2023-01-24 14:31         ` Sasa Ostrouska
2023-01-24 21:38           ` Sasa Ostrouska
2023-01-25 15:48             ` Lukasz Majczak
2023-01-24 11:30   ` Sasa Ostrouska
2023-01-26 12:59 ` Linux kernel regression tracking (#adding)
2023-01-27 10:06   ` Sasa Ostrouska
2023-02-09 14:11     ` Sasa Ostrouska
2023-02-24  1:10       ` Sasa Ostrouska
2023-02-24 20:43         ` Sasa Ostrouska

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='CALFERdw=GwNYafR3q=5=k=H_jrzTZMyDBQLouFGV0JGu8i9sCg@mail.gmail.com' \
    --to=casaxa@gmail.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=cezary.rojewski@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jmontleo@redhat.com \
    --cc=lma@semihalf.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).