From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:25:04 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 CA22816A41F for ; Tue, 15 Nov 2005 22:25:04 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 524CA43D45 for ; Tue, 15 Nov 2005 22:25:04 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1503030nzo for ; Tue, 15 Nov 2005 14:25:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CWXXov5dAfdMaI0Pr1lLtjhzVzM35MNEhYqRfatJ0WMYLDRTqQg4DcACR3MvbDaEAlKJfBjd0cY8OrjRsZyMbNZhjygqDBABmv4petULftDQsZLk1K3H7b2sjzNN1mBTMkZ/T6BJ+ruBBViyPeMzY6oIblaZIc3qu9nUOea8L1U= Received: by 10.36.13.10 with SMTP id 10mr5641339nzm; Tue, 15 Nov 2005 14:25:03 -0800 (PST) Received: by 10.37.20.33 with HTTP; Tue, 15 Nov 2005 14:25:03 -0800 (PST) Message-ID: Date: Wed, 16 Nov 2005 01:25:03 +0300 From: "Andrew P." To: "Bjoern A. Zeeb" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: 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: Tue, 15 Nov 2005 22:25:04 -0000 On 11/16/05, Bjoern A. Zeeb wrote: > On Wed, 16 Nov 2005, 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. > > is it fast_ispec? > > best place to contriubte might be: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Damd64/73211 > > I just gave it a try w/o any policy loaded and the bt looks like this: > > y2k# setkey -D > [thread pid 471 tid 100057 ] > Stopped at kdebug_sockaddr+0xb0: decl 0xffffffffffffff8d(%rax) > db> where > Tracing pid 471 tid 100057 td 0xffffff010bfc7750 > kdebug_sockaddr() at kdebug_sockaddr+0xb0 > raw_usend() at raw_usend+0x74 > key_send() at key_send+0xa > sosend() at sosend+0x726 > kern_sendit() at kern_sendit+0x12f > sendit() at sendit+0x1d3 > sendto() at sendto+0x52 > syscall() at syscall+0x350 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (133, FreeBSD ELF64, sendto), rip =3D 0x8007e9a6c, rsp =3D 0x= 7fffffff6b98, rbp =3D 0x2 --- > db> show alllocks > db> No, it's just options IPSEC (without IPSEC_ESP). Can you please remove all IPSEC options except for IPSEC itself and try setkey -D?