stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasa Ostrouska <casaxa@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: stable@vger.kernel.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Lukasz Majczak <lma@semihalf.com>,
	Cezary Rojewski <cezary.rojewski@intel.com>
Subject: Re: Google Pixelbook EVE, no sound in kernel 6.1.x
Date: Fri, 24 Feb 2023 02:10:31 +0100	[thread overview]
Message-ID: <CALFERdy2+shxBo=sSXYfJBLZtzMq9rHY8X=Krh52T4-LW=-CKw@mail.gmail.com> (raw)
In-Reply-To: <CALFERdwvq5day_sbDfiUsMSZCQu9HG8-SBpOZDNPeMdZGog6XA@mail.gmail.com>

Hi again. I have today upgraded my slackware install pixelbook from
kernel 6.1.12 to 6.1.13 and this solved the issue of powering down the
notebook. Now it has no problem
to poweroff, I do not need anymore to keep the power button to switch
off. But the thing now is that I have no longer a working sound.
I see that for some reason the firmware seems is no longer loaded:

root@goopix:~# dmesg | grep snd
[    5.599427] snd_hda_intel 0000:00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[    5.907375] snd_soc_skl 0000:00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[    5.990054] snd_soc_skl 0000:00:1f.3: bound 0000:00:02.0 (ops
i915_audio_component_bind_ops [i915])
[    7.382484] snd_soc_skl 0000:00:1f.3: ASoC: no sink widget found
for AEC Capture
[    7.382952] snd_soc_skl 0000:00:1f.3: ASoC: Failed to add route
echo_ref_out cpr 7 -> direct -> AEC Capture
[    7.384409] snd_soc_skl 0000:00:1f.3: Direct firmware load for
intel/dsp_fw_kbl.bin failed with error -2
[    7.386037] snd_soc_skl 0000:00:1f.3: Request firmware failed -2
[    7.388099] snd_soc_skl 0000:00:1f.3: Load base fw failed : -5
[    7.390630] snd_soc_skl 0000:00:1f.3: Failed to boot first fw: -5
[    7.393598] snd_soc_skl 0000:00:1f.3: ASoC: error at
snd_soc_component_probe on 0000:00:1f.3: -5
root@goopix:~#

root@goopix:~# dmesg | grep kbl
[    5.946463] i915 0000:00:02.0: [drm] Finished loading DMC firmware
i915/kbl_dmc_ver1_04.bin (v1.4)
[    6.293440] kbl_r5514_5663_max kbl_r5514_5663_max: Failed to get
ssp1_mclk, defer probe
[    7.383448] kbl_r5514_5663_max kbl_r5514_5663_max: ASoC: Parent
card not yet available, widget card binding deferred
[    7.384409] snd_soc_skl 0000:00:1f.3: Direct firmware load for
intel/dsp_fw_kbl.bin failed with error -2
[    7.397157] kbl_r5514_5663_max kbl_r5514_5663_max: ASoC: failed to
instantiate card -5
[    7.399749] kbl_r5514_5663_max: probe of kbl_r5514_5663_max failed
with error -5
root@goopix:~#

But I have the firmware in place:

root@goopix:~# ls -l /lib/firmware/9d71-GOOGLE-EVEMAX-0-tplg.bin
-rw-r--r-- 1 root root 37864 Jan 26 07:48
/lib/firmware/9d71-GOOGLE-EVEMAX-0-tplg.bin
root@goopix:~# ls -l /lib/firmware/dsp*
-rw-r--r-- 1 root root 16556 Jan 26 07:49
/lib/firmware/dsp_lib_dsm_core_spt_release.bin

root@goopix:~# ls -l /lib/firmware/intel/dsp_fw_*
-rw-r--r-- 1 root root  73728 Jan 26 07:50
/lib/firmware/intel/dsp_fw_C75061F3-F2B2-4DCC-8F9F-82ABB4131E66.bin
lrwxrwxrwx 1 root root     28 Feb 23 21:22
/lib/firmware/intel/dsp_fw_bxtn.bin -> intel/avs/apl/dsp_basefw.bin
-rw-r--r-- 1 root root 505608 Feb 22 22:10
/lib/firmware/intel/dsp_fw_bxtn_v2219.bin
-rw-r--r-- 1 root root 505608 Feb 22 22:10
/lib/firmware/intel/dsp_fw_bxtn_v3366.bin
lrwxrwxrwx 1 root root     28 Feb 23 21:22
/lib/firmware/intel/dsp_fw_cnl.bin -> intel/avs/cnl/dsp_basefw.bin
-rw-r--r-- 1 root root 583852 Feb 22 22:10
/lib/firmware/intel/dsp_fw_cnl_v1191.bin
-rw-r--r-- 1 root root 583852 Feb 22 22:10
/lib/firmware/intel/dsp_fw_cnl_v1858.bin
lrwxrwxrwx 1 root root     28 Feb 23 21:22
/lib/firmware/intel/dsp_fw_glk.bin -> intel/avs/apl/dsp_basefw.bin
-rw-r--r-- 1 root root 505608 Feb 22 22:10
/lib/firmware/intel/dsp_fw_glk_v1814.bin
-rw-r--r-- 1 root root 505608 Feb 22 22:10
/lib/firmware/intel/dsp_fw_glk_v2768.bin
-rw-r--r-- 1 root root 505608 Feb 22 22:10
/lib/firmware/intel/dsp_fw_glk_v2880.bin
-rw-r--r-- 1 root root 505608 Feb 22 22:10
/lib/firmware/intel/dsp_fw_glk_v3366.bin
lrwxrwxrwx 1 root root     28 Feb 23 21:22
/lib/firmware/intel/dsp_fw_kbl.bin -> intel/avs/skl/dsp_basefw.bin
-rw-r--r-- 1 root root 238920 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v1037.bin
-rw-r--r-- 1 root root 238920 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v2042.bin
-rw-r--r-- 1 root root 243016 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v2630.bin
-rw-r--r-- 1 root root 243016 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v3266.bin
-rw-r--r-- 1 root root 247112 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v3402.bin
-rw-r--r-- 1 root root 243016 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v3420.bin
-rw-r--r-- 1 root root 238920 Feb 22 22:10
/lib/firmware/intel/dsp_fw_kbl_v701.bin
lrwxrwxrwx 1 root root     28 Feb 23 21:22
/lib/firmware/intel/dsp_fw_release.bin -> intel/avs/skl/dsp_basefw.bin
-rw-r--r-- 1 root root 247112 Feb 22 22:10
/lib/firmware/intel/dsp_fw_release_v3402.bin
-rw-r--r-- 1 root root 221184 Feb 22 22:10
/lib/firmware/intel/dsp_fw_release_v969.bin
root@goopix:~#

At least to me all seems in place.
Anybody can help me understand how to see why the firmware is not
loading or what could be the problem now ?

Rgds
Sasa

On Thu, Feb 9, 2023 at 3:11 PM Sasa Ostrouska <casaxa@gmail.com> wrote:
>
> Hi, I dont know how much this is relevant but I am getting this kind
> of traces in dmesg on both, Salckware and Fedora installs.
>
> [   16.286097] ------------[ cut here ]------------
> [   16.286100] memcpy: detected field-spanning write (size 100) of
> single field "cpr_mconfig->gtw_cfg.config_data" at
> sound/soc/intel/skylake/skl-messages.c:554 (size 4)
> [   16.286128] WARNING: CPU: 1 PID: 1232 at
> sound/soc/intel/skylake/skl-messages.c:554 skl_init_module+0x757/0x770
> [snd_soc_skl]
> [   16.286156] Modules linked in: nf_nat_ftp nf_conntrack_ftp
> nft_objref nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet
> nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4
> nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack
> nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables nfnetlink
> snd_soc_skl_ssp_clk snd_sof_pci_intel_skl snd_sof_intel_hda_common
> soundwire_intel soundwire_generic_allocation soundwire_cadence
> snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils
> qrtr soundwire_bus snd_soc_avs snd_soc_kbl_rt5663_rt5514_max98927
> snd_soc_hda_codec cros_ec_light_prox cros_ec_sensors
> cros_ec_sensors_core bnep industrialio_triggered_buffer kfifo_buf
> snd_soc_hdac_hdmi snd_soc_dmic industrialio i2c_hid_acpi i2c_hid
> snd_soc_skl cros_ec_chardev snd_soc_hdac_hda cros_ec_sensorhub
> snd_hda_ext_core cros_usbpd_charger cros_ec_sysfs cros_usbpd_logger
> snd_soc_sst_ipc binfmt_misc iTCO_wdt snd_soc_sst_dsp
> snd_soc_acpi_intel_match intel_pmc_bxt
> [   16.286215]  iTCO_vendor_support intel_tcc_cooling
> x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp coretemp kvm_intel
> snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi cros_ec_dev
> snd_hda_codec kvm intel_rapl_msr iwlmvm uvcvideo videobuf2_vmalloc
> irqbypass mac80211 rapl videobuf2_memops snd_hda_core videobuf2_v4l2
> intel_cstate intel_uncore libarc4 pcspkr i2c_i801 sunrpc snd_hwdep
> videobuf2_common videodev i2c_smbus btusb btrtl spi_pxa2xx_platform
> dw_dmac btbcm iwlwifi btintel mc snd_soc_rt5663 btmtk snd_soc_rt5514
> snd_soc_max98927 snd_soc_rt5514_spi snd_soc_rl6231 bluetooth
> snd_soc_core cfg80211 mei_me joydev snd_compress mei ac97_bus
> snd_pcm_dmaengine intel_pch_thermal rfkill idma64 snd_seq
> snd_seq_device snd_pcm snd_timer processor_thermal_device_pci_legacy
> processor_thermal_device snd cros_ec_i2c processor_thermal_rfim
> processor_thermal_mbox soundcore processor_thermal_rapl cros_ec_lpcs
> cros_ec tpm_tis_i2c_cr50 cros_usbpd_notify int3403_thermal
> intel_rapl_common
> [   16.286285]  int340x_thermal_zone intel_xhci_usb_role_switch
> int3400_thermal chromeos_pstore cros_kbd_led_backlight
> acpi_thermal_rel chromeos_acpi intel_soc_dts_iosf zram
> hid_logitech_hidpp hid_logitech_dj i915 drm_buddy video
> crct10dif_pclmul crc32_pclmul crc32c_intel wmi polyval_clmulni nvme
> polyval_generic drm_display_helper nvme_core sdhci_pci cqhci cec sdhci
> ghash_clmulni_intel hid_multitouch mmc_core sha512_ssse3 nvme_common
> serio_raw ttm pinctrl_sunrisepoint r8152 mii ip6_tables ip_tables fuse
> [last unloaded: i2c_hid]
> [   16.286324] CPU: 1 PID: 1232 Comm: pulseaudio Not tainted
> 6.1.9-201.pixelbook.fc37.x86_64 #1
> [   16.286328] Hardware name: Google Eve/Eve, BIOS
> Google_Eve.9584.230.0 09/06/2021
> [   16.286330] RIP: 0010:skl_init_module+0x757/0x770 [snd_soc_skl]
> [   16.286355] Code: bd fe ff ff b9 04 00 00 00 4c 89 fe 4c 89 04 24
> 48 c7 c2 00 e7 42 c1 48 c7 c7 58 e7 42 c1 c6 05 0e 36 02 00 01 e8 3f
> 1b 95 fb <0f> 0b 4c 8b 04 24 e9 8c fe ff ff e9 96 ab 00 00 66 0f 1f 84
> 00 00
> [   16.286358] RSP: 0000:ffffb3c2816c7ae0 EFLAGS: 00010296
> [   16.286362] RAX: 000000000000009a RBX: ffff8d7ce355e028 RCX: 0000000000000000
> [   16.286364] RDX: 0000000000000001 RSI: ffffffffbd74c48b RDI: 00000000ffffffff
> [   16.286366] RBP: ffff8d7cc3854028 R08: 0000000000000000 R09: ffffb3c2816c7980
> [   16.286368] R10: 0000000000000003 R11: ffffffffbe1465a8 R12: 00000000000000b8
> [   16.286370] R13: 00000000000000b8 R14: ffff8d7d0d73c840 R15: 0000000000000064
> [   16.286372] FS:  00007fcb6eca02c0(0000) GS:ffff8d802ec80000(0000)
> knlGS:0000000000000000
> [   16.286375] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [   16.286377] CR2: 00002dc17c298000 CR3: 000000016ccfa004 CR4: 00000000003706e0
> [   16.286379] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> [   16.286381] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> [   16.286382] Call Trace:
> [   16.286386]  <TASK>
> [   16.286391]  skl_tplg_mixer_event+0x72f/0xd20 [snd_soc_skl]
> [   16.286412]  ? __schedule+0x367/0x1360
> [   16.286420]  dapm_seq_check_event+0x108/0x1c0 [snd_soc_core]
> [   16.286464]  dapm_seq_run_coalesced+0x84/0x1c0 [snd_soc_core]
> [   16.286501]  dapm_seq_run+0x16e/0x3e0 [snd_soc_core]
> [   16.286542]  dapm_power_widgets+0x5db/0xa40 [snd_soc_core]
> [   16.286581]  snd_soc_dapm_stream_event+0xf5/0x170 [snd_soc_core]
> [   16.286619]  __soc_pcm_prepare+0x53/0xf0 [snd_soc_core]
> [   16.286659]  dpcm_fe_dai_prepare+0xac/0x150 [snd_soc_core]
> [   16.286699]  snd_pcm_do_prepare+0x26/0x40 [snd_pcm]
> [   16.286718]  snd_pcm_action_single+0x33/0x80 [snd_pcm]
> [   16.286733]  snd_pcm_action_nonatomic+0x95/0xa0 [snd_pcm]
> [   16.286749]  snd_pcm_ioctl+0x23/0x40 [snd_pcm]
> [   16.286764]  __x64_sys_ioctl+0x8d/0xd0
> [   16.286770]  do_syscall_64+0x58/0x80
> [   16.286774]  ? syscall_exit_to_user_mode+0x17/0x40
> [   16.286777]  ? do_syscall_64+0x67/0x80
> [   16.286780]  ? snd_pcm_ioctl+0x23/0x40 [snd_pcm]
> [   16.286795]  ? __x64_sys_ioctl+0x8d/0xd0
> [   16.286799]  ? syscall_exit_to_user_mode+0x17/0x40
> [   16.286801]  ? do_syscall_64+0x67/0x80
> [   16.286805]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
> [   16.286809] RIP: 0033:0x7fcb6f593d6f
> [   16.286841] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24
> 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00
> 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28
> 00 00
> [   16.286843] RSP: 002b:00007ffe5ea27370 EFLAGS: 00000246 ORIG_RAX:
> 0000000000000010
> [   16.286847] RAX: ffffffffffffffda RBX: 0000563cd8d93160 RCX: 00007fcb6f593d6f
> [   16.286849] RDX: 0000000000000000 RSI: 0000000000004140 RDI: 0000000000000015
> [   16.286851] RBP: 0000000000000000 R08: 00000000000012bd R09: 00007ffe5ea27324
> [   16.286853] R10: 0000000000000004 R11: 0000000000000246 R12: 00007ffe5ea27aa4
> [   16.286855] R13: 00007ffe5ea27680 R14: 00007ffe5ea27a90 R15: 00007fcb6ec07290
> [   16.286861]  </TASK>
> [   16.286863] ---[ end trace 0000000000000000 ]---
>
> Seems sound related. Also I suffer from not be able to reboot or
> powerdown on Slackware with 6.1.8,6.1.9 and 6.1.10 kernels.
>
> Rgds
> Sasa
>
> On Fri, Jan 27, 2023 at 11:06 AM Sasa Ostrouska <casaxa@gmail.com> wrote:
> >
> > Hi Lucasz, I don't know if this could be relevant, but when I
> > installed slackware64-current on the other pixelbook I have the sound
> > works with
> > kernel 6.1.8 but not all the time and seems there are some crashes of
> > the sound. Also it is very amplified.
> > I attach the dmesg here.

  reply	other threads:[~2023-02-24  1:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 20:44 Google Pixelbook EVE, no sound in kernel 6.1.x 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 [this message]
2023-02-24 20:43         ` Sasa Ostrouska
2023-01-28 17:09 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
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)

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='CALFERdy2+shxBo=sSXYfJBLZtzMq9rHY8X=Krh52T4-LW=-CKw@mail.gmail.com' \
    --to=casaxa@gmail.com \
    --cc=cezary.rojewski@intel.com \
    --cc=lma@semihalf.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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).