From owner-freebsd-current@FreeBSD.ORG  Sun Dec 26 22:40:48 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 33CC616A4CE
	for <current@FreeBSD.org>; Sun, 26 Dec 2004 22:40:48 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D3E7543D41
	for <current@FreeBSD.org>; Sun, 26 Dec 2004 22:40:47 +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 iBQMbWrv067105
	for <current@FreeBSD.org>; Sun, 26 Dec 2004 17:37:32 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)iBQMbWhn067102
	for <current@FreeBSD.org>; Sun, 26 Dec 2004 22:37:32 GMT
	(envelope-from robert@fledge.watson.org)
Date: Sun, 26 Dec 2004 22:37:32 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: current@FreeBSD.org
Message-ID: <Pine.NEB.3.96L.1041226223521.46391E-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Occasional wedging entering DDB via serial break
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: Sun, 26 Dec 2004 22:40:48 -0000


I'm seeing occasional wedging attempting to enter DDB via a serial break
on a dual-Xeon box (4 logical processors).  The symptoms usually look
something like this:

hippy# ./tmp.csh
~KDB: enter: Line break on console
[thread pid 560 tid 100202 ]
Stopped at      kdb_enter+0x2c: leave
db> show alllocks
db> cont
load: 0.04  cmd: super-smack 619 [runnable] 0.02u 0.51s 2% 2216k
~KDB: enter: Line break on console
[thread pid 560 tid 100201 ]
Stopped at      kdb_enter+0x2c: leave
db> show alllocks
Process 560 (mysqld)
Thread 0x18769
exclusive sleep mutex so_rcv r = 0 (0xc2a25bcc) locked @
kern/uipc_usrreq.c:464
exclusive sleep mutex unp r = 0 (0xc091a740) locked @
kern/uipc_usrreq.c:392
db> cont
load: 0.92  cmd: super-smack 619 [runnable] 0.05u 1.36s 6% 2216k
~KDB: enter: Line break on console
[thread pid 560 tid 100199 ]
Stopped at      kdb_enter+0x2c: leave
db> show alllocks
db> cont
load: 2.12  cmd: super-smack 616 [running] 0.08u 2.90s 10% 2216k
~KDB: enter: Line break on console
<wedge>

After that point, a serial break will no longer drop to DDB, respond to
pings, etc.  The box is running 6.x-CURRENT from this morning.  Is anyone
else seeing this, or does anyone else have ideas about what might cause
this?

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