From owner-freebsd-current Mon Sep 18 7: 1:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lychee.itojun.org (ny-ppp015.iij-us.net [216.98.99.15]) by hub.freebsd.org (Postfix) with ESMTP id AB26737B423 for ; Mon, 18 Sep 2000 07:01:49 -0700 (PDT) Received: from kiwi.itojun.org (localhost [127.0.0.1]) by itojun.org (8.10.0/3.7W) with ESMTP id e8IE1U302050; Mon, 18 Sep 2000 23:01:30 +0900 (JST) Message-Id: <200009181401.e8IE1U302050@itojun.org> To: rbezuide@oskar.nanoteq.co.za Cc: snap-users@kame.net, freebsd-current@freebsd.org In-reply-to: rbezuide's message of Mon, 18 Sep 2000 10:05:53 +0200. 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 3337) RE: Panic on current (12 Sept) From: Jun-ichiro itojun Hagino Date: Mon, 18 Sep 2000 23:01:30 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Without starting the racoon daemon and doing a secure connect >everything works fine without a problem. If I start racoon, >do a tunnel connection and then run daily, the machine panics .. I bet you can panic the kernel with setkey(8) in that case. am I correct? if so, something is not friendly with fine grain SMP, under sys/netkey. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message