[BUG][TGL][v7.0-rc10]Wov will repeat about 1~2s of the end of recorded file

[Liviali155]

Describe the bug
Wov will repeat about 1~2s of the end of recorded file

To Reproduce
1."sudo reboot" to reboot system
2.arecord -Dhw:0,100 -M -N -f s32_le -r 16000 -i -vvv -c2 --buffer-size=96000 ./tmp.wav

Reproduce Rate
1/3

Expected behavior
Recorded file normal

Impact
Wov will repeat about 1~2s of the end of recorded file

Environment
Kernel:https://github.com/keyonjie/linux/commits/keyon-002(commit:082d5f6f2334824388b2e80de98e1f501106b756)
Firmware:https://github.com/thesofproject/sof/commits/releases/tgl/v7.0-rc10 ,(commit: fb801c8)

TPLG:sof-tgl-max98373-rt5682.tplg
Platform:Chromebook with codec 98373 in I2S mode.

dmesg0715.log
sof-logger0715.log
tmp.zip

[ClarexZhou]

Error also can be reproduced with kernel https://github.com/thesofproject/linux/tree/tgl-007-20200716 and Firmware:https://github.com/thesofproject/sof/commits/releases/tgl/v7.0-rc10

[ClarexZhou]

Error only occurred when stop capture via CTRL+C, error not occurred if run and stop stream via -d 10, arecord -Dhw:0,100 -M -N -f s32_le -r 16000 -d 10 -i -vv -c2 --buffer-size=96000 ./tmp.wav, verified 10 interactions

[keyonjie]

Hi @mrajwa this issue can be reproduced with 98357a machine on S0 also, please try it more times(3~5 times) to reproduce it.

[slawblauciak]

To be clarified with the Chrome team, if forceful stopping of the pipeline is to be supported.

[Liviali155]

On JSL Chromebook with codec da7219max98360a in i2s mode also has this issue
dmesgjsl.log
sof-loggetjsl.log
tmp.zip

https://github.com/thesofproject/linux/commits/topic/sof-dev(797eb03a)
https://github.com/thesofproject/sof/tree/releases/jsl/v4.0-rc1(21c8900f)

[slawblauciak]

When the user forcefully stops the pipeline during draining, the flow of data is aborted. There's no likely scenario that could cause the firmware to keep sending repeating data afterwards. I would recommend verifying the way the buffer read in the driver.

[mwasko]

@ranj063 can we ask for SOF driver expertise? The initial FW debug indicate problem at driver/kernel layer

[ranj063]

@ranj063 can we ask for SOF driver expertise? The initial FW debug indicate problem at driver/kernel layer

@mrajwa checking at my end but can you please elaborate on which part of your debug indicated a driver problem?