From owner-freebsd-current Tue Jul 16 7:31:53 2002 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 86C0437B400 for ; Tue, 16 Jul 2002 07:31:50 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64F8043E58 for ; Tue, 16 Jul 2002 07:31:49 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g6GEUvwr027315; Tue, 16 Jul 2002 07:31:02 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200207161431.g6GEUvwr027315@gw.catspoiler.org> Date: Tue, 16 Jul 2002 07:30:57 -0700 (PDT) From: Don Lewis Subject: Re: VOP_GETATTR panic on Alpha To: des@ofug.org Cc: gallatin@cs.duke.edu, current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 16 Jul, Dag-Erling Smorgrav wrote: > Andrew Gallatin writes: >> Just clear panicstr (w panicstr 0) when you drop into >> the debugger on a panic. > > No luck. However, I added an ASSERT_VOP_LOCKED() to vn_statfile(), > and confirmed that vn_lock() fails to lock the vnode. Unfortunately, > without a dump it's hard to tell exactly what kind of vnode we're > dealing with. > > I thought the problem might be an incorrect vop_lock implementation in > devfs (the only synthetic filesystem mounted on the box), but devfs > uses std_{islocked,lock,unlock}, and visual inspection didn't uncover > any obvious flaws in any of those. > > Any other suggestions before I just turn off DEBUG_VFS_LOCKS? Turn it off. I ran into similar problems about a week ago and the author told me that this option was broken because only part of the stuff in his private source tree was committed. I haven't heard anything since then to make me think that this option has been fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message