On 2011-05-23 Steven M. Hartman wrote:
> Dirk Zimoch wrote:
> > Second incident:
> > An other IOC lost CA connectivity. This time the error message was
> > different:
> > CA beacon (send to "...") error was "ENOBUFS"
> This one is similar to what SNS has seen over the years with mv2100
> and related boards with the DEC network driver. The precipitating
> event is a temporary loss of the physical network layer (i.e.
> unplugged network cable to IOC, or edge network switch powered
> down). It looks like a buggy network driver that cannot recover from
> this fault when there are lots of UDP packets queuing in the
> outgoing buffers. This one does not seem to be recoverable except by
> a reboot so we have taken steps to reduce the likelihood of loosing
> the physical link. We do not see this with other boards.
I found and fixed a few issues in the dec21x40End.c driver for vxWorks 5.5.x
in 2009. The main one was to make DMA underflow a recoverable event (which
might be relevant to this problem), but I also fixed the packet counting which
wasn't working properly in this driver. I believe I sent Dave Thompson my
fixes at the time, but whether they got into the SNS version or not I don't
On a related question, have you ever heard of an mv2100 BSP for vxWorks 6.x?
I'm currently working on upgrading the mv2700 BSP from 6.4 to 6.8, but I can't
find an mv2100 BSP for any 6.x OS version at the Wind River website.
Optimization is the process of taking something that works and
replacing it with something that almost works, but costs less.
-- Roger Needham
- Re: vxWorks network problems Dirk Zimoch
- vxWorks network problems Dirk Zimoch
- Re: vxWorks network problems Steven M. Hartman
- Navigate by Date:
Re: caGateway crashes / use of *MustSucceed functions Benjamin Franksen
Windows XP Cygwin difficulties for building EPICS base Cid, Florencio A
- Navigate by Thread:
Re: vxWorks network problems Steven M. Hartman
Re: vxWorks network problems Dirk Zimoch