From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 16 07:43:23 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C6D316A41F for ; Wed, 16 Nov 2005 07:43:23 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FDD043D45 for ; Wed, 16 Nov 2005 07:43:23 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [83.242.63.242] (242-63-242-83.dip.h-tel.de [83.242.63.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id C352830004B7; Wed, 16 Nov 2005 08:43:20 +0100 (CET) Message-ID: <437AE312.4090709@mail.uni-mainz.de> Date: Wed, 16 Nov 2005 08:43:14 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051106) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <437A993B.8080204@roq.com> In-Reply-To: <437A993B.8080204@roq.com> Content-Type: multipart/mixed; boundary="------------040801010705030006020706" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: amd64@freebsd.org Subject: Re: IPSec panic? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 07:43:23 -0000 This is a multi-part message in MIME format. --------------040801010705030006020706 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Michael Vince wrote: > Andrew P. wrote: > >> I'm gravely sorry to annoy. I've googled for a little >> while and found out that IPSec panics are a known >> issue on amd64. Is it still so? >> >> I was surprised that setkey -D causes panic and >> a memory dump on my 6-Stable box. Come on, >> it's _FreeBSD_ for crying out loud. We can't live >> with that. >> >> I'm willing to help debugging this nasty thing if >> help's needed. >> _______________________________________________ >> >> > FAST_IPSEC broken on amd64 is still broken. As far as I know > VANHULLEBUS Yvan appears to be the most active IPSEC guy in FreeBSD > and he has talked about fixing it but probably hasn't got the time, > probably only money is a viable motivator if you wanted this problem > fixed soon. > > Mike Indeed, but IPSEC seems also to be broken. With IPSEC or FAST_IPSEC it is possible to force a crash as described further below in this thread. O. --------------040801010705030006020706--