From owner-freebsd-hardware Tue Aug 10 14: 7:34 1999 Delivered-To: freebsd-hardware@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id A9B5F14D41 for ; Tue, 10 Aug 1999 14:07:26 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (209-122-196-239.s239.tnt5.lnh.md.dialup.rcn.com [209.122.196.239]) by tasam.com (8.9.3/8.9.1) with SMTP id RAA06936; Tue, 10 Aug 1999 17:06:57 -0400 (EDT) Message-ID: <001401bee374$41aa8bc0$0286860a@tasam.com> From: "Joe Gleason" To: , References: <37b042f0.7cfd.0@socket.net> Subject: Re: Problems with a pair of 3c905b's Date: Tue, 10 Aug 1999 17:06:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For the network card issue, I suggest that you either upgrade to 3.2-stable or goto http://www.freebsd.org/~wpaul/ and see if there are newer xl0 drives you could use. The later is the simplest, but will require a kernel recompile. I remember a discussion on one of the list a while back. The main idea of it was that increasing individual items such NMBCLUSTERS instead of increasing MAXUSERS will yeild better/more reliable results. Look in LINT for examples of how to do either. Joe Gleason Tasam ----- Original Message ----- From: To: Sent: Tuesday, August 10, 1999 12:19 Subject: Problems with a pair of 3c905b's > I've got a 3.2 box running squid on a Internet routed network and a separate > local network, used by the customers of the ISP I work for. It probably deals > with a significant amount of traffic. Since I brought the machine to life, > I've had virtually no problems. However, occasionally, the server will loose > it's network connectivity. > The console had panic messages of "kernel: xl0: no memory for rx list -- packet > dropped!" for xl0 and xl1. > > Upon reboot, the system would be fine. I fear that this has happened before, > and will occur again. In the /var/log/messages archive, I located what looked > like the beginning of the problem, "kernel: Out of mbuf clusters - adjust NMBCLUSTERS > or increase maxusers". I'm running the generic 3.2 kernel which has maxusers > 32, which i thought would be more than sufficient. > NMBCLUSTERS I'm not sure of. > > Does anyone have any suggestions or info about this situation? > > > Nathan Mahon > vaevictus@socket.net > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message