From owner-freebsd-current@FreeBSD.ORG Tue Apr 3 13:31:40 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A83E106566B; Tue, 3 Apr 2012 13:31:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4E7858FC15; Tue, 3 Apr 2012 13:31:40 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.5/8.14.5) with ESMTP id q33DVYfE021581; Tue, 3 Apr 2012 06:31:34 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id q33DVYNo021580; Tue, 3 Apr 2012 06:31:34 -0700 (PDT) (envelope-from david) Date: Tue, 3 Apr 2012 06:31:34 -0700 From: David Wolfskill To: John Baldwin Message-ID: <20120403133134.GN1420@albert.catwhisker.org> References: <20120330131833.GV1709@albert.catwhisker.org> <201203301346.58219.jhb@freebsd.org> <20120330213307.GA1709@albert.catwhisker.org> <201204030855.34922.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NJSRbAqOy4NeGDns" Content-Disposition: inline In-Reply-To: <201204030855.34922.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Failure to rebuild x11/nvidia-driver on head at r233697 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2012 13:31:40 -0000 --NJSRbAqOy4NeGDns Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 03, 2012 at 08:55:34AM -0400, John Baldwin wrote: > ... > > > You can actually use that on 8 and 9 as well. I think it's a likely = a bug > > > that it used VM_MEMATTR_UNCACHED in the first place and that it shoul= d have > > > been using VM_MEMATTR_UNCACHEABLE all along. (Which is why I've rena= med > > > the obscure and not really useful VM_MEMATTR_UNCACHED.) > > > ... > >=20 > > OK; that seems to work, at least under stable/8 -- thanks! >=20 > FYI, this should be fixed in the next driver release from NVIDIA. > ... Cool; thanks for mentioning it. In the mean time, the patch (that I posted earlier) that replaces VM_MEMATTR_UNCACHED with VM_MEMATTR_UNCACHEABLE works for me under stable/8, stable/9, and head, so folks may want to use something like that if they don't want to wait. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --NJSRbAqOy4NeGDns Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk96+7UACgkQmprOCmdXAD1SmgCfbI2NLfnHzWYpDSkeD4YIEVou 6Z0Anj7zYUxwSc926FLKu4mdeMbKrZ06 =3M8p -----END PGP SIGNATURE----- --NJSRbAqOy4NeGDns--