EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: Asyn assertion failure (long)
From: "Denison, PN \(Peter\)" <[email protected]>
To: "Dirk Zimoch" <[email protected]>
Cc: TechTalk EPICS <[email protected]>
Date: Fri, 22 Jun 2007 11:05:41 +0100
> From: Dirk Zimoch [mailto:[email protected]] 
> 
> Denison, PN (Peter) wrote:
> > Asyn 4-8, streamDevice 2-2, EPICS 3.14.8.2, vxWorks 5.5.1 
> > on MVME5500
> > 
> What port driver are you using? One of those provided with 
> asyn (serial, TCP, ...) or a third party driver?

We're using the asynSerialPort, on top of a Hytec 8516 RS-485 module in
a Hytec 8002 IP carrier.
 
> About 600 chars: The asynInterposeEos layer uses an internal 
> buffer of 600 chars which it passes to lower level drivers.
> 
> As it may also be a bug in StreamDevice, please send me your 
> protocol file and records so that I can try to reproduce your
> problem.

Sure. We are trying to cut it down to the minimum to cause it to fail,
and also trying to reproduce on a test system, as the production IOC
will have to roll back to a working version for our next run starting on
Monday.

The crash appears to be in StreamDevice (data is trashed between the
calls to callInterruptUsers() and interruptEnd(), seemingly in the
intrCallbackOctet callback).

However, in trying to isolate it, the behaviour changes when autosave
state changes. We are using autosave 4-2-1, with local modifications to
the names of the status PVs.

Thanks for your help - I'll keep you posted.

-- 
Peter Denison, Senior Software Engineer
Diamond Light Source Ltd.
Tel: +44 1235 778511
(apologies in advance for the lines below. I have no control over it)

<DIV><FONT size="1" color="gray">This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
</FONT></DIV> 


Replies:
Re: Asyn assertion failure (long) Dirk Zimoch
References:
Re: Asyn assertion failure (long) Dirk Zimoch

Navigate by Date:
Prev: Re: Basic Question regarding input links Benjamin Franksen
Next: Re: Asyn assertion failure (long) Dirk Zimoch
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Asyn assertion failure (long) Dirk Zimoch
Next: Re: Asyn assertion failure (long) Dirk Zimoch
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·