stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Montleon <jmontleo@redhat.com>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Sasa Ostrouska <casaxa@gmail.com>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	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>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Mon, 6 Feb 2023 08:51:42 -0500	[thread overview]
Message-ID: <CAJD_bPKO+zCeRojkOr2uY+nXvhsjO3Um86Lh53ZCuCUm3Ci3PA@mail.gmail.com> (raw)
In-Reply-To: <a423c627-d303-3b50-5f11-78c06ed3b985@linux.intel.com>

On Mon, Feb 6, 2023 at 4:04 AM Amadeusz Sławiński
<amadeuszx.slawinski@linux.intel.com> wrote:
>
> On 2/4/2023 4:16 PM, Jason Montleon wrote:
> > I have built kernels for 6.0.19 (I don't think anyone confirmed
> > whether or not it worked), plus every 6.1 tag from 6.1-rc1 up to
> > 6.1.7. 6.0.19 worked. No 6.1 kernels worked. For rc1 to rc5 I built
> > with and without the legacy dai renaming patch added in rc6 that I
> > believe would be necessary, but it made no difference either way.
>
> Hi,
>
> thank you for trying to narrow it down, if I understand correctly -rc1
> doesn't work, which means that problem was introduced somewhere between
> 6.0 and 6.1-rc1 (just for the sake of being sure, can you test 6.0
> instead of 6.0.19?) There is one commit which I'm bit suspicious about:
> ef6f5494faf6a37c74990689a3bb3cee76d2544c it changes how HDMI are
> assigned and as a machine board present on EVE makes use of HDMI, it may
> potentially cause some problems. Can you try reverting it?
> (If reverting on top of v6.1.8 you need to revert both
> f9aafff5448b1d8d457052271cd9a11b24e4d0bd and
> ef6f5494faf6a37c74990689a3bb3cee76d2544c which has minor conflict,
> easily resolved with just adding both lines.
>

Yes, happy to give that a shot and will report back.

> I also still wonder, why problem reproduces only on some
> distributions... any chance you can try and boot with
> pipewire/pulseaudio disabled and see if it still happens, iirc those
> tools try to check all FEs and this may be breaking something during
> enumeration.

I can definitely try disabling pulseaudio and switching to pipewire
and seeing if anything changes as well.

FWIW, I installed Arch on a thumb drive this weekend and was able to
reproduce the issue and work around it by reverting the commit from my
first bisect. So, for me it behaves just like Fedora. The instructions
for Arch for building a custom kernel are great except they generalize
the bootloader instructions, so you need to know what to do at the end
to add the grub boot entries, if using grub for example, and I suspect
that may be where the confusion came from, though I don't know. I'm
trying to get one of the two to reproduce my results to confirm and at
least get them a workaround.

I have slackware on another thumb drive already, but I have yet to
even get it updated to 6.1.8.

If any of them behave differently I was hoping to tease out whether
it's firmware, kernel config, or something else, but so far the first
has been more of the same.

> Thanks,
> Amadeusz
>
> >
> > On Wed, Feb 1, 2023 at 9:33 AM Jason Montleon <jmontleo@redhat.com> wrote:
> >>
> >> On Wed, Feb 1, 2023 at 6:05 AM Amadeusz Sławiński
> >> <amadeuszx.slawinski@linux.intel.com> wrote:
> >>>
> >>> On 1/31/2023 4:16 PM, Jason Montleon wrote:
> >>>> On Tue, Jan 31, 2023 at 7:37 AM Cezary Rojewski
> >>>> <cezary.rojewski@intel.com> wrote:
> >>>>>
> >>>>> On 2023-01-30 1:22 PM, Sasa Ostrouska wrote:
> >>>>>
> >>>>>> 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.
> >>>>>
> >>>>>
> >>>>> Hello Sasa,
> >>>>>
> >>>>> Could you provide us with the topology and firmware binary present on
> >>>>> your machine?
> >>>>>
> >>>>> Audio topology is located at /lib/firmware and named:
> >>>>>
> >>>>> 9d71-GOOGLE-EVEMAX-0-tplg.bin
> >>>>> -or-
> >>>>> dfw_sst.bin
> >>>>>
> >>>>> Firmware on the other hand is found in /lib/firmware/intel/.
> >>>>> 'dsp_fw_kbl.bin' will lie there, it shall be a symlink pointing to an
> >>>>> actual AudioDSP firmware binary.
> >>>>>
> >>>> Maybe this is the problem.
> >>>>
> >>>> I think most of us are pulling the topology and firmware from the
> >>>> chromeos recovery images for lack of any other known source, and it
> >>>> looks a little different than this. Those can be downloaded like so:
> >>>> https://gist.github.com/jmontleon/8899cb83138f2653f520fbbcc5b830a0
> >>>>
> >>>> After placing the topology file you'll see these errors and audio will
> >>>> not work until they're also copied in place.
> >>>> snd_soc_skl 0000:00:1f.3: Direct firmware load for
> >>>> dsp_lib_dsm_core_spt_release.bin failed with error -2
> >>>> snd_soc_skl 0000:00:1f.3: Direct firmware load for
> >>>> intel/dsp_fw_C75061F3-F2B2-4DCC-8F9F-82ABB4131E66.bin failed with
> >>>> error -2
> >>>>
> >>>> Once those were in place, up to 6.0.18 audio worked.
> >>>>
> >>>> Is there a better source for the topology file?
> >>>>
> >>>>> The reasoning for these asks is fact that problem stopped reproducing on
> >>>>> our end once we started playing with kernel versions (moved away from
> >>>>> status quo with Fedora). Neither on Lukasz EVE nor on my SKL RVP.
> >>>>> However, we might be using newer configuration files when compared to
> >>>>> equivalent of yours.
> >>>>>
> >>>>> Recent v6.2-rc5 broonie/sound/for-next - no repro
> >>>>> Our internal tree based on Mark's for-next - no repro
> >>>>> 6.1.7 stable [1] - no repro
> >>>>>
> >>>>> Of course we will continue with our attempts. Will notify about the
> >>>>> progress.
> >>>>>
> >>>>>
> >>>>> [1]:
> >>>>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.7&id=21e996306a6afaae88295858de0ffb8955173a15
> >>>>>
> >>>>>
> >>>>> Kind regards,
> >>>>> Czarek
> >>>>>
> >>>>
> >>>>
> >>>
> >>> Hi Jason,
> >>>
> >>> as I understand you've tried to do bisect, can you instead try building
> >>> kernels checking out following tags:
> >>> v6.1      v6.1.1    v6.1.2    v6.1.3    v6.1.4    v6.1.5    v6.1.6
> >>> v6.1.7    v6.1.8
> >>> and report when it stops working, so it narrows scope of what we look
> >>> at? I assume that kernel builds are done using upstream stable kernel
> >>> (from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/).
> >>>
> >>> Thanks,
> >>> Amadeusz
> >>>
> >> Hi Amadeusz,
> >> Yes, I did the bisects using
> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
> >>
> >> The only thing I did to these was add
> >> 392cc13c5ec72ccd6bbfb1bc2339502cc59dd285, otherwise audio breaks with
> >> the dai not registered error message in dmesg from the rt5514 bug from
> >> 6.0 and up. It wasn't added to 6.1 until rc6, I believe. If there's a
> >> better way to work around the multiple bugs I can try again, otherwise
> >> I will start working on builds from tags and see if I learn anything.
> >>
> >> FWIW, I've seen two people complain that Arch isn't working either
> >> since it moved to 6.1. For the one who was trying, patching out the
> >> commit I came to with the first bisect did not regain them sound like
> >> it did for me. And yet Sasa reports Slackware is mostly working for
> >> him with 6.1.8 on Slackware. I don't know what to make of it, but
> >> thought I'd share in case it helps point someone else to something.
> >> https://github.com/jmontleon/pixelbook-fedora/issues/51#issuecomment-1410222840
> >> https://github.com/jmontleon/pixelbook-fedora/issues/51#issuecomment-1410673371
> >> https://github.com/jmontleon/pixelbook-fedora/issues/53#issuecomment-1408699252
> >>
> >> Probably less relevant since they aren't from upstream and I know they
> >> don't mean as much, but I have tried 6.1.5-6.1.8 Fedora packages for
> >> certain, and went back trying several others from koji back into rc
> >> builds, although using prebuilt kernels, anything before 6.1-rc6 won't
> >> work, as mentioned above. Nothing worked. But as I said I'll build
> >> from tags and see if I can learn anything.
> >>
> >> Thank you,
> >> Jason Montleon
> >>
> >> --
> >> Jason Montleon        | email: jmontleo@redhat.com
> >> Red Hat, Inc.         | gpg key: 0x069E3022
> >> Cell: 508-496-0663    | irc: jmontleo / jmontleon
> >
> >
> >
>


--
Jason Montleon        | email: jmontleo@redhat.com
Red Hat, Inc.         | gpg key: 0x069E3022
Cell: 508-496-0663    | irc: jmontleo / jmontleon


  reply	other threads:[~2023-02-06 13:55 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
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 [this message]
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=CAJD_bPKO+zCeRojkOr2uY+nXvhsjO3Um86Lh53ZCuCUm3Ci3PA@mail.gmail.com \
    --to=jmontleo@redhat.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=casaxa@gmail.com \
    --cc=cezary.rojewski@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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).