From owner-freebsd-current  Thu May  9 01:28:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id BAA27511
          for current-outgoing; Thu, 9 May 1996 01:28:59 -0700 (PDT)
Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA27500
          Thu, 9 May 1996 01:28:53 -0700 (PDT)
Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id BAA14028; Thu, 9 May 1996 01:28:40 -0700
From: Brian Litzinger <brian@MediaCity.com>
Message-Id: <199605090828.BAA14028@MediaCity.com>
Subject: Re: Continued MBUF problem with ET V.35 card
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Thu, 9 May 1996 01:28:40 -0700 (PDT)
Cc: randy@zyzzyva.com, et-users@netrail.net, freebsd-isp@FreeBSD.ORG,
        stable@FreeBSD.ORG, current@FreeBSD.ORG
In-Reply-To: <199605090148.LAA01217@genesis.atrad.adelaide.edu.au> from Michael Smith at "May 9, 96 11:18:23 am"
Reply-To: brian@MediaCity.com
X-Mailer: ELM [version 2.4ME+ PL11 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Michael Smith wrote:
> Randy Terbush stands accused of saying:
> > 
> > As some of you may remember, I reported a problem with MBUF leakage
> > on a FreeBSD-stable system running an Emerging Technologies ET5025
> > card. After Dennis' indication that the problem was FreeBSD-stable
> > and rather strong suggestion that I need to be running 2.1.0, I 
> > have reinstalled this system running stock FreeBSD-2.1.0. The
> > problem still exists and can be directly related to activity over
> > the 56K connection. A much busier system of same kernel vintage
> > without the ET drivers hovers at around '75 mbufs in use' after
> > several days of uptime.  The system will reach it's max of 4096K
> > after about 48 hours of uptime and eventually reboot. I'm at a loss
> > for how to track this down and would heartily welcome more 
> > productive suggestions.
> 
> Hit Dennis on the head and get him to admit that it's his drivers 8)

Some months ago, I worked with Dennis to track down the mbuf leak
problem.  The leak was in FreeBSD code, not his driver.

Disclaimer:  dennis may have introduced a new leak since we worked on
             tracking down the one I ran into.

Brian Litzinger
brian@mediacity.com