From owner-freebsd-current  Mon May  6 08:46:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA20595
          for current-outgoing; Mon, 6 May 1996 08:46:16 -0700 (PDT)
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id IAA20576
          Mon, 6 May 1996 08:46:12 -0700 (PDT)
Received: from acpc.cs.rice.edu (acpc.cs.rice.edu [128.42.1.67]) by cs.rice.edu (8.7.1/8.7.1) with ESMTP id KAA10387; Mon, 6 May 1996 10:46:10 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1]) by acpc.cs.rice.edu (8.7.3/8.7.3) with ESMTP id KAA00271; Mon, 6 May 1996 10:46:10 -0500 (CDT)
Message-Id: <199605061546.KAA00271@acpc.cs.rice.edu>
To: Randy Terbush <randy@zyzzyva.com>
cc: "Matthew N. Dodd" <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 10:15:13 CDT."
             <199605061516.KAA16859@sierra.zyzzyva.com> 
Date: Mon, 06 May 1996 10:46:08 -0500
From: Alan Cox <alc@cs.rice.edu>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> I found after much hair pulling that if I define NMBCLUSTERS=4096
> for my -stable kernel build, the machine will crash every time I
> try to run X.

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.

	Alan