Skip to content
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 samples/boards/mec15xxevb_assy6853/power_management/ failed #28150

Closed
Zhaoningx opened this issue Sep 8, 2020 · 4 comments
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@Zhaoningx
Copy link
Collaborator

Describe the bug
running samples/boards/mec15xxevb_assy6853/power_management/, and the result just keep looping until the system hangs.

To Reproduce
Steps to reproduce the behavior:

west build -b mec15xxevb_assy6853 samples/boards/mec15xxevb_assy6853/power_management/
~/software/ci/tools/usbgpio_ftdi/pre_script.sh
west flash
~/software/ci/tools/usbgpio_ftdi/post_script.sh
see error

*** Booting Zephyr OS build v2.4.0-rc1-11-g8c3efc7be5fe ***
[00:00:00.005,279] pwrmgmt_test: PM single-thread test started for cycles: 5, logging: 0
[00:00:00.005,279] pwrmgmt_test: About to enter light sleep
Wake from Light Sleep
PM >
[00:00:01.507,293] pwrmgmt_test: About to enter deep Sleep
[00:00:01.507,843] pwrmgmt_test: PM sleep entry latency 0.000 seconds
Wake from Deep Sleep
PM <
Wake from Light Sleep
PM >
[00:00:04.610,229] pwrmgmt_test: PM sleep residency 3.103 seconds
[00:00:04.610,229] pwrmgmt_test: About to enter light sleep
[00:00:06.112,243] pwrmgmt_test: About to enter deep Sleep
[00:00:06.730,072] pwrmgmt_test: PM sleep entry latency 0.618 seconds
[00:00:06.730,072] pwrmgmt_test: Sleep entry latency is higher than expected
Wake from Deep Sleep
PM <
Wake from Light Sleep
PM >
[00:00:09.215,179] pwrmgmt_test: PM sleep residency 2.485 seconds
[00:00:09.215,179] pwrmgmt_test: About to enter light sleep
[00:00:10.717,193] pwrmgmt_test: About to enter deep Sleep
[00:00:11.335,021] pwrmgmt_test: PM sleep entry latency 0.617 seconds
[00:00:11.335,021] pwrmgmt_test: Sleep entry latency is higher than expected
Wake from Deep Sleep
PM <
Wake from Light Sleep
PM >
[00:00:13.820,129] pwrmgmt_test: PM sleep residency 2.486 seconds
[00:00:13.820,129] pwrmgmt_test: About to enter light sleep
[00:00:15.322,143] pwrmgmt_test: About to enter deep Sleep
[00:00:15.939,971] pwrmgmt_test: PM sleep entry latency 0.617 seconds
[00:00:15.939,971] pwrmgmt_test: Sleep entry latency is higher than expected
Wake from Deep Sleep
PM <
Wake from Light Sleep
PM >
.
.
.

Environment (please complete the following information):
OS: Fedora28
Toolchain: Zephyr-sdk-0.11.3
Commit ID: g8c3efc7be5fe

@Zhaoningx Zhaoningx added the bug The issue is a bug, or the PR is fixing a bug label Sep 8, 2020
@MaureenHelm MaureenHelm assigned dcpleung and unassigned dcpleung Sep 8, 2020
@MaureenHelm MaureenHelm added the priority: low Low impact/importance bug label Sep 8, 2020
@MaureenHelm
Copy link
Member

cc: @scottwcpg

@dcpleung
Copy link
Member

@albertofloyd I tried going back to the commit where the warning messages were introduced, and the sleep latency is about 0.650 seconds (which is higher then the 500ms threshold). Also I got PM state[0] counter being 6 instead 5. Just wondering if there is any special setup required for this this test.

@albertofloyd
Copy link
Collaborator

@dcpleung no special HW setup (other than debug pins indicated in the test case)
That discrepancy you observed is why I added the counters, intermittently the entry and exit do not match across kernel versions.
Regarding the latency that's a limitation on the system which sleep entry time is unbounded, even if all threads are stopped.
I filed this as an enhancement to guarantee a bounded time. #26889

@dcpleung
Copy link
Member

Regarding the sample (ignoring the latency and cycle counts), this is expected behavior. It runs 4 sets of scenarios, each repeating 5 times. So you will see repeating messages. After all these, it simply idles with nothing to do. So closing this as this is not a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants