AW: Deadlock on VxWorks 6.7

["Zimoch Dirk \(PSI\) via Core-talk" <core-talk at aps.anl.gov>]

I have not tried vxWorks 6.9 yet. But on vxWorks 5.5 it works fine.

> -----Ursprüngliche Nachricht-----
> Von: Mark Rivers <rivers at cars.uchicago.edu>
> Gesendet: Mittwoch, 2. Juni 2021 15:44
> An: Zimoch Dirk (PSI) <dirk.zimoch at psi.ch>
> Cc: core-talk at aps.anl.gov
> Betreff: Re: Deadlock on VxWorks 6.7
> 
> I am running base 7.0.4 with an MVME5100 and vxWorks 6.9.4.1.  I don't see
> this problem.
> 
> 
> Mark
> 
> 
> 
> ________________________________
> From: Core-talk <core-talk-bounces at aps.anl.gov> on behalf of Zimoch Dirk
> (PSI) via Core-talk <core-talk at aps.anl.gov>
> Sent: Wednesday, June 2, 2021 8:23 AM
> To: 'core-talk at aps.anl.gov'
> Subject: AW: Deadlock on VxWorks 6.7
> 
> This is the stack:
> 0x00129904 vxTaskEntry  +0x48 : epicsThreadEntry ()
> 0x010ff634 epicsThreadEntry+0x80 : epicsThreadCallEntryPoint ()
> 0x010f5638 epicsThreadCallEntryPoint+0xe8 : timerQueueActive::run() ()
> 0x0110c594 timerQueueActive::run()+0x6c : timerQueue::process(const
> epicsTime &) ()
> 0x0110bb2c timerQueue::process(const epicsTime &)+0x30c:
> epicsTimerForC::expire(const epicsTime &) ()
> 0x01109f40 epicsTimerForC::expire(const epicsTime &)+0x20 : 0x00775500 ()
> 0x0077556c __dso_handle +0x254c: scanIoRequest ()
> 0x0105d708 scanIoRequest+0x8c : 0x01068bd0 ()
> 0x01068c88 callbackRequest+0xbc : epicsRingPointerPush ()
> 0x0110649c epicsRingPointerPush+0x38 : epicsSpinLock ()
> 0x01100270 epicsSpinLock+0x168: cantProceed ()
> 0x010ecba8 cantProceed  +0x11c: epicsThreadSuspendSelf ()
> 0x010ff3b8 epicsThreadSuspendSelf+0x2c : taskSuspend ()
> 
> > -----Ursprüngliche Nachricht-----
> > Von: Core-talk <core-talk-bounces at aps.anl.gov> Im Auftrag von Zimoch
> Dirk
> > (PSI) via Core-talk
> > Gesendet: Mittwoch, 2. Juni 2021 11:24
> > An: 'core-talk at aps.anl.gov' <core-talk at aps.anl.gov>
> > Betreff: Deadlock on VxWorks 6.7
> >
> > 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?
> >
> > Why spinlocks on a single core CPU machine?
> >
> > Dirk