Repository navigation
[BUG][mtl-006] ipc timed out for 0x47000000|MOD_SET_DX on MTL secondary cores #8155
Description
Activity
- addedbugSomething isn't working as expectedSomething isn't working as expectedP1Blocker bugs or important featuresBlocker bugs or important featuresIPC timeoutIPC timeout observedIPC timeout observedmulticoreIssues observed when not only core#0 is used.Issues observed when not only core#0 is used.MTLApplies to Meteor Lake platformApplies to Meteor Lake platform
on Sep 5, 2023 - changed the title
[-][BUG][mtl-006] ipc timed out for 0x47000000|MOD_SET_DX on MTL multicore platform[/-][+][BUG][mtl-006] ipc timed out for 0x47000000|MOD_SET_DX on MTL secondary cores[/+]on Sep 5, 2023 serhiy-katsyuba-intel commented
on Sep 6, 2023 ContributorMore actionsLooks like this issue was fixed yesterday by this commit fa1572c
Without such commit I also reproduce timeout (due to failed assert in Zephyr scheduler code) on Windows test test_113_02_simple_internal_loopback_run_slave_core_during_transfer[48000Hz_16in16bit_2ch-ssp_0_to_ssp_0] when switching off core 1. That commit fixes the problem.
@keqiaozhang , could you retest once again using latest firmware from mtl-006-drop-stable branch?
cc @tmleman
this issue is still easily reproducible with either bba6300c0d33( checked in 8 hours ago) or 202439ebf443 (checked in 1day 8 hours ago)
@fredoh9 Thank you for testing the updates!
@serhiy-katsyuba-intel @tmleman Rander ported 2 multi-core fixes from main branch to mtl-006-drop-stable: #8179 can you please review?
- addedFix SubmittedFix has been submitted, to be fully verifiedFix has been submitted, to be fully verified
on Sep 8, 2023 #8155 cannot be reproduced on main branch (IMR context save enabled by default), but can still be reproduced on mtl-006-drop-stable with multi-core IPC time out fixes PR #8179
Please find more info in #8179 (comment)- removedFix SubmittedFix has been submitted, to be fully verifiedFix has been submitted, to be fully verified
on Sep 8, 2023 @serhiy-katsyuba-intel Confirmed that this issue cannot be reproduced on tip main branch 9ccfbc4 with IMR context save disabled (by setting CONFIG_ADSP_IMR_CONTEXT_SAVE=n in PR #8156)
@mengdonglin @keqiaozhang this is timing issue, works fine on HPRO (main & mtl-006) but fails when lowest clock in use, please verify if it works now on mtl-006, based on my tests it should be fixed (commit af4554dfdb66 )
We have easy way to reproduce this. yes, it looks working fine with latest mtl-006-stable-drop ( 37bd281 ). Already started longer test plan for mtl-006. Will update when the test is finished
@abonislawski,this issue cannot be reproduced on tip mtl-006 branch.
- addedMOD_SET_DXIssue related to IPC MOD_SET_DXIssue related to IPC MOD_SET_DX
on Jan 3, 2024
Describe the bug
Observed this issue on MTL-006 branch, it happens when testing the playback pipeline on secondary cores. The reproduce rate is 100%, very easy to reproduce it.
dmesg
To Reproduce
Test the playback on secondary cores (hw:0,1 is on core#1, hw:0,2 is on core#2)
aplay -Dhw:0,1 -r 48000 -c 2 -f S16_LE -d 3 /dev/zero -v -q
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