From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5444DC61DA4 for ; Sat, 4 Feb 2023 15:17:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233443AbjBDPRS (ORCPT ); Sat, 4 Feb 2023 10:17:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56984 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233379AbjBDPRO (ORCPT ); Sat, 4 Feb 2023 10:17:14 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 091A0241FE for ; Sat, 4 Feb 2023 07:16:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675523789; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ms8eBc48Rg3NStcu4ZOpEF4W9fY8TJN/5yrtf8umZlg=; b=T/fEdvbMNEL9HkjFImAPSdY0eNzU7Y/i5obflIcCc+zMbXdbRuUm8bCGeW1IPNCbgiIIax MLt9TkMX1ChHtujPBZIwHKpk/lH6Jld+dzNxLvuCdBqdSsQxYilq0Z25cs9kv2YniG8qKE Yc1SQ96/5w6uGVvUfHqPLGmz0uNNgKc= Received: from mail-yb1-f200.google.com (mail-yb1-f200.google.com [209.85.219.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-515-AvnXuxvIP-66x3zW8HvnWA-1; Sat, 04 Feb 2023 10:16:28 -0500 X-MC-Unique: AvnXuxvIP-66x3zW8HvnWA-1 Received: by mail-yb1-f200.google.com with SMTP id k204-20020a256fd5000000b007b8b040bc50so7570628ybc.1 for ; Sat, 04 Feb 2023 07:16:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Ms8eBc48Rg3NStcu4ZOpEF4W9fY8TJN/5yrtf8umZlg=; b=ZTAO/JTh4psqFuFDQ1x/fLULzqcjjFXaW7TmsY3C7KU3BoFI5185w8oNFSRYrCvbiB XCS7MP+h7evD4cIG4ok9bQG3ARMCTSt2l9eTtm0LvsZokOHQafy5jOvqSFd439ziaq9K 485TSt0G772KBdyQ/QpZiqnlWNUWCZGDcx5OK+sAHTB/gY7YyeM7sGiFoc4REFRXqg6f iYUh5YP37II9PCJMVEFVn9yGcs72GPuk6FVuBl2JdD3n5pITRKAONUPSRC7UGipKwAtx qXWMO8p/sp5QlcqgltI7Uf8IaClW8Zwumbxewd6tk5QZfZ+9BW6lNVMjRZziNgCctZz9 fdDA== X-Gm-Message-State: AO0yUKUbS8u/Kgv3XJ5wNjcD8CFJYYtbBC6xR+lksjccW+tBnkNRcpBJ C7lMPIstmLnO0qIy7FmYa+w/vgbWI8KHNseNJM42r0fqNG8H6cSRs3E88hDHJuIxxhRGIJSc6PC My09/9Q7WHLBk7XHAPpmXT5DSo19H9Ev9 X-Received: by 2002:a81:5455:0:b0:507:4ba0:f1bc with SMTP id i82-20020a815455000000b005074ba0f1bcmr1615508ywb.293.1675523786648; Sat, 04 Feb 2023 07:16:26 -0800 (PST) X-Google-Smtp-Source: AK7set/z4nqUGxrT5mGhN+3vcEvHvdHOxeequ+3Lt5QZZsSTVuGGwHDqHsvF6Uvpd6jwn8uEyBdidRMVyaKUDukaOZ4= X-Received: by 2002:a81:5455:0:b0:507:4ba0:f1bc with SMTP id i82-20020a815455000000b005074ba0f1bcmr1615499ywb.293.1675523786206; Sat, 04 Feb 2023 07:16:26 -0800 (PST) MIME-Version: 1.0 References: <02834fa9-4fb0-08fb-4b5f-e9646c1501d6@leemhuis.info> <288d7ff4-75aa-7ad1-c49c-579373cab3ed@intel.com> <04a9f939-8a98-9a46-e165-8e9fb8801a83@intel.com> <6262bd72-cc2b-9d2a-e8f0-55c2b2bb7861@linux.intel.com> In-Reply-To: From: Jason Montleon Date: Sat, 4 Feb 2023 10:16:14 -0500 Message-ID: Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x To: =?UTF-8?B?QW1hZGV1c3ogU8WCYXdpxYRza2k=?= Cc: Cezary Rojewski , Sasa Ostrouska , Linux regressions mailing list , Greg KH , lma@semihalf.com, Pierre-Louis Bossart , stable@vger.kernel.org, Takashi Iwai Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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. On Wed, Feb 1, 2023 at 9:33 AM Jason Montleon wrote: > > On Wed, Feb 1, 2023 at 6:05 AM Amadeusz S=C5=82awi=C5=84ski > wrote: > > > > On 1/31/2023 4:16 PM, Jason Montleon wrote: > > > On Tue, Jan 31, 2023 at 7:37 AM Cezary Rojewski > > > 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 o= n > > >> 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 a= n > > >> 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 wil= l > > > 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 reproducin= g on > > >> our end once we started playing with kernel versions (moved away fro= m > > >> status quo with Fedora). Neither on Lukasz EVE nor on my SKL RVP. > > >> However, we might be using newer configuration files when compared t= o > > >> 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/com= mit/?h=3Dv6.1.7&id=3D21e996306a6afaae88295858de0ffb8955173a15 > > >> > > >> > > >> 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-1410= 222840 > https://github.com/jmontleon/pixelbook-fedora/issues/51#issuecomment-1410= 673371 > https://github.com/jmontleon/pixelbook-fedora/issues/53#issuecomment-1408= 699252 > > 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 --=20 Jason Montleon | email: jmontleo@redhat.com Red Hat, Inc. | gpg key: 0x069E3022 Cell: 508-496-0663 | irc: jmontleo / jmontleon