From owner-freebsd-current Sat Sep 16 4:18:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mine.kame.net. (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id 8466A37B422 for ; Sat, 16 Sep 2000 04:18:26 -0700 (PDT) Received: from localhost ([202.249.11.124]) by mine.kame.net. (8.9.3/3.7W) with ESMTP id UAA28076; Sat, 16 Sep 2000 20:10:51 +0900 (JST) To: rbezuide@oskar.nanoteq.co.za Cc: freebsd-current@freebsd.org, snap-users@kame.net Subject: Re: (KAME-snap 3318) Panic on current (12 Sept) In-Reply-To: Your message of "Thu, 14 Sep 2000 11:25:28 +0200 (SAST)" References: X-Mailer: Cue version 0.6 (000609-1000/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20000916202011C.sakane@ydc.co.jp> Date: Sat, 16 Sep 2000 20:20:11 +0900 From: "Shoichi 'Ne' Sakane" X-Dispatcher: imput version 990905(IM130) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm running a current machine of 12 Sept although this problem > also occured on a current of a few days earlier ... > > This only happens when using the IPv6 IPSec code during the day, > it is readily reproduceable. > > If during the day I load the racoon daemon and load keys and > establish a IPSec tunnel connection everything works fine till > 2:00 am when the daily script runs OR if I run the daily script > by hand ... I generated the following dump and backtrace ... > > It seems to crash in a makedev routine using FOREACH list macro's. > > The problem doesn't seem to be with the list or the makedev function > in kern_conf.c. It seems to me that something in the kernel > corrupts the static list dev_hash when using the IPSec code. > > Summary - when ising IPSec ... machine panics during daily > script execution. I think IPsec is not relative to this issue. To make sure, does your machine run healthy without IPsec ? Please try the following. case 1) with option IPSEC, but no SPD entry. case 2) without option IPSEC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message