Skip to content

tests/kernel/pipe/pipe test cases are failing on ARM boards #10474

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
Closed
spoorthik opened this issue Oct 10, 2018 · 3 comments
Closed

tests/kernel/pipe/pipe test cases are failing on ARM boards #10474

spoorthik opened this issue Oct 10, 2018 · 3 comments
Assignees
@dcpleung
Labels
bug The issue is a bug, or the PR is fixing a bug priority: high High impact/importance bug

Comments

@spoorthik
Copy link
Contributor

Execution log:


***** Booting Zephyr OS 1.13.99 (delayed boot 1000ms) *****
Running test suite test_pipe
===================================================================
starting test - test_pipe_on_single_elements
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_on_single_elements
===================================================================
starting test - test_pipe_on_multiple_elements
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_on_multiple_elements
===================================================================
starting test - test_pipe_forever_wait
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_forever_wait
===================================================================
starting test - test_pipe_timeout
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_timeout
===================================================================
starting test - test_pipe_get_on_empty_pipe
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_get_on_empty_pipe
===================================================================
starting test - test_pipe_forever_timeout
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_forever_timeout
===================================================================
starting test - test_pipe_get_timeout
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_get_timeout
===================================================================
starting test - test_pipe_get_invalid_size
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x200021d0
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_get_invalid_size
===================================================================
PROJECT EXECUTION FAILED

Platforms tested: frdm_k64f, nrf52840_pca10056, nrf52_pca10040
@spoorthik spoorthik added the bug The issue is a bug, or the PR is fixing a bug label Oct 10, 2018
AdithyaBaglody added a commit to AdithyaBaglody/zephyr that referenced this issue Oct 11, 2018
@AdithyaBaglody
arch: arm: linker.ld: Fixed incorrect placement of noinit section
74ac785 
This was causing an incorrect hash for privileged stack.

Fixes: zephyrproject-rtosGH-10473
Fixes: zephyrproject-rtosGH-10474
Fixes: zephyrproject-rtosGH-10475
Fixes: zephyrproject-rtosGH-10476

Signed-off-by: Adithya Baglody <[email protected]>
@AdithyaBaglody AdithyaBaglody mentioned this issue Oct 11, 2018
Merged
nashif pushed a commit that referenced this issue Oct 11, 2018
@AdithyaBaglody @nashif
arch: arm: linker.ld: Fixed incorrect placement of noinit section
4f78d86 
This was causing an incorrect hash for privileged stack.

Fixes: GH-10473
Fixes: GH-10474
Fixes: GH-10475
Fixes: GH-10476

Signed-off-by: Adithya Baglody <[email protected]>
@spoorthik
Copy link
Contributor Author

spoorthik commented Oct 12, 2018 •
edited
Loading

@nashif @AdithyaBaglody : The test cases still fail on freedom_k64f even after the fix is merged.

Execution log:

***** Booting Zephyr OS 1.13.99 (delayed boot 1000ms) *****
Running test suite test_pipe
===================================================================
starting test - test_pipe_on_single_elements
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_on_single_elements
===================================================================
starting test - test_pipe_on_multiple_elements
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_on_multiple_elements
===================================================================
starting test - test_pipe_forever_wait
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_forever_wait
===================================================================
starting test - test_pipe_timeout
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_timeout
===================================================================
starting test - test_pipe_get_on_empty_pipe
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_get_on_empty_pipe
===================================================================
starting test - test_pipe_forever_timeout
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_forever_timeout
===================================================================
starting test - test_pipe_get_timeout
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_get_timeout
===================================================================
starting test - test_pipe_get_invalid_size
***** USAGE FAULT *****
  Attempt to execute undefined instruction
***** Hardware exception *****
Current thread ID = 0x20002210
Faulting instruction address = 0x7e92
Caught system error -- reason 0
FAIL - test_pipe_get_invalid_size
===================================================================
===================================================================
PROJECT EXECUTION FAILED

@spoorthik spoorthik reopened this Oct 12, 2018
@nashif nashif added the priority: high High impact/importance bug label Oct 14, 2018
@nashif
Copy link
Member

nashif commented Oct 14, 2018

@dcpleung this is related to the linker changes, we might want to revert them until we have a solution. This turns out to be very fragile.

@AdithyaBaglody
Copy link
Contributor

@nashif @dcpleung #10542 Fixes all issues introduced by orphan sections.

@dcpleung dcpleung mentioned this issue Oct 18, 2018
Merged
dcpleung pushed a commit to dcpleung/zephyr that referenced this issue Oct 19, 2018
@AdithyaBaglody @dcpleung
linker: arm: place priv.noinit at the end of RAM
c2e977c 
This puts the priviledged stack at the end of RAM.
This combines PR zephyrproject-rtos#10507 and zephyrproject-rtos#10542.

Fixes zephyrproject-rtos#10473
Fixes zephyrproject-rtos#10474
Fixes zephyrproject-rtos#10515

Signed-off-by: Adithya Baglody <[email protected]>
Signed-off-by: Daniel Leung <[email protected]>
dcpleung added a commit to dcpleung/zephyr that referenced this issue Oct 19, 2018
@dcpleung
linker: warn about orphan sections
b9632d3 
(Previous patch set was reverted due to issue with priv_stack.
 Resubmitting after fixing the faults caused by priv_stack.noinit
 not at the end of RAM.)

This adds a linker flag and necessary changes to linker scripts
so that linker will warn about orphan sections.

Relates to zephyrproject-rtos#5534.

Fixes zephyrproject-rtos#10473, zephyrproject-rtos#10474, zephyrproject-rtos#10515.

Signed-off-by: Daniel Leung <[email protected]>
@nashif nashif closed this as completed in 1fa8cf9 Oct 19, 2018
nashif pushed a commit that referenced this issue Oct 19, 2018
@dcpleung @nashif
linker: warn about orphan sections
6600c64 
(Previous patch set was reverted due to issue with priv_stack.
 Resubmitting after fixing the faults caused by priv_stack.noinit
 not at the end of RAM.)

This adds a linker flag and necessary changes to linker scripts
so that linker will warn about orphan sections.

Relates to #5534.

Fixes #10473, #10474, #10515.

Signed-off-by: Daniel Leung <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dcpleung dcpleung

Labels
bug The issue is a bug, or the PR is fixing a bug priority: high High impact/importance bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nashif @AdithyaBaglody @spoorthik @dcpleung