chirping78 commented on PR #10496:
URL: https://github.com/apache/nuttx/pull/10496#issuecomment-1751691440
> @chirping78
>
> > But for some reason, the local interrupt on CPU1 is already disabled, so
CPU1 will never ack the SGI interrupt.
>
> Can you identify where the local interrupt on cpu1 was disabled when the
deadlock happened?
>
> Also, I’d like to know that what happens if the DEBUGASSERTION is enabled.
I got the board today, and can reproduce the issue w/o this PR change.
About "where the local interrupt on cpu1 was disabled", I can't find a
proper way to find this answer. Could you sugguest a method, maybe gdb script
or log? @masayuki2009
About `DEBUGASSERTION`, I found `CONFIG_DEBUG_ASSERTIONS` is opened:
````
nuttx$ grep DEBUG_ .config|grep ASS
CONFIG_DEBUG_ASSERTIONS=y
````
but it does not print assert when this issue happend.
--
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
