Date: Fri, 23 Jan 2009 12:07:57 +0000 From: Gavin Atkinson <gavin@FreeBSD.org> To: Paul Tice <ptice@aldridge.com> Cc: freebsd-current@FreeBSD.org Subject: Re: UFS/VFS lock order reversal on stock 8.0-200812-AMD64 Message-ID: <1232712477.89022.7.camel@buffy.york.ac.uk> In-Reply-To: <E8FEAE26C87DED4EB49EFF99D1C7A51DFF6927@ald-mail02.corporate.aldridge.com> References: <E8FEAE26C87DED4EB49EFF99D1C7A51DFF6927@ald-mail02.corporate.aldridge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2009-01-22 at 21:33 -0600, Paul Tice wrote: > I'm new, so please advise me (gently?) about list protocol and such if ne= eded. >=20 > Using stock 8.0-CURRENT-200812-amd64, I am getting the messages below. 8.0-CURRENT is essentially the bleeding-edge of FreeBSD, and is where development happens that has not necessarily proven itself as being stable. As it is the development branch, it also has a lot of extra debugging enabled, which is what you are seeing with the "lock order reversals". If you are not running 8-CURRENT for a specific reason (e.g. because you are doing FreeBSD OS development work, or you are prepared to help debug issues as you encounter them, or similar), you probably shouldn't be running CURRENT. Stick with 7.1. Gavin > I've run memtest 3.4 through 3 passes with no errors. > I did go through an entire boot/install with no errors by setting all cac= hing to Write-Through in BIOS, but that leads to unacceptable performance, = and I'm not sure the slowness wasn't masking the problem. > Motherboard is a Supermicro x7dvl3, 8G of RAM (4 x 2G matched within a sm= all range of serial numbers.) > Chipset is an Intel 5000V with a ESB2 Southbridge. Cpu is 2 Quad core Xeo= n 5400 Series @ 2GHz. This is a fairly new CPU with a larger cache than pre= vious Xeons (12Meg L2). > The error occurs whether I use the LSI 1068E attached via PCI-E(x4) or th= e ESB2 onboard SATA. > I do not get the error when mounting another drive after booting, I do se= e the same error when shutting down. > I also notice (maybe related) text video corruption during shutdown. (XGI= Volari=99 Z7 PCI-E Graphics Processor) >=20 > Am I too wordy, or did I forget something? >=20 >=20 > Trying to mount root from ufs:/dev/ad20s1a > lock order reversal: > 1st 0xffffff0001701070 user map (user map) @ /usr/src/sys/vm/vm_map.c:31= 15 > 2nd 0xffffff0001ea87f8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2079 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x81e > __lockmgr_args() at __lockmgr_args+0xca8 > ffs_lock() at ffs_lock+0x8c > VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b > _vn_lock() at _vn_lock+0x47 > vget() at vget+0x8b > vnode_pager_lock() at vnode_pager_lock+0x1d0 > vm_fault() at vm_fault+0x1e2 > trap_pfault() at trap_pfault+0x128 > trap() at trap+0x51c > calltrap() at calltrap+0x8 > --- trap 0xc, rip =3D 0x40014f, rsp =3D 0x7fffffffee70, rbp =3D 0x7ffffff= fee90 --- >=20 > Later in the boot sequence > lock order reversal: > 1st 0xfffffffec0491330 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2= 443 > 2nd 0xffffff0004163000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirh= ash.c:263 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x81e > _sx_xlock() at _sx_xlock+0x55 > ufsdirhash_acquire() at ufsdirhash_acquire+0x33 > ufsdirhash_add() at ufsdirhash_add+0x19 > ufs_direnter() at ufs_direnter+0x889 > ufs_makeinode() at ufs_makeinode+0x338 > VOP_CREATE_APV() at VOP_CREATE_APV+0x8d > vn_open_cred() at vn_open_cred+0x479 > kern_openat() at kern_openat+0x169 > syscall() at syscall+0x1bf > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (5, FreeBSD ELF64, open), rip =3D 0x800daceac, rsp =3D 0x7fff= ffffe7c8, rbp =3D 0x8 --- >=20 > Thanks > Paul > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1232712477.89022.7.camel>