From owner-freebsd-current@FreeBSD.ORG  Thu Jul 31 13:05:12 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 50CA237B401
	for <current@freebsd.org>; Thu, 31 Jul 2003 13:05:12 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 630DB43F85
	for <current@freebsd.org>; Thu, 31 Jul 2003 13:05:11 -0700 (PDT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h6VK4Bai063266;
	Thu, 31 Jul 2003 16:04:11 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)h6VK4BFW063263;
	Thu, 31 Jul 2003 16:04:11 -0400 (EDT)
Date: Thu, 31 Jul 2003 16:04:11 -0400 (EDT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Lars Eggert <larse@ISI.EDU>
In-Reply-To: <3F29410A.4040500@isi.edu>
Message-ID: <Pine.NEB.3.96L.1030731160243.37179E-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: panic: spin lock sched lock held
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2003 20:05:12 -0000

On Thu, 31 Jul 2003, Lars Eggert wrote:

> got this panic overnight. Machine was wedged solid and didn't enter ddb
> after the panic. I'll recompile with verbose diagnostics and see if it
> happens again. In the meantime, maybe the message will give someone a
> clue: 
> 
> panic: spin lock sched lock held by 0xca462390 for > 5 seconds
> cpuid = 0; lapic.id = 00000000
> Debugger("panic")

If this is reproduceable, you might try setting 'debug.trace_on_panic' so
that you get an automatic trace even if you can't get into DDB.  This
might or might not work, but it's worth a try.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories