From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7952DBD08 for ; Wed, 1 Feb 2023 11:05:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675249547; x=1706785547; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=wUI9fwdxyITvbXcc3bSr/O1oZNGcCUvap6bRqf8k2dQ=; b=aNMBhHCAYtY8ynITrxnhbURqIexBpETNPD9jQ7rsaELghqE0yV84Hhfc LWNKWk8mnBfTFJ+O1/U+EeeGsPAQkaw5DMnCy4RcYTnS5aTQ97V6iAPx1 5Hn1vaLporo3fHtfLv90rQDVDMGgnP20MyJTkILR9S82trK91ei8BAJay 7X7P/ng8TDNHVIoMR9RAPatXYtNwy9ZxUjnreuqVJwiuzC8KZZXxB0kTW 5NWkRDKUAWpM4w8Ozx1EBZ7FhMyO80qESj830cA2ZTO10RNoridvE1Fz+ Grf85Aj37w4SroSnfuUGeOATdQDeOUTItAXxwFnnqfrNUcEnLASDwGIVO Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10607"; a="390501511" X-IronPort-AV: E=Sophos;i="5.97,263,1669104000"; d="scan'208";a="390501511" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2023 03:05:46 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10607"; a="773395829" X-IronPort-AV: E=Sophos;i="5.97,263,1669104000"; d="scan'208";a="773395829" Received: from aslawinx-mobl.ger.corp.intel.com (HELO [10.99.16.144]) ([10.99.16.144]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2023 03:05:44 -0800 Message-ID: <6262bd72-cc2b-9d2a-e8f0-55c2b2bb7861@linux.intel.com> Date: Wed, 1 Feb 2023 12:05:41 +0100 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x Content-Language: en-US To: Jason Montleon , Cezary Rojewski Cc: Sasa Ostrouska , Linux regressions mailing list , Greg KH , lma@semihalf.com, Pierre-Louis Bossart , stable@vger.kernel.org, Takashi Iwai References: <02834fa9-4fb0-08fb-4b5f-e9646c1501d6@leemhuis.info> <288d7ff4-75aa-7ad1-c49c-579373cab3ed@intel.com> <04a9f939-8a98-9a46-e165-8e9fb8801a83@intel.com> From: =?UTF-8?Q?Amadeusz_S=c5=82awi=c5=84ski?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 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