Date: Wed, 3 May 2000 10:24:36 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Howard Leadmon <howardl@account.abs.net> Cc: Greg Lehey <grog@lemis.com>, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Debugging Kernel/System Crashes, can anyone help?? Message-ID: <200005031724.KAA63381@apollo.backplane.com> References: <200005030925.FAA91225@account.abs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005031724.KAA63381>