From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:20:13 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 DB32F16A41F for ; Tue, 15 Nov 2005 22:20:13 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F9CB43D60 for ; Tue, 15 Nov 2005 22:20:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 9275F1FFAD5; Tue, 15 Nov 2005 23:20:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 224401FFAD2; Tue, 15 Nov 2005 23:20:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 2AEA215823; Tue, 15 Nov 2005 22:18:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 20791155EB; Tue, 15 Nov 2005 22:18:11 +0000 (UTC) Date: Tue, 15 Nov 2005 22:18:11 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "Andrew P." In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de 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:20:14 -0000 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=amd64/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 = 0x8007e9a6c, rsp = 0x7fffffff6b98, rbp = 0x2 --- db> show alllocks db> -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT