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/kernel/fatal/exception failed on nsim_sem_mpu_stack_guard board #29139

Closed
IRISZZW opened this issue Oct 13, 2020 · 1 comment · Fixed by #29141
Closed

tests/kernel/fatal/exception failed on nsim_sem_mpu_stack_guard board #29139

IRISZZW opened this issue Oct 13, 2020 · 1 comment · Fixed by #29141
Assignees
@abrodkin @IRISZZW @YuguoWH
Labels
area: ARC ARC Architecture bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug Stale

Comments

@IRISZZW
Copy link
Contributor

IRISZZW commented Oct 13, 2020

To Reproduce
Steps to reproduce the behavior:

  1. west build -b nsim_sem_mpu_stack_guard -p auto tests/kernel/fatal/exception
  2. west flash
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Impact
What impact does this issue have on your progress (e.g., annoyance, showstopper)

Logs and console output

*** Booting Zephyr OS build zephyr-v2.4.0-557-gdc37f988e030  ***
Running test suite fatal
===================================================================
START - test_fatal
test alt thread 1: generic CPU exception
E: ***** Exception vector: 0x8, cause code: 0x0, parameter 0x0
E: Address 0x3c4
E: EV_SWI
E:  r0: 0x00000000  r1: 0x00000000  r2: 0x00000000  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0xfffffff5
E:  r8: 0x00000000  r9: 0x00000000 r10: 0x00000000 r11: 0x00000000
E: r12: 0x000003bc r13: 0x00000000  pc: 0x000003c4
E:  blink: 0x00000f5c status32: 0x80300002
E: lp_end: 0x00000000 lp_start: 0x00000000 lp_count: 0x00000000
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 0
test alt thread 2: initiate kernel oops
E:  r0: 0x00000003  r1: 0x00000000  r2: 0x00000031  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0xfffffff5
E:  r8: 0x80000110  r9: 0x00000031 r10: 0x80000040 r11: 0x80000110
E: r12: 0x000003d4 r13: 0x00000000  pc: 0x000003e6
E:  blink: 0x00000f5c status32: 0x00300002
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 3
test alt thread 3: initiate kernel panic
E:  r0: 0x00000004  r1: 0x00000000  r2: 0x00000031  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0xfffffff5
E:  r8: 0x80000110  r9: 0x00000031 r10: 0x80000040 r11: 0x80000110
E: r12: 0x000003e8 r13: 0x00000000  pc: 0x000003fa
E:  blink: 0x00000f5c status32: 0x00300002
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 4
test alt thread 4: fail assertion
ASSERTION FAIL [0] @ WEST_TOPDIR/zephyr/tests/kernel/fatal/exception/src/main.c:124
        intentionally failed assertion
E:  r0: 0x00000004  r1: 0x0000007c  r2: 0x80000040  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000001  r6: 0x00000020  r7: 0xffffffff
E:  r8: 0x80000110  r9: 0x00000031 r10: 0x80000040 r11: 0x80000110
E: r12: 0x00001000 r13: 0x0000c5f0  pc: 0x00001580
E:  blink: 0x00000452 status32: 0x80300602
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 4
test alt thread 5: initiate arbitrary SW exception
E:  r0: 0x7fffffff  r1: 0x00000000  r2: 0x00000031  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0xfffffff5
E:  r8: 0x80000110  r9: 0x00000031 r10: 0x80000040 r11: 0x80000110
E: r12: 0x000003fc r13: 0x000029fe  pc: 0x00000418
E:  blink: 0x00000f5c status32: 0x00300002
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 2147483647: Unknown error on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 2147483647
test stack HW-based overflow - supervisor 1
E: ***** Exception vector: 0x6, cause code: 0x2, parameter 0x4
E: Address 0x80001554
E: EV_ProtV
E: Memory write protection violation (MPU)
E:  r0: 0x00000000  r1: 0x00000000  r2: 0x00000000  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0x00000005
E:  r8: 0x80000110  r9: 0x00000031 r10: 0x80000040 r11: 0x80000110
E: r12: 0x000000d8 r13: 0x000029fe  pc: 0x00000078
E:  blink: 0x0000008c status32: 0x80300002
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 2
test stack HW-based overflow - supervisor 2
E: ***** Exception vector: 0x6, cause code: 0x2, parameter 0x4
E: Address 0x80001554
E: EV_ProtV
E: Memory write protection violation (MPU)
E:  r0: 0x00000000  r1: 0x00000000  r2: 0x00000000  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0x00000005
E:  r8: 0x80000110  r9: 0x00000031 r10: 0x80000040 r11: 0x80000110
E: r12: 0x000000d8 r13: 0x000029fe  pc: 0x00000078
E:  blink: 0x0000008c status32: 0x80300002
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 2
test stack HW-based overflow - user 1
E: ***** Exception vector: 0x6, cause code: 0x2, parameter 0x4
E: Address 0x80001554
E: EV_ProtV
E: Memory write protection violation (MPU)
E:  r0: 0x00000000  r1: 0x00000000  r2: 0x00000000  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0x00000000
E:  r8: 0x00000000  r9: 0x00000000 r10: 0x00000000 r11: 0x00000000
E: r12: 0x000000d8 r13: 0x00000000  pc: 0x00000078
E:  blink: 0x0000008c status32: 0x80300082
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 2
test stack HW-based overflow - user 2
E: ***** Exception vector: 0x6, cause code: 0x2, parameter 0x4
E: Address 0x80001554
E: EV_ProtV
E: Memory write protection violation (MPU)
E:  r0: 0x00000000  r1: 0x00000000  r2: 0x00000000  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x00000000  r7: 0x00000000
E:  r8: 0x00000000  r9: 0x00000000 r10: 0x00000000 r11: 0x00000000
E: r12: 0x000000d8 r13: 0x00000000  pc: 0x00000078
E:  blink: 0x0000008c status32: 0x80300082
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 2
test stack HW-based overflow - user priv stack 1
E: ***** Exception vector: 0x6, cause code: 0x2, parameter 0x4
E: Address 0x80001158
E: EV_ProtV
E: Memory write protection violation (MPU)
E:  r0: 0x00000000  r1: 0x00000000  r2: 0x00000000  r3: 0x00000000
E:  r4: 0x00000000  r5: 0x00000000  r6: 0x000000b8  r7: 0x8000150c
E:  r8: 0x00000000  r9: 0x00000000 r10: 0x00000000 r11: 0x00000000
E: r12: 0x0000010c r13: 0x800002e8  pc: 0x00000078
E:  blink: 0x0000008c status32: 0x80300002
E: lp_end: 0x00000000 lp_start: 0x00000030 lp_count: 0x80000040
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x80000040 (unknown)
Caught system error -- reason 0
Wrong crash type got 0 expected 2

Environment (please complete the following information):

  • OS: Linux
  • Toolchain: Zephyr SDK
  • Commit SHA: dc37f988
@IRISZZW IRISZZW added the bug The issue is a bug, or the PR is fixing a bug label Oct 13, 2020
@IRISZZW IRISZZW mentioned this issue Oct 13, 2020
Merged
@nashif nashif added priority: medium Medium impact/importance bug area: ARC ARC Architecture labels Oct 13, 2020
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Dec 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abrodkin abrodkin

@IRISZZW IRISZZW

@YuguoWH YuguoWH

Labels
area: ARC ARC Architecture bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug Stale
Projects
None yet
Milestone
No milestone
4 participants
@nashif @abrodkin @IRISZZW @YuguoWH