From owner-freebsd-current@FreeBSD.ORG  Mon Nov 15 13:22:56 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 9ECC416A4CE; Mon, 15 Nov 2004 13:22:56 +0000 (GMT)
Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 685EC43D1D; Mon, 15 Nov 2004 13:22:55 +0000 (GMT)
	(envelope-from mb@imp.ch)
Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9])
	by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id iAFDMkXY010351;
	Mon, 15 Nov 2004 14:22:47 +0100 (CET)
	(envelope-from Martin.Blapp@imp.ch)
Date: Mon, 15 Nov 2004 14:22:46 +0100 (CET)
From: Martin Blapp <mb@imp.ch>
To: Robert Watson <rwatson@freebsd.org>
In-Reply-To: <Pine.NEB.3.96L.1041115124708.66223J-100000@fledge.watson.org>
Message-ID: <20041115142036.D53544@cvs.imp.ch>
References: <Pine.NEB.3.96L.1041115124708.66223J-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checksum: 5718ad17193357f5ffefbc32e69012c1
X-Virus-Message-Status: No
X-Virus-Status: No, scantime="0.0012 seconds"
X-Spam-Status: No, hits=-4.9 required=5 scantime="3.5415 seconds"
	tests=BAYES_00
X-Scanned-By: MIMEDefang 2.48 on 192.168.0.2
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:22:56 -0000


Hi,

> Are you able to get into DDB using a serial console?  Not getting in via
> 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.

 But that would be a useful first step.  Are you able to reproduce this
> problem with INVARIANTS and/or WITNESS compiled in, btw?

Since this is a production box I have no chance testing it out. The second
and third box we have are now in production too. On different boxes I was
not able to reproduce it. So this problem seems only to happen on high load
situations.

Martin