From owner-freebsd-stable Tue Jun 18 21:38:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by hub.freebsd.org (Postfix) with ESMTP id 1965237B403 for ; Tue, 18 Jun 2002 21:38:14 -0700 (PDT) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.4/8.12.1) with ESMTP id g5J4c3XU029472; Wed, 19 Jun 2002 00:38:03 -0400 (EDT) X-Authentication-Warning: angelica.unixdaemons.com: Host bmilekic@localhost.unixdaemons.com [127.0.0.1] claimed to be angelica.unixdaemons.com Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.4/8.12.1/Submit) id g5J4c2nE029467; Wed, 19 Jun 2002 00:38:02 -0400 (EDT) (envelope-from bmilekic) Date: Wed, 19 Jun 2002 00:38:02 -0400 From: Bosko Milekic To: "Scot W. Hetzel" Cc: FreeBSD-Stable Subject: Re: System running out of mbufs Message-ID: <20020619003802.A28956@unixdaemons.com> References: <011101c2165e$cbc5f400$11fd2fd8@ADMIN00> <20020617220556.A97210@unixdaemons.com> <000001c21730$d36cff00$12fd2fd8@Admin01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <000001c21730$d36cff00$12fd2fd8@Admin01>; from hetzels@westbend.net on Mon, Jun 17, 2002 at 09:22:58PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 17, 2002 at 09:22:58PM -0500, Scot W. Hetzel wrote: > From: "Bosko Milekic" > > Can you try something other than the ET Inc. driver? They may be > > right, but you should still try to make sure. > > > There is no other driver for the ET Inc ET/5025PQ QUAD Adapter (4 Port T1). > The only part of their driver we are using is the pre-compiled et5025.o > object. We don't replace if_ethersub.c with if_etherbwmgr.o, as we are > currently not using any bandwidth management features of the driver. Uhm, yeah, I know that there are no other drivers for their devices! What I suggested was that you try ANOTHER device entirely with another driver. I have had an unfortunate experience previously where I had spent about a day helping someone debug this sort of problem, someone who was also using an ET Inc device and finally we reached the conclusion that the driver was outdated by some minor interface changes. I had received less than helpful support from the ET Inc guys then and I am not about to begin debugging a problem of this sort involving their driver until I am sure that it is not their driver that is somehow involved in the problem. > We have tried two different versions of their driver (3.21i & 3.21k), > without any success to resolving this problem. > > Scot Regards, -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message