From owner-freebsd-bugs Mon Nov 5 4:40:10 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 59CB137B417 for ; Mon, 5 Nov 2001 04:40:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id fA5Ce8o83653; Mon, 5 Nov 2001 04:40:08 -0800 (PST) (envelope-from gnats) Date: Mon, 5 Nov 2001 04:40:08 -0800 (PST) Message-Id: <200111051240.fA5Ce8o83653@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Murray Stokely Subject: Re: kern/28844: Router/nameserver system crashes 2-3 times monthl y Reply-To: Murray Stokely Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/28844; it has been noted by GNATS. From: Murray Stokely To: Rudi Mathijssen Cc: "'freebsd-gnats-submit@FreeBSD.org'" , "'kruse@kruse-ict.nl'" Subject: Re: kern/28844: Router/nameserver system crashes 2-3 times monthl y Date: Mon, 5 Nov 2001 04:31:46 -0800 On Sun, Nov 04, 2001 at 10:59:37AM +0100, Rudi Mathijssen wrote: > Modifications tested: (1) removed xl and (suspect) fxp, added more SMC > cards, now we have six interfaces > de0-de5. These all run half-duplex 100Mbps. (2) Furthermore, as netstat -m > showed that the peak use of > mbuf clusters (944) came awfully close to 1024 (default), NMBCLUSTERS=4096 > was set. After a flawless > operation from 4-sep-2001 on, it crashed again on oct-29 and oct-31 (the > panic message is: page fault in kernel mode). This is not acceptable. Should > we upgrade to 4.4? Go back to 4.0? Is there a special kernel param NO_PANIC > which should be set to 1? > I stress, this is not a test lab, it's a production environment. If FreeBSD > is not suitable for this, please tell me. Can you generate a backtrace of the kernel crash and post it to freebsd-stable@FreeBSD.org or freebsd-net@FreeBSD.org? This document should help narrow down the cause of the failure : http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#AEN4392 What version of FreeBSD are you running? Does this problem still exist with 4.4 or 4.4-STABLE? - Murray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message