From owner-freebsd-current  Mon Sep 24 17:51:10 2001
Delivered-To: freebsd-current@freebsd.org
Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9])
	by hub.freebsd.org (Postfix) with ESMTP id 4B94337B416
	for <freebsd-current@freebsd.org>; Mon, 24 Sep 2001 17:51:07 -0700 (PDT)
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA52436;
	Mon, 24 Sep 2001 18:26:02 -0700 (PDT)
Date: Mon, 24 Sep 2001 18:26:01 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Bill Fenner <fenner@research.att.com>
Cc: peter@wemm.org, mark@grondar.za, evms@cs.bu.edu,
	freebsd-current@freebsd.org
Subject: Re: panic on mount
In-Reply-To: <200109250019.RAA08335@windsor.research.att.com>
Message-ID: <Pine.BSF.4.21.0109241824480.52270-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

You could probably set teh device using DDB, but I just use a serial debug
link


On Mon, 24 Sep 2001, Bill Fenner wrote:

> 
> I also started getting this error with recent kernels (in the last
> day or so).
> 
> Mounting root from ufs:/dev/ad0s1a
> panic: lock (sleep mutex) vnode interlock not locked @ /usr/src/sys/kern/vfs_default.c:460
> Debugger("panic")
> Stopped at      Debugger+0x44:  pushl   %ebx
> db> t
> Debugger(c03c5bbb) at Debugger+0x44
> panic(c03c8c40,c03c4b80,c03ccf20,c03cc8a0,1cc) at panic+0x70
> witness_unlock(c7765f2c,8,c03cc8a0,1cc,c7765f2c,1,c03c4ba0,f6) at witness_unlock+0x1d0
> _mtx_unlock_flags(c7765f2c,0,c03cc8a0,1cc,c0567bd0) at _mtx_unlock_flags+0x59
> vop_nolock(c0567be8,c0567bf8,c02920c2,c0567be8,c0567d4c) at vop_nolock+0x24
> vop_defaultop(c0567be8) at vop_defaultop+0x15
> vn_lock(c7765ec0,20002,c049f7c4,c0567d4c,c1346680) at vn_lock+0xca
> ffs_mountfs(c7765ec0,c1351600,c049f7c4,c0446900,c0567d4c) at ffs_mountfs+0x7e
> ffs_mount(c1351600,0,0,0,c049f7c4) at ffs_mount+0x67
> vfs_mountroot_try(c05447a8,c03cc48c) at vfs_mountroot_try+0x14e
> vfs_mountroot(0,564c00,564000,0,c012caac) at vfs_mountroot+0x5a
> mi_startup() at mi_startup+0x90
> begin() at begin+0x43
> 
> I dunno how to get a dump from this point since kern.dumpdev hasn't been
> set..
> 
>   Bill
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message