From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 15 22:09:43 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 D458C16A41F for ; Tue, 15 Nov 2005 22:09:43 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37A4443D72 for ; Tue, 15 Nov 2005 22:09:34 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so1500256nzo for ; Tue, 15 Nov 2005 14:09:33 -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=CxuXAmT/ve+ZhUJzg4+MyI0OnJ3CBc1BbgHQg8gqZAGn+e4fPCBM0cuovaflJeugqrnLok4YZraX5zGZq+Vjpv86D/WDrZBL6XRfg3hLihLTRTDNQAbDRaaYVDqsUQlukvFS5ozXNCOzKspbDe8ymMLFQkTDpq1+Hdroj0bAjBI= Received: by 10.36.216.6 with SMTP id o6mr2699782nzg; Tue, 15 Nov 2005 14:09:33 -0800 (PST) Received: by 10.37.20.33 with HTTP; Tue, 15 Nov 2005 14:09:33 -0800 (PST) Message-ID: Date: Wed, 16 Nov 2005 01:09:33 +0300 From: "Andrew P." To: Kris Kennaway In-Reply-To: <20051115215517.GA47583@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051115215517.GA47583@xor.obsecurity.org> 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:09:44 -0000 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. It's a relief that you don't know about it. I have to hope that I've done something wrong. I'm compiling latest stable world/kernel now, then I might want to try 6.0-release. Well, there are some PR's: http://www.freebsd.org/cgi/query-pr-summary.cgi?text=3Dipsec Some are close to what I see, none are exactly similar, but they are all very outdated. 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. Still, give me some time so I can rule out some very simple mistakes.