From owner-freebsd-current@FreeBSD.ORG Fri Jan 14 02:30:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 778AC16A4CE for ; Fri, 14 Jan 2005 02:30:41 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8A9343D41 for ; Fri, 14 Jan 2005 02:30:40 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id j0E2Ue4b003435; Thu, 13 Jan 2005 18:30:40 -0800 (PST) (envelope-from marcel@xcllnt.net) In-Reply-To: <41E721A7.3010302@uq.edu.au> References: <41E44CD0.1000008@uq.edu.au> <41E5F22A.6010607@uq.edu.au> <20050113093955.P12838@carver.gumbysoft.com> <41E721A7.3010302@uq.edu.au> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4781326B-65D4-11D9-A004-000D93C47836@xcllnt.net> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 13 Jan 2005 18:30:39 -0800 To: Matthew Sullivan X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org Subject: Re: Fatal Trap 12: Page fault while in kernel mode (racoon/amd64/5.3-RELEASE-p4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 02:30:41 -0000 On Jan 13, 2005, at 5:34 PM, Matthew Sullivan wrote: >> >> Hm, null pointer+offset dereference. Are you using IPSEC or >> FAST_IPSEC in >> your kernel? When did you grab the sources last? >> > IPSEC (see: http://www.au.sorbs.net/~matthew/freebsd/ for all kernel, > config, cores and info I can give) > > Source was updated after finding this issue (within the last 10 days) > and it made no difference. Note that "setkey -D" should be enough to trigger the page fault on amd64. Note also that i386 and ia64 don't have this problem. I don't know about alpha or sparc64, but it looks amd64 specific. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net