You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] [MTL] set pipeline state returned error when running RTC AEC on secondary core #8024
changed the title [-][BUG] [MTL] failed to run RTC AEC capture on secondary core[/-][+][BUG] [MTL] set pipeline state returned error when running RTC AEC on secondary core[/+]on Aug 11, 2023
This is one kinds of IPC timed out tracked by #7774 with multi-core , seems to be a duplicate .
If I remove google-rtc-aec.18.1 from the pipeline, then the issue is not reproducible, otherwise it's 100%, so there seems to be a very specific reason.
The issue is no longer reproducible due to another issue. Now (with kernel from August 21) running arecord on AEC capture fails on driver side, driver does not even send any IPC to firmware:
[ 929.217962] sof-audio-pci-intel-mtl 0000:00:1f.3: Init input audio formats for google-rtc-aec.18.1
[ 929.217964] sof-audio-pci-intel-mtl 0000:00:1f.3: Pin index #0: 48000Hz, 16bit (ch_map 0xffffff10 ch_cfg 1 interleaving_style 0 fmt_cfg 0x1002) buffer size 192
[ 929.217966] sof-audio-pci-intel-mtl 0000:00:1f.3: RTC_AEC (UUID: B780A0A6-269F-466F-B477-23DFA05AF758): No mod_cfg available for CPC lookup in the firmware file's manifest (ibs/obs: 192/192)
[ 929.236913] sof-audio-pci-intel-mtl 0000:00:1f.3: google-rtc-aec.18.1: ibs / obs / cpc: 192 / 192 / 0
[ 929.236914] sof-audio-pci-intel-mtl 0000:00:1f.3: input pin 1 format not found for google-rtc-aec.18.1
[ 929.247315] sof-audio-pci-intel-mtl 0000:00:1f.3: failed to prepare widget google-rtc-aec.18.1
[ 929.256941] sof-audio-pci-intel-mtl 0000:00:1f.3: Failed to prepare connected widgets
[ 929.265691] sof-audio-pci-intel-mtl 0000:00:1f.3: error: failed widget list set up for pcm 27 dir 1
[ 929.275799] sof-audio-pci-intel-mtl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[ 929.287718] DMIC0 RTC AEC: ASoC: error at __soc_pcm_hw_params on DMIC0 RTC AEC: -22
[ 929.296374] DMIC0 RTC AEC: ASoC: error at dpcm_fe_dai_hw_params on DMIC0 RTC AEC: -22
Maybe we have missing Input Pin 1 format description in manifest? Somethere on start in dmesg (note, Pin index #0 is present 2 times but no Pin index # 1):
@RanderWang , @yongzhi1 , can you check if AEC component input pin 1 description is correct (is present) in manifest? Or maybe you have any idea why recent driver is complaining for missing input pin 1 format of AEC?
Thanks! yong. the PR was thesofproject/rimage#125, but too many requirement can't be supported and it was only a example for AEC, so closed it. Now chrome team are working on it so @yongzhi1 you can submit one.
The problem is caused by one of the components was created with extension.r.proc_domain == COMP_PROCESSING_DOMAIN_DP.
DP scheduling is NOT supported on mtl-005-drop-stable branch. Sadly, there is no clear error message when trying to use DP scheduling but just crash. That crash resulted in IPC timeout.
The problem is in mtl.toml. domain_types = "1" is specified for RTC_AEC component. That parameter selects type of processing: 0 for LL, 1 for DP. Modifying domain_types to "0" solves the problem.
Activity
[-][BUG] [MTL] failed to run RTC AEC capture on secondary core[/-][+][BUG] [MTL] set pipeline state returned error when running RTC AEC on secondary core[/+]yongzhi1 commentedon Aug 11, 2023
Cherry-picked #8000 to get new mtrace for more insight:
mtrace-echo-core1.txt
The issue is not reproducible if google-rtc-aec.18.1 being removed from the connection:
cc @abonislawski @lgirdwood @RanderWang
RanderWang commentedon Aug 14, 2023
We have observed various IPC timeout with multi-core even with normal playback, especially if we disable mtrace output.
#7774 (comment)
yongzhi1 commentedon Aug 14, 2023
The error is slightly different than #7774 though, in this case:
yongzhi1 commentedon Aug 17, 2023
cc @serhiy-katsyuba-intel
mengdonglin commentedon Aug 21, 2023
This is one kinds of IPC timed out tracked by #7774 with multi-core , seems to be a duplicate .
yongzhi1 commentedon Aug 21, 2023
If I remove google-rtc-aec.18.1 from the pipeline, then the issue is not reproducible, otherwise it's 100%, so there seems to be a very specific reason.
abonislawski commentedon Aug 22, 2023
Please verify if this will work with IMR context restore disabled (or just before first suspend)
serhiy-katsyuba-intel commentedon Aug 22, 2023
The issue is no longer reproducible due to another issue. Now (with kernel from August 21) running arecord on AEC capture fails on driver side, driver does not even send any IPC to firmware:
In dmesg:
Maybe we have missing Input Pin 1 format description in manifest? Somethere on start in dmesg (note, Pin index #0 is present 2 times but no Pin index # 1):
Tested with firmware build from mtl-005-drop-stable branch with enabled
with this rimage manifest commit RanderWang/rimage@bbdbf09
and topology from PR build #8050.
@RanderWang , @yongzhi1 , can you check if AEC component input pin 1 description is correct (is present) in manifest? Or maybe you have any idea why recent driver is complaining for missing input pin 1 format of AEC?
yongzhi1 commentedon Aug 22, 2023
Hi, @serhiy-katsyuba-intel , the input pin 1 is defined here:
RanderWang/rimage@bbdbf09#diff-7d97bf1f90e10dc1f06355450d648d5dcd03b8010aaad7101077fe54611012d6R503
For the ACE use case, playback needs to be started first, followed by EchoRef, then "DMIC0 RTC AEC" at last, did you try in that order? thanks,
RanderWang commentedon Aug 23, 2023
Thanks! yong. the PR was thesofproject/rimage#125, but too many requirement can't be supported and it was only a example for AEC, so closed it. Now chrome team are working on it so @yongzhi1 you can submit one.
serhiy-katsyuba-intel commentedon Aug 25, 2023
The problem is caused by one of the components was created with extension.r.proc_domain == COMP_PROCESSING_DOMAIN_DP.
DP scheduling is NOT supported on mtl-005-drop-stable branch. Sadly, there is no clear error message when trying to use DP scheduling but just crash. That crash resulted in IPC timeout.
serhiy-katsyuba-intel commentedon Aug 25, 2023
The problem is in mtl.toml. domain_types = "1" is specified for RTC_AEC component. That parameter selects type of processing: 0 for LL, 1 for DP. Modifying domain_types to "0" solves the problem.
cc: @RanderWang , @abonislawski .