-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
mec15xxevb_assy6853: running tests/subsys/power/power_mgmt_soc failed #30192
Comments
The testcase worked well on zephyr version v2.3.0. The failure might be because of the code change in versions.
|
Yes, it might be a code change. You have to find the latest stable zephyr commit which worked well, and then investigate what code changes where did right after that causing an error. |
The testcase passed without failures by cherry-pick the testcase on top of the commit of the release of v2.4.0 on Sep.26. Then I used bisect between the cherry-pick commit and my merged commit #27733, which gave me this commit as the exact one that introduced the change causing the failure of this testcase. @andrewboie Can you look into this please? |
Test suite test_power_mgmt succeeded E: ***** USAGE FAULT ***** E: Illegal use of the EPSR E: r0/a1: 0x00000000 r1/a2: 0x00118598 r2/a3: 0x00118598 E: r3/a4: 0x00000000 r12/ip: 0x00000000 r14/lr: 0x000e246f E: xpsr: 0x60000000 E: Faulting instruction address (r15/pc): 0x00000014 E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0 E: Current thread: 0x00118598 (main) E: Halting system Fixes: zephyrproject-rtos#30192 Signed-off-by: Flavio Ceolin <[email protected]>
Test suite test_power_mgmt succeeded E: ***** USAGE FAULT ***** E: Illegal use of the EPSR E: r0/a1: 0x00000000 r1/a2: 0x00118598 r2/a3: 0x00118598 E: r3/a4: 0x00000000 r12/ip: 0x00000000 r14/lr: 0x000e246f E: xpsr: 0x60000000 E: Faulting instruction address (r15/pc): 0x00000014 E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0 E: Current thread: 0x00118598 (main) E: Halting system Fixes: #30192 Signed-off-by: Flavio Ceolin <[email protected]>
This has not been fixed. See the latest log on micro chip below:
|
That is not the same error message, I'd used |
@maksimmasalski could you re-run the test with that option to see if you get rid of the fault? |
Here's the log after changing idle stack size to 2048. It just seems it's not a once-for-all solution. Build log
|
that is a different problem, let me look it. This one seems to be a real issue and not only a stack overflow |
This is no longer a failure since 0ba9437. |
Describe the bug
test_pm_multithread
andtest_pm_singlethread
fail, Assertion failed in both cases.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Test must pass.
Impact
Power Management issue.
Logs and console output
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: