From owner-freebsd-bugs@FreeBSD.ORG  Mon Mar 14 17:57:50 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id CFD5616A4CE; Mon, 14 Mar 2005 17:57:50 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B7F0B43D31; Mon, 14 Mar 2005 17:57:50 +0000 (GMT)
	(envelope-from mlaier@FreeBSD.org)
Received: from freefall.freebsd.org (mlaier@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2EHvork045363;
	Mon, 14 Mar 2005 17:57:50 GMT
	(envelope-from mlaier@freefall.freebsd.org)
Received: (from mlaier@localhost)
	by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2EHvo7R045359;
	Mon, 14 Mar 2005 17:57:50 GMT
	(envelope-from mlaier)
Date: Mon, 14 Mar 2005 17:57:50 GMT
From: Max Laier <mlaier@FreeBSD.org>
Message-Id: <200503141757.j2EHvo7R045359@freefall.freebsd.org>
To: claudiuc@terrasat.ro, mlaier@FreeBSD.org,
	freebsd-bugs@FreeBSD.org, mlaier@FreeBSD.org
Subject: Re: kern/78818: pf crash on high load if use route-to
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2005 17:57:50 -0000

Synopsis: pf crash on high load if use route-to

State-Changed-From-To: open->feedback
State-Changed-By: mlaier
State-Changed-When: Mon Mar 14 17:56:48 GMT 2005
State-Changed-Why: 
In order to debug this properly I need more information:
 - complete ruleset (via private mail if you prefer)
 - kernel config and dmesg
 - debug.mpsafenet setting and NICs involved
   + You could also try to set debug.mpsafenet=0 in loader.conf to see if
     that makes the problem go away.
 - If you have a chance to run a WITNESS enabled kernel, any related output
   from the console
 - If you are able to attach a serial console - can you break into the
   debugger from there?


Responsible-Changed-From-To: freebsd-bugs->mlaier
Responsible-Changed-By: mlaier
Responsible-Changed-When: Mon Mar 14 17:56:48 GMT 2005
Responsible-Changed-Why: 
Take over.

http://www.freebsd.org/cgi/query-pr.cgi?pr=78818