-
Notifications
You must be signed in to change notification settings - Fork 318
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] FW reported error: 6 - Unknown error while processing the request when disabling a secondary core #8588
Comments
This issue can be reproduced manually and the reproduction rate is about 50%+ with stress test case. |
This issue seems to be a common issue with IMR context save DISABLED + multicore in latest code base. This issue is not only on mtl-007. It can also be reproduced on sof main branch if we disable IMR context save:
|
The problem seems to relate to multicore scenarios and error in powering down a secondary core. In the original mtrace:
In a more recent case (Intel test plan 35669):
|
Observed this issue on LNL-NOCODEC when testing multiple-pause-resume-50. Inner test ID:35712. |
@keqiaozhang does the problem also appear on mtl-006? |
@wszypelt we didn't observe this issue on mtl-006 |
@abonislawski @softwarecki any insights here ? Anything we can check in SW ? |
This issue also can be reproduced on SOF main branch. Inner test ID:36158. |
This is an old bug and can be reproduced two month ago although it is rare. I debug the issue and found that: the secondary core is in idle status with "waiti 0". Primary core calls arch_sched_ipi to wake up it but failed. Idc interrupt is not triggered on secondary core BTW I did stress test on TGL and didn't found this issue |
I was also debugging this one, main problem is very low reproduction rate, in the end primary core will fail on timeout because secondary core stays in idle didnt enter power-down flow. |
I have hit this a few times on (Onecloud) MTL RVP while debugging #8642. E.g. the bug also happens when running multiple-pipeline test. |
Now fixed with latest Zephyr update #8968 |
Describe the bug
I did a pre-test on mtl-007-drop-stable branch and found this issue when recording for a long time. The reproduction rate is unclear, I'm doing the manual check now.
dmesg
To Reproduce
~/sof-test/test-case/check-capture.sh -d 500 -l 1 -r 1
Reproduction Rate
50%+
Environment
dmesg.txt
mtrace.txt
The text was updated successfully, but these errors were encountered: