Date: Wed, 26 May 2010 19:51:41 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Alan Cox <alc@cs.rice.edu> Cc: alc@freebsd.org, Garrett Cooper <yanefbsd@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and Message-ID: <20100526165141.GF83316@deviant.kiev.zoral.com.ua> In-Reply-To: <4BFD4AE6.5040105@cs.rice.edu> References: <AANLkTil33IEVGXxsjV1oqfBgKQq-aIJ9Ur1U0Gn8Gplt@mail.gmail.com> <4BFD4AE6.5040105@cs.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--qbWslfj5jix8J1iW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: > Garrett Cooper wrote: > > Just reporting the fact that nvidia-driver 195.22 is horribly > >broken between r206173 and r208486 (my machine consistency livelocks > >at X11 startup); the latest driver is still broken as well with the > >same symptoms. I realize that's a huge revision difference, and I'll > >definitely try and track down the root cause via a binary search, but > >I wanted to make sure that other folks knew of the issue and don't > >upgrade and their systems break horribly as well. > > I suspect that the locking changes are causing the issue, but I > >don't have any hard data to backup my claim at this time. > > =20 >=20 > I'm sure they are. The Nvidia driver directly accesses low-level=20 > virtual memory structures on which the synchronization rules have=20 > changed. (In contrast, the Xorg dri drivers in our source tree are=20 > using higher-level interfaces that have remained stable.) >=20 > I don't think that a binary search is needed. The lock assertion=20 > failures should indicate most if not all of the changes that are needed= =20 > in the driver. When Kip got this process started, he bumped=20 > FreeBSD_version, so it should be possible to condition the locking=20 > changes in the driver. >=20 > Good luck! I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. --qbWslfj5jix8J1iW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkv9UZwACgkQC3+MBN1Mb4jx+ACfcqwH2Tj17rNp/JhcVogezvoz cYAAnjS5f1sblFbGHuH/u3Xry7N2lqKt =bT4i -----END PGP SIGNATURE----- --qbWslfj5jix8J1iW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100526165141.GF83316>