From owner-freebsd-current Mon Sep 24 18:31:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 9FBC737B403 for ; Mon, 24 Sep 2001 18:31:40 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f8P1VeM20217 for ; Mon, 24 Sep 2001 18:31:40 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3466A3808; Mon, 24 Sep 2001 18:31:40 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Julian Elischer Cc: Bill Fenner , mark@grondar.za, evms@cs.bu.edu, freebsd-current@freebsd.org Subject: Re: panic on mount In-Reply-To: Date: Mon, 24 Sep 2001 18:31:40 -0700 From: Peter Wemm Message-Id: <20010925013140.3466A3808@overcee.netplex.com.au> 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 Julian Elischer wrote: > You could probably set teh device using DDB, but I just use a serial debug > link Not a good strategy. dev_t is a pointer in -current. We probably need a 'dumpon 13,0x00020001' ddb command that does something like what sysctl_kern_dumpdev() does.. > 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/vf s_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_u nlock+0x1d0 > > _mtx_unlock_flags(c7765f2c,0,c03cc8a0,1cc,c0567bd0) at _mtx_unlock_flags+0x 59 > > 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+0x 7e > > 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 > > > > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message