Re: issues with drvEtherIP V2.19 - ControlLogix 5000 PLC via EtherNet/IP

["Steven M. Hartman" <hartmansm@ornl.gov>]

Jeff Hill wrote:
> -> tt 0x1b22fd0
> 194e58 vxTaskEntry    +60 : 1c286f4 ()
> 1c28860 epicsTimeToStrftime+12a8: 1c28150 ()
> 1c2868c epicsTimeToStrftime+10d4: 1c244ec ()
> 1c24878 drvSerialGetFile+bac: scanOnce (1bdff10)
> 13eafc rngBufPut      +e0 : bcopy ()

Hello, Jeff--

We have a large number of VxWorks IOC running ether-ip 2.19 and we 
have not seen this problem.

From the limited information in the task trace, it looks like one 
of the check_xxx_callback functions in devEtherIP.c is calling 
scanOnce(rec). In dbScan.c, I'm guessing epicsRingPointerPush() is 
calling rngBufPut (or at least something nearby) which is calling 
bcopy which is apparently trying to use some memory which it 
shouldn't, throwing an exception.

As Kay pointed out, the argument to scanOnce() should be a pointer 
to a record. As long as this is a valid pointer to a valid record, 
I don't see how this exception could be caused by a bug in 
ether-ip. Can you poke around 0x1bdff10 and see what's there? If 
it is not really a record, try to get some more information as to 
what is happening (EIP_verbosity=7 or more, maybe recompile 
devEtherIP without static for the check_xxx_callback functions so 
the trace will tell us which one, set record TPRO=1, etc).

Also, can you run your IOC stripped down without the other device 
drivers? It could be that some other driver is clobbering some 
memory somewhere which ether-ip is stumbling over.

--
Steven Hartman
hartmansm@ornl.gov || 865-466-6473