Date: Tue, 25 Jan 2005 11:56:25 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Jeff Roberson <jroberson@chesapeake.net> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: tree may not be buildable for an hour. Message-ID: <20050125195625.GA76358@xor.obsecurity.org> In-Reply-To: <20050125043000.R18864@mail.chesapeake.net> References: <20050124040646.H97135@mail.chesapeake.net> <20050124055400.U97135@mail.chesapeake.net> <20050125044210.GA46896@xor.obsecurity.org> <20050125043000.R18864@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 25, 2005 at 04:30:46AM -0500, Jeff Roberson wrote: >=20 > On Mon, 24 Jan 2005, Kris Kennaway wrote: >=20 > > On Mon, Jan 24, 2005 at 05:56:48AM -0500, Jeff Roberson wrote: > > > That's all of it. If you wait for your cvsup mirror to catch up, you= can > > > try running with a smpsafe vfs by setting the debug.mpsafevfs tunable. > > > This option requires mpsafevm as well. I have two known bugs that ha= ve > > > only been triggered by peter holm's excellent stress suite, but none = are > > > known to cause problems if mpsafevfs is disabled, and none of them ha= ve > > > been seen on normal systems to my knowledge. > > > > Still seeing this one: > > >=20 > What did you do to reproduce this? Is there any chance you can recompile > with DEBUG_LOCKS in your kernel and fetch the file and line strings out of > the lockmgr lock for me? I've never seen this one myself. >=20 > > panic: lockmgr: locking against myself This machine panicked again, but did the usual: v--deadlocks trying to panic, then the other CPU holding the spin lock pani= cs pspin lock sched lock held by 0xc3502cf0 for > 5 seconds panic: spin lock held too long cpuid =3D 0 KDB: enter: panic so I wasn't able to get the trace yet. > > Also, another machine panicked with mpsafevfs=3D0, but as is commonplace > > on SMP machines it hung trying to print the panic string, so I can't > > tell whether it's related to your commits or not. This machine panicked again with mpsafevfs=3D0: panic: softdep_deallocate_dependencies: dangling deps cpuid =3D 1 KDB: enter: panic [thread pid 56889 tid 100248 ] Stopped at kdb_enter+0x30: leave db> tr Tracing pid 56889 tid 100248 td 0xc5b9eb80 kdb_enter(c06f2a2c,1,c070488e,f12c58fc,c5b9eb80) at kdb_enter+0x30 panic(c070488e,1,f12c593c,c05732ac,de837840) at panic+0x13e softdep_deallocate_dependencies(de837840,c0517311,c0750d20,0,c06f0dcc) at s= oftdep_deallocate_dependencies+0x1b brelse(de837840,2090022,c882f450,c5b9eb80,23) at brelse+0x96 flushbuflist(c882f498,4,c882f450,0,0) at flushbuflist+0x27a vinvalbuf(c882f450,4,c5b9eb80,0,0) at vinvalbuf+0x1a0 ffs_truncate(c882f450,0,0,c00,0) at ffs_truncate+0x6fa ufs_inactive(f12c5c10,c5b9eb80,1,f12c5c28,c0584ddc) at ufs_inactive+0x10a VOP_INACTIVE_AP(f12c5c10,0,c06fb21e,7a2,c074a9a0) at VOP_INACTIVE_AP+0x76 vput(c882f450,ffffffdf,2,6af,c59e3000) at vput+0x11a kern_unlink(c5b9eb80,804f6a8,0,f12c5d40,c06b2487) at kern_unlink+0x1c1 unlink(c5b9eb80,f12c5d14,4,3ff,1) at unlink+0x22 syscall(2f,2f,2f,1,804d000) at syscall+0x271 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (10, FreeBSD ELF32, unlink), eip =3D 0x280b8bf7, esp =3D 0xbfbf= e88c, ebp =3D 0xbfbfe8b8 --- db> Kris --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB9qRpWry0BWjoQKURAreNAJ4jsTwzrfEAMPnL4N2DhHFppw39VACfYwPY 2/1F8dAaSKh4fXNLto4v+ZM= =mvRz -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050125195625.GA76358>