From owner-freebsd-current@FreeBSD.ORG  Mon Dec  1 06:26:38 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 8DDDF16A4CE
	for <freebsd-current@FreeBSD.org>;
	Mon,  1 Dec 2003 06:26:38 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DEAD144027
	for <freebsd-current@FreeBSD.org>;
	Mon,  1 Dec 2003 06:26:02 -0800 (PST)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hB1ENLMg048054;
	Mon, 1 Dec 2003 09:23:21 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)hB1ENLOr048051;
	Mon, 1 Dec 2003 09:23:21 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Date: Mon, 1 Dec 2003 09:23:21 -0500 (EST)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: Jun Kuriyama <kuriyama@imgsrc.co.jp>
In-Reply-To: <7mznedas57.wl@black.imgsrc.co.jp>
Message-ID: <Pine.NEB.3.96L.1031201092204.74465L-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Current <freebsd-current@FreeBSD.org>
Subject: Re: -current lockup (how to diagnose?)
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, 01 Dec 2003 14:26:38 -0000


On Mon, 1 Dec 2003, Jun Kuriyama wrote:

> I got lockups in recent -current box.  This box is my main workstation
> and usually be up to date kernel. 
> 
> In recent days, I usually locked up.  This is not a panic, only locks
> up.  My situation is: 
> 
> o KDE's clock is working.
> o KDE's virtual screen switching is working.
> o Apache does not reply on 80/tcp from remote.
> o ssh from this box is still working.
> o zsh on this box does not go next prompt when I press enter key at
>   promprt.
> 
> It looks kernel is working, but fork/exec is not working when I enter to
> this situation. 
> 
> So, what can I diagnose with this situation?  Of course this box has
> serial console. 

This could be a sign of a VM or VFS lock leak or deadlock.  I'd advise
hooking up a serial console, dropping to DDB over serial line, and posting
the results of "ps" and "show lockedvnods".  We might then ask you to use
the "show locks" command on various processes.  You'll need to have DDB
and WITNESS compiled in.

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