Repository navigation
[BUG][BYT-NOCODEC]Input/output error when aplay via (0,1) using format s24_le/s32_le #3171
Description
Describe the bug
Input/output error when aplay via (0,1) using format s24_le/s32_le
After error occured all the pipeline can work
To Reproduce
1."sudo reboot" to reboot system
2.cd sof-test
3.cd test-case
4.export TPLG=sof-byt-nocodec.tplg
5.check-playback.sh -d 3 -l 1 -r 1 -F
Reproduction Rate
10/10
Expected behavior
No error occured
Impact
Input/output error when aplay via (0,1) using format s24_le/s32_le
ubuntu@jf-byt-mb-nocodec-1:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofnocodec [sof-nocodec], device 0: PCM (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: sofnocodec [sof-nocodec], device 1: PCM Deep Buffer (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
ubuntu@jf-byt-mb-nocodec-1:~$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: sofnocodec [sof-nocodec], device 0: PCM (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
No error dmesg,no error sof error trace
Environment
Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
Kernel: {sof-dev fa7850de}
SOF: {master:318dc9f7}
Name of the topology file
Topology: {sof-byt-nocodec.tplg }
Name of the platform(s) on which the bug is observed.
Platform: {BYT MB with nocodec}
sof-logger_0713.log
Activity
Liviali155 commentedon Jul 13, 2020
BYT_MB_RT5682 also has this issue
mengdonglin commentedon Jul 14, 2020
sof-byt-nocodec.tplg is created from "sof-cht-nocodec.m4", updated in #3080 to remove SRC for Baytrail and CherryTrail by @plbossart
lgirdwood commentedon Jul 14, 2020
@Liviali155 as @mengdonglin says lets reduce the BYT/CHT tests to reflect the new topologies.
plbossart commentedon Jul 14, 2020
we use the same pipe type of the two PCM devices, so not sure why one would support a format and not the other. This looks like a fundamental bug or a topology edit issue.
plbossart commentedon Jul 29, 2020
Can you retry with SOF PR ##3245
Thanks!
Liviali155 commentedon Jul 29, 2020
After applied #3245,issue still can be reproduced on BYT MB with nocodec
0729dmesg.log
sof-logger0729.log
plbossart commentedon Jul 29, 2020
@Liviali155 work-around suggested with #3257
Can you double-check the results? Also shouldn't this test be part of CI? It's been reporting no issues on this.
Liviali155 commentedon Jul 30, 2020
Tried with #3257,error not seen on byt-nocodec and byt-mb-rt5682
topology: bytcht: reduce deep-buffer to 5ms
slawblauciak commentedon Aug 10, 2020
@Liviali155 that change has been merged, good to close now?
plbossart commentedon Aug 10, 2020
I'd like to keep it for now, there's no rational explanation as to why reducing the period size solves the problem. I think we have more fundamental problem with scheduling.
slawblauciak commentedon Sep 15, 2020
@mengdonglin please assign it to somebody who maintains legacy platforms.
keqiaozhang commentedon Sep 15, 2020
Confirmed that this issue is not reproducible for a long time.
mengdonglin commentedon Sep 15, 2020
@plbossart @keqiaozhang Close this issue . We can monitor if this issue will happen again on BYT.
topology: imx8: reduce deep-buffer to 5ms for mixer component