ssanitycheck --coverage -p mps2_an385: Some remaing test cases that are still failing

[cinlyooi-intel]

Describe the bug
There are two cases that generate Hardware failure, and one that generates an Assertion Failure.
sanitycheck (without coverage) passed for all the test case noted here.

To Reproduce

./scripts/sanitycheck --coverage --coverage-platform mps2_an385 -p mps2_an385  -T tests/kernel -T tests/subsys/logging 

Screenshots or console output
37/214 mps2_an385 tests/kernel/mem_protect/stackprot/kernel.memory_protection FAILED: timeout
see: sanity-out/mps2_an385/tests/kernel/mem_protect/stackprot/kernel.memory_protection/handler.log

***** Booting Zephy***** USAGE FAULT *****
  Illegal load of EXC_RETURN into PC
***** Hardware exception *****
Current thread ID = 0x200143c0
Faulting instruction address = 0x2001cef8
Fatal fault in essential thread! Spinning...

56/214 mps2_an385 tests/kernel/profiling/profiling_api/kernel.profiling FAILED: timeout
see: sanity-out/mps2_an385/tests/kernel/profiling/profiling_api/kernel.profiling/handler.log

***** BUS FAULT *****
  Precise data bus error
  BFAR Address: 0xaaaaaaaa
***** Hardware exception *****
Current thread ID = 0x20010228
Faulting instruction address = 0xa226
Fatal fault in thread 0x20010228! Aborting.
***** USAGE FAULT *****
  Illegal load of EXC_RETURN into PC
***** Hardware exception *****
Current thread ID = 0x2000b120
Faulting instruction address = 0x7095
Fatal fault in thread 0x2000b120! Aborting.
***** MPU FAULT *****
  Data Access Violation
  MMFAR Address: 0x78
***** Hardware exception *****
Current thread ID = 0x00000000
Faulting instruction address = 0x70c0
Fatal fault in ISR! Spinning...

40/214 mps2_an385 tests/kernel/mem_protect/userspace/kernel.memory_protection.userspace FAILED: timeout
see: sanity-out/mps2_an385/tests/kernel/mem_protect/userspace/kernel.memory_protection.userspace/handler.log

Please note that we are expecting the "BUS Fault" because the test case is expected to generate and test this fault. It is the "Assertion failed" that is not expected and the reason for listing the testcase as having a bug.

***** BUS FAULT *****
  Precise data bus error
  BFAR Address: 0xaaaaaaaa
***** Hardware exception *****
Current thread ID = 0x2001ff0c
Faulting instruction address = 0x11d02
Caught system error -- reason 0

    Assertion failed at /home/cinlyooi/tests/zephyrproject/zephyr/tests/kernel/mem_protect/userspace/src/main.c:107: z_SysFatalErrorHandler: (Re
ached unreachable code)
Unexpected fault during test
ASSERTION FAIL [(u32_t)thread->stack_obj == guard_start] @ /home/cinlyooi/tests/zephyrproject/zephyr/arch/arm/core/cortex_m/mpu/arm_core_mpu.c:2
23
	Guard start (0xffffffe0) not beginning at stack object (0x0)

Environment (please complete the following information):

• OS: fedora29
• Toolchain : zephyr
• Commit SHA or Version used: 06ab394

[wentongwu]

I think the BUS FAULT error as below has already been fixed by PR #16099.

***** BUS FAULT *****
Precise data bus error
BFAR Address: 0xaaaaaaaa

[nashif]

stale