From owner-freebsd-stable@FreeBSD.ORG  Sat Oct 21 07:10:21 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from localhost.my.domain (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9FEA316A4D1;
	Sat, 21 Oct 2006 07:10:20 +0000 (UTC)
	(envelope-from davidxu@freebsd.org)
From: David Xu <davidxu@freebsd.org>
To: freebsd-stable@freebsd.org
Date: Sat, 21 Oct 2006 15:10:09 +0800
User-Agent: KMail/1.8.2
References: <17718.20457.799395.602805@gromit.timing.com>
	<20061021035749.GY55428@deviant.kiev.zoral.com.ua>
	<17721.50338.220767.201120@gromit.timing.com>
In-Reply-To: <17721.50338.220767.201120@gromit.timing.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610211510.09350.davidxu@freebsd.org>
Cc: Kostik Belousov <kostikbel@gmail.com>, John E Hein <jhein@timing.com>,
	jhb@freebsd.org
Subject: Re: locked vnode / nfs... requires kill -9 in ddb
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: Sat, 21 Oct 2006 07:10:21 -0000

On Saturday 21 October 2006 14:56, John E Hein wrote:

> David, here's the original report.
> http://lists.freebsd.org/pipermail/freebsd-stable/2006-October/029755.html
>
> Indeed, as Kostik surmised, the mount point is mounted intr.
>
> I did not notice this problem while running with releng_6 from late
> June for 3 months.  Could it be this problem was introduced between
> then and now?
>
> This also just happened today on a system I just updated from 5.3
> to 5.5-p8.

This is also RELENG_4's behavior, if PCATCH is set, the tsleep will
call CURSIG() which will suspends current process if there is a
SIGTSTP or SIGSTOP signal.