This error:
> interrupt
> eio: reset
> I have seen references to "interrupt, eio: reset" in tech-talk"
> whatever causes that message seems to be benign.
I have seen this error in 2 circumstances, and only on MVME167 CPUs under
vxWorks 5.4 and EPICS R3.13.3.
1) Right after iocInit. In that case it seems to be benign, as you suggest.
2) After several hours of intense communication with some non-TCP/IP
Ethernet modules, using etherInputHookAdd. In that case the error is
serious, the IOC cannot communicate on the network at all, although there is
no other indication from the vxWorks console that anything is amiss. This
problem is an active case with WRS for me now.
The software which is running when we get this failure is basically
unchanged from software which works fine under vxWorks 5.3 and EPICS
R3.13.1.1.
Mark Rivers
- Navigate by Date:
- Prev:
socket creation errors Graham Waters
- Next:
RE: socket creation errors Jeff Hill
- 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: socket creation errors Graham Waters
- Next:
Keithley 7002/2010 data aquisition Mathew Rippa
- 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
|