-
Notifications
You must be signed in to change notification settings - Fork 43
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
Multicore PE test fail #411
Comments
Hello Pankaj, When multi-core is enabled, the same payload runs on all cores. The test status is marked as PASS if it succeeds on all cores; otherwise, it is marked as FAIL. Most PE tests are expected to run with multi-core enabled. If possible, could you please share the logs for further debugging? Additionally, could you confirm whether you are using a prebuilt image to run these tests or building it yourself, and specify if it is an ACPI or Device Tree platform? Regards, |
bsa_verbose.txt I am using prebuilt image @rajatgoyal47 |
Hello Pankaj, As per the logs, PE Index 1 seems to be always on even before ACS is running, due to this the payload is not running on PE Index 1 and the test is failing on PE Index 1. Regards, |
yes @rajatgoyal47 both PE is ON. |
If more than one core is already enabled, then this test case will not be valid. It is expected to fail since the same payload should be executed together. |
Hi, Is there a particular reason why multiple PEs (PE index 0 and 1) are ON in this case? Regards |
We have our requirement to enable multicore system. I mention that with single core mostly test are pass, so asking is ACS is only design to run in single core enable system? Br, |
Hi, Currently, the ACS enables secondary cores when tests need to be executed on multiple cores. Regards, |
We are encountering issues during PE testing. When testing with a single core, most tests pass. However, when testing with multi-core enabled, most PE tests fail. Is it recommended to enable only a single core? attaching result
The text was updated successfully, but these errors were encountered: