Re: Deadlock on VxWorks 6.7

[Michael Davidsaver via Core-talk <core-talk at aps.anl.gov>]

On 6/2/21 2:23 AM, Zimoch Dirk (PSI) via Core-talk wrote:
> Hi,
> 
> When I use EPICS 7.0.5.1 or 7.0.4.1 on mv mv5100 running VxWorks 6.7, I see shortly after booting:
> 
> 0x132f380 (timerQueue): epicsSpinLock(0x1fda0b79): Deadlock.
> Recursive lock, missed unlock or block when locked.Thread timerQueue (0x132f380) can't proceed, suspending.
> 
> Any idea?

Not immediately, though I'm more familiar with the RTEMS side.
I don't see any recursive call in the stack trace you provided.
Is it possible that the behavior of taskLock() has changed wrt. disabling interrupts?

> Why spinlocks on a single core CPU machine?

The RTEMS and vxWorks implementations don't actually spin.

https://github.com/epics-base/epics-base/blob/b777233efb06fa4e988c4f0738b0270dd3d095a3/modules/libcom/src/osi/os/vxWorks/osdSpin.c#L64-L86