EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: channel access
From: "Jeff Hill" <[email protected]>
To: "Coleman, Thomas A." <[email protected]>, <[email protected]>
Date: Mon, 19 Nov 2001 14:56:17 -0700
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"

There is a pool of network buffers called "MBUFS" and in some cases
"clusters" that are maintained by your vxWorks IP kernel.
In situations where these buffers are scarce, programs
such as CA detect that the socket interface is returning the ENOBUFS 
error number, and network requests are refused.

To determine the number of free network buffers in your system type 
mbufShow. On Tornado II you may also find that netStackDataPollShow() 
and netStackSysPoolShow() provide useful information.

I have heard rumors that with certain versions of vxWorks operating in
a scarce network buffers situation can have severe consequences such as 
IP kernel lock ups.

You can increase the default number of buffers. This is done differently
depending on whether the SENS IP kernel is installed. The SENS IP kernel
is optional in Tornado I and mandatory in Tornado II.

When configuring the original vxWorks IP kernel look at section 5.3.10 in 
the Tornado I programmer's guide.

When configuring Tornado II systems look at chapter 4.6.3 in the vxWorks
network programmer's guide.

Jeff


> 
> Any suggestions on where to look for this problem?
> "No Buffers"? What buffers are limited
> and how to I increase them?
> I'm running 3.13.5 on a 4MB 680x0 ioc.
> Thanks
> 
> Tom
> 
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> sendto failed: S_errno_ENOBUFS
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> sendto failed: S_errno_ENOBUFS
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"
> 0x149bc8 (CA_online): ../online_notify.c: CA beacon error was
> "S_errno_ENOBUFS"


References:
RE: channel access Coleman, Thomas A.

Navigate by Date:
Prev: Re: channel access Andrew Johnson
Next: RE: channel access Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  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: channel access Andrew Johnson
Next: increasing the number of file descriptors Geoff Savage
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·