-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] [stable-v2.2] [NOCODEC] ERROR pipeline_comp_reset(): failed to recover (multiple-pipeline-all) #9135
Comments
Exact same multi pipeline tests failing exactly the same in the same configuration in the daily test run of the next day (test run 41235) EDIT: and again in 41277. 100% deterministic. |
SOF error logs
|
Impact only on no_codec topology so correct at P3. |
Maybe we can "reduce" these two NOCODEC topologies a little bit to silence the constant and distracting failure noise? |
Yes - for stable 2.2 we should only be testing kernel updates on real user configurations. Lets disable and not delete nocodec, as it could be useful as a means to debug. |
Describe the bug
On ADLP_RVP_NOCODEC-ipc3 and APL_UP2_NOCODEC-ipc3, using all pipeline concurrently prints this error repeatedly.
EDIT: some error in some TWL configurations.
This error is likely old, discovered only now thanks to:
Example from daily test run:
41199?model=APL_UP2_NOCODEC-ipc3&testcase=multiple-pipeline-all-50
Same error message in:
41199?model=APL_UP2_NOCODEC-ipc3&testcase=multiple-pause-resume-25
41199?model=ADLP_RVP_NOCODEC-ipc3&testcase=multiple-pipeline-playback-50
41199?model=ADLP_RVP_NOCODEC-ipc3&testcase=multiple-pause-resume-25
41199?model=ADLP_RVP_NOCODEC-ipc3&testcase=multiple-pipeline-all-50
To Reproduce
Reproduction Rate
100%?
Environment
Start Time: 2024-05-16 16:26:28 UTC
End Time: 2024-05-16 19:23:14 UTC
Linux Build Result: 1847
Linux Branch: topic/sof-dev
Linux Commit: 055cba4766af
KConfig Branch: master
KConfig Commit: 8fee06f8fd8a
SOF Branch: stable-v2.2
SOF Commit: 64416ba51354
Screenshots or console output
The text was updated successfully, but these errors were encountered: