From owner-freebsd-questions Tue Jul 3 14:47:57 2001 Delivered-To: freebsd-questions@freebsd.org Received: from aries.ai.net (aries.ai.net [205.134.163.4]) by hub.freebsd.org (Postfix) with ESMTP id 42C4F37B401 for ; Tue, 3 Jul 2001 14:47:50 -0700 (PDT) (envelope-from deepak@ai.net) Received: from blood (adsl-138-88-44-228.bellatlantic.net [138.88.44.228]) by aries.ai.net (8.9.3/8.9.3) with SMTP id RAA19110 for ; Tue, 3 Jul 2001 17:50:59 -0400 (EDT) (envelope-from deepak@ai.net) Reply-To: From: "Deepak Jain" To: Subject: RE: TX buffer in 4.3 Date: Tue, 3 Jul 2001 17:51:50 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <20010703161057.O47870@elvis.mu.org> Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill's explanation here is very thorough, but unless you know what he means by the last comment, it won't necessarily help you. What he is suggesting is adding a line to your kernel config, options NMBCLUSTERS=2048 (for example) and loading the new kernel. This should solve your transmit issues on the server in question. The FreeBSD handbook probably tells you how to get the kernel sources if you don't have them and build the new kernel. If you already know how to do this, then I am just mentioning it for pedantic concerns. Deepak Jain AiNET -----Original Message----- From: owner-freebsd-hackers@FreeBSD.ORG [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Bill Fumerola Sent: Tuesday, July 03, 2001 5:11 PM To: Randy -Harborside Internet Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: TX buffer in 4.3 [ not -hackers material, moved to questions ] On Tue, Jul 03, 2001 at 01:53:43PM -0700, Randy -Harborside Internet wrote: > We are having a problem with our mail server. It recently got > upgraded to 4.3 from 4.2, and now it is having problems with the TX > buffer somehow on the network card. Every once in awhile it will shut > off all network traffic and give these errors: > no memory for tx listrl0 > Then in a few minutes (presumably when the buffer is flushed somehow) > the network device resumes normal operation. s#flushed#drained# > We have tried 3 different NICs, and all have had the same problem. > The three models were: > 1. Realtek RTL8139A 10/100TX rl(4): rl%d: no memory for tx list The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. > 2. Intel chipset:82558B fxp(4): fxp%d: Failed to malloc memory There are not enough mbuf's available for allocation. > 3. 3Com somethingerather. I'll assume you mean the etherlink(3c905) chips... xl(4): xl%d: no memory for tx list The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an mbuf chain into a cluster. > We are running with 512MB of RAM, and it usually has about 200 or > more megs free at the time of this occurance. Which doesn't matter if you don't allocate enough memory to the mbuf subsystem. See below. > Is this a problem with the network drivers in 4.3? Or something else > that can be corrected? (Manual way to flush the network card > buffers??) Flush the network card buffers? That really wouldn't help anything. > Here is the output of ulimit -a, just in case that helps. It doesn't. If you look at the output of 'netstat -m' you'll see you've run mbufs (well, mbuf clusters) and that is whats causing this problem. The "requests for memory" lines will show you how many times this has bitten you in the proverbial ass. options NMBCLUSTERS is your friend. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message