Bug#800574: backport to sid/stable? (was RE: libc6: lock elision hazard on Intel Broadwell and Skylake)

2015-10-26 Thread Carlos Alberto Lopez Perez
On 23/10/15 22:10, Henrique de Moraes Holschuh wrote: > On Fri, Oct 23, 2015, at 11:13, Carlos Alberto Lopez Perez wrote: >> I was having trouble (crashes with the NVIDIA proprietary driver) on a >> Debian system with an i7-5775C and libc6=2.19-18+deb8u1 (stable) > > This is very very likely to

Bug#800574: backport to sid/stable? (was RE: libc6: lock elision hazard on Intel Broadwell and Skylake)

2015-10-26 Thread Carlos Alberto Lopez Perez
On 26/10/15 20:13, Carlos Alberto Lopez Perez wrote: > On 23/10/15 22:10, Henrique de Moraes Holschuh wrote: >> On Fri, Oct 23, 2015, at 11:13, Carlos Alberto Lopez Perez wrote: >>> I was having trouble (crashes with the NVIDIA proprietary driver) on a >>> Debian system with an i7-5775C and

Bug#800574: backport to sid/stable? (was RE: libc6: lock elision hazard on Intel Broadwell and Skylake)

2015-10-23 Thread Carlos Alberto Lopez Perez
Hi, Thanks for this patch. I was having trouble (crashes with the NVIDIA proprietary driver) on a Debian system with an i7-5775C and libc6=2.19-18+deb8u1 (stable) I tried first to update the Intel microcode with the "unreleased" 0x13 microcode version but it didn't disabled the TSX-NI

Bug#800574: backport to sid/stable? (was RE: libc6: lock elision hazard on Intel Broadwell and Skylake)

2015-10-23 Thread Henrique de Moraes Holschuh
On Fri, Oct 23, 2015, at 11:13, Carlos Alberto Lopez Perez wrote: > I was having trouble (crashes with the NVIDIA proprietary driver) on a > Debian system with an i7-5775C and libc6=2.19-18+deb8u1 (stable) This is very very likely to be braindamage on the NVIDIA driver, though. Are you sure that

Bug#800574: backport to sid/stable? (was RE: libc6: lock elision hazard on Intel Broadwell and Skylake)

2015-10-23 Thread Aurelien Jarno
On 2015-10-23 18:10, Henrique de Moraes Holschuh wrote: > On Fri, Oct 23, 2015, at 11:13, Carlos Alberto Lopez Perez wrote: > > > Should this patch be backported both to stable and unstable? > > It needs to go to stable sooner than later, yes. But it seems wise to > let it cook in