zephyr: tests/kernel/mem_protect/protection/kernel.memory_protection.protection fails on qemu_cortex_r5

Describe the bug Hi, seems like tests/kernel/mem_protect/protection/kernel.memory_protection.protection fails started timing out on qemu_cortex_r5 since 33a25371b6dcc3cfeb7df31f7ae9ba014830545f.

@tnmysh: any chance you could look into it?

To Reproduce ./scripts/twister -v -n -M -p qemu_cortex_r5 -T tests/kernel/mem_protect/protection on main

Also https://github.com/zephyrproject-rtos/zephyr/runs/15955541825, fails with Timeout.

Bisected down to 33a25371b6dcc3cfeb7df31f7ae9ba014830545f, reverting om main fixes the issue.

Expected behavior Test should pass.

Impact Broken in CI, pretty bad.

Environment (please complete the following information): Linux, main (77698e8a22), Zephyr SDK 0.16.1

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 31 (31 by maintainers)

Commits related to this issue

Most upvoted comments

@gramsay0 Thanks for looking into this. I’m still working on a new (device tree- based) MPU setup in the UltraScale MPU init code, I’ll apply your patch to that right away.

@gramsay0 could you open a PR for that and then we can use that to followup with the ARM maintainers about it?

Sure but if it used to work then there’s probably something wrong with https://github.com/zephyrproject-rtos/zephyr/commit/36997de796261cf17a59072fd3f4b77e4706c93e, I’d be laying toward reverting https://github.com/zephyrproject-rtos/zephyr/pull/60368 at this point, unless you folks have a better workaround in mind.

About to run the test on actual R5 hardware now in order to determine if QEMU is at fault.

@fabiobaltieri Sure I will look into it.