Bug#809324: Same issue here

2016-01-14 Thread Luca Boccassi
On 14 January 2016 at 22:38, Andreas Beckmann wrote: > On 2016-01-12 23:43, Luca Boccassi wrote: >> Andreas, what do you think we should do? I've committed a patch to SVN >> (tested that the module builds on x86 and x86_64 on 3.16, 4.2, 4.3 and >> 4.4, but I don't have hardware to do anything beyo

Bug#809324: Same issue here

2016-01-14 Thread Andreas Beckmann
On 2016-01-12 23:43, Luca Boccassi wrote: > Andreas, what do you think we should do? I've committed a patch to SVN > (tested that the module builds on x86 and x86_64 on 3.16, 4.2, 4.3 and > 4.4, but I don't have hardware to do anything beyond that > unfortunately). Hopefully the next upstream patch

Bug#809324: Same issue here

2016-01-12 Thread Luca Boccassi
On Sun, 2016-01-10 at 16:23 +, Luca Boccassi wrote: > On Tue, 5 Jan 2016 12:15:03 +0100 Arturo Borrero Gonzalez > wrote: > > Hi, > > > > I'm suffering the same issue here. > > > > best regards. > > Hi, > > Unfortunately there might not be much we can do until Nvidia releases a fix. > > The

Bug#809324: Same issue here

2016-01-10 Thread Luca Boccassi
On Tue, 5 Jan 2016 12:15:03 +0100 Arturo Borrero Gonzalez wrote: > Hi, > > I'm suffering the same issue here. > > best regards. Hi, Unfortunately there might not be much we can do until Nvidia releases a fix. The kernel module in 304 (but not in more recent releases) is using a kernel API that

Bug#809324: Same issue here

2016-01-05 Thread Arturo Borrero Gonzalez
Hi, I'm suffering the same issue here. best regards. -- Arturo Borrero González