From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 13:36:50 2004
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 C307616A4CE
	for <current@freebsd.org>; Mon, 15 Nov 2004 13:36:50 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4116E43D49
	for <current@freebsd.org>; Mon, 15 Nov 2004 13:36:50 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAFDZQEY081081;
	Mon, 15 Nov 2004 08:35:26 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)iAFDZQah081078;
	Mon, 15 Nov 2004 13:35:26 GMT
	(envelope-from robert@fledge.watson.org)
Date: Mon, 15 Nov 2004 13:35:26 +0000 (GMT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Martin Blapp <mb@imp.ch>
In-Reply-To: <20041115142036.D53544@cvs.imp.ch>
Message-ID: <Pine.NEB.3.96L.1041115133457.80435A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: Deadlock problems with 'kill PID' on CURRENT
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: Mon, 15 Nov 2004 13:36:50 -0000

On Mon, 15 Nov 2004, Martin Blapp wrote:

> > syscons is typically a sign that some thread holding Giant is spinning, or
> > that Giant has been leaked.  Alternatively, some other lock is leaked, and
> > a thread with Giant waits on that lock.  You may be able to get into DDB
> > using the serial console as it doesn't require Giant (or you might not).
> 
> I was not able to get into DDB over serial console. Sorry for not saying
> this exactly. Hardlock. 

Any chance that any of the boxes has an NMI button?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research