You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] glitch in test 02_02_TestPtpSimpleLoopbackMasterRecord16000Hz32b32b4ch #4080
Describe the bug
Glitch was found in test 02_02_TestPtpSimpleLoopbackMasterRecord16000Hz32b32b4ch
Playback pipeline is connected to slave SSP, capture pipeline is connected to master SSP.
This image can be a little bit confusing as "Host plb" and "Host cap" component are a part of pipelines (test documentation needs a fix). Regarding buffers: buffers shown on topology are buffers that are explicitly created by test logic by IPC "TplgBuffNew" but as far as I know one another buffer is being created implicitly by FW for data from host DMA - those buffers are not included in tests topology drawings. Please correct me if I'm wrong.
Align these under one issue and mark the others as duplicates, they all seem to show repeated or skipped samples which is usually indicative of races between DMA and DSP buffer IO.
Duplicate these failures using an existing upstream topology as its difficult to reproduce for developers who do not have access to HW with the slim test framework.
Glitch was found also in test where playback pipeline is connected to master SSP, capture pipeline is connected to slave SSP (02_01_TestPtpSimpleLoopbackMasterPlayback48000Hz32b32b4ch).
Reproduction rate: 2/75.
@kkarask we think we may be getting closer to why the python driver and the no_codec CI devices are showing some issues as more reproducible. Python driver and no codec mode are probably sending IPCs for some sequences faster that the kernel driver in codec mode (as codec mode means lots of slow & blocking I2C IO with codecs).
Can you rerun the test with #4471 locally merged and let us know if there are any changes to above result with Python driver. @mwasko fyi.
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.
Activity
lgirdwood commentedon Apr 27, 2021
@wszypelt @zrombel Not sure if we can use the same buffer for both host and DAI DMA - please confirm if topology diagram is correct.
zrombel commentedon Apr 27, 2021
As I mentioned in #4076:
wszypelt commentedon May 11, 2021
The same issue at the same reproduction appears in test
02_01_TestPtpSimpleLoopbackMasterPlayback16000Hz32b32b4ch
lgirdwood commentedon May 12, 2021
@zrombel @kkarask @wszypelt @XiaoyunWu6666 @keqiaozhang @keyonjie @slawblauciak fwiw we are seeing a lot of glitches being reported recently in various loopback tests.
Can we do the following here
lgirdwood commentedon May 13, 2021
Duplicate of simpler #4076
kkarask commentedon Jul 20, 2021
Glitch was found also in test where playback pipeline is connected to master SSP, capture pipeline is connected to slave SSP (02_01_TestPtpSimpleLoopbackMasterPlayback48000Hz32b32b4ch).
Reproduction rate: 2/75.
lgirdwood commentedon Jul 21, 2021
@kkarask we think we may be getting closer to why the python driver and the no_codec CI devices are showing some issues as more reproducible. Python driver and no codec mode are probably sending IPCs for some sequences faster that the kernel driver in codec mode (as codec mode means lots of slow & blocking I2C IO with codecs).
Can you rerun the test with #4471 locally merged and let us know if there are any changes to above result with Python driver.
@mwasko fyi.
kkarask commentedon Jul 22, 2021
@lgirdwood I rerun tests on #4471 and tests passed, but problem can still exists because reproduction rate is not high. See also related issue: #4180
lgirdwood commentedon Jul 22, 2021
Thanks @kkarask, do you mean that #4471 decreases the reproduction rate ? if so by how much ?
kkarask commentedon Jul 23, 2021
@lgirdwood yes, it looks like reproduction rate was decreased. After run 3000 tests result is 0.001% fail.
lgirdwood commentedon Jul 23, 2021
@lyakh fyi
github-actions commentedon Jun 19, 2025
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.