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.

Sign up for GitHub

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

Jump to bottom

tests-ci : kernel: scheduler: multiq test failed #37265

Closed
hakehuang opened this issue Jul 28, 2021 · 9 comments
Closed

tests-ci : kernel: scheduler: multiq test failed #37265

hakehuang opened this issue Jul 28, 2021 · 9 comments
Assignees
@dleach02
Labels
area: Kernel bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP priority: low Low impact/importance bug

Comments

@hakehuang
Copy link
Collaborator

Describe the bug
multiq test is failed on zephyr-v2.6.0-1424-g14f09a3b00d4 on lpcxpresso54114_m4

see logs for details

To Reproduce
1.

scripts/twister --device-testing --device-serial /dev/ttyACM0 -p lpcxpresso54114_m4  --sub-test kernel.scheduler
  1. See error

Expected behavior
test pass

Impact

Logs and console output

*** Booting Zephyr OS build zephyr-v2.6.0-1424-g14f09a3b00d4  ***
Running test suite threads_scheduling
===================================================================
START - test_bad_priorities
PASS - test_bad_priorities in 0.1 seconds
===================================================================
START - test_priority_cooperative
PASS - test_priority_cooperative in 0.101 seconds
===================================================================
START - test_priority_preemptible
PASS - test_priority_preemptible in 0.102 seconds
===================================================================
START - test_priority_preemptible_wait_prio
PASS - test_priority_preemptible_wait_prio in 0.32 seconds
===================================================================
START - test_yield_cooperative
PASS - test_yield_cooperative in 0.2 seconds
===================================================================
START - test_sleep_cooperative
PASS - test_sleep_cooperative in 0.101 seconds
===================================================================
START - test_busy_wait_cooperative
PASS - test_busy_wait_cooperative in 0.102 seconds
===================================================================
START - test_sleep_wakeup_preemptible
PASS - test_sleep_wakeup_preemptible in 0.2 seconds
===================================================================
START - test_pending_thread_wakeup
PASS - test_pending_thread_wakeup in 0.1 seconds
===================================================================
START - test_time_slicing_preemptible
PASS - test_time_slicing_preemptible in 0.502 seconds
===================================================================
START - test_time_slicing_disable_preemptible
PASS - test_time_slicing_disable_preemptible in 0.502 seconds
===================================================================
START - test_lock_preemptible
PASS - test_lock_preemptible in 0.201 seconds
===================================================================
START - test_unlock_preemptible
PASS - test_unlock_preemptible in 0.102 seconds
===================================================================
START - test_unlock_nested_sched_lock
PASS - test_unlock_nested_sched_lock in 0.102 seconds
===================================================================
START - test_sched_is_preempt_thread
PASS - test_sched_is_preempt_thread in 0.2 seconds
===================================================================
START - test_slice_reset
PASS - test_slice_reset in 1.802 seconds
===================================================================
START - test_slice_scheduling
ABCDEFGHI
AB
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
C
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
D
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
E
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
F
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
G
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
H
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
I
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
A
Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/sched/schedule_api/src/test_slice_scheduling.c:61: thread_tslice: ((tdelta >= expected_slice_min) && (tdelta <= expected_slice_max) && (idx == thread_idx)) is false
FAIL - test_slice_scheduling in 2.599 seconds
===================================================================
START - test_priority_scheduling
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
ABCDEFGHI
PASS - test_priority_scheduling in 0.16 seconds
===================================================================
START - test_wakeup_expired_timer_thread
PASS - test_wakeup_expired_timer_thread in 0.2 seconds
===================================================================
START - test_user_k_wakeup
PASS - test_user_k_wakeup in 0.2 seconds
===================================================================
START - test_user_k_is_preempt
PASS - test_user_k_is_preempt in 0.2 seconds
===================================================================
START - test_k_thread_suspend_init_null
E: (nil) is not a valid k_thread
E: address is not a known kernel object
E: syscall z_vrfy_k_thread_suspend failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_thread_suspend_init_null in 0.46 seconds
===================================================================
START - test_k_thread_resume_init_null
E: (nil) is not a valid k_thread
E: address is not a known kernel object
E: syscall z_vrfy_k_thread_resume failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_thread_resume_init_null in 0.46 seconds
===================================================================
START - test_k_thread_priority_get_init_null
E: (nil) is not a valid k_thread
E: address is not a known kernel object
E: syscall z_vrfy_k_thread_priority_get failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_thread_priority_get_init_null in 0.46 seconds
===================================================================
START - test_k_thread_priority_set_init_null
E: (nil) is not a valid k_thread
E: address is not a known kernel object
E: syscall z_vrfy_k_thread_priority_set failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_thread_priority_set_init_null in 0.46 seconds
===================================================================
START - test_k_thread_priority_set_overmax
E: syscall z_vrfy_k_thread_priority_set failed check: invalid thread priority 15
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_thread_priority_set_overmax in 0.41 seconds
===================================================================
START - test_k_thread_priority_set_upgrade
E: syscall z_vrfy_k_thread_priority_set failed check: thread priority may only be downgraded (-1 < 0)
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_thread_priority_set_upgrade in 0.43 seconds
===================================================================
START - test_k_wakeup_init_null
E: (nil) is not a valid k_thread
E: address is not a known kernel object
E: syscall z_vrfy_k_wakeup failed check: access denied
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x200019d0 (unknown)
Caught system error -- reason 3 1
Fatal error expected as part of test case.
PASS - test_k_wakeup_init_null in 0.45 seconds
===================================================================
Test suite threads_scheduling failed.
===================================================================
PROJECT EXECUTION FAILED

Environment (please complete the following information):

  • OS: (e.g. Linux )
  • Toolchain (e.g Zephyr SDK)
  • Commit SHA or Version used: zephyr-v2.6.0-1424-g14f09a3b00d4
@hakehuang hakehuang transferred this issue from zephyrproject-rtos/test_results Jul 28, 2021
@hakehuang
Copy link
Collaborator Author

@dleach02 @MaureenHelm

@FRASTM
Copy link
Collaborator

FRASTM commented Jul 28, 2021

A similar issue was reported on stm32: #35793

@dleach02 dleach02 self-assigned this Aug 2, 2021
@dleach02
Copy link
Member

dleach02 commented Aug 2, 2021

I have a lpc54114 board. @hakehuang does this occur on any other boards?

@MaureenHelm MaureenHelm added the bug The issue is a bug, or the PR is fixing a bug label Aug 2, 2021
@dleach02
Copy link
Member

dleach02 commented Aug 3, 2021

@hakehuang I have not been able to reproduce this. I'm using:

west build -b lpcxpresso54114_m4 -p always tests\kernel\sched\schedule_api

@nashif nashif added the priority: low Low impact/importance bug label Aug 3, 2021
@hakehuang
Copy link
Collaborator Author

I have a lpc54114 board. @hakehuang does this occur on any other boards?

@dleach02 only found in this platform for NXP

@hakehuang
Copy link
Collaborator Author

west build -b lpcxpresso54114_m4 -p always tests\kernel\sched\schedule_api

@dleach02 some extra parameter need add if you using west build

  kernel.scheduler.multiq:
    extra_args: CONF_FILE=prj_multiq.conf
    extra_configs:
      - CONFIG_TIMESLICING=y
 
est build -b lpcxpresso54114_m4 -p always tests\kernel\sched\schedule_api -- -DCONF_FILE=prj_multiq.conf -DCONFIG_TIMESLICING=y

@dleach02
Copy link
Member

@hakehuang, still not reproducing for me on my board. Not sure what to do. Does this reproduce reliably on your board?

@hakehuang
Copy link
Collaborator Author

@dleach02 this issue is gone with latest main line build in zerphyr, I guess this has fixed

@dleach02
Copy link
Member

Hake, there is also a duplicate #37104

@dleach02 dleach02 mentioned this issue Aug 17, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dleach02 dleach02

Labels
area: Kernel bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP priority: low Low impact/importance bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nashif @hakehuang @MaureenHelm @dleach02 @FRASTM