Repository navigation
[BUG][MTL] S0ix long run failure, Firmware boot failure due to timeout (ROM status: 0x50000005, ROM error: 0x0) #7866
Description
Activity
@RDharageswari can you please not ignore the entire bug template? It has a number of specific and important fields.
Hi Marc,
Sure.I am trying to get the exact scenario, hence did not update it right.Will update the entire configuration once availableReacted by Marc Herbert@RDharageswari Can you still reproduce this issue with mtl-005.0.3 (Hot Fix 3) release?
@mengdonglin: No reports of this in the recent days..But @yongzhi1 was able to repro this issue in the PnP set up with mtl-005-hotfix3 release
@mengdonglin , I also found the ipc time out during suspend resume test on customer MTL board.
The issue can be reproduced on fw branch mtl-005-drop-stable and mtl-005-hotfix3 as well.@yongzhi1 , I saw that your linux PR about page fault
ASoC: SOF: Intel: MTL: catch invalid IRQ IP ptr #4344
Is it relative to this?... <3>[ 124.809909] sof-audio-pci-intel-mtl 0000:00:1f.3: ipc timed out for 0x47000000|0x0 <3>[ 124.818406] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ IPC dump start ]------------ <3>[ 124.830259] sof-audio-pci-intel-mtl 0000:00:1f.3: Host IPC initiator: 0xc7000000|0x0|0x0, target: 0xe7000000|0x0|0x0, ctl: 0x3 <3>[ 124.856211] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ IPC dump end ]------------ <3>[ 124.874460] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ DSP dump start ]------------ <3>[ 124.893443] sof-audio-pci-intel-mtl 0000:00:1f.3: IPC timeout <3>[ 124.906717] sof-audio-pci-intel-mtl 0000:00:1f.3: fw_state: SOF_FW_BOOT_COMPLETE (7) <3>[ 124.924700] sof-audio-pci-intel-mtl 0000:00:1f.3: ROM status: 0xffffffff, ROM error: 0xffffffff <3>[ 124.944330] sof-audio-pci-intel-mtl 0000:00:1f.3: ROM debug status: 0x50000005, ROM debug error: 0x0 <3>[ 124.966038] sof-audio-pci-intel-mtl 0000:00:1f.3: ROM feature bit not enabled <3>[ 124.982946] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ DSP dump end ]------------ <4>[ 125.001601] sof-audio-pci-intel-mtl 0000:00:1f.3: ctx_save IPC error: -110, proceeding with suspend <1>[ 125.199974] BUG: unable to handle page fault for address: ffffbffbcb40001f <1>[ 125.207668] #PF: supervisor read access in kernel modeattach the crash logs.
kernel.20230815.094120.64594.txt@macchian @RDharageswari @yongzhi1 This issue seems similar to #7990 and #8028 that happens with mtl-005.0.3 when CPC-based clock selection and IMR context save are both enabled.
Now for main branch, IMR context save is already enabled and PR of CPC-based clock selection is under review #8019
We found on main branch, with both IMR context save and CPC-based clock selection (PR) enabled, we cannot reproduce #7990 and #8028. Please find details and recipe in #7990 (comment)
Maybe you can try this FW recipe of main branch as well?
Or you may try this kernel test PR #8007 with MTL-005.0.3 FW? This kernel PR will make FW always run at highest clock by always sending ZERO CPC values to FW?
74 remaining items
@lgirdwood @ujfalusi @RDharageswari I proposed a fix (pull request to Zephyr zephyrproject-rtos/zephyr#66135), it's one of many possible solutions. I encourage you to discuss it.
I don't have confirmation that this fix resolves this issue. I would need assistance in verifying this.
@RDharageswari can you check if the issue still reproduces on the main branch?
@RDharageswari can you check if the issue still reproduces on the main branch?
@tmleman I guess we need a west update to pick up the Zephyr commit now its merged ?
@lgirdwood The patch I'm interested in has already been integrated. The kernel version in SOF has also been updated earlier.
@macchian could you help in fix verification on main branch?
Due to lack of response, reduces to P2
@RDharageswari Can you confirm that the issue no longer occurs?@RDharageswari Can you confirm that the issue no longer occurs?
Due to the lack of response from the reporting person, I am closing the task
EDIT: the kernel part of this issue has been transferred to newer:
We see this error reported in multiple scenario:
One was long run S0ix testing.
cc: