EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: mutex lock assertion failure
From: Christian Pulvermacher <[email protected]>
To: "Mark Rivers" <[email protected]>
Cc: tech-talk <[email protected]>
Date: Tue, 15 Nov 2016 14:41:09 +0900
Hello Mark,

yes, there are a number of explicit calls to lockPort(), and also corresponding unlocks in what looks like every case.

Sadly, I ran across this only once, but I'll try to see if I can get a traceback in the future.

Thanks, and kind regards,
Christian

 ---- On Tue, 15 Nov 2016 05:31:12 +0900 Mark Rivers <[email protected]> wrote ---- 
 > Hi Christian, 
 >  
 > The failure indicates to me a problem in your code, because it should not happen.  The failure is happening in pasynManager->lockPort().  Is your code calling that function explicitly?   
 >  
 > Is the failure reproducible? 
 >  
 > Is this on Linux?  If so, you can generate a core file and run gdb on it to get a traceback. 
 >  
 > Mark 
 >  
 >  
 > -----Original Message----- 
 > From: [email protected] [mailto:[email protected]] On Behalf Of Christian Pulvermacher 
 > Sent: Sunday, November 13, 2016 11:35 PM 
 > To: tech-talk 
 > Subject: mutex lock assertion failure 
 >  
 > Hello, 
 >  
 > I encountered the following assertion failure in one of our IOCs. Is this EPICS-internal, or something  that can originate from our own code? 
 >  
 > > A call to 'assert(status == epicsMutexLockOK)'  
 > > by thread 'jtag:dhh.hll0' failed in ../../asyn/asynDriver/asynManager.c line 1694.  
 > > EPICS Release EPICS R3.14.12.5-belle2 $Date: Tue 2015-03-24 09:57:35 -0500$.  
 > > Local time is 2016-11-09 10:44:18.525347533 JST  
 > > Please E-mail this message to the author or to [email protected]  
 >  
 >  
 > Kind regards, 
 > Christian 
 >  
 > 



References:
mutex lock assertion failure Christian Pulvermacher
RE: mutex lock assertion failure Mark Rivers

Navigate by Date:
Prev: Re: OS X edm/medm openmotif woes Jiro Fujita
Next: IOC for keithley 6485 using asyn Paramveer Jain
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: mutex lock assertion failure Mark Rivers
Next: IOC for keithley 6485 using asyn Paramveer Jain
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Nov 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·