-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
esp32s3/smp: Dual Core Scheduling Problem. #11567
Comments
HI @w2016561536 ! I didn't get exactly what is your problem, but I saw no problems regarding your process scheduling in the images you shared. Could you please elaborate what is the problem? |
In picture 1, wq:rate_ctrl take up all the cpu resources. But actually, it does not run, just stuck there. It look like cpu 0 is dead |
The picture does not show that. It shows that |
In NuttX,when dual core is enabled and system has very low load, each Idle task takes 50% time. Thank you for your advice. I will use debugger to inspect what happens on Core 0 next day. Here is middle night. I need to go to bed. Have a nice day. @tmedicci |
@masayuki2009 since you did many improvements over original SMP, maybe you can have some suggestion to help here. |
I think @tmedicci's comments are correct. |
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.
The text was updated successfully, but these errors were encountered: