From owner-freebsd-current@FreeBSD.ORG Wed Aug 29 04:18:29 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A2E616A418 for ; Wed, 29 Aug 2007 04:18:29 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 4D53013C465 for ; Wed, 29 Aug 2007 04:18:29 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l7T4HwAg008560; Tue, 28 Aug 2007 21:17:59 -0700 (PDT) Date: Wed, 29 Aug 2007 10:52:23 +0900 Message-ID: From: gnn@freebsd.org To: "Pawel Worach" In-Reply-To: References: <46D2EB88.7020905@gmail.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.1 (i386-apple-darwin8.9.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: current@freebsd.org Subject: Re: IPSec panics X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Aug 2007 04:18:29 -0000 At Tue, 28 Aug 2007 16:03:09 +0200, Pawel Worach wrote: > > On 8/28/07, gnn@freebsd.org wrote: > > At Mon, 27 Aug 2007 17:19:36 +0200, > > Pawel Worach wrote: > > > > > > Hi, > > > > > > While testing IPSec I got this panic on two different -CURRENT systems. > > > I think they happened when racoon was updating the SAD. kernel.debug and > > > vmcore is still available if more info needed. > > > > > > > Given the backtraces you showed I didnt' see any IPsec related code > > being run. Did I miss something? > > > > Come to think of it.. this case was that I had a ssh session to the > peer when there was no policy loaded and the peer paniced when setkey > -f ipsec.conf was executed so the existing connection now suddenly > would require IPSec. Am I making any sense at all ? > Well, I think we need to tease the issues apart. I have your report of an infinite loop in esp6_ctlinput and I will look at that. I am hoping someone else will look at the first error you posted which seems to point to issues in other parts of the system. Best, George