w2016561536 opened a new issue, #11567: URL: https://github.com/apache/nuttx/issues/11567
At first, thank you for reading this issue. I'm not quite sure if it occurred by NuttX scheduling. Perhaps applications cause this issue.  Here is the process information of my board. It is running PX4-Autopilot, which is based on NuttX. On CPU0, there is one task taking up all the resources. And no new task can be scheduled on CPU0 (if I run smp test at this moment). Howerver this application has no problem on single core. The process information below.  And what makes me puzzled that ALWAYS CPU0 happens this problem and it never happens on CPU1. And, the task stuck on the CPU0 is random. It could change after reset. But sometimes the app runs well and no task stuck on one core. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
