From owner-freebsd-arm@FreeBSD.ORG Mon Jun 25 11:30:14 2012 Return-Path: Delivered-To: freebsd-arm@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A04D51065679 for ; Mon, 25 Jun 2012 11:30:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 896F78FC08 for ; Mon, 25 Jun 2012 11:30:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5PBUEp0099767 for ; Mon, 25 Jun 2012 11:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5PBUEXl099764; Mon, 25 Jun 2012 11:30:14 GMT (envelope-from gnats) Date: Mon, 25 Jun 2012 11:30:14 GMT Message-Id: <201206251130.q5PBUEXl099764@freefall.freebsd.org> To: freebsd-arm@FreeBSD.org From: Kristof Provost Cc: Subject: Re: arm/149288: mail/dovecot causes panic during configure on Sheevaplug (ARM) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kristof Provost List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 11:30:14 -0000 The following reply was made to PR arm/149288; it has been noted by GNATS. From: Kristof Provost To: bug-followup@FreeBSD.org Cc: Subject: Re: arm/149288: mail/dovecot causes panic during configure on Sheevaplug (ARM) Date: Mon, 25 Jun 2012 13:25:29 +0200 The problem appears to be fixed in HEAD, by commit r237367 (Enable deadlock avoidance code for NFS client.). As near as I can tell this fixes the panic: diff --git a/sys/fs/nfsclient/nfs_clvfsops.c b/sys/fs/nfsclient/nfs_clvfsops.c index af0e33b..966688f 100644 --- a/sys/fs/nfsclient/nfs_clvfsops.c +++ b/sys/fs/nfsclient/nfs_clvfsops.c @@ -1136,7 +1136,8 @@ nfs_mount(struct mount *mp) out: if (!error) { MNT_ILOCK(mp); - mp->mnt_kern_flag |= (MNTK_MPSAFE|MNTK_LOOKUP_SHARED); + mp->mnt_kern_flag |= MNTK_MPSAFE | MNTK_LOOKUP_SHARED | + MNTK_NO_IOPF; MNT_IUNLOCK(mp); } return (error); I'm not quite sure why that is, but I can now run both the sample code above and the dovecot configure script without panics. -- Kristof