-
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] ipc timed out for 0x13000004|GLB_SET_PIPELINE_STATE with multiple-pipeline-capture on TGLU_NOCODEC_IPC4 #7361
Comments
I think this has the same rootcause as #7191 (or at least this will mask 7191). I was trying to reproduce 7191 with current main, but I get a IPC timeout like the one here instead. I'll keep these as separate until we can prove these have the same rootcause. But as I can't repro 7191 without hitting this one first, assigning this to myself. |
I could now reproduce this with the reported steps. No DSP panic and no error in the firmware log prior to IPC timeout, so no clues yet on what is the cause. |
@keqiaozhang Does the issue only affect TGL? |
There's a fix now for #7191 . Let's see a few daily rounds whether this bug still occurs. Either this bug starts to appear again (i.e. it was masked by #7191), or it has been solved. I don't think the rootcause is the same as this bug spefifically happens around dmic start, while #7191 was related to smart-amp-test. |
@keqiaozhang Does the issue only affect TGL? |
This issue has not appeared in CI within three weeks. Closing it. |
This issue still exists in CI test. Reopening it. |
if the issue is not related to MTL, I lower the priority to P2 |
Found same issue with ADLP_RVP_NOCODEC_IPC4ZPH. multiple-pipeline-all failed in PCM27, DMIC0 RAW pipeline.
Intel internal daily test: |
We only observed this issue on TGL/ADL-IPC4 platforms, no reproductions on MTL, but the reproduce rate is high. After this issue occurs, the audio will be in a bad state, which will affect subsequent test cases. Changing the priority to P1. |
This issue also happens on MTL-NOCODEC platform: |
Potential fix: #7439 |
After #7439 merged, this is not reproducible for 3 consecutive daily tests. Good sign. |
@keqiaozhang please check if the issue still exists |
The reproduce rate of this issue is decreased, but I still encountered this issue once yesterday. |
@keqiaozhang @fredoh9 Potential fix that might solve the remaining failues in #7660 . Please report if you see ayny cases of this error with this PR merged. |
Observed this issue again in CI. Test ID:26591. mtrace
@kv2019i , please help to confirm if they are the same issue? |
@keqiaozhang The test case looks a bit different, in 26591, it's check-playback.sh while this bug (and 7191) have capture and playback concurrently (which led to the bug fixed in #7660 ). The mtrace log does look very similar to the original #7191. I think we can use #7191 still to follow this. |
Thanks for the confirmation. The original bug cannot be reproduced in CI. Let's close this bug. |
Describe the bug
Observed this issue in CI testing and only happened on TGLU_RVP_NOCODEC_IPC4ZPH so far. The reproduction rate >50%.
To Reproduce
~/sof-test/test-case/multiple-pipeline.sh -f c -l 50
Reproduction Rate
dmesg
mtrace
Environment
dmesg.txt
mtrace.txt
The text was updated successfully, but these errors were encountered: