Date: Thu, 13 Apr 2000 13:42:35 +0000 (GMT) From: Kiril Mitev <kiril@ideaglobal.com> To: sheldonh@uunet.co.za (Sheldon Hearn) Cc: kiril@ideaglobal.com, freebsd-questions@FreeBSD.ORG Subject: Re: "no memory for rx list" Message-ID: <200004131342.NAA78342@loki.ideaglobal.com> In-Reply-To: <8237.955632901@axl.ops.uunet.co.za> from Sheldon Hearn at "Apr 13, 2000 3:35: 1 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you. :-)) > > > On Thu, 13 Apr 2000 13:07:57 GMT, Kiril Mitev wrote: > > > Dear All .... therein a log dump from one of our > > (rather busy) servers: > > I'm glad you mentioned that, since it makes the explanation more > plausible. :-) > > > Apr 12 23:32:39 excalibur /kernel: xl1: no memory for rx list -- > > packet dropped! > > The manual page for the xl(4) driver says: > > xl%d: no memory for rx list The driver failed to allocate an > mbuf for the receiver ring. > > Using the search engine on the FreeBSD web page to search for "mbuf", > the first hit I get turns up this: > > The panic indicates that the system ran out of virtual memory > for network buffers (specifically, mbuf clusters). You can > increase the amount of VM available for mbuf clusters by adding: > > options "NMBCLUSTERS=<n>" > > to your kernel config file, where <n> is a number in the range > 512-4096, depending on the number of concurrent TCP connections > you need to support. I'd recommend trying 2048 - this should get > rid of the panic completely. You can monitor the number of mbuf > clusters allocated/in use on the system with netstat -m. The > default value for NMBCLUSTERS is 512 + MAXUSERS * 16. > > While you're not getting a panic, the advice is still sound. > > Ciao, > Sheldon. -- Kiril Mitev, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004131342.NAA78342>