jarivanewijk opened a new issue #4684:
URL: https://github.com/apache/incubator-nuttx/issues/4684
I just found that enabling the CONFIG_SCHED_CPULOAD option ("Enable CPU load
monitoring") causes a lockup soon after the NuttShell initialization. If I'm
quick a get less than a second to start typing some command, then it gets
completely stuck. No more input is possible. No more output comes out. It's
just dead. It seems no asserts are triggered and there's nothing being logged
to the SYSLOG. I am not sure what's going on here.
I have checked this on a few boards with an NXP S32K144 MCU (single Arm
Cortex-M4F core). I don't have boards with other MCUs at hand, but I don't
think this is a MCU specific issue. I was able to trace this issue back to PR
https://github.com/apache/incubator-nuttx/pull/4666, specifically commit
https://github.com/apache/incubator-nuttx/commit/8b67944c75b81d17174bd207ad63acfa22da8983.
There's no issues if I checkout an earlier commit from master.
@xiaoxiang781216, since you made the changes that seem to be causing the
issue, would you be willing to have a look at this? Would be much appreciated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
