From owner-freebsd-bugs Mon Apr 8 03:05:28 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA16959 for bugs-outgoing; Mon, 8 Apr 1996 03:05:28 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA16954 for ; Mon, 8 Apr 1996 03:05:25 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA18674; Mon, 8 Apr 1996 12:03:05 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id MAA14007; Mon, 8 Apr 1996 12:03:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id LAA04290; Mon, 8 Apr 1996 11:41:14 +0200 (MET DST) From: J Wunsch Message-Id: <199604080941.LAA04290@uriah.heep.sax.de> Subject: Re: Machines locking To: adf@cafu.fl.net.au (Andrew Foster) Date: Mon, 8 Apr 1996 11:41:13 +0200 (MET DST) Cc: freebsd-bugs@freebsd.org, cinder@cafu.fl.net.au Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Andrew Foster" at Apr 8, 96 12:22:45 pm X-Phone: +49-351-2012 669 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-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Andrew Foster wrote: > I've observed this on several machines : > > 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. > - My syslog.conf mentions a file which doesn't exist - as a result when I > press C-A-D I see a syslogd error - so the machine tries to respawn > something (this is my guess) but can't. This is unrelated. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)