Repository navigation
[BUG][MTL] S0ix long run failure, Firmware boot failure due to timeout (ROM status: 0x50000005, ROM error: 0x0) #7866
Copy link
Copy link
Closed
Labels
BootFirmware boot or code signing related.Firmware boot or code signing related.IMRRelated to IMR (Isolated Memory Region) on Intel platformsRelated to IMR (Isolated Memory Region) on Intel platformsIMR context saveIPC timeoutIPC timeout observedIPC timeout observedMTLApplies to Meteor Lake platformApplies to Meteor Lake platformP2Critical bugs or normal featuresCritical bugs or normal featuresbugSomething isn't working as expectedSomething isn't working as expectedmtl-005mtl-006suspend-resumeIssues observed when doing system suspend and resumeIssues observed when doing system suspend and resume
Description
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.
[ 352.971033] sof-audio-pci-intel-mtl 0000:00:1f.3: ipc timed out for 0x47000000|0x0
[ 352.979537] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ IPC dump start ]------------
[ 352.988991] sof-audio-pci-intel-mtl 0000:00:1f.3: Host IPC initiator: 0xc7000000|0x0|0x0, target: 0x67000000|0x0|0x0, ctl: 0x3
[ 353.001735] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ IPC dump end ]------------
[ 353.010979] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ DSP dump start ]------------
[ 353.020423] sof-audio-pci-intel-mtl 0000:00:1f.3: IPC timeout
[ 353.026868] sof-audio-pci-intel-mtl 0000:00:1f.3: fw_state: SOF_FW_BOOT_COMPLETE (7)
[ 353.035552] sof-audio-pci-intel-mtl 0000:00:1f.3: ROM status: 0xffffffff, ROM error: 0xffffffff
[ 353.045287] sof-audio-pci-intel-mtl 0000:00:1f.3: ROM debug status: 0x50000005, ROM debug error: 0x0
[ 353.055497] sof-audio-pci-intel-mtl 0000:00:1f.3: ROM feature bit not enabled
[ 353.063477] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ DSP dump end ]------------
[ 353.072721] sof-audio-pci-intel-mtl 0000:00:1f.3: ctx_save IPC error: -110, proceeding with suspend
[ 689.764439] sof-audio-pci-intel-mtl 0000:00:1f.3: GAIN (UUID: 61BCA9A8-18D0-4A18-8E7B-2639219804B7): No CPC match in the firmware file's manifest (ibs/obs: 768/768)
[ 692.922594] sof-audio-pci-intel-mtl 0000:00:1f.3: ipc timed out for 0x47000000|0x0
[ 692.931113] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ IPC dump start ]------------
[ 692.940571] sof-audio-pci-intel-mtl 0000:00:1f.3: Host IPC initiator: 0xc7000000|0x0|0x0, target: 0x67000000|0x0|0x0, ctl: 0x3
[ 692.953325] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ IPC dump end ]------------
[ 692.962576] sof-audio-pci-intel-mtl 0000:00:1f.3: ------------[ DSP dump start ]---------
cc:
- [BUG][MTL] HD-Audio playback IO error on Speakers #7990
- [mtl-005] pipeline: Ignore CPC value and use always the safe maximum #8007
- pipeline: register KCPS consumption and enable dynamic clock control #8019
- [BUG][MTL-005.0.3] ipc timedout on killing speaker pipeline aplay #8028
- [BUG][MTL] S0ix long run failure - timed out for 0x47000000 then kernel oops on page fault linux#4608
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BootFirmware boot or code signing related.Firmware boot or code signing related.IMRRelated to IMR (Isolated Memory Region) on Intel platformsRelated to IMR (Isolated Memory Region) on Intel platformsIMR context saveIPC timeoutIPC timeout observedIPC timeout observedMTLApplies to Meteor Lake platformApplies to Meteor Lake platformP2Critical bugs or normal featuresCritical bugs or normal featuresbugSomething isn't working as expectedSomething isn't working as expectedmtl-005mtl-006suspend-resumeIssues observed when doing system suspend and resumeIssues observed when doing system suspend and resume
Activity
marc-hb commentedon Jun 27, 2023
@RDharageswari can you please not ignore the entire bug template? It has a number of specific and important fields.
RDharageswari commentedon Jun 29, 2023
Hi Marc,
Sure.I am trying to get the exact scenario, hence did not update it right.Will update the entire configuration once available
mengdonglin commentedon Jul 27, 2023
@RDharageswari Can you still reproduce this issue with mtl-005.0.3 (Hot Fix 3) release?
RDharageswari commentedon Aug 14, 2023
@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
macchian commentedon Aug 16, 2023
@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?
macchian commentedon Aug 16, 2023
attach the crash logs.
kernel.20230815.094120.64594.txt
mengdonglin commentedon Aug 16, 2023
@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
tmleman commentedon Dec 22, 2023
@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.
tmleman commentedon Jan 11, 2024
@RDharageswari can you check if the issue still reproduces on the main branch?
lgirdwood commentedon Jan 11, 2024
@tmleman I guess we need a west update to pick up the Zephyr commit now its merged ?
tmleman commentedon Jan 19, 2024
@lgirdwood The patch I'm interested in has already been integrated. The kernel version in SOF has also been updated earlier.
abonislawski commentedon Jan 23, 2024
@macchian could you help in fix verification on main branch?
wszypelt commentedon Feb 9, 2024
Due to lack of response, reduces to P2
@RDharageswari Can you confirm that the issue no longer occurs?
wszypelt commentedon Apr 12, 2024
@RDharageswari Can you confirm that the issue no longer occurs?
wszypelt commentedon Jul 19, 2024
Due to the lack of response from the reporting person, I am closing the task