From owner-freebsd-hackers Wed May 3 10:25:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0D28237BC1F; Wed, 3 May 2000 10:25:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA63381; Wed, 3 May 2000 10:24:36 -0700 (PDT) (envelope-from dillon) Date: Wed, 3 May 2000 10:24:36 -0700 (PDT) From: Matthew Dillon Message-Id: <200005031724.KAA63381@apollo.backplane.com> To: Howard Leadmon Cc: Greg Lehey , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Debugging Kernel/System Crashes, can anyone help?? References: <200005030925.FAA91225@account.abs.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Judging by your original bug report, Howard, it seems likely that either the machine or the network the machine is sitting on is being attacked and the machine is running out of some resource (probably network mbufs). Increasing the NMBCLUSTERS any more will probably not help. What you need to do is figure out what kind of attack it is and start experimenting with the various kernel config (see LINT) and sysctl features to try to stem the attack. Now, of course the kernel should not be crashing... if you can obtain a backtrace from some of your core's it might help us locate the problem. gunzip vmcore.*.gz kernel.*.gz gdb -k kernel.0 vmcore.0 back gdb -k kernel.1 vmcore.1 back I do not think this is vinum or fxp related. If fxp is getting device timeouts its probably due to the machine or network being attacked. It's also possible that bad network cabling or a bad switch port is to blame. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message