Date: Mon, 3 May 2010 11:00:46 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Rene Ladan <rene@freebsd.org> Cc: Alexey Dokuchaev <danfe@freebsd.org>, Doug Barton <dougb@freebsd.org>, Max Laier <max@laiers.net>, cvs-all@freebsd.org, ports-committers@freebsd.org, Max Laier <max@love2party.net>, cvs-ports@freebsd.org Subject: Re: cvs commit: ports/x11/nvidia-driver Makefile distinfo pkg-plist Message-ID: <i2h7d6fde3d1005031100ja0ebaa0dl10a8a051d68083d5@mail.gmail.com> In-Reply-To: <s2z7d6fde3d1004261626i273ba1d7k3a05ba41f4a53e52@mail.gmail.com> References: <201004101340.o3ADe78U052886@repoman.freebsd.org> <201004252230.00453.max@love2party.net> <20100426143512.GA57194@FreeBSD.org> <201004262241.40603.max@laiers.net> <4BD6006D.6020205@freebsd.org> <s2z7d6fde3d1004261626i273ba1d7k3a05ba41f4a53e52@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 26, 2010 at 4:26 PM, Garrett Cooper <yanefbsd@gmail.com> wrote: > 2010/4/26 Rene Ladan <rene@freebsd.org>: >> On 26-04-2010 22:41, Max Laier wrote: >>> On Monday 26 April 2010 16:35:12 Alexey Dokuchaev wrote: >>>> On Sun, Apr 25, 2010 at 10:30:00PM +0200, Max Laier wrote: >>>>> On Sunday 25 April 2010 22:20:49 Doug Barton wrote: >>>>>> On 04/25/10 11:17, Max Laier wrote: >>>>>>> On Saturday 10 April 2010 15:40:07 Alexey Dokuchaev wrote: >>>>>>>> danfe =A0 =A0 =A0 2010-04-10 13:40:07 UTC >>>>>>>> >>>>>>>> =A0 FreeBSD ports repository >>>>>>>> >>>>>>>> =A0 Modified files: >>>>>>>> =A0 =A0 x11/nvidia-driver =A0 =A0Makefile distinfo pkg-plist >>>>>>>> =A0 Log: >>>>>>>> =A0 - Update nVidia BETA drivers to version 195.36.15 >>>>>>> >>>>>>> might be me, but it looks like the BETA driver has been more stable= . >>>>>>> I just downgraded back to BETA and now X doesn't hang anymore after >>>>>>> ~30min. >>>>>> >>>>>> I had to downgrade back to 195.22. When running the latest version I >>>>>> had freezes similar to what Max described. If it ran successfully fo= r >>>>>> any length of time it would lock up as soon as xscreensaver kicked i= n. >>>>> >>>>> not related to xscreensaver in my case, I don't think. =A0It was lock= ing up >>>>> while playing video in xine which - afaik - disables the screensaver.= =A0As >>>>> always, X lock ups are hard to track down unfortunately. =A0On the pl= us >>>>> side, it doesn't seem to be a hard lock up - i.e. the power button wo= uld >>>>> still get me to a clean shutdown eventually, but interrupts didn't fi= re >>>>> anymore (at least the network stops working). =A0I can't attach a ser= ial >>>>> console at the moment to get into DDB. =A0Will try to, tomorrow. >>>> >>>> Please do. =A0I am still not able to reproduce it here on Februarish >>>> -CURRENT/amd64 with GFX260. =A0You might also want to lurk on nVidia >>>> forums at http://www.nvnews.net/vbulletin/forumdisplay.php?f=3D47 to s= ee >>>> if someone has similar issues. >>> >>> There are quite a few reports. =A0I did a diff on the glue code and the= re are a >>> few changes between 22 and 36 that could be the culprit. =A0I'll invest= igate >>> further and let you know. =A08.0-RELEASE here, by the way - does anyone= know if >>> there are (missing) MFCs regarding the cdevpriv API? =A0That's one of t= he bigger >>> changes in the glue code. >>> >> The drviver seems to run ok here. X.org 7.4 has been running for 27 >> hours now, without lockups. =A0I'm using the blank screensaver inside >> X.org (first blank the screen, then power down the screen). >> >> This is on an Acer Aspire 7738G with this video card: >> (II) Apr 25 20:10:17 NVIDIA(0): NVIDIA GPU GeForce GT 240M (GT216) at >> PCI:1:0:0 (GPU-0) > > =A0 =A0Hmmm... this is part of an issue I need to triage on my two > machines. I have two machines with similar hardware specs: > > Intel W3520 in both > 12GB RAM, same vendor in both > Different nvidia cards; same model -- 9600GT, different memory > amounts, different vendors > Different DVD drives (shouldn't matter) > Different hard drives > An LSI RAID card in one > A snd_emu10kx sound card in the server/workstation. > > =A0 =A0There are a few variables in the mix, but my machines hardlock > from approximately a week usage with sources based off r206031, using > ahci(4) [instead of ata(4) -- I switched over my machines to use > ahci(4) 2 weeks ago], and this particular driver version... I'll > downgrade nvidia-drivers and see what happens. Downgrading nvidia-driver to 195.22 has been pointing a smoking gun at a regression in 195.36.15 with my configuration, as my system has not hung up once since I downgraded both machines, whereas I ruled out the issue by disabling all of the other experimental features I may have been tweaking around with rather quickly (my monkeying around with the power settings and the rtc was causing some variance as well between the two machines). Others have reported similar issues with panics on #bsdports. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?i2h7d6fde3d1005031100ja0ebaa0dl10a8a051d68083d5>