-
Notifications
You must be signed in to change notification settings - Fork 314
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][Multi-core] ipc timed out for 0x13000004|0x1GLB_SET_PIPELINE_STATE when testing non-core 0 pipeline on MTL-NOCODEC #7649
Comments
Multi-core fix added to 005, it should cover case when several pipelines used on a single secondary core. |
This issue is still reproducible on latest mtl-005/ddc2ef6. But it won't fail immediately and the errors are also changed.
|
This is not the same issue, just another one |
Probably now we hit this one |
I checked this issue again today and found that this issue only happened at the first/second round of test after system reboot. But this issue cannot be reproduced after reloading kmod,
|
Verified today with latest 005 version. Right now it can hit another issue, aplay -Dhw:0,1 is working fine one by one but (as @keqiaozhang advised) we can add delay and break it.
and restore when we start another aplay, core 1 will be powered up successfully but hit timeout on the first IPC (create pipeline). I think this is already third issue in this thread so it would be great to close this and open another one for D3 restore scenario. @mengdonglin FYI: IMR context save is enabled only on 005, thats why it can behave differently on main branch. |
Reproduced the issue, checked sof main branch with my 2 modified PRs:
|
The root cause of the issue is that IDC interrupt was not re-enabled after exiting D3. |
This issue has been fixed on latest mtl-005 branch, closing it. |
Describe the bug
Testing mtl-005-stable-drop branch on MTL-NOCODEC platform with multi-core tplg, but all non-core0 pipelines failed the test with IPC times out. The reproduce rate is 100%.
DMESG
TPLG
To Reproduce
$ aplay -Dhw:0,1 -r 48000 -c 2 -f S16_LE -d 3 /dev/zero -v -q
or
$ aplay -Dhw:0,2 -r 48000 -c 2 -f S16_LE -d 3 /dev/zero -v -q
Reproduction Rate
100%
Environment
dmesg.txt
mtrace.txt
The text was updated successfully, but these errors were encountered: