EPICS Deadlock on VxWorks 6.7

Experimental Physics and Industrial Control System

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024	Index	2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024
<== Date ==>		<== Thread ==>

Subject:	Deadlock on VxWorks 6.7
From:	"Zimoch Dirk \(PSI\) via Core-talk" <core-talk at aps.anl.gov>
To:	"'core-talk at aps.anl.gov'" <core-talk at aps.anl.gov>
Date:	Wed, 2 Jun 2021 09:23:40 +0000

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

Replies:: AW: Deadlock on VxWorks 6.7 Zimoch Dirk (PSI) via Core-talk; Re: Deadlock on VxWorks 6.7 Michael Davidsaver via Core-talk

Navigate by Date:: Prev: [Bug 541371] Re: assert (ev_que->evque[ev_que->putix] == EVENTQEMPTY) failed in dbEvent.c Dirk Zimoch via Core-talk; Next: AW: Deadlock on VxWorks 6.7 Zimoch Dirk (PSI) via Core-talk; Index: 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024
Navigate by Thread:: Prev: Build failed: epics-base base-integration-708 AppVeyor via Core-talk; Next: AW: Deadlock on VxWorks 6.7 Zimoch Dirk (PSI) via Core-talk; Index: 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024