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 [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
>
>
>
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
