Date: Tue, 3 Oct 2000 12:47:37 -0400 From: Bill Fumerola <billf@chimesnet.com> To: Forrest Aldrich <forrie@forrie.com> Cc: cjclark@alum.mit.edu, freebsd-ipfw@FreeBSD.ORG Subject: Re: 4.1.1 Kernel ipfw, brought to its knees Message-ID: <20001003124737.U38472@jade.chc-chimes.com> In-Reply-To: <5.0.0.25.2.20001003120347.020eb050@64.20.73.233>; from forrie@forrie.com on Tue, Oct 03, 2000 at 12:14:29PM -0400 References: <5.0.0.25.2.20001002154554.01bfe310@64.20.73.233> <5.0.0.25.2.20001002154554.01bfe310@64.20.73.233> <20001002233136.O25121@149.211.6.64.reflexcom.com> <5.0.0.25.2.20001003120347.020eb050@64.20.73.233>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 03, 2000 at 12:14:29PM -0400, Forrest Aldrich wrote:
> So, given that we're using FreeBSD on our infrastructure, we're very
> concerned about this.
add 'options DDB' into your kernel, hit ctrl-alt-esc when this happens,
type 'trace' and send that output.
for bonus hacker points, setup savecore and panic the machine when this
happens and use gdb to debug this. make sure your shiney new kernel was
config'd with 'config -g'
thanks.
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
billf@chimesnet.com / billf@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ipfw" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001003124737.U38472>