Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jun 2007 21:37:17 +0200
From:      "Diego Depaoli" <trebestie@gmail.com>
To:        current@freebsd.org
Subject:   Re: recent nvidia-driver trouble
Message-ID:  <83e5fb980706151237j6f4b31adjf5399dfd4b9de37a@mail.gmail.com>
In-Reply-To: <20070615203136.402a2df5.garyj@jennejohn.org>
References:  <1181929982.1086.6.camel@worf> <20070615203136.402a2df5.garyj@jennejohn.org>

next in thread | previous in thread | raw e-mail | index | archive | help
2007/6/15, Gary Jennejohn <garyj@jennejohn.org>:
> On Fri, 15 Jun 2007 19:53:02 +0200
> Pascal Hofstee <caelian@gmail.com> wrote:
>
> > Sometime during the last week i have started to encounter trouble with
> > my system locking up trying to switch from X to console, but only when
> > using the nvidia-driver kernel module. Using the plain "nv" driver
> > works without any problems ... When the lock up happens the system
> > seems to no longer respond to keyboard input etc. (haven't been able
> > to confirm wether or not remote access is still possible).
> >
> > Is anybody else experiencing similar problems out there ... this has
> > used to work for months without problems ... i made sure to force a
> > reinstall of the nvidia-driver port on every new kernel install but
> > that just doesn't seem to solve the problem either.
Me too
> >
>
> I've seen this also. It's a panic due to a NULL-pointer dereference
> someplace in the nvidia-driver. I suspect that it's related to the
> recent locking/mutex/whatever changes but can't prove it. All the
> crash dumps which I have are corrupted so I can't do a backtrace :-(
I agree.
This time nvidia-driver and xorg-server rebuild doesn't solve the problem.

-- 
Diego Depaoli



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83e5fb980706151237j6f4b31adjf5399dfd4b9de37a>