From owner-freebsd-bugs@FreeBSD.ORG Thu Mar 5 11:54:03 2009 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CBC11065670 for ; Thu, 5 Mar 2009 11:54:03 +0000 (UTC) (envelope-from 7ogcg7g02@sneakemail.com) Received: from sneak1.sneakemail.com (sneakemail.com [38.113.6.61]) by mx1.freebsd.org (Postfix) with SMTP id B17CE8FC1B for ; Thu, 5 Mar 2009 11:54:02 +0000 (UTC) (envelope-from 7ogcg7g02@sneakemail.com) Received: (qmail 15229 invoked by uid 508); 5 Mar 2009 11:27:21 -0000 Date: 5 Mar 2009 11:27:21 -0000 To: freebsd-bugs@FreeBSD.org Encoding: 8bit From: "Edward Fisk" <7ogcg7g02@sneakemail.com> Message-ID: <31832-65829@sneakemail.com> Cc: Subject: Re: kern/132068: [zfs] page fault when using ZFS over NFS on 7.1-RELEASE/amd64 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2009 11:54:03 -0000 I tried with the patch kindly provided by Jaakko. The machine would no longer panic, but would instead deadlock every 1-2 hours when in use. I then did a source upgrade to 8-CURRENT (27022008) with a GENERIC kernel, which had the same result: a deadlock every 1 to 2 hours when in use. The machine is now running a GENERIC kernel with the following options added: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC Unfortunately, I've yet to be able to get it to deadlock, despite the workload on the machine not having changed.