From owner-freebsd-bugs Tue Apr 9 04:08:54 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA03324 for bugs-outgoing; Tue, 9 Apr 1996 04:08:54 -0700 (PDT) Received: from ter2.fl.net.au (root@ter2.fl.net.au [203.63.198.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA03314 for ; Tue, 9 Apr 1996 04:08:45 -0700 (PDT) Received: from cafu.fl.net.au (adf@cafu.fl.net.au [203.63.198.10]) by ter2.fl.net.au (2.0/adf) with SMTP id VAA11143; Tue, 9 Apr 1996 21:07:46 +1000 (EST) Date: Tue, 9 Apr 1996 21:04:51 +0000 () From: Andrew Foster To: Joerg Wunsch cc: freebsd-bugs@freebsd.org, cinder@cafu.fl.net.au Subject: Re: Machines locking In-Reply-To: <199604080941.LAA04290@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 8 Apr 1996, J Wunsch wrote: > > 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. Thanks, Andrew ---------- Andrew Foster adf@fl.net.au