From owner-freebsd-questions  Tue Apr  9 05:58:47 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA09824
          for questions-outgoing; Tue, 9 Apr 1996 05:58:47 -0700 (PDT)
Received: from tad.cetlink.net (tad-external.cetlink.net [206.31.104.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA09815
          for <questions@freebsd.org>; Tue, 9 Apr 1996 05:58:42 -0700 (PDT)
Received: (from jeff@localhost) by tad.cetlink.net (8.7.5/8.6.12) id JAA15480; Tue, 9 Apr 1996 09:03:19 -0400 (EDT)
From: Jeffrey Wheat <jeff@tad.cetlink.net>
Message-Id: <199604091303.JAA15480@tad.cetlink.net>
Subject: Re: Machines locking
To: adf@cafu.fl.net.au (Andrew Foster)
Date: Tue, 9 Apr 1996 09:03:18 -0400 (EDT)
Cc: questions@freebsd.org
In-Reply-To: <Pine.BSF.3.91.960409210354.324A-100000@cafu.fl.net.au> from "Andrew Foster" at Apr 9, 96 09:04:51 pm
X-Mailer: ELM [version 2.4 PL24 ME8a]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> > > A lockup in which :
> > > 
> > > -  pings return
> > > -  some programs will still work via opening a socket (e.g. telnetting to
> > > port 80 will sometimes work, but not always)
> > > -  I can telnet in (no connection refused) but nothing will happen
> > > -  I can switch vtys at the console
> > > -  Pressing enter at the console login prompt will redisplay the banner
> > > -  Entering a username and pressing enter will do nothing - the machine just
> > > sits there
> > > -  The only way to fix it is to press reset
> > 
> > Out of mbufs?  I think it's the same appearance.
> > 
> > Try
> > 
> > 	options		"NMBCLUSTERS=2048"
> > 
> > in your config file.
> 
> Latest update :
> 
> these machines still lock despite :
> 
> 	options		"NMBCLUSTERS=2048"
> 	options		NO_SWAPPING
> 
> Anyone else got any other ideas ?  Someone I spoke to said their machines
> were fine with 2.0.5 and as soon as they switched to 2.1.0 they had this
> problem.
> 

I have seen this same exact thing under 2.1.0-STABLE. Even with NMBCLUSTERS
set to 4096, there is the occasional "freeze". Error logs show nothing, and
an attempt to enable debugging messages result in nothing. The symptoms are
the same as above. 

-jeff