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  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: sscan, asyn and mutexes [SEC=UNCLASSIFIED]
From: "LYNCH, Damien" <[email protected]>
To: <[email protected]>
Date: Tue, 17 Nov 2009 11:20:47 +1100
Hi Tim,

It looks like the modified sscanRecod.c file has fixed the problem. I
started the IOC 500 times and could not reproduce the problem. Thanks
for that, and thanks to Mark as well.

Damien

> -----Original Message-----
> From: Tim Mooney [mailto:[email protected]]
> Sent: Tuesday, 17 November 2009 10:18 AM
> To: LYNCH, Damien
> Cc: [email protected]
> Subject: Re: sscan, asyn and mutexes [SEC=UNCLASSIFIED]
> 
> Damien,
> I think the problem might that version 2-6-5 of the sscan module is
not
> ready for a 64-bit architecture. sscanRecord.c contains some
structures
> that are supposed to match exactly the record structure defined in the
> sscanRecord.h include file, which is generated by the EPICS build from
> sscanRecord.dbd. But the definitions in sscanRecord.c do not match
> exactly anymore, and the code must be modified. Mark Rivers did this,
> but I haven't published a version of the sscan module with Mark's
fixes.
> I'm sending you a copy of the most recent sscanRecord.c, but I'll not
> blast it to all tech-talk recipients. Please try this and see if the
> problem goes away or at least changes.
> 
> Tim
> 
> LYNCH, Damien wrote:
> > Has anyone run into the following mutex locking failure before? I
have
> > only seen the problem when drvSerialPortConfigure is called and a
sscan
> > record is loaded. In the example below there is only the sscan
record
> > specified in sscantest.db. Occasionally the IOC will start fine.
> > We have been running an IOC using base 3.14.9, asyn 4.9 and sscan
2-5-6
> > and never seen this problem.
> >
> >
> > dly@antares14:~/sscantest/iocBoot/iocsscantest>
> > ../../bin/linux-x86_64/sscantest st.cmd
> > #!../../bin/linux-x86_64/sscantest
> > ## You may have to change sscantest to something else
> > ## everywhere it appears in this file
> > < envPaths
> > epicsEnvSet("ARCH","linux-x86_64")
> > epicsEnvSet("IOC","iocsscantest")
> > epicsEnvSet("TOP","/home/dly/sscantest")
> > epicsEnvSet("ASYN","/usr/local/src/EPICS/asyn/4-12")
> > epicsEnvSet("SSCAN","/usr/local/src/EPICS/sscan/2-6-5")
> > epicsEnvSet("EPICS_BASE","/usr/local/src/EPICS/base-3.14.11")
> > cd /home/dly/sscantest
> > ## Register all support components
> > dbLoadDatabase "dbd/sscantest.dbd"
> > sscantest_registerRecordDeviceDriver pdbbase
> > drvAsynSerialPortConfigure("src", "/dev/ttyr07")
> > ## Load record instances
> > dbLoadRecords("db/sscantest.db","user=dlyHost")
> > cd /home/dly/sscantest/iocBoot/iocsscantest
> > iocInit
> > Starting iocInit
> >
########################################################################
> > ####
> > ## EPICS R3.14.11 $R3-14-11$ $2009/08/28 18:47:36$
> > ## EPICS Base built Nov 16 2009
> >
########################################################################
> > ####
> >
> >
> >
> > A call to 'assert(status == epicsMutexLockOK)'
> >     by thread '_main_' failed in ../dbPvdLib.c line 90.
> > EPICS Release EPICS R3.14.11 $R3-14-11$ $2009/08/28 18:47:36$.
> > Local time is 2009-11-16 14:24:25.500100161 EST
> > Please E-mail this message to the author or to [email protected]
> > Calling epicsThreadSuspendSelf()
> >
> >
> > Thanks,
> > Damien Lynch
> > Accelerator IT Systems Engineer
> > Institute of Environmental Research
> > Australian Nuclear Science and Technology Organisation
> > PMB 1, Menai NSW 2234
> >
> > Important: This transmission is intended only for the use of the
> > addressee. It is confidential and may contain privileged information
or
> > copyright material. If you are not the intended recipient, any use
or
> > further disclosure of this communication is strictly forbidden. If
you
> > have received this transmission in error, please notify me
immediately
> > by telephone and delete all copies of this transmission as well as
any
> > attachments.
> >
> >
> >
> >
> 
> 
> --
> Tim Mooney ([email protected]) (630)252-5417
> Beamline Controls & Data Acquisition Group (www.aps.anl.gov/aod/bcda)
> Advanced Photon Source, Argonne National Lab



References:
sscan, asyn and mutexes [SEC=UNCLASSIFIED] LYNCH, Damien
Re: sscan, asyn and mutexes [SEC=UNCLASSIFIED] Tim Mooney

Navigate by Date:
Prev: Re: sscan, asyn and mutexes [SEC=UNCLASSIFIED] Tim Mooney
Next: why doesnt the include file install set the file permisions to unwritable? Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: sscan, asyn and mutexes [SEC=UNCLASSIFIED] Tim Mooney
Next: why doesnt the include file install set the file permisions to unwritable? Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·