From owner-freebsd-current@FreeBSD.ORG  Tue Jan 25 09:40:24 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4980316A4D1
	for <current@freebsd.org>; Tue, 25 Jan 2005 09:40:24 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 00E8C43D49
	for <current@freebsd.org>; Tue, 25 Jan 2005 09:40:16 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 55484513D5; Tue, 25 Jan 2005 01:40:14 -0800 (PST)
Date: Tue, 25 Jan 2005 01:40:14 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Jeff Roberson <jroberson@chesapeake.net>
Message-ID: <20050125094014.GB13880@xor.obsecurity.org>
References: <20050124040646.H97135@mail.chesapeake.net>
	<20050124055400.U97135@mail.chesapeake.net>
	<20050125044210.GA46896@xor.obsecurity.org>
	<20050125043000.R18864@mail.chesapeake.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ADZbWkCsHQ7r3kzd"
Content-Disposition: inline
In-Reply-To: <20050125043000.R18864@mail.chesapeake.net>
User-Agent: Mutt/1.4.2.1i
cc: current@freebsd.org
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: tree may not be buildable for an hour.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2005 09:40:24 -0000


--ADZbWkCsHQ7r3kzd
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?

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

--ADZbWkCsHQ7r3kzd
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFB9hP+Wry0BWjoQKURAvDBAJ9ZnMa0e1cbApIr3LJGVE80NFfUnQCdHj/5
HGObbpmm1BMqsWWLOTmmJhA=
=zV93
-----END PGP SIGNATURE-----

--ADZbWkCsHQ7r3kzd--