From owner-freebsd-stable@FreeBSD.ORG  Fri Jul 21 16:23:46 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: stable@freebsd.org
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AB10616A4DD
	for <stable@freebsd.org>; Fri, 21 Jul 2006 16:23:46 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 14F1B43D4C
	for <stable@freebsd.org>; Fri, 21 Jul 2006 16:23:46 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 8479946CAF;
	Fri, 21 Jul 2006 12:23:45 -0400 (EDT)
Date: Fri, 21 Jul 2006 17:23:45 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Holtor <holtor@yahoo.com>
In-Reply-To: <20060721014004.85734.qmail@web31708.mail.mud.yahoo.com>
Message-ID: <20060721172221.Q79560@fledge.watson.org>
References: <20060721014004.85734.qmail@web31708.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: stable@freebsd.org
Subject: Re: Frozen Processes
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2006 16:23:46 -0000

On Thu, 20 Jul 2006, Holtor wrote:

> Since upgrading some of our 5.4 servers to the latest 6.1-STABLE we've had 
> some processes stuck in the *inp state as listed in 'top'. Those processes 
> can't be killed and any resources they use up in terms of bound IP addresses 
> or ports can't be freed. Does anyone know what this *inp state means or how 
> to fix this problem?

Processes in state '*inp' are waiting for an inpcb lock, suggesting a deadlock 
or lock leak.  Can you compile your kernel with invariants, witness, ddb, etc, 
and do a bit of kernel debugging?  You can find basic instructions in the 
handbook; what I'm particularly interested in is the output of "alltrace", 
"show alllocks", "show allpcpu".

Robert N M Watson
Computer Laboratory
University of Cambridge