Re:The behavior of spin_lock needs everyone's advice

I reverted the relevant changes. https://github.com/apache/nuttx/pull/15767 At 2025-02-05 13:06:29, "chao an" wrote: >Hi, > >The behavior of spin_lock needs everyone's advice > >After PR14578 was merged into >the NuttX, the behavior of s

Re:sched lock/unlock issue on rp2350

It seems to have nothing to do with the race condition, and since the rtcb is this_task, it will only be modified by one CPU. As for why your modification can solve the problem, I haven't figured it out yet. Can you further analyze the reasons for the failure to boot? At 2025

Re:sched lock/unlock issue on rp2350

It seems to have nothing to do with the race condition, and since the rtcb is this_task, it will only be modified by one CPU. As for why your modification can solve the problem, I haven't figured it out yet. Can you further analyze the reasons for the failure to boot? At 2025-04

Re:sched lock/unlock issue on rp2350

It seems to have nothing to do with the race condition, and since the rtcb is this_task, it will only be modified by one CPU.As for why your modification can solve the problem, I haven't figured it out yet. Can you further analyze the reasons for the failure to boot? At 2025-04-22 13:25:13, "Ser

Re:Re: sched lock/unlock issue on rp2350

cb != NULL && rtcb->lockcount == 1) > { >irqstate_t flags = enter_critical_section_wo_note(); >+ rtcb->lockcount = 0; > >/* Note that we no longer have pre-emption disabled. */ > >-- >2.49.0 >On 4/22/25 14:32, hujun260 w