Date: Tue, 25 Sep 2001 19:22:25 -0400 (EDT) From: Evan Sarmiento <evms@cs.bu.edu> To: freebsd-hackers@freebsd.org, freebsd-current@freebsdorg.FreeBSD.ORG Subject: IMPORTANT!! Re: panic on mount Message-ID: <15281.4529.188277.263940@csa.bu.edu> In-Reply-To: <XFMail.010925135203.jhb@FreeBSD.org> References: <200109250019.RAA08335@windsor.research.att.com> <XFMail.010925135203.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Just to clarify things for everyone who may be having this probme: there is a panic on bootup with current, within the witness* code. You can avoid this by commenting out WITNESS in your kernel configuration and recompiling. It worked for me.. Hope this helps someone. Thanks, Evan John Baldwin writes: > > On 25-Sep-01 Bill Fenner wrote: > > > > I also started getting this error with recent kernels (in the last > > day or so). > > It looks like the mutex is really held since the mtx_assert before > witness_unlock didn't trigger. You can try turning witness off for the time > being as a workaround. I'm not sure why witness would be broken, however. > > > 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 > > -- > > John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15281.4529.188277.263940>