From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:20:44 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 231FF16A420 for ; Tue, 15 Nov 2005 22:20:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 827B143D5D for ; Tue, 15 Nov 2005 22:20:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 552B11A3C25; Tue, 15 Nov 2005 14:20:40 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 78C7D533D0; Tue, 15 Nov 2005 17:20:39 -0500 (EST) Date: Tue, 15 Nov 2005 17:20:39 -0500 From: Kris Kennaway To: "Andrew P." Message-ID: <20051115222039.GA63863@xor.obsecurity.org> References: <20051115215517.GA47583@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, Kris Kennaway 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:44 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 16, 2005 at 01:09:33AM +0300, Andrew P. wrote: > On 11/16/05, Kris Kennaway wrote: > > On Wed, Nov 16, 2005 at 12:50:42AM +0300, 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. > > > > Start by determining whether an adequately documented PR (with > > backtrace, etc) is filed on this issue, and if not, then file one. >=20 >=20 > It's a relief that you don't know about it. I wouldn't read too much into it :) > Actually, I've never sent a proper bug-related PR, > so I'll need some hand-holding support from a > kind soul. I can cvsup to anything, recompile to > anything and I might be able to get a serial console. > root access is not impossible to provide. The main thing is to follow the directions in the developers handbook chapter on kernel debugging, which explains how to obtain the necessary debugging backtrace. Kris --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDel82Wry0BWjoQKURArgDAKD5OEzA32xzNBexgRjfa3ufplmv7ACgklEn Pac2XKMSF7mkyCUxN3KcL+c= =pP7i -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb--