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: run interrupt testcases failed on ADSP #35241

Closed
KangJianX opened this issue May 13, 2021 · 0 comments · Fixed by #35302
Closed

intel_adsp_cavs15: run interrupt testcases failed on ADSP #35241

KangJianX opened this issue May 13, 2021 · 0 comments · Fixed by #35302
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: Intel ADSP Intel Audio platforms priority: low Low impact/importance bug

Comments

@KangJianX
Copy link
Collaborator

Describe the bug
run tests/kernel/interrupt/ failed on ADSP

To Reproduce
Steps to reproduce the behavior:

  1. twister -p intel_adsp_cavs15 --device-testing -T tests/kernel/interrupt/ --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/rimage/config,/home/ztest/work/rimage/build/rimage" --device-serial-pty="/home/ztest/work/zephyrproject/zephyr/boards/xtensa/intel_adsp_cavs15/tools/adsplog.py,--no-history"

Logs and console output

DEBUG - DEVICE: ===================================================================
DEBUG - DEVICE: START - test_isr_offload_job_multiple
DEBUG - DEVICE: case 0
DEBUG - DEVICE: case 0
DEBUG - DEVICE:
DEBUG - DEVICE: ASSERTION FAIL [work->queue != ((void *)0)] @ WEST_TOPDIR/zephyr/kernel/work.c:334
DEBUG - DEVICE: @ WEST_TOPDIR/zephyr/lib/os/assert.c:45

Environment (please complete the following information):
OS: Fedora28
Toolchain: Zephyr-sdk-0.12.4
Commit id: 929c573

@KangJianX KangJianX added the bug The issue is a bug, or the PR is fixing a bug label May 13, 2021
@KangJianX KangJianX added the platform: Intel ADSP Intel Audio platforms label May 14, 2021
@galak galak added priority: low Low impact/importance bug has-pr labels May 18, 2021
enjiamai pushed a commit to enjiamai/zephyr that referenced this issue May 20, 2021
The interrupt offload testcases fail on some boards because the timing
of the delay is too short. Refine the testcases and make it not rely
on the delay timing.

Fixes zephyrproject-rtos#35097
Fixes zephyrproject-rtos#35241

Signed-off-by: Enjia Mai <enjiax.mai@intel.com>
nashif pushed a commit that referenced this issue May 20, 2021
The interrupt offload testcases fail on some boards because the timing
of the delay is too short. Refine the testcases and make it not rely
on the delay timing.

Fixes #35097
Fixes #35241

Signed-off-by: Enjia Mai <enjiax.mai@intel.com>
tejlmand pushed a commit to tejlmand/zephyr that referenced this issue May 25, 2021
…delay timing

The interrupt offload testcases fail on some boards because the timing
of the delay is too short. Refine the testcases and make it not rely
on the delay timing.

Fixes zephyrproject-rtos#35097
Fixes zephyrproject-rtos#35241

Signed-off-by: Enjia Mai <enjiax.mai@intel.com>
(cherry picked from commit 04c736d)
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
jori-nordic pushed a commit to jori-nordic/zephyr that referenced this issue Jun 15, 2021
…delay timing

The interrupt offload testcases fail on some boards because the timing
of the delay is too short. Refine the testcases and make it not rely
on the delay timing.

Fixes zephyrproject-rtos#35097
Fixes zephyrproject-rtos#35241

Signed-off-by: Enjia Mai <enjiax.mai@intel.com>
(cherry picked from commit 04c736d)
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
(cherry picked from commit b54109c)
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: Intel ADSP Intel Audio platforms priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants