Am Sonntag, den 06.11.2016, 01:12 -0200 schrieb Henrique de Moraes
Holschuh:
>
>
>
> Unfortunately, when hardware lock elision support was added to glibc
> upstream, libpthreads was *not* changed to properly assert() this
> forbidden condition on the non-hardware-elision codepaths. Such an
> as
On 12/11/16 at 18:51 -0200, Henrique de Moraes Holschuh wrote:
> Lucas,
>
> Thanks for trying a build run with TSX enabled.
>
> On Sat, 12 Nov 2016, Lucas Nussbaum wrote:
> > I did an archive rebuild on Amazon EC2 using m4.16xlarge instances, that
> > use a CPU with TSX enabled.
>
> What microco
Lucas,
Thanks for trying a build run with TSX enabled.
On Sat, 12 Nov 2016, Lucas Nussbaum wrote:
> I did an archive rebuild on Amazon EC2 using m4.16xlarge instances, that
> use a CPU with TSX enabled.
What microcode revision is that Xeon E5-2686 running?
> I've filed bugs for the packages tha
On 07/11/16 at 21:52 +0100, Lucas Nussbaum wrote:
> Hi,
>
> On 06/11/16 at 17:41 -0200, Henrique de Moraes Holschuh wrote:
> > On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > > It's worth noting that TSX is broken in 'Haswell' processors and is
> > > supposed to be disabled via a microcode update.
On Mon, 07 Nov 2016, Lucas Nussbaum wrote:
> On 06/11/16 at 17:41 -0200, Henrique de Moraes Holschuh wrote:
> > On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > > It's worth noting that TSX is broken in 'Haswell' processors and is
> > > supposed to be disabled via a microcode update. I don't know whe
On 07/11/16 at 21:52 +0100, Lucas Nussbaum wrote:
> Hi,
>
> On 06/11/16 at 17:41 -0200, Henrique de Moraes Holschuh wrote:
> > On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > > It's worth noting that TSX is broken in 'Haswell' processors and is
> > > supposed to be disabled via a microcode update.
Hi,
On 06/11/16 at 17:41 -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > It's worth noting that TSX is broken in 'Haswell' processors and is
> > supposed to be disabled via a microcode update. I don't know whether
> > glibc avoids using it on these proces
On Sun, 06 Nov 2016, Adrian Bunk wrote:
> On Sun, Nov 06, 2016 at 05:41:34PM -0200, Henrique de Moraes Holschuh wrote:
> > On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > > It's worth noting that TSX is broken in 'Haswell' processors and is
> > > supposed to be disabled via a microcode update. I don
On Sun, Nov 06, 2016 at 08:04:39AM +0100, Petter Reinholdtsen wrote:
> [Henrique de Moraes Holschuh]
> > And what should we do about Debian stretch, then?
>
> I believe a good start would be to add an assert() in a test version of
> glibc and then run all the autopkgtest scripts on the packages in
On 2016-11-06 01:12, Henrique de Moraes Holschuh wrote:
> On Sat, 05 Nov 2016, Ian Jackson wrote:
> > Looking at the code, I think that gs in jessie is plainly violating
> > the rules about the use of pthread locks. On my partner's machine,
>
> Per logs from message #15 on bug #842796:
> https://
[Jeff Epler]
> I believe that similar bugs have been afflicting hurd and kfreebsd
> debian ports for some time. In retrospect, it's too bad these reports
> weren't given more attention, because it could have made things better
> for Linux platforms as well. :-/
Yeah, too bad. :/
On the other ha
On Sun, Nov 06, 2016 at 05:41:34PM -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 06 Nov 2016, Ben Hutchings wrote:
> > It's worth noting that TSX is broken in 'Haswell' processors and is
> > supposed to be disabled via a microcode update. I don't know whether
> > glibc avoids using it on the
Henrique de Moraes Holschuh writes ("Re: libc recently more aggressive about
pthread locks in stable ?"):
> Per logs from message #15 on bug #842796:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842796#15
>
> SIGSEGV on __lll_unlock_elision is a signature (IME with very high
> confidence)
[resending with correct Cc:]
I believe that similar bugs have been afflicting hurd and kfreebsd debian ports
for some time. In retrospect, it's too bad these reports weren't given more
attention, because it could have made things better for Linux platforms as well.
:-/
see e.g.,
https://bugs.deb
On Sun, 06 Nov 2016, Ben Hutchings wrote:
> It's worth noting that TSX is broken in 'Haswell' processors and is
> supposed to be disabled via a microcode update. I don't know whether
> glibc avoids using it on these processors if the microcode update is
> not applied. (Linux doesn't appear to hid
On Sat, 2016-11-05 at 20:32 +0100, Christian Seiler wrote:
> On 11/05/2016 08:13 PM, Ian Jackson wrote:
> > I have just been debugging a ghostscript segfault on jessie amd64.
> >
> > Looking at the code, I think that gs in jessie is plainly violating
> > the rules about the use of pthread locks.
[Henrique de Moraes Holschuh]
> And what should we do about Debian stretch, then?
I believe a good start would be to add an assert() in a test version of
glibc and then run all the autopkgtest scripts on the packages in the
archive to see how widespread the problem is. It will not cover all
packa
On Sat, 05 Nov 2016, Ian Jackson wrote:
> Looking at the code, I think that gs in jessie is plainly violating
> the rules about the use of pthread locks. On my partner's machine,
Per logs from message #15 on bug #842796:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842796#15
SIGSEGV on __ll
On 2016-11-05 19:13, Ian Jackson wrote:
> I have just been debugging a ghostscript segfault on jessie amd64.
>
> Looking at the code, I think that gs in jessie is plainly violating
> the rules about the use of pthread locks. On my partner's machine,
> this makes it segfault on termination (with s
On 11/05/2016 08:13 PM, Ian Jackson wrote:
> I have just been debugging a ghostscript segfault on jessie amd64.
>
> Looking at the code, I think that gs in jessie is plainly violating
> the rules about the use of pthread locks. On my partner's machine,
> this makes it segfault on termination (wit
I have just been debugging a ghostscript segfault on jessie amd64.
Looking at the code, I think that gs in jessie is plainly violating
the rules about the use of pthread locks. On my partner's machine,
this makes it segfault on termination (with some input files, at
least). On my machine it work
21 matches
Mail list logo
