From owner-freebsd-bugs Wed Dec 19 6: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 9126737B419 for ; Wed, 19 Dec 2001 06:40:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBJEe3907020; Wed, 19 Dec 2001 06:40:03 -0800 (PST) (envelope-from gnats) Date: Wed, 19 Dec 2001 06:40:03 -0800 (PST) Message-Id: <200112191440.fBJEe3907020@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Yar Tikhiy" Subject: Re: kern/31471: Specific IPFW's FWD rule crashes the kernel (panic fatal double fault) Reply-To: "Yar Tikhiy" 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/31471; it has been noted by GNATS. From: "Yar Tikhiy" To: , Cc: Subject: Re: kern/31471: Specific IPFW's FWD rule crashes the kernel (panic fatal double fault) Date: Wed, 19 Dec 2001 17:34:51 +0300 Ivan, First of all, do you realize that IPFIREWALL and IPFILTER are alternative packet filter facilities? Second, would you mind following the FreeBSD Developers Handbook instructions on how to inspect kernel crashes with ``gdb'': http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld ebug.html and sending a post-mortem kernel stack trace? Without it, it's rather hard to guess a sequence of calls that leads to the particular crash. Thank you. --Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message