From owner-freebsd-current  Mon May  6 13:24:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA06000
          for current-outgoing; Mon, 6 May 1996 13:24:41 -0700 (PDT)
Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA05975
          Mon, 6 May 1996 13:24:36 -0700 (PDT)
Received: from Root.COM (implode.Root.COM [198.145.90.17]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id NAA15300; Mon, 6 May 1996 13:24:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id NAA07341; Mon, 6 May 1996 13:23:10 -0700 (PDT)
Message-Id: <199605062023.NAA07341@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol
To: Randy Terbush <randy@zyzzyva.com>
cc: michael butler <imb@scgt.oz.au>, alc@cs.rice.edu (Alan Cox),
        winter@jurai.net, freebsd-stable@freebsd.org,
        freebsd-current@freebsd.org
Subject: Re: MBUFs leaking? 
In-reply-to: Your message of "Mon, 06 May 1996 13:15:09 CDT."
             <199605061815.NAA03012@sierra.zyzzyva.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Mon, 06 May 1996 13:23:10 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> Alan Cox writes:
>> 
>> > I've had a similar problem.  However, I hadn't noticed any correlation
>> > with NMBCLUSTERS.  Try rolling back your pmap.c to the -RELEASE version.
>> > That "solved" the problem for me.
>> 
>> Are you running with the associated new ld.so ? If not, try installing it
>> instead of backing out pmap.c,
>> 
>> 	michael
>
>I assume this hasn't been commited to -stable?
>
>I'm beginning to think that I need to run -current to get around
>much of the instability I am running into....

   This is the first I've heard about instability problems with the -stable
pmap.c. You're going to need to provide a lot more information before I'll
be able to diagnose the problem. Also make sure you are running with the most
recent version (1.58.4.3).

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project