Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 14-06-2010 23:31, Christian Zander wrote: > On Mon, Jun 14, 2010 at 02:30:03PM -0700, Rene Ladan wrote: > (...) >>> I've asked the driver author if the calls to vm_page_wire() and >>> vm_page_unwire() can simply be removed but have not heard back yet. >>> >> >> Is there any n

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/14/10 19:14, Doug Barton wrote: Details, I'm running today's -current (r209174) and I've had it up for 4.5 hours already, which is 3 hours longer than I was able to run with anything > 195.22 for months. I've done full "normal" use which includes lots of terminals, tbird, firefox, flash, et

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Mon, Jun 14, 2010 at 2:31 PM, Christian Zander wrote: > On Mon, Jun 14, 2010 at 02:30:03PM -0700, Rene Ladan wrote: > (...) >> > I've asked the driver author if the calls to vm_page_wire() and >> > vm_page_unwire() can simply be removed but have not heard back yet. >> > >> >> >

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Mon, Jun 14, 2010 at 02:30:03PM -0700, Rene Ladan wrote: (...) > > I've asked the driver author if the calls to vm_page_wire() and > > vm_page_unwire() can simply be removed but have not heard back yet. > > > > Is there any news on this? I have updated to the latest current

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 14-06-2010 14:48, John Baldwin wrote: > On Sunday 13 June 2010 11:23:07 pm Doug Barton wrote: >> On 06/13/10 19:09, Alan Cox wrote: >>> On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: >>> On 06/01/10 08:26, John Baldwin wrote: > > I've asked the driver author if the calls

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/14/10 14:30, Rene Ladan wrote: On 14-06-2010 14:48, John Baldwin wrote: On Sunday 13 June 2010 11:23:07 pm Doug Barton wrote: On 06/13/10 19:09, Alan Cox wrote: On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: On 06/01/10 08:26, John Baldwin wrote: I've asked the driver author

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Mon, Jun 14, 2010 at 05:48:55AM -0700, John Baldwin wrote: (...) > > >>> > > >>> I've asked the driver author if the calls to vm_page_wire() and > > >>> vm_page_unwire() can simply be removed but have not heard back yet. > > >>> > > >> > > >> Is there any news on this? I have updated to the late

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sunday 13 June 2010 11:23:07 pm Doug Barton wrote: > On 06/13/10 19:09, Alan Cox wrote: > > On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: > > > >> On 06/01/10 08:26, John Baldwin wrote: > >> > >>> > >>> I've asked the driver author if the calls to vm_page_wire() and > >>> vm_page_unwire()

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/13/10 19:09, Alan Cox wrote: On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: On 06/01/10 08:26, John Baldwin wrote: I've asked the driver author if the calls to vm_page_wire() and vm_page_unwire() can simply be removed but have not heard back yet. Is there any news on this? I h

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton wrote: > On 06/01/10 08:26, John Baldwin wrote: > >> >> I've asked the driver author if the calls to vm_page_wire() and >> vm_page_unwire() can simply be removed but have not heard back yet. >> > > Is there any news on this? I have updated to the lates

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 06/01/10 08:26, John Baldwin wrote: I've asked the driver author if the calls to vm_page_wire() and vm_page_unwire() can simply be removed but have not heard back yet. Is there any news on this? I have updated to the latest current so I'm running the nv driver now, but I'd like to get the

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Saturday 29 May 2010 10:55:41 pm Craig Rodrigues wrote: > On Sun, May 30, 2010 at 02:48:13AM +0800, datastream datastream.freecity wrote: > > > http://www.nvnews.net/vbulletin/showthread.php?t=150719 > > NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. > > Hi, > > I

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sat, May 29, 2010 at 12:31 PM, Garrett Cooper wrote: > On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity > wrote: >> >> On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: >>> >>> On 05/26/10 09:51, Kostik Belousov wrote: I did a quick glance over the driver, try this

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, May 30, 2010 at 02:48:13AM +0800, datastream datastream.freecity wrote: > > http://www.nvnews.net/vbulletin/showthread.php?t=150719 > NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. Hi, I did the following: - updated r208649 - applied following patch to nvidia-

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity wrote: > > On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: >> >> On 05/26/10 09:51, Kostik Belousov wrote: >>> >>> I did a quick glance over the driver, try this: >>> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.pat

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >> >> I did a quick glance over the driver, try this: >> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch >> I did no

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/10 09:51, Kostik Belousov wrote: 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. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 5/27/2010 12:12 PM, Kostik Belousov wrote: I think you have stale/wrong includes used by the build. I just checked that driver indeed builds with my patch. vm_page_lock() and vm_page_unlock() are the macros defined in vm/vm_page.h that are present since first Kip commit. As I reported earlie

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Thu, May 27, 2010 at 11:54:27AM -0700, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >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. > > cc -pipe -g -g -g -DNV_V

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/10 09:51, Kostik Belousov wrote: 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. cc -pipe -g -g -g -DNV_VERSION_STRING=\"195.36.15\" -D__KERNEL__ -DNVRM -O -Werror -D_KERNEL -DK

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 5/26/2010 2:56 PM, Ryan Stone wrote: I'm by no means an expert in this area, but isn't removing the locking on free a bad thing? Looking at the code, it seems that vm_page_unwire() only requires the page to be locked if it is managed. As it was acquired by contigmalloc, the page should

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

> I'm by no means an expert in this area, but isn't removing the locking > on free a bad thing? Looking at the code, it seems that vm_page_unwire() only requires the page to be locked if it is managed. As it was acquired by contigmalloc, the page should be unmanaged so that should be ok. I am co

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Wed, May 26, 2010 at 12:41:51PM -0500, Alan Cox wrote: > Kostik Belousov wrote: > >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

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On Wed, May 26, 2010 at 10:41 AM, Alan Cox wrote: > Kostik Belousov wrote: >> >> 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 mach

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 5/26/2010 9:51 AM, Kostik Belousov wrote: 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. Kostik, Thanks for taking a look at this! I sent the following to Alexey recently in regard

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

Kostik Belousov wrote: 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

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

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 > >sa

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

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 def

Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

On 05/26/2010 12:00 AM, 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 rev

nvidia-driver 195.22 use horribly broken on amd64 between r206173 and

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 do