Date: 16 Jul 2002 15:48:28 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@FreeBSD.ORG Subject: Re: VOP_GETATTR panic on Alpha Message-ID: <xzpznwr2383.fsf@flood.ping.uio.no> In-Reply-To: <15668.7489.398182.956144@grasshopper.cs.duke.edu> References: <xzpele33kq0.fsf@flood.ping.uio.no> <15668.5911.639776.253419@grasshopper.cs.duke.edu> <xzpador3jhw.fsf@flood.ping.uio.no> <15668.7489.398182.956144@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin <gallatin@cs.duke.edu> 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?
DES
--
Dag-Erling Smorgrav - des@ofug.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpznwr2383.fsf>