NVidia driver stability?
bruce at cran.org.uk
Thu Jul 10 18:19:46 PDT 2003
On Thu, Jul 10, 2003 at 04:41:40PM -0700, Evan Dower wrote:
> The new nvidia-driver was unstable for me as well. So much so that I
> deinstalled it so I could get some actual work done. I never was able o get
> any specifics about it, as I don't have a serial console set up, and when
> it crashes it freezes the screen. I can tell you this much though.
> Sometimes when it locked up, I was able to ssh in from another machine, see
> that XFree86 was taking 98-99% of CPU time, kill XFree86, and continue on.
> Other times, I couldn't even ssh in, as the connection hung, so I had to do
> a hard restart. The timing of these crashes was entirely unpredictable.
> I have a GeForce 3 Ti 200 and FreeBSD 5.1-RELENG. I tried with both AGP's.
> Loading nvidia-driver into a debug kernel (INVARIANTS and WITNESS) still
> causes an immediate panic. I don't know how the Nvidia people can do QA on
> this without a debugging kernel. Just poorly I guess. I hope someone finds
> this helpful though I would be shocked if it did. I would be happy
> (ecstatic, actually) to run any experiments someone might be interested in.
I've found the nvidia driver to be very stable, using a new -CURRENT
build and the NVidia agp driver. I've got a GeForce 4200 Go, and the only
thing the nvidia driver doesn't seem to like is changing resolutions - I've
had a few problems including a reboot from that. Unloading the module
panics the kernel, with
possibly freeing with wrong type, but maybe not here.
I can get a backtrace, if anybody's interested.
I also get a few LORs from the driver, which trace back to the sources in
> Many thanks,
> Evan Dower
> Undergraduate, Computer Science
> University of Washington
> >From: "Brian Kincaid" <bmk at geek.com>
> >To: current at freebsd.org
> >Subject: Re: NVidia driver stability?
> >Date: 10 Jul 2003 15:45:41 -0700
> >MIME-Version: 1.0
> >Received: from mx2.freebsd.org ([22.214.171.124]) by
> >mc3-f9.law16.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Thu, 10
> >Jul 2003 15:46:07 -0700
> >Received: from hub.freebsd.org (hub.freebsd.org [126.96.36.199])by
> >mx2.freebsd.org (Postfix) with ESMTPid 1BF42562AC; Thu, 10 Jul 2003
> >15:45:50 -0700 (PDT)(envelope-from owner-freebsd-current at freebsd.org)
> >Received: from hub.freebsd.org (localhost [127.0.0.1])by hub.freebsd.org
> >(Postfix) with ESMTPid AE42737B40B; Thu, 10 Jul 2003 15:45:49 -0700 (PDT)
> >Received: from mx1.FreeBSD.org (mx1.freebsd.org [188.8.131.52])by
> >hub.freebsd.org (Postfix) with ESMTP id 1A39337B401for
> ><current at freebsd.org>; Thu, 10 Jul 2003 15:45:42 -0700 (PDT)
> >Received: from smtp.webbox.com (66.234.quiknet.com [184.108.40.206])by
> >mx1.FreeBSD.org (Postfix) with ESMTP id 87FCE43FD7for
> ><current at freebsd.org>; Thu, 10 Jul 2003 15:45:41 -0700 (PDT)(envelope-from
> >bmk at geek.com)
> >Received: from mdev ([220.127.116.11]) by smtp.webbox.com with
> >MicrosoftSMTPSVC(5.5.1877.197.19); Thu, 10 Jul 2003 15:45:41 -0700
> >X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
> >Delivered-To: freebsd-current at freebsd.org
> >Message-Id: <100703191.56741 at webbox.com>
> >X-BeenThere: freebsd-current at freebsd.org
> >X-Mailman-Version: 2.1.1
> >Precedence: list
> >List-Id: Discussions about the use of
> ><http://lists.freebsd.org/mailman/listinfo/freebsd-current>,<mailto:freebsd-current-request at freebsd.org?subject=unsubscribe>
> >List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
> >List-Post: <mailto:freebsd-current at freebsd.org>
> >List-Help: <mailto:freebsd-current-request at freebsd.org?subject=help>
> ><http://lists.freebsd.org/mailman/listinfo/freebsd-current>,<mailto:freebsd-current-request at freebsd.org?subject=subscribe>
> >Sender: owner-freebsd-current at freebsd.org
> >Errors-To: owner-freebsd-current at freebsd.org
> >Return-Path: owner-freebsd-current at freebsd.org
> >X-OriginalArrivalTime: 10 Jul 2003 22:46:07.0824 (UTC)
> >Yes, I can replicate the behavior you describe upon running glxinfo
> >repeatedly. I have not yet had any trouble with xvinfo. I have
> >also seen a couple of crashes (not repeatable) after running
> >some of the xscreensaver-demo examples and/or some of the GL
> >apps for xscreensaver directly.
> >I am running a freshly built 4.8-STABLE system, plus a GeForce3
> >Ti 200 PCI card and a rebuilt version of the nvidia-driver port.
> >Before I rebuilt the entire system and kernel the nvidia-port
> >driver caused the system to page fault immediately upon starting
> >I reverted to the standard nv driver for a while, then read a
> >couple of messages on one of the freebsd mailing lists about
> >the necessity of rebuilding everything due to a change in proc.h.
> >After the cvsup, rebuild process, the nvidia driver seems to
> >work, except for the problems mentioned above.
> >freebsd-current at freebsd.org mailing list
> >To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current