Repository navigation
[BUG][IPC4] various IPC errors on TGLU_UP_HDA_IPC4ZPH when testing multiple-pipeline-all #6466
Description
Describe the bug
We Observed some different IPC times out on TGLU_UP_HDA_IPC4ZPH when testing multiple-pipeline-all.
if you run multiple-pipeline-all several times, you will get the following different IPC errors:
- ipc timed out for 0x12070000|0x0 GLB_DELETE_PIPELINE
- ipc error for msg 0x13050003|0x0,FW reported error: 6 - Unknown error while processing the request
- FW reported error: 104 - Other failure of module instance initialization request,ipc error for msg 0x40070004|0x70015
- ipc timed out for 0x13070002|0x0 GLB_SET_PIPELINE_STATE
- FW reported error: 7 - Unsupported operation requested, ipc error for msg 0x130a0004|0x0
- ipc timed out for 0x46010002|0x1000003 MOD_UNBIND
To Reproduce
~/sof-test/test-case/multiple-pipeline.sh -f p -c 20 -l 25
Reproduction Rate
100%
Environment
Kernel Branch: topic/sof-dev 7d2d29c3fc54
SOF Branch: main adce54445012
Zephyr Commit: zephyr-v3.2.0-441-ged661a6c6909
Platform: TGLU_UP_HDA_IPC4ZPH
TPLG
Activity
lgirdwood commentedon Oct 24, 2022
@keqiaozhang does this test work if we remove mixout pipelines ? i.e. we just keep the passthrough pipelines
lyakh commentedon Oct 25, 2022
@keqiaozhang sorry, I don't understand this report. It lists 5 different errors, of which we've just close several as "fixed," you say "run multiple-pipeline-all several times" and the reproduction rate is 100%. Could you clarify?
lgirdwood commentedon Oct 25, 2022
@keqiaozhang Can we split this to a GH BUG per open issue above ?
keqiaozhang commentedon Oct 31, 2022
@lgirdwood and @lyakh
One week ago, there're various 'IPC errors ' on HDA platform when testing with multiple-pipeline-all, the error types are different each time. I didn't want to cause unnecessary panic by submitting so many bugs for one case. So I merged all errors in one bug.
But now almost all errors have been fixed, so I did a stress test this morning for this case and only observed one type of IPC times error, I have submitted a new bug #6503 to track that issue. The bug can be closed now.