From owner-freebsd-current@FreeBSD.ORG  Tue Oct 26 10:30:56 2004
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 6C82516A4CE; Tue, 26 Oct 2004 10:30:56 +0000 (GMT)
Received: from ptcnat.era.pl (ptcnat.era.pl [213.158.197.100])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 282FA43D41; Tue, 26 Oct 2004 10:30:56 +0000 (GMT)
	(envelope-from zaks@era.pl)
Received: by localhost (Postfix, from userid 1001)
	id 158DB11445; Tue, 26 Oct 2004 12:30:55 +0200 (CEST)
From: =?iso-8859-2?q?S=B3awek_=AFak?= <zaks@prioris.mini.pw.edu.pl>
To: current@freebsd.org
References: <86k6tdeq84.fsf@thirst.unx.era.pl>
Date: Tue, 26 Oct 2004 12:30:55 +0200
In-Reply-To: <86k6tdeq84.fsf@thirst.unx.era.pl> 
 =?iso-8859-2?q?=28S=B3awek's?= message of "Tue, 26 Oct 2004 12:19:39 +0200")
Message-ID: <86zn29db4w.fsf@thirst.unx.era.pl>
User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.4 (Reasonable Discussion,
 berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
cc: rwatson@freebsd.org
Subject: Re: Hard hangs on AMD64 with mpsafenet enabled
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: Tue, 26 Oct 2004 10:30:56 -0000

Sławek Żak <zaks@prioris.mini.pw.edu.pl> writes:

> Hi,
>
>     I've got a Sun V20z 2 cpu Opteron box. I experience hard hangs when
>     accessing NFS simulatneously from 2 processes (tested with parallel port
>     builds with /usr/ports mounted over NFS with
>     nosuid,nodev,soft,bg,intr). rpc.lockd and rpc.statd are both enabled for
>     NFS.

    Bah, following up to my mail. With mpsafenet disable everything seems fine
    and stable. The system is yesterday's 5.3-STABLE (RELENG_5 branch).

/S