Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Jul 2006 17:23:45 +0100 (BST)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        Holtor <holtor@yahoo.com>
Cc:        stable@freebsd.org
Subject:   Re: Frozen Processes
Message-ID:  <20060721172221.Q79560@fledge.watson.org>
In-Reply-To: <20060721014004.85734.qmail@web31708.mail.mud.yahoo.com>
References:  <20060721014004.85734.qmail@web31708.mail.mud.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060721172221.Q79560>