MBED_TICKLESS causing error in rtx_idle thread (since 5.13.4)

[maciejbocianski]

Description

I noticed that tickless enabled in 5.13.4 for k64f is causing that below code is failing

#include "mbed.h"
 
int main() {

    wait_ms(1);
}

test command: mbed compile -t GCC_ARM -m k64f -f

 ++ MbedOS Error Info ++
Error Status: 0x80010133 Code: 307 Module: 1
Error Message: Mutex: 0x20001E08, Not allowed in ISR context
Location: 0x30D1
Error Value: 0x20001E08
Current Thread: rtx_idle  Id: 0x20000EDC Entry: 0x30DD StackSize: 0x200 StackMem: 0x20001220 SP: 0x2002FE58
For more info, visit: https://mbed.com/s/error?error=0x80010133&tgt=K64F
-- MbedOS Error Info --

= System will be rebooted due to a fatal error =
= Reboot count(=95) reached maximum, system will halt after rebooting

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

[0xc0170]

cc @ARMmbed/team-nxp (#10796 might be causing this?)

[jamesbeyond]

Hi @mmahadevan108 , seem the K64F not quite working with TICKLESS mode,
it crashed due to your PR #10796
please review the implementation.

meanwhile @gpsimenos could you update the test results for other NXP boards please and turn off TICKLESS on K64F temperately

[mmahadevan108]

Its strange, it passed all mbed-os tests before being enabled

[jamesbeyond]

Its strange, it passed all mbed-os tests before being enabled

I think this is a corner case, which not covered by our greentea tests

[mmahadevan108]

Its strange that mbed-os tests does not cover this, something to look into?

[maciejbocianski]

the clue could be that adding printf before wait fixes the problem!
That is probably the reason why greente tests all had pass, they prints a lot

[gpsimenos]

PR #11403 opened to disable tickless mode on K64F for now

[gpsimenos]

In the last couple of weeks I have been enabling and testing tickless mode (by running all greentea tests on RaaS) on a number of boards that can theoretically support it.

The K66F, K82F and KW41Z passed all tests successfully.
The K22F, K64F and KW24D failed with several errors (some of them might be due to RaaS)
The KL82Z could not be tested due to RaaS problems.

[mmahadevan108]

I am unable to reproduce the failure on the current master branch

[kjbracey]

Can we confirm mbed_app.json contents, if any?