Skip to content

mpu_stack_guard_test fails on many arm platforms, including qemu #5735

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

Closed
nashif opened this issue Jan 19, 2018 · 3 comments
Closed

mpu_stack_guard_test fails on many arm platforms, including qemu #5735

nashif opened this issue Jan 19, 2018 · 3 comments
Assignees
Labels
area: ARM ARM (32-bit) Architecture bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@nashif
Copy link
Member

nashif commented Jan 19, 2018

sample samples/mpu/mpu_stack_guard_test fails on frdm_k64f:

Connecting to /dev/ttyACM0
***** BOOTING ZEPHYR OS v1.10.99 - BUILD: Jan 19 2018 03:15:21 *****
STACK_ALIGN 0x8
MPU STACK GUARD Test
Canary Initial Value = 0xf0cacc1a threads 0x200010e0
Canary = 0x20000240	Test not passed.
***** BUS FAULT *****
  Executing thread ID (thread): 0x200010e0
  Faulting instruction address:  0x209c
  Imprecise data bus error
Fatal fault in thread 0x200010e0! Aborting.
***** HARD FAULT *****
  Fault escalation (see below)
***** BUS FAULT *****
  Executing thread ID (thread): 0x200010e0
  Faulting instruction address:  0x1f4
  Imprecise data bus error
Fatal fault in ISR! Spinning...
@nashif nashif added area: ARM ARM (32-bit) Architecture area: Debugging labels Jan 19, 2018
@nashif nashif added bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug and removed area: Debugging labels Jan 19, 2018
nashif added a commit to nashif/zephyr that referenced this issue Jan 24, 2018
Do not build for some unsupported architecture and exclude ARM qemu
platform due to bug zephyrproject-rtos#5735.

STACK_ALIGN 0x8
MPU STACK GUARD Test
Canary Initial Value = 0xf0cacc1a threads 0x200010e0
Canary = 0x20000240    Test not passed.
***** BUS FAULT *****
  Executing thread ID (thread): 0x200010e0
  Faulting instruction address:  0x209c
  Imprecise data bus error
Fatal fault in thread 0x200010e0! Aborting.
***** HARD FAULT *****
  Fault escalation (see below)
***** BUS FAULT *****
  Executing thread ID (thread): 0x200010e0
  Faulting instruction address:  0x1f4
  Imprecise data bus error
Fatal fault in ISR! Spinning...

Signed-off-by: Anas Nashif <[email protected]>
nashif added a commit that referenced this issue Jan 24, 2018
Do not build for some unsupported architecture and exclude ARM qemu
platform due to bug #5735.

STACK_ALIGN 0x8
MPU STACK GUARD Test
Canary Initial Value = 0xf0cacc1a threads 0x200010e0
Canary = 0x20000240    Test not passed.
***** BUS FAULT *****
  Executing thread ID (thread): 0x200010e0
  Faulting instruction address:  0x209c
  Imprecise data bus error
Fatal fault in thread 0x200010e0! Aborting.
***** HARD FAULT *****
  Fault escalation (see below)
***** BUS FAULT *****
  Executing thread ID (thread): 0x200010e0
  Faulting instruction address:  0x1f4
  Imprecise data bus error
Fatal fault in ISR! Spinning...

Signed-off-by: Anas Nashif <[email protected]>
@agross-oss
Copy link
Collaborator

Just double checked this. The expected case when using the default prj file is to fail. The output given above indicates the prj.conf was used. If the prf_stack_guard.prj is used, the error's will be correctly determined to be stacking errors.

@agross-oss
Copy link
Collaborator

It should be noted that qemu (current version in zephyr) does not support MPU. And not all boards have MPUs. So perhaps we need to adjust the whitelist.

@nashif nashif added priority: low Low impact/importance bug and removed priority: medium Medium impact/importance bug labels Feb 20, 2018
@nashif
Copy link
Member Author

nashif commented Nov 5, 2018

AFAIK should be resolved with the new SDK support MPU on ARM.

@nashif nashif closed this as completed Nov 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ARM ARM (32-bit) Architecture bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

2 participants