Andrew Gallatin <[EMAIL PROTECTED]> writes: > Welcome to hell.
Thanks, it sure looks cozy in here :) > If you clear panicstr, you have a chance of getting a dump. How do I do that? BTW, I've looked at the code in vn_statfile(): vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, td); error = vn_stat(vp, sb, td); VOP_UNLOCK(vp, 0, td); it seems that either vn_lock() fails to actually lock the vnode, or there's a race condition that causes the vnode to get unlocked between vn_lock() and vn_stat(). Since the panic is 100% reproducible, I'm inclined to think it's the former. Note that vn_statfile() fails to check the return code from vn_lock(), but LK_RETRY is supposed to mean vn_lock() never fails. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message