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

intel_adsp_cavs15: running testcases failed tests/kernel/workq/work on adsp #33898

Closed
KangJianX opened this issue Mar 31, 2021 · 0 comments · Fixed by #33930
Closed

intel_adsp_cavs15: running testcases failed tests/kernel/workq/work on adsp #33898

KangJianX opened this issue Mar 31, 2021 · 0 comments · Fixed by #33930
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@KangJianX
Copy link
Collaborator

Describe the bug
tests/kernel/workq/work run failed on adsp

To Reproduce
Steps to reproduce the behavior:

  1. twister -p intel_adsp_cavs15 --device-testing -T tests/kernel/workq/work --west-flash="/home/ztest/work/zephyrproject/zephyr/boards/xtensa/intel_adsp_cavs15/tools/flash.sh,/home/ztest/work/zephyrproject/modules/audio/sof/keys/otc_private_key.pem,/home/ztest/work/zephyrproject/modules/audio/sof/zephyr/ext/rimage/config,/home/ztest/work/zephyrproject/modules/audio/sof/zephyr/ext/rimage/build/rimage" --device-serial-pty="/home/ztest/work/zephyrproject/zephyr/boards/xtensa/intel_adsp_cavs15/tools/adsplog.py,--no-history"
  2. See error

Expected behavior
testcases can pass.

Logs and console output
START - test_smp_running_cancel
PASS - test_smp_running_cancel in 0.101 seconds
...................................................................................................................................................................................................................
START - test_drain_empty
PASS - test_drain_empty in 0.1 seconds
...................................................................................................................................................................................................................
START - test_1cpu_drain_wait
PASS - test_1cpu_drain_wait in 0.202 seconds
...................................................................................................................................................................................................................
START - test_1cpu_plugged_drain
PASS - test_1cpu_plugged_drain in 0.102 seconds
...................................................................................................................................................................................................................
START - test_1cpu_basic_schedule
PASS - test_1cpu_basic_schedule in 0.102 seconds
...................................................................................................................................................................................................................
START - test_1cpu_basic_schedule_running
ASSERTION FAIL [arch_mem_coherent(to)] @ WEST_TOPDIR/zephyr/kernel/timeout.c:90
@ WEST_TOPDIR/zephyr/lib/os/assert.c:45

Environment (please complete the following information):

  • OS: Fedora28
  • Toolchain: Zephyr-sdk-0.12.3
  • Commit id: 59a3def
@KangJianX KangJianX added the bug The issue is a bug, or the PR is fixing a bug label Mar 31, 2021
@galak galak added the priority: low Low impact/importance bug label Mar 31, 2021
@dcpleung dcpleung assigned andyross and unassigned dcpleung Mar 31, 2021
andyross pushed a commit to andyross/zephyr that referenced this issue Mar 31, 2021
Shared data can't live on thread stacks if they are incoherent.  These
are all just per-test-case data, so make them static.

Fixes zephyrproject-rtos#33898

Signed-off-by: Andy Ross <[email protected]>
nashif pushed a commit that referenced this issue Apr 2, 2021
Shared data can't live on thread stacks if they are incoherent.  These
are all just per-test-case data, so make them static.

Fixes #33898

Signed-off-by: Andy Ross <[email protected]>
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

Successfully merging a pull request may close this issue.

4 participants