[BUG][CML-007] ipc error in dmic pause-release test

[aiChaoSONG]

Describe the bug
capture via dmic, then press SPACE to pause-release capture very quickly and rapidly, first you will see io error in the terminal, check dmesg, you'll see ipc error.

To Reproduce

1. capture via dmic: arecord -Dhw:0,1 -f s32_le -r 48000 -c4 -i -vvv ./dmic.wav
2. press SPACE very quickly

Reproduction Rate
reproduced within less than 20 quick press on SPACE

Environment
Kernel: Chrome OS 4.19.79-07473-g5a6eeaee512fe
SOF: cml-007-drop-stable
tplg: sof-cml-rt1011-rt5682.tplg

all above are from ChromeOS image 12607.8.0 v79

sof_trace_dmic_pause_release.log
dmesg_dmic_pause_release.log

[aiChaoSONG]

this issue is the same as #2044 , we may need cherry-pick the fix from PR2078 to cml-007-drop-stable.

[mengdonglin]

@aiChaoSONG Please confirm if the fix for SOF #2044 can also fix this issue.

[aiChaoSONG]

@mengdonglin the fix for #2044 cannot be applied to cml-007-drop-stable, I think it is because the 007 branch is too old.

[lgirdwood]

@lbetlej should'n the cml007 branch now all be merged into master ? if so, we can cut another release with this #2044 fix.

[wwittbrx]

I cannot reproduce this issue with the following recipe (cml-008-drop):

PLATFORM: CML HATCH
OS: UBUNTU 19.04
FW: f7dfd05 sof-cml-rt5682-max98357a.m4
KERNEL: 5d67c4b + PR1383 + 169c659

Could you check if this is true on your side as well? I would strongly recommend switching to CML 008 as it is much more stable, with multiple fixes.

[aiChaoSONG]

@wwittbrx could you try cml-007 directly on asus chromebook, and see if you can reproduce this issue? we now should pay more attention on this device.

Bty, what is the branch of the kernel you mentioned (KERNEL: 5d67c4b + PR1383 + 169c659)? is it sof-dev, keyword_detect or other branch?

[aiChaoSONG]

This issue can also be reproduced with https://github.com/thesofproject/sof/tree/cml-007-pm-ctx-save. The reproduce rate is similar to cml-007-drop-stable.
Test recipe:
ChromeOS R79 12607.28.0 Chrome Kernel commit id: a5e05a63
@sathyap-chrome @wwittbrx

[aiChaoSONG]

kernel issue, Kernel PR #1070 can fix this. close this