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 news on this? I have updated to the
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 Bartondo...@freebsd.org 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
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 latest current so I'm
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 Bartondo...@freebsd.org wrote:
On 06/01/10 08:26, John Baldwin wrote:
I've asked
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 Bartondo...@freebsd.org wrote:
On 06/01/10 08:26, John Baldwin wrote:
I've asked the driver author if the calls to
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 so I'm
running the nv
On Mon, Jun 14, 2010 at 2:31 PM, Christian Zander czan...@nvidia.com 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
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, etc.
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
On Sun, Jun 13, 2010 at 8:38 PM, Doug Barton do...@freebsd.org 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
On 06/13/10 19:09, Alan Cox wrote:
On Sun, Jun 13, 2010 at 8:38 PM, Doug Bartondo...@freebsd.org 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
On Sat, May 29, 2010 at 12:31 PM, Garrett Cooper yanef...@gmail.com wrote:
On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity
datastream.freec...@gmail.com wrote:
On Sun, May 30, 2010 at 2:11 AM, Doug Barton do...@freebsd.org wrote:
On 05/26/10 09:51, Kostik Belousov wrote:
I
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 did the
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
On Sun, May 30, 2010 at 2:11 AM, Doug Barton do...@freebsd.org 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.patchhttp://people.freebsd.org/%7Ekib/misc/nvidia-vm_page_lock.1.patch
I
On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity
datastream.freec...@gmail.com wrote:
On Sun, May 30, 2010 at 2:11 AM, Doug Barton do...@freebsd.org wrote:
On 05/26/10 09:51, Kostik Belousov wrote:
I did a quick glance over the driver, try this:
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
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
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
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
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
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
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
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
On Wed, May 26, 2010 at 10:41 AM, Alan Cox a...@cs.rice.edu 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 machine
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 machine
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
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
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
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
30 matches
Mail list logo
