hujun260 commented on PR #9065:
URL: https://github.com/apache/nuttx/pull/9065#issuecomment-1540002733

   > > In smp when cpu0 calls up_cpu_resume to release the cpu1 lock, another 
locked cpu1 did not execute immediately, and soon cpu0 called up_cpu_resume 
again, now cpu1 unable to respond to the interrupt at this time, resulting in a 
deadlock. Our solution is to restore cpu1 execution from asynchronous to 
synchronous to ensure that cpu1 is restored.
   > 
   > @hujun260 Could you tell us how to reproduce the issue with the ostest?
   
   I found that this issue is in the test case pthread_rwlock_cancel_test(), 
where pthread_cancel() will get stuck.
   The replication method is to start multiple qemu and conduct stress testing. 
   There is a certain probability that it will occur,
   and the analysis conclusion is that the CPU cannot respond to interrupts, 
resulting in a deadlock.


-- 
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

Reply via email to