Date: Wed, 3 Jan 2001 10:10:09 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: "C. Stephen Gunn" <csg@waterspout.com> Cc: freebsd-net@freebsd.org Subject: Re: 'no memory for rx list' Message-ID: <20010103101008.I19572@fw.wintelcom.net> In-Reply-To: <20010103092448.A594@waterspout.com>; from csg@waterspout.com on Wed, Jan 03, 2001 at 09:24:48AM -0500 References: <20010102071809.G19572@fw.wintelcom.net> <20010103092448.A594@waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* C. Stephen Gunn <csg@waterspout.com> [010103 06:22] wrote: > On Tue, Jan 02, 2001 at 07:18:10AM -0800, Alfred Perlstein wrote: > > > I notice that if_fxp.c seems to fail silently when unable to > > allocate network buffers, perhaps the fact that the kernel can > > be doing about 200 or more messages per-second makes me guess > > that it's not helping things, especially when the box has a > > serial console. > > > > I'm taking the printf's out of my copy of if_xl.c on a 3.5 > > system, I'll let you know if it still goes nuts for extended > > amounts of time. > > You could change the printf()'s to log()'s, and allow syslogd > to filter/combine/report them on your console. I'm sure you > already know this, you could increase NBMCLUSTERS and friends > in your kernel config, or at boot time. (For posterity in > the list archives). I really don't see any point in assisting a cascade-like failure situation by adding more work that the kernel has to do when faced with a shortage. Raising nmbclusters will help, but only to delay the problem. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010103101008.I19572>