On Saturday 17 July 2010 17:25:27 Christian Zander wrote:
> On Sat, Jul 17, 2010 at 07:24:54AM -0700, David Naylor wrote:
> (...)
>
> > > >>> These freezes and panics are due to the driver using a spin mutex
> > > >>> instead of a
> > > >>> regular mutex for the per-file descriptor event_mtx. If
On Sunday 11 July 2010 22:14:44 Doug Barton wrote:
> On 07/08/10 14:52, Rene Ladan wrote:
> > On 08-07-2010 22:09, Doug Barton wrote:
> >> On Thu, 8 Jul 2010, John Baldwin wrote:
> >>> These freezes and panics are due to the driver using a spin mutex
> >>> instead of a
> >>> regular mutex for the p
On 07/08/10 14:52, Rene Ladan wrote:
> On 08-07-2010 22:09, Doug Barton wrote:
>> On Thu, 8 Jul 2010, John Baldwin wrote:
>>
>>> These freezes and panics are due to the driver using a spin mutex
>>> instead of a
>>> regular mutex for the per-file descriptor event_mtx. If you patch the
>>> driver
>
On Thursday, July 08, 2010 5:52:10 pm Rene Ladan wrote:
> On 08-07-2010 22:09, Doug Barton wrote:
> > On Thu, 8 Jul 2010, John Baldwin wrote:
> >
> >> These freezes and panics are due to the driver using a spin mutex
> >> instead of a
> >> regular mutex for the per-file descriptor event_mtx. If y
On 08-07-2010 22:09, Doug Barton wrote:
> On Thu, 8 Jul 2010, John Baldwin wrote:
>
>> These freezes and panics are due to the driver using a spin mutex
>> instead of a
>> regular mutex for the per-file descriptor event_mtx. If you patch the
>> driver
>> to change it to be a regular mutex I think
On Thu, 8 Jul 2010, John Baldwin wrote:
These freezes and panics are due to the driver using a spin mutex instead of a
regular mutex for the per-file descriptor event_mtx. If you patch the driver
to change it to be a regular mutex I think that should fix the problems.
Can you give an example?
On Friday, July 02, 2010 12:55:38 pm David Naylor wrote:
> On Friday 02 July 2010 14:57:35 René Ladan wrote:
> > 2010/7/2 Yuri Pankov :
> > > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote:
> > >> Hi,
> > >>
> > >> I'm not sure this has been reported before but I am experience crashe
On Friday 02 July 2010 14:57:35 René Ladan wrote:
> 2010/7/2 Yuri Pankov :
> > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote:
> >> Hi,
> >>
> >> I'm not sure this has been reported before but I am experience crashes
> >> with nvidia-driver on -current (cvsup ~day ago).
> >>
> >> If
On Fri, Jul 02, 2010 at 02:57:35PM +0200, René Ladan wrote:
> 2010/7/2 Yuri Pankov :
> > On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote:
> >> Hi,
> >>
> >> I'm not sure this has been reported before but I am experience crashes with
> >> nvidia-driver on -current (cvsup ~day ago).
> >>
2010/7/2 Yuri Pankov :
> On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote:
>> Hi,
>>
>> I'm not sure this has been reported before but I am experience crashes with
>> nvidia-driver on -current (cvsup ~day ago).
>>
>> If I remove all the debugging options from the kernel config then it i
On Fri, Jul 02, 2010 at 11:46:41AM +0200, David Naylor wrote:
> Hi,
>
> I'm not sure this has been reported before but I am experience crashes with
> nvidia-driver on -current (cvsup ~day ago).
>
> If I remove all the debugging options from the kernel config then it is very
> usable.
>
> H
Hi,
I'm not sure this has been reported before but I am experience crashes with
nvidia-driver on -current (cvsup ~day ago).
If I remove all the debugging options from the kernel config then it is very
usable.
Here are the backtraces from two nvidia-driver versions:
nvidia-driver-195.36.15
12 matches
Mail list logo
