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

kernel: timer: timer_behavior: kernel.timer.timer fails #83268

Open
katgiadla opened this issue Dec 20, 2024 · 0 comments
Open

kernel: timer: timer_behavior: kernel.timer.timer fails #83268

katgiadla opened this issue Dec 20, 2024 · 0 comments
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: nRF Nordic nRFx priority: low Low impact/importance bug

Comments

@katgiadla
Copy link
Collaborator

katgiadla commented Dec 20, 2024

Describe the bug
The test tests/kernel/timer/timer_behavior/kernel.timer.timer fails.

Observed for:

  • nrf54l15dk/nrf54l05/cpuapp
  • nrf54l15dk/nrf54l15/cpuapp

To Reproduce
Steps to reproduce the behavior:

  1. have nrf54l15dk/nrf54l15/cpuapp connected
  2. go to your zephyr dir
  3. call ./scripts/twister -s kernel.timer.timer -p nrf54l15dk/nrf54l15/cpuapp --device-testing --device-serial /dev/ttyACM1 -v --inline-logs --west-flash="--erase"
  4. See console output with error

Expected behavior
Valid console output

Impact
Not clear

Logs and console output

===================================================================
START - test_one_tick_timer_train
Initializing 4 Timers, Tick Rate 31250Hz, Expecting 78125 callbacks in 11000 ms
Starting Timers with Skews
Faking busy work, remaining timers is 4, timer callbacks 2
Faking busy work, remaining timers is 4, timer callbacks 6197
Faking busy work, remaining timers is 4, timer callbacks 12396
Faking busy work, remaining timers is 4, timer callbacks 18592
Faking busy work, remaining timers is 4, timer callbacks 24790
Faking busy work, remaining timers is 4, timer callbacks 30983
Faking busy work, remaining timers is 4, timer callbacks 37178
Faking busy work, remaining timers is 4, timer callbacks 43377
Faking busy work, remaining timers is 4, timer callbacks 49574
Faking busy work, remaining timers is 4, timer callbacks 55771
Faking busy work, remaining timers is 4, timer callbacks 61969
Faking busy work, remaining timers is 4, timer callbacks 68169
Faking busy work, remaining timers is 4, timer callbacks 74363
One Tick Timer Train Done, took 10099 ms, busy loop ran 13 times
    Perfect delta 128 cycles or 128 us
Timer 0 max delta 129 cycles or 129 us, 0 late callbacks (0.0%)
RECORD: {"testcase":"one_tick_timer_train", "timer":0, "max_delta_cycles":129, "max_delta_us":129, "late_callbacks":0, "perfect_delta_cycles":128, "perfect_delta_us":128, "train_time_ms":10099, "busy_loops":13, "timers":4, "expected_callbacks":78125, "expected_time_ms":11000, "CONFIG_SYS_CLOCK_TICKS_PER_SEC":31250}
Timer 1 max delta 129 cycles or 129 us, 0 late callbacks (0.0%)
RECORD: {"testcase":"one_tick_timer_train", "timer":1, "max_delta_cycles":129, "max_delta_us":129, "late_callbacks":0, "perfect_delta_cycles":128, "perfect_delta_us":128, "train_time_ms":10099, "busy_loops":13, "timers":4, "expected_callbacks":78125, "expected_time_ms":11000, "CONFIG_SYS_CLOCK_TICKS_PER_SEC":31250}
Timer 2 max delta 129 cycles or 129 us, 0 late callbacks (0.0%)
RECORD: {"testcase":"one_tick_timer_train", "timer":2, "max_delta_cycles":129, "max_delta_us":129, "late_callbacks":0, "perfect_delta_cycles":128, "perfect_delta_us":128, "train_time_ms":10099, "busy_loops":13, "timers":4, "expected_callbacks":78125, "expected_time_ms":11000, "CONFIG_SYS_CLOCK_TICKS_PER_SEC":31250}
Timer 3 max delta 129 cycles or 129 us, 0 late callbacks (0.0%)
RECORD: {"testcase":"one_tick_timer_train", "timer":3, "max_delta_cycles":129, "max_delta_us":129, "late_callbacks":0, "perfect_delta_cycles":128, "perfect_delta_us":128, "train_time_ms":10099, "busy_loops":13, "timers":4, "expected_callbacks":78125, "expected_time_ms":11000, "CONFIG_SYS_CLOCK_TICKS_PER_SEC":31250}
!! The busy loop didn't run as much as expected.
!! Consider making CONFIG_SYS_CLOCK_TICKS_PER_SEC smaller.

    Assertion failed at zephyr/tests/kernel/timer/timer_behavior/src/tick_timer_train.c:180: timer_tick_train_test_one_tick_timer_train: (busy_loops > acceptable_busy_loops is false)
Expected thread to run while 1 tick timers are firing
 FAIL - test_one_tick_timer_train in 10.286 seconds
===================================================================
TESTSUITE timer_tick_train failed.

Environment (please complete the following information):

  • OS: Ubuntu 20.04.1 LTS
  • Toolchain: Zephyr SDK 0.17.0
  • Commit SHA or Version used: v4.0.0-2414-g73af32

Addtional information
Probably introduced by 3543592

@katgiadla katgiadla added bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug platform: nRF Nordic nRFx labels Dec 20, 2024
@github-project-automation github-project-automation bot moved this to To triage in nRF platform Dec 20, 2024
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 platform: nRF Nordic nRFx priority: low Low impact/importance bug
Projects
Status: To triage
Development

No branches or pull requests

3 participants