echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

[Alex Natalsson]

Hello friends.
Suspend to RAM on Amlogic A311D chip (Khadas VIM3 SBC) was broken with
5.17.13 and with 5.18.2 it also presents.

When I trying do this I recieve error message:
VIM3 ~ # LANG=C echo mem > /sys/power/state
[  952.824117] PM: suspend entry (deep)
[  952.828333] Filesystems sync: 0.003 seconds
[  952.829473] Freezing user space processes ...
[  972.833509] Freezing of tasks failed after 20.003 seconds (1 tasks
refusing to freeze, wq_busy=0):
[  972.841178] task:mplayer         state:D stack:    0 pid:  779
ppid:   736 flags:0x00000205
[  972.849457] Call trace:
[  972.851868]  __switch_to+0xf8/0x150
[  972.855315]  __schedule+0x1f8/0x570
[  972.858758]  schedule+0x48/0xc0
[  972.861856]  schedule_preempt_disabled+0x10/0x20
[  972.866417]  __mutex_lock.constprop.0+0x158/0x590
[  972.871071]  __mutex_lock_slowpath+0x14/0x20
[  972.875296]  mutex_lock+0x5c/0x70
[  972.878573]  dpcm_fe_dai_open+0x44/0x194
[  972.882456]  snd_pcm_open_substream+0xa4/0x174
[  972.886857]  snd_pcm_open.part.0+0xd8/0x1dc
[  972.890994]  snd_pcm_playback_open+0x64/0x94
[  972.895223]  snd_open+0xac/0x1d0
[  972.898411]  chrdev_open+0xdc/0x2c4
[  972.901861]  do_dentry_open+0x12c/0x380
[  972.905652]  vfs_open+0x30/0x3c
[  972.908758]  do_open+0x1e4/0x3a0
[  972.911948]  path_openat+0x10c/0x280
[  972.915486]  do_filp_open+0x80/0x130
[  972.919019]  do_sys_openat2+0xb4/0x170
[  972.922731]  __arm64_sys_openat+0x64/0xb0
[  972.926700]  invoke_syscall+0x48/0x114
[  972.930421]  el0_svc_common.constprop.0+0xd4/0xfc
[  972.935070]  do_el0_svc+0x28/0x90
[  972.938347]  el0_svc+0x34/0xb0
[  972.941367]  el0t_64_sync_handler+0xa4/0x130
[  972.945595]  el0t_64_sync+0x18c/0x190

[  972.950674] OOM killer enabled.
[  972.953781] Restarting tasks ... done.
-bash: echo: write error: Device or resource busy
VIM3 ~ :( #

With 5.16.2 kernel version suspend to RAM is working, but system very
slow after resume.

Re: echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

[Greg KH]

On Fri, Jun 10, 2022 at 01:18:56PM +0300, Alex Natalsson wrote:
> Hello friends.
> Suspend to RAM on Amlogic A311D chip (Khadas VIM3 SBC) was broken with
> 5.17.13 and with 5.18.2 it also presents.
> 
> When I trying do this I recieve error message:
> VIM3 ~ # LANG=C echo mem > /sys/power/state
> [  952.824117] PM: suspend entry (deep)
> [  952.828333] Filesystems sync: 0.003 seconds
> [  952.829473] Freezing user space processes ...
> [  972.833509] Freezing of tasks failed after 20.003 seconds (1 tasks
> refusing to freeze, wq_busy=0):
> [  972.841178] task:mplayer         state:D stack:    0 pid:  779
> ppid:   736 flags:0x00000205
> [  972.849457] Call trace:
> [  972.851868]  __switch_to+0xf8/0x150
> [  972.855315]  __schedule+0x1f8/0x570
> [  972.858758]  schedule+0x48/0xc0
> [  972.861856]  schedule_preempt_disabled+0x10/0x20
> [  972.866417]  __mutex_lock.constprop.0+0x158/0x590
> [  972.871071]  __mutex_lock_slowpath+0x14/0x20
> [  972.875296]  mutex_lock+0x5c/0x70
> [  972.878573]  dpcm_fe_dai_open+0x44/0x194
> [  972.882456]  snd_pcm_open_substream+0xa4/0x174
> [  972.886857]  snd_pcm_open.part.0+0xd8/0x1dc
> [  972.890994]  snd_pcm_playback_open+0x64/0x94
> [  972.895223]  snd_open+0xac/0x1d0
> [  972.898411]  chrdev_open+0xdc/0x2c4
> [  972.901861]  do_dentry_open+0x12c/0x380
> [  972.905652]  vfs_open+0x30/0x3c
> [  972.908758]  do_open+0x1e4/0x3a0
> [  972.911948]  path_openat+0x10c/0x280
> [  972.915486]  do_filp_open+0x80/0x130
> [  972.919019]  do_sys_openat2+0xb4/0x170
> [  972.922731]  __arm64_sys_openat+0x64/0xb0
> [  972.926700]  invoke_syscall+0x48/0x114
> [  972.930421]  el0_svc_common.constprop.0+0xd4/0xfc
> [  972.935070]  do_el0_svc+0x28/0x90
> [  972.938347]  el0_svc+0x34/0xb0
> [  972.941367]  el0t_64_sync_handler+0xa4/0x130
> [  972.945595]  el0t_64_sync+0x18c/0x190
> 
> [  972.950674] OOM killer enabled.
> [  972.953781] Restarting tasks ... done.
> -bash: echo: write error: Device or resource busy
> VIM3 ~ :( #
> 
> With 5.16.2 kernel version suspend to RAM is working, but system very
> slow after resume.
> 

Can you use 'git bisect' to track down the offending commit?

And does 5.19-rc1 also have this issue?

thanks,

greg k-h

Re: echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

[Alex Natalsson]

Yes, I can finding broken commit, but it may requiring lot of time
with my system.

5.19-rc1 suspending successfully, but at resuming kernel freezing. Is
big core frequency not small?)
The log:
bl30 get wakeup sources!
process command 00000006
bl30 enter suspend!
Little core clk suspend rate 1000000000
Big core clk suspend rate 24000000
store restore gp0 pll
suspend_counter: 1
Enter ddr suspend
ddr suspend time: 15us
alarm=0S
process command 00000001
cec ver:2018/04/29
CEC cfg:0x0000
use vddee new table!
use vddee new table!
exit_reason:0x06
Enter ddr resume
ddr resume time: 123us
store restore gp0 pll
cfg15 3b00000
cfg15 63b00000
Little core clk resume rate 1000000000
Big core clk resume rate 50000000


пт, 10 июн. 2022 г. в 13:30, Greg KH <gregkh@linuxfoundation.org>:
>
> On Fri, Jun 10, 2022 at 01:18:56PM +0300, Alex Natalsson wrote:
> > Hello friends.
> > Suspend to RAM on Amlogic A311D chip (Khadas VIM3 SBC) was broken with
> > 5.17.13 and with 5.18.2 it also presents.
> >
> > When I trying do this I recieve error message:
> > VIM3 ~ # LANG=C echo mem > /sys/power/state
> > [  952.824117] PM: suspend entry (deep)
> > [  952.828333] Filesystems sync: 0.003 seconds
> > [  952.829473] Freezing user space processes ...
> > [  972.833509] Freezing of tasks failed after 20.003 seconds (1 tasks
> > refusing to freeze, wq_busy=0):
> > [  972.841178] task:mplayer         state:D stack:    0 pid:  779
> > ppid:   736 flags:0x00000205
> > [  972.849457] Call trace:
> > [  972.851868]  __switch_to+0xf8/0x150
> > [  972.855315]  __schedule+0x1f8/0x570
> > [  972.858758]  schedule+0x48/0xc0
> > [  972.861856]  schedule_preempt_disabled+0x10/0x20
> > [  972.866417]  __mutex_lock.constprop.0+0x158/0x590
> > [  972.871071]  __mutex_lock_slowpath+0x14/0x20
> > [  972.875296]  mutex_lock+0x5c/0x70
> > [  972.878573]  dpcm_fe_dai_open+0x44/0x194
> > [  972.882456]  snd_pcm_open_substream+0xa4/0x174
> > [  972.886857]  snd_pcm_open.part.0+0xd8/0x1dc
> > [  972.890994]  snd_pcm_playback_open+0x64/0x94
> > [  972.895223]  snd_open+0xac/0x1d0
> > [  972.898411]  chrdev_open+0xdc/0x2c4
> > [  972.901861]  do_dentry_open+0x12c/0x380
> > [  972.905652]  vfs_open+0x30/0x3c
> > [  972.908758]  do_open+0x1e4/0x3a0
> > [  972.911948]  path_openat+0x10c/0x280
> > [  972.915486]  do_filp_open+0x80/0x130
> > [  972.919019]  do_sys_openat2+0xb4/0x170
> > [  972.922731]  __arm64_sys_openat+0x64/0xb0
> > [  972.926700]  invoke_syscall+0x48/0x114
> > [  972.930421]  el0_svc_common.constprop.0+0xd4/0xfc
> > [  972.935070]  do_el0_svc+0x28/0x90
> > [  972.938347]  el0_svc+0x34/0xb0
> > [  972.941367]  el0t_64_sync_handler+0xa4/0x130
> > [  972.945595]  el0t_64_sync+0x18c/0x190
> >
> > [  972.950674] OOM killer enabled.
> > [  972.953781] Restarting tasks ... done.
> > -bash: echo: write error: Device or resource busy
> > VIM3 ~ :( #
> >
> > With 5.16.2 kernel version suspend to RAM is working, but system very
> > slow after resume.
> >
>
> Can you use 'git bisect' to track down the offending commit?
>
> And does 5.19-rc1 also have this issue?
>
> thanks,
>
> greg k-h

Re: echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

[Alex Natalsson]

New kernels freezing after resume only when scaling governor is
"conservative". Yes, I using this because my solar battery produce a
few of electricity. When scaling governor is performance system not
freezing after resume.
However, sometimes I received "Device or resource busy" error after
echo mem > /sys/power/state.
Later I found out what this was related with another bug:
pipewire-media-session is <defunct>, nosound and many processes which
using audio as mplayer, ffplay, alsamixer and etc was not responding
and not terminating even throught kill -9.
The log after alsamixer launch:
[  103.786358] Internal error: Oops: 96000004 [#1] SMP
[  103.786509] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq
snd_seq_device bnep nls_utf8 mt7601u mac80211 hci_uart libarc4 joydev
brcmfmac btbcm panfrost bluetooth meson_vdec(C) brcmutil gpu_sched
cfg80211 dwmac_generic videobuf2_dma_contig v4l2_mem2mem
videobuf2_memops videobuf2_v4l2 videobuf2_common drm_shmem_helper
ecdh_generic dwmac_meson8b stmmac_platform dw_hdmi_i2s_audio stmmac
ecc ir_nec_decoder videodev pcs_xpcs rc_khadas phylink ptp
meson_saradc meson_ir rc_core snd_soc_meson_axg_frddr
snd_soc_meson_axg_toddr snd_soc_meson_axg_sound_card
snd_soc_meson_card_utils snd_soc_meson_axg_fifo ao_cec_g12a
snd_soc_meson_axg_tdmin snd_soc_meson_axg_tdm_interface
snd_soc_meson_axg_tdmout snd_soc_meson_axg_tdm_formatter rfkill
meson_gxbb_wdt fuse crypto_user uas usb_storage adc_keys
gpio_keys_polled industrialio
[  103.857778] CPU: 3 PID: 530 Comm: pipewire-media- Tainted: G
 C        5.16.0-ARCH+ #8
[  103.857791] Hardware name: Khadas VIM3 (DT)
[  103.857795] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[  103.857801] pc : dpcm_be_connect+0xd0/0x2d0
[  103.881758] lr : dpcm_add_paths.isra.0+0xcc/0x1e0
[  103.881763] sp : ffff800009f4b870
[  103.881765] x29: ffff800009f4b870 x28: ffff000003b944c0 x27: 0000000000000001
[  103.881772] x26: 0000000000000001 x25: 0000000000000340 x24: 00000000000002a0
[  103.881777] x23: 0000000000000001 x22: 0000000000000000 x21: ffff000005b18080
[  103.881782] x20: ffff000005b183c0 x19: ffff000005b1c080 x18: 0000000000000000
[  103.881787] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[  103.881792] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[  103.881797] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
[  103.881801] x8 : ffff000012020400 x7 : 0000000000000000 x6 : 000000000000003f
[  103.881806] x5 : 0000000000000040 x4 : 0000000000000000 x3 : ffff000002822000
[  103.881811] x2 : ffff000002861b50 x1 : ffff00000282f800 x0 : ffff000002861800
[  103.881817] Call trace:
[  103.881819]  dpcm_be_connect+0xd0/0x2d0
[  103.881823]  dpcm_add_paths.isra.0+0xcc/0x1e0
[  103.881826]  dpcm_fe_dai_open+0x80/0x194
[  103.881831]  snd_pcm_open_substream+0xa4/0x174
[  103.881838]  snd_pcm_open.part.0+0xd8/0x1dc
[  103.881843]  snd_pcm_capture_open+0x64/0x94
[  103.992730]  snd_open+0xac/0x1d0
[  103.992739]  chrdev_open+0xe0/0x2d0
[  103.999389]  do_dentry_open+0x12c/0x3a0
[  103.999397]  vfs_open+0x30/0x3c
[  103.999401]  do_open+0x204/0x414
[  103.999405]  path_openat+0x10c/0x27c
[  103.999408]  do_filp_open+0x80/0x130
[  103.999412]  do_sys_openat2+0xb4/0x170
[  103.999414]  __arm64_sys_openat+0x64/0xb0
[  103.999416]  invoke_syscall+0x48/0x114
[  103.999426]  el0_svc_common.constprop.0+0xd4/0xfc
[  103.999429]  do_el0_svc+0x28/0x90
[  103.999432]  el0_svc+0x28/0x80
[  103.999440]  el0t_64_sync_handler+0xa4/0x130
[  103.999442]  el0t_64_sync+0x1a0/0x1a4
[  103.999451] Code: 8b000020 f9406841 f9406816 f9400020 (f94002c1)
[  103.999457] ---[ end trace e01b673b8147057d ]---


After I removed pipewire software "Device or resource busy" error was
disappear. But the sound and media still doesn't working and alsamixer
cannot change sound card to my usb audio device after commit
bbf7d3b1c4f40eb02dd1dffb500ba00b0bff0303.

> On Fri, Jun 10, 2022 at 01:18:56PM +0300, Alex Natalsson wrote:
> > Hello friends.
> > Suspend to RAM on Amlogic A311D chip (Khadas VIM3 SBC) was broken with
> > 5.17.13 and with 5.18.2 it also presents.
> >
> > When I trying do this I recieve error message:
> > VIM3 ~ # LANG=C echo mem > /sys/power/state
> > [  952.824117] PM: suspend entry (deep)
> > [  952.828333] Filesystems sync: 0.003 seconds
> > [  952.829473] Freezing user space processes ...
> > [  972.833509] Freezing of tasks failed after 20.003 seconds (1 tasks
> > refusing to freeze, wq_busy=0):
> > [  972.841178] task:mplayer         state:D stack:    0 pid:  779
> > ppid:   736 flags:0x00000205
> > [  972.849457] Call trace:
> > [  972.851868]  __switch_to+0xf8/0x150
> > [  972.855315]  __schedule+0x1f8/0x570
> > [  972.858758]  schedule+0x48/0xc0
> > [  972.861856]  schedule_preempt_disabled+0x10/0x20
> > [  972.866417]  __mutex_lock.constprop.0+0x158/0x590
> > [  972.871071]  __mutex_lock_slowpath+0x14/0x20
> > [  972.875296]  mutex_lock+0x5c/0x70
> > [  972.878573]  dpcm_fe_dai_open+0x44/0x194
> > [  972.882456]  snd_pcm_open_substream+0xa4/0x174
> > [  972.886857]  snd_pcm_open.part.0+0xd8/0x1dc
> > [  972.890994]  snd_pcm_playback_open+0x64/0x94
> > [  972.895223]  snd_open+0xac/0x1d0
> > [  972.898411]  chrdev_open+0xdc/0x2c4
> > [  972.901861]  do_dentry_open+0x12c/0x380
> > [  972.905652]  vfs_open+0x30/0x3c
> > [  972.908758]  do_open+0x1e4/0x3a0
> > [  972.911948]  path_openat+0x10c/0x280
> > [  972.915486]  do_filp_open+0x80/0x130
> > [  972.919019]  do_sys_openat2+0xb4/0x170
> > [  972.922731]  __arm64_sys_openat+0x64/0xb0
> > [  972.926700]  invoke_syscall+0x48/0x114
> > [  972.930421]  el0_svc_common.constprop.0+0xd4/0xfc
> > [  972.935070]  do_el0_svc+0x28/0x90
> > [  972.938347]  el0_svc+0x34/0xb0
> > [  972.941367]  el0t_64_sync_handler+0xa4/0x130
> > [  972.945595]  el0t_64_sync+0x18c/0x190
> >
> > [  972.950674] OOM killer enabled.
> > [  972.953781] Restarting tasks ... done.
> > -bash: echo: write error: Device or resource busy
> > VIM3 ~ :( #
> >
> > With 5.16.2 kernel version suspend to RAM is working, but system very
> > slow after resume.
> >
>
> Can you use 'git bisect' to track down the offending commit?
>
> And does 5.19-rc1 also have this issue?
>
> thanks,
>
> greg k-h

Re: echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

[Greg KH]

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Sat, Jun 25, 2022 at 06:01:22PM +0300, Alex Natalsson wrote:
> New kernels freezing after resume only when scaling governor is
> "conservative". Yes, I using this because my solar battery produce a
> few of electricity. When scaling governor is performance system not
> freezing after resume.
> However, sometimes I received "Device or resource busy" error after
> echo mem > /sys/power/state.
> Later I found out what this was related with another bug:
> pipewire-media-session is <defunct>, nosound and many processes which
> using audio as mplayer, ffplay, alsamixer and etc was not responding
> and not terminating even throught kill -9.
> The log after alsamixer launch:
> [  103.786358] Internal error: Oops: 96000004 [#1] SMP
> [  103.786509] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq
> snd_seq_device bnep nls_utf8 mt7601u mac80211 hci_uart libarc4 joydev
> brcmfmac btbcm panfrost bluetooth meson_vdec(C) brcmutil gpu_sched
> cfg80211 dwmac_generic videobuf2_dma_contig v4l2_mem2mem
> videobuf2_memops videobuf2_v4l2 videobuf2_common drm_shmem_helper
> ecdh_generic dwmac_meson8b stmmac_platform dw_hdmi_i2s_audio stmmac
> ecc ir_nec_decoder videodev pcs_xpcs rc_khadas phylink ptp
> meson_saradc meson_ir rc_core snd_soc_meson_axg_frddr
> snd_soc_meson_axg_toddr snd_soc_meson_axg_sound_card
> snd_soc_meson_card_utils snd_soc_meson_axg_fifo ao_cec_g12a
> snd_soc_meson_axg_tdmin snd_soc_meson_axg_tdm_interface
> snd_soc_meson_axg_tdmout snd_soc_meson_axg_tdm_formatter rfkill
> meson_gxbb_wdt fuse crypto_user uas usb_storage adc_keys
> gpio_keys_polled industrialio
> [  103.857778] CPU: 3 PID: 530 Comm: pipewire-media- Tainted: G
>  C        5.16.0-ARCH+ #8

But this is 5.16.0, the commit you pointed to is in 5.17.



> [  103.857791] Hardware name: Khadas VIM3 (DT)
> [  103.857795] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [  103.857801] pc : dpcm_be_connect+0xd0/0x2d0
> [  103.881758] lr : dpcm_add_paths.isra.0+0xcc/0x1e0
> [  103.881763] sp : ffff800009f4b870
> [  103.881765] x29: ffff800009f4b870 x28: ffff000003b944c0 x27: 0000000000000001
> [  103.881772] x26: 0000000000000001 x25: 0000000000000340 x24: 00000000000002a0
> [  103.881777] x23: 0000000000000001 x22: 0000000000000000 x21: ffff000005b18080
> [  103.881782] x20: ffff000005b183c0 x19: ffff000005b1c080 x18: 0000000000000000
> [  103.881787] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
> [  103.881792] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
> [  103.881797] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000
> [  103.881801] x8 : ffff000012020400 x7 : 0000000000000000 x6 : 000000000000003f
> [  103.881806] x5 : 0000000000000040 x4 : 0000000000000000 x3 : ffff000002822000
> [  103.881811] x2 : ffff000002861b50 x1 : ffff00000282f800 x0 : ffff000002861800
> [  103.881817] Call trace:
> [  103.881819]  dpcm_be_connect+0xd0/0x2d0
> [  103.881823]  dpcm_add_paths.isra.0+0xcc/0x1e0
> [  103.881826]  dpcm_fe_dai_open+0x80/0x194
> [  103.881831]  snd_pcm_open_substream+0xa4/0x174
> [  103.881838]  snd_pcm_open.part.0+0xd8/0x1dc
> [  103.881843]  snd_pcm_capture_open+0x64/0x94
> [  103.992730]  snd_open+0xac/0x1d0
> [  103.992739]  chrdev_open+0xe0/0x2d0
> [  103.999389]  do_dentry_open+0x12c/0x3a0
> [  103.999397]  vfs_open+0x30/0x3c
> [  103.999401]  do_open+0x204/0x414
> [  103.999405]  path_openat+0x10c/0x27c
> [  103.999408]  do_filp_open+0x80/0x130
> [  103.999412]  do_sys_openat2+0xb4/0x170
> [  103.999414]  __arm64_sys_openat+0x64/0xb0
> [  103.999416]  invoke_syscall+0x48/0x114
> [  103.999426]  el0_svc_common.constprop.0+0xd4/0xfc
> [  103.999429]  do_el0_svc+0x28/0x90
> [  103.999432]  el0_svc+0x28/0x80
> [  103.999440]  el0t_64_sync_handler+0xa4/0x130
> [  103.999442]  el0t_64_sync+0x1a0/0x1a4
> [  103.999451] Code: 8b000020 f9406841 f9406816 f9400020 (f94002c1)
> [  103.999457] ---[ end trace e01b673b8147057d ]---
> 
> 
> After I removed pipewire software "Device or resource busy" error was
> disappear. But the sound and media still doesn't working and alsamixer
> cannot change sound card to my usb audio device after commit
> bbf7d3b1c4f40eb02dd1dffb500ba00b0bff0303.

Can you send the info to the sound mailing list and cc the developers of
that commit with your information?  That commit looks odd to be causing
problems.

thanks,

greg k-h

Re: echo mem > /sys/power/state write error "Device or resource busy" on Amlogic A311D device

[Alex Natalsson]

> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
Thanks))


> But this is 5.16.0, the commit you pointed to is in 5.17.
>
I don't understanding why so it... At present  HEAD points to 5.19-rc2...

commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3 (HEAD, tag: v5.19-rc2)
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jun 12 16:11:37 2022 -0700

    Linux 5.19-rc2

....but
leha@VIM3 ~/ArchlinuxVIM/linux-git-sound/src/linux $ make kernelrelease
5.16.0-rc1-ARCH+
leha@VIM3 ~/ArchlinuxVIM/linux-git-sound/src/linux $ make kernelversion
5.16.0-rc1
leha@VIM3 ~/ArchlinuxVIM/linux-git-sound/src/linux $ zcat
/proc/config.gz |head -n 5
#
# Automatically generated file; DO NOT EDIT.
# Linux/arm64 5.16.0-rc1 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 12.1.0"
leha@VIM3 ~/ArchlinuxVIM/linux-git-sound/src/linux $


> Can you send the info to the sound mailing list and cc the developers of
> that commit with your information?  That commit looks odd to be causing
> problems.
OK. I will be to try.