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
Description:
Simultaneous playback and capture on external loopback (same SSP) with signal amplitude verification.
Playback pipeline contains volume component.
Volume gain is explicitly set to 1 before playback starts.
To Reproduce
Run tests with diagnostic driver
with argument: --playback_iterations=2
03_00_TestVolumeSimple8000Hz16b16b1ch
Reproduction Rate
100%
Environment
Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
@wszypelt@kfrydryx is this only reproducing with the loopback ? What happens if gain is NOT set prior to test. The DEAD code is an assert(). @lyakh can you take a look at this, thanks !
@lyakh@kfrydryx@lgirdwood
Issue still reproducing, with playback iteration > 1. In CI we test all tests with playback_iteration = 1. Therefore, it does not show this issue. We perform stress tests every two weeks.
@lyakh@kfrydryx@lgirdwood
Issue still reproducing, with playback iteration > 1. In CI we test all tests with playback_iteration = 1. Therefore, it does not show this issue. We perform stress tests every two weeks.
Ok, so the Linux CI will test multiple times, but I dont think it uses the loopback mode above. @fredoh9 can you confirm if we have a similar loopback test in the Jenkins CI ?
Activity
lgirdwood commentedon Jul 21, 2022
@ranj063 module adapter related ?
kfrydryx commentedon Aug 2, 2022
Still reproducing. Bisect points to module adapter - first bad commit f7663de.
lgirdwood commentedon Aug 2, 2022
@wszypelt @kfrydryx is this only reproducing with the loopback ? What happens if gain is NOT set prior to test. The DEAD code is an assert().
@lyakh can you take a look at this, thanks !
lyakh commentedon Aug 15, 2022
@wszypelt can this still be reproduced? But this test isn't in the standard CI, so we don't see it in PR testing?
wszypelt commentedon Aug 22, 2022
@lyakh @kfrydryx @lgirdwood
Issue still reproducing, with playback iteration > 1. In CI we test all tests with playback_iteration = 1. Therefore, it does not show this issue. We perform stress tests every two weeks.
lgirdwood commentedon Aug 24, 2022
Ok, so the Linux CI will test multiple times, but I dont think it uses the loopback mode above. @fredoh9 can you confirm if we have a similar loopback test in the Jenkins CI ?
module: set state to INITIALIZED after reset
module_adapter: volume: set state to INITIALIZED after reset