From owner-freebsd-stable@FreeBSD.ORG  Mon Dec 12 11:03:43 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D3F6916A420
	for <freebsd-stable@freebsd.org>; Mon, 12 Dec 2005 11:03:43 +0000 (GMT)
	(envelope-from pherman@frenchfries.net)
Received: from alcatraz.frenchfries.net (216-73-106-93.ocdc-01.net
	[216.73.106.93])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E68D743D45
	for <freebsd-stable@freebsd.org>; Mon, 12 Dec 2005 11:03:21 +0000 (GMT)
	(envelope-from pherman@frenchfries.net)
Received: from localhost (alcatraz [216.73.106.93])
	by alcatraz.frenchfries.net (Postfix) with ESMTP id 6D0B3C6481
	for <freebsd-stable@freebsd.org>; Mon, 12 Dec 2005 03:02:59 -0800 (PST)
Date: Mon, 12 Dec 2005 12:02:57 +0100 (CET)
From: Paul Herman <pherman@frenchfries.net>
X-X-Sender: pherman@tahoe.cgn.cleverbridge.com
To: FreeBSD Stable <freebsd-stable@freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Message-Id: <20051212110259.6D0B3C6481@alcatraz.frenchfries.net>
Subject: 6.0-STABLE setkey panic
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2005 11:03:43 -0000

Hi all,

Just installed 6.0-STABLE/amd64 (cvsup from within the last day) 
onto a K8 Sempron with IPSEC compiled in and I get a kernel panic 
when I try to run racoon.  Anyone else seen this?

Unfortunately the usual ways I know how to debug don't work:
   * "kgdb /path/to/kernel.debug /var/crash/vmcore.0" hangs and takes
     100% CPU (20% user, 80% system)

   * "kgdb /boot/kernel/kernel /var/crash/vmcore.0" gives me a
     backtrace, but no symbols and looks like the stack is mangled
     anyway.

   * Falling into DDB on the console after the panic refuses to
     provide any kind of backtrace, it complains that the stack is
     garbled.

The good news:  I can reproduce this at any time with just "setkey -D".
No special kernel tweaks except for adding IPSEC into the config, 
so I'm hoping many of you can reproduce this, and hopefuly someone 
else with more debugging foo.

Anyone?

-Paul.