tmedicci commented on issue #11567: URL: https://github.com/apache/nuttx/issues/11567#issuecomment-1900914400
> 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 `wq:rate_ctrl` takes 50.2% of the CPU time. It is expected it to be that high because this task takes the highest priority (perhaps you should lower it). About being stuck: you would need to analyze the app itself: try to attach the debugger and check where it is being stuck. -- 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
