EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: Problem with dbCaLink task in 3.14.4
From: "Mark Rivers" <[email protected]>
To: "Marty Kraimer" <[email protected]>
Cc: <[email protected]>
Date: Fri, 31 Oct 2003 08:42:44 -0600
Marty wrote:

> Nothing obvious. The failure occurs on the statement
> 
> epicsMutexMustLock(pca->lock);
> 
> Other than memory corruption it is hard to explain why this fails.
> 
> Does this happen the very first time $(P)AbortScansSEQ is processed?

Yes.

> Before it is processed issue the instruction
> 
> dbcar "$(P)AbortScansSEQ",3
> 
> Does it show everything connected?

Here's the output, everything is connected.

ioc13lab> dbcar "13LAB:AbortScansSEQ",3
    connected ioc13lab 13LAB:AbortScansSEQ.LNK1 13LAB:scanH.EXSC
    connected ioc13lab 13LAB:AbortScansSEQ.LNK2 13LAB:scan1.EXSC
    connected ioc13lab 13LAB:AbortScansSEQ.LNK3 13LAB:scan2.EXSC
    connected ioc13lab 13LAB:AbortScansSEQ.LNK4 13LAB:scan3.EXSC
    connected ioc13lab 13LAB:AbortScansSEQ.LNK5 13LAB:scan4.EXSC
ncalinks 5 not connected 0 no_read_access 0 no_write_access 0
 nDisconnect 0 nNoWrite 0
ca_client_context at 0x15baf50 pndRecvCnt=0 ioSeqNo=0
epicsMutexId 0x15bad58 source ../../../src/libCom/osi/epicsMutex.cpp line 196
Channel Access Client Context at 0x15a3cf0 for user iocboot
        revision "@(#) EPICS 3.14.4, CA Portable Server Library Oct  6 2003"
        preemptive callback is enabled
        there are 0 unsatisfied IO operations blocking ca_pend_io()
        the current io sequence number is 0
IO done event:

Semaphore Id        : 0x15a6c90   
Semaphore Type      : BINARY    
Task Queuing        : FIFO      
Pended Tasks        : 0         
State               : EMPTY     

Is the message about the epicsMutexId with the source code line number normal?

Memory corruption is certainly possible, but if I don't process that one record then the IOC runs for many weeks with no other symptoms of problems.  The same record causes the same problem in multiple IOCs with very different configurations (records loaded, SNL programs running, etc.).

Mark



Navigate by Date:
Prev: Re: Problem with dbCaLink task in 3.14.4 Marty Kraimer
Next: RE: Problem with dbCaLink task in 3.14.4 Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Problem with dbCaLink task in 3.14.4 Marty Kraimer
Next: RE: Problem with dbCaLink task in 3.14.4 Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·