From owner-freebsd-isp  Thu May  9 08:59:47 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA18437
          for isp-outgoing; Thu, 9 May 1996 08:59:47 -0700 (PDT)
Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA18382
          Thu, 9 May 1996 08:59:31 -0700 (PDT)
Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id KAA24196; Thu, 9 May 1996 10:59:03 -0500 (CDT)
Message-Id: <199605091559.KAA24196@sierra.zyzzyva.com>
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: brian@mediacity.com, et-users@netrail.net, freebsd-isp@freebsd.org,
        stable@freebsd.org, current@freebsd.org
Subject: Re: Continued MBUF problem with ET V.35 card 
In-reply-to: msmith's message of Thu, 09 May 1996 18:28:30 +0930.
         <199605090858.SAA04548@genesis.atrad.adelaide.edu.au> 
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 09 May 1996 10:59:02 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Brian Litzinger stands accused of saying:
> > > 
> > > 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.
> 
> I should have been more verbose there; it was meant as a joke (hence
> following up with a lengthy suggestion on mbuf-leak-tracing.
> 
> > Disclaimer:  dennis may have introduced a new leak since we worked on
> >              tracking down the one I ran into.
> 
> Did the leak you found get reported and fixed??
> 

Did this get fixed?  I find that the problem exists both in 2.1.0
and -stable.

I can directly connect this problem to packets going over the V.35
interface.