From nobody@FreeBSD.ORG Fri Aug 27 23:11:01 1999 Return-Path: Received: by hub.freebsd.org (Postfix, from userid 32767) id 8386514F8F; Fri, 27 Aug 1999 23:11:01 -0700 (PDT) Message-Id: <19990828061101.8386514F8F@hub.freebsd.org> Date: Fri, 27 Aug 1999 23:11:01 -0700 (PDT) From: bifrost@dis.org Sender: nobody@FreeBSD.ORG To: freebsd-gnats-submit@freebsd.org Subject: Natd Causes Kernel Panic under 3.2-STABLE X-Send-Pr-Version: www-1.0 >Number: 13434 >Category: kern >Synopsis: Natd Causes Kernel Panic under 3.2-STABLE >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Aug 27 23:20:01 PDT 1999 >Closed-Date: Tue Sep 14 02:34:23 PDT 1999 >Last-Modified: Tue Sep 14 02:38:06 PDT 1999 >Originator: Bifrost >Release: 3.2-STABLE >Organization: Dis.Org >Environment: FreeBSD firewall.XXXXX.com 3.2-STABLE FreeBSD 3.2-STABLE #3: Mon Aug 16 17:07:51 PDT 1999 root@firewall.XXXXX.com:/usr/src/sys/compile/FIREWALL i386 >Description: After setting up IPFW rules to enable divert sockets, running natd will cause a kernel panic. This machine has Three Ethernet Interfaces, with bridging enabled. Bridging includes IPFW support. add 300 divert 8668 all from any to X.X.X via fxp0 add 400 divert 8669 all from 10.1.0.0 to any via fxp2 natd -i 8668 -o 8669 -a X.X.X.X -log Instant Kernel Panic. >How-To-Repeat: Start natd with specified parameters. >Fix: N/A >Release-Note: >Audit-Trail: From: Chris Costello To: bifrost@dis.org Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE Date: Sat, 28 Aug 1999 04:37:02 -0500 On Fri, Aug 27, 1999, bifrost@dis.org wrote: > Instant Kernel Panic. Perhaps you could provide us with some more information. What did the kernel panic message say? -- |Chris Costello |Tomorrow will be canceled due to lack of interest. `-------------------------------------------------- From: Evil Bifrost To: Chris Costello Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE Date: Sun, 29 Aug 1999 23:36:27 -0700 (PDT) > Perhaps you could provide us with some more information. What > did the kernel panic message say? Sorry about that, I'll try to provide more info. Its an onsite gig that I'm not at that frequently, I'll put in a debugging kernel and copy down the messages by hand. Do you want a kdump? From: Chris Costello To: Evil Bifrost Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE Date: Mon, 30 Aug 1999 03:03:33 -0500 On Sun, Aug 29, 1999, Evil Bifrost wrote: > Sorry about that, I'll try to provide more info. > Its an onsite gig that I'm not at that frequently, I'll put > in a debugging kernel and copy down the messages by hand. > Do you want a kdump? I was thinking of a backtrace from the kernel debugger, actually. -- |Chris Costello |Every program is either trivial or it contains at least one bug. `---------------------------------------------------------------- From: Evil Bifrost To: Chris Costello Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE Date: Mon, 30 Aug 1999 23:05:50 -0700 (PDT) > > Sorry about that, I'll try to provide more info. > > Its an onsite gig that I'm not at that frequently, I'll put > > in a debugging kernel and copy down the messages by hand. > > Do you want a kdump? > > I was thinking of a backtrace from the kernel debugger, > actually. ok, I'll give that a shot. I won't be there till sometime next week though From: Ruslan Ermilov To: freebsd-gnats-submit@freebsd.org, Evil Bifrost Cc: Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE Date: Fri, 3 Sep 1999 14:14:30 +0300 On Mon, Aug 30, 1999 at 11:10:02PM -0700, Evil Bifrost wrote: > > ok, I'll give that a shot. > I won't be there till sometime next week though So, does the problem still exist? If yes, what about `gdb -k' trace? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age From: Ruslan Ermilov To: Evil Bifrost , freebsd-gnats-submit@freebsd.org Cc: Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE Date: Sun, 12 Sep 1999 19:44:37 +0300 On Mon, Aug 30, 1999 at 11:10:02PM -0700, Evil Bifrost wrote: > The following reply was made to PR kern/13434; it has been noted by GNATS. > > From: Evil Bifrost > To: Chris Costello > Cc: freebsd-gnats-submit@freebsd.org > Subject: Re: kern/13434: Natd Causes Kernel Panic under 3.2-STABLE > Date: Mon, 30 Aug 1999 23:05:50 -0700 (PDT) > > > > Sorry about that, I'll try to provide more info. > > > Its an onsite gig that I'm not at that frequently, I'll put > > > in a debugging kernel and copy down the messages by hand. > > > Do you want a kdump? > > > > I was thinking of a backtrace from the kernel debugger, > > actually. > > ok, I'll give that a shot. > I won't be there till sometime next week though > Evil! If you won't tell us whether the problem still exists, I will close this PR in two days, since I can't reproduce it on any of my -stable systems and there is no feedback from your side. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age State-Changed-From-To: open->closed State-Changed-By: ru State-Changed-When: Tue Sep 14 02:34:23 PDT 1999 State-Changed-Why: Can't reproduce myself, originator doesn't respond. >Unformatted: