Date: Tue, 25 Jan 2005 01:40:14 -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: <20050125094014.GB13880@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
[-- Attachment #1 --] On Tue, Jan 25, 2005 at 04:30:46AM -0500, Jeff Roberson wrote: > > On Mon, 24 Jan 2005, Kris Kennaway wrote: > > > 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 have > > > 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 have > > > been seen on normal systems to my knowledge. > > > > Still seeing this one: > > > > What did you do to reproduce this? Nothing I can easily pin down, it happens after several hours of package building. > 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. Will do! Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB9hP+Wry0BWjoQKURAvDBAJ9ZnMa0e1cbApIr3LJGVE80NFfUnQCdHj/5 HGObbpmm1BMqsWWLOTmmJhA= =zV93 -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050125094014.GB13880>