From owner-freebsd-current  Sat Sep 16 21:32:23 2000
Delivered-To: freebsd-current@freebsd.org
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by hub.freebsd.org (Postfix) with ESMTP id 6A2A737B42C
	for <freebsd-current@freebsd.org>; Sat, 16 Sep 2000 21:32:21 -0700 (PDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id NAA19653;
	Sun, 17 Sep 2000 13:32:08 +0900 (JST)
To: snap-users@kame.net
Cc: rbezuide@oskar.nanoteq.co.za, freebsd-current@freebsd.org
In-reply-to: sakane's message of Sat, 16 Sep 2000 20:20:11 JST.
      <20000916202011C.sakane@ydc.co.jp>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (KAME-snap 3327) Re: Panic on current (12 Sept) 
From: itojun@iijlab.net
Date: Sun, 17 Sep 2000 13:32:08 +0900
Message-ID: <19651.969165128@coconut.itojun.org>
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 ...

	"current machine" meaning FreeBSD-current?  if so, are there any
	locking behavior changes due to the introduction of fine grain locks?
	what happens if you go back to coarse grain lock kernel?

itojun


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message