From owner-freebsd-arch@FreeBSD.ORG  Sat Jun 20 16:50:57 2009
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 96E871065676
	for <freebsd-arch@FreeBSD.org>; Sat, 20 Jun 2009 16:50:57 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from dhcp-172-28-77-157.eur.corp.google.com (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 803248FC12;
	Sat, 20 Jun 2009 16:50:56 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <4A3D136F.1090106@FreeBSD.org>
Date: Sat, 20 Jun 2009 17:50:55 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Bruce Evans <brde@optusnet.com.au>
References: <20090619162328.GA79975@stack.nl>	<20090619194654.GC2884@deviant.kiev.zoral.com.ua>
	<20090620121543.F29239@delplex.bde.org>
In-Reply-To: <20090620121543.F29239@delplex.bde.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Kostik Belousov <kostikbel@gmail.com>, Jilles Tjoelker <jilles@stack.nl>,
	freebsd-arch@FreeBSD.org
Subject: Re: deadlocks with intr NFS mounts and ^Z (or: PCATCH and sleepable
 locks)
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jun 2009 16:50:57 -0000

Bruce Evans wrote:

> These problems seemed to go away, but right now the following problem
> like the second set above occurs consistently (I first noticed this
> last week):
> 
>     Script started on Sat Jun 20 02:32:51 2009
>     pts/0:bde@ref8-i386:~/sys7/i386/compile> sh zm
>     ^Z
>     [1]+  Stopped                 sh zm
>     pts/0:bde@ref8-i386:~/sys7/i386/compile> %
>     sh zm
>     *** Stopped -- signal 18
>     *** Stopped -- signal 18
>     *** Stopped -- signal 18
>     *** Signal 1
>     *** Signal 1
>     *** Signal 1
>     `all' not remade because of errors.
>     linking kernel
>     ^C
>     pts/0:bde@ref8-i386:~/sys7/i386/compile> exit
> 
>     Script done on Sat Jun 20 02:34:41 2009
> 
> The shell script zm builds 6 kernels in parallel using make -k -j8 for
> each.  Signal 18 is SIGTSTP.  Receiving this is normal, but the shell
> shouldn't print any meesages about it.  Signal 1 is SIGHUP.  This
> shouldn't occur.  On another run, ISTR getting messages about i/o
> errors or unrestartable processes.  Anyway, the messages about signals
> are associated with failing jobs in the build.

That's a long standing bug that I don't think is limited to NFS.  I 
first started seeing it several years ago after some changes to make(1), 
but I don't recall if phk disputed that they were to blame.

Kris