Peter,
intrCallbackOctet is used to implement "I/O Intr" scanning.
To get more information (which record are involved, etc), try to enable
debugging and direct the debug output to a file:
StreamDebugFile=fopen("filename","w")
streamDebug=1
However, this might give lots of output and the timing might change slightly. I
have seen situations, where the bug disappears when debugging is enabled.
Have you seen similar effects on Linux IOCs? I can't test everything on vxWorks
here, because of the variety of existing hardware.
Does it happen during startup or later? I can't see any direct relation between
autosave and StreamDevice/asyn.
Dirk
Denison, PN (Peter) wrote:
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.
--
Dr. Dirk Zimoch
Computing and Controls
Paul Scherrer Institut
phone +41 56 310 5182
fax +41 56 310 4413
- References:
- RE: Asyn assertion failure (long) Denison, PN (Peter)
- Navigate by Date:
- Prev:
RE: Asyn assertion failure (long) Denison, PN (Peter)
- Next:
ARCnet on Linux Jiro Fujita
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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:
RE: Asyn assertion failure (long) Denison, PN (Peter)
- Next:
Asyn and a 3rd party API? Bertrand H.J. Biritz
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|