-
Notifications
You must be signed in to change notification settings - Fork 349
Closed
Labels
APLApplies to Apollolake platformApplies to Apollolake platformIntel Linux Daily testsThis issue can be found in internal Linux daily testsThis issue can be found in internal Linux daily testsP1Blocker bugs or important featuresBlocker bugs or important featuresbugSomething isn't working as expectedSomething isn't working as expectedxrunXRUN is observed and firmware may not recoverXRUN is observed and firmware may not recover
Milestone
Description
Describe the bug
The pcm512x topology hasn't been tested by CI for some time. Having re-added it to daily tests, pause-resume tests showed a regression. It is supposedly related to that topology's non-traditional mixer placement in the pipeline and to recent changes in trigger processing.
To Reproduce
TPLG=/lib/firmware/intel/sof-tplg/sof-apl-pcm512x.tplg MODEL=APL_UP2_PCM512X sof-test/test-case/check-pause-resume.sh -c 100 -m playback
or
TPLG=/lib/firmware/intel/sof-tplg/sof-apl-pcm512x.tplg MODEL=APL_UP2_PCM512X ~/sof-test/test-case/multiple-pause-resume.sh -r 50
Reproduction Rate
Seems easy enough to reproduce. E.g. at the above link it happened on 18th / 19th iteration
Expected behavior
pipelines with embedded forking components like mixers should work too.
Impact
This is also relevant for QuickBuild CI tests
Environment
- Branch name and commit hash of the 2 repositories: sof (firmware/topology) and linux (kernel driver).
- Kernel: sof-dev
- SOF: main
- Name of the topology file
- Topology: sof-apl-pcm512x.tplg
- Name of the platform(s) on which the bug is observed.
- Platform: UP2
Metadata
Metadata
Assignees
Labels
APLApplies to Apollolake platformApplies to Apollolake platformIntel Linux Daily testsThis issue can be found in internal Linux daily testsThis issue can be found in internal Linux daily testsP1Blocker bugs or important featuresBlocker bugs or important featuresbugSomething isn't working as expectedSomething isn't working as expectedxrunXRUN is observed and firmware may not recoverXRUN is observed and firmware may not recover