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
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a change to branch sid
in repository glibc.
from fd76a49 hurd: Restore march version _pthread_spin_lock
new ee6ffab debian/patches/git-updates.diff: update from upstream
stable branch:
The 1 rev
Processing commands for cont...@bugs.debian.org:
> tag 841304 pending
Bug #841304 [glibc] invalid code in glibc tests
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
841304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841304
Debian Bug T
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a commit to branch sid
in repository glibc.
commit ee6ffabef0baa307624c273367706d1bc261770e
Author: Aurelien Jarno
Date: Sun Nov 6 22:08:07 2016 +0100
debian/patches/git-updates.diff: update from upstream st
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)
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
[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 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.
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a commit to branch wheezy
in repository tzdata.
commit eb649b86267bdbfc03e37fc86b8c34e05dcc7203
Author: Emilio Pozuelo Monfort
Date: Sun Nov 6 11:11:17 2016 +0100
New upstream version
New upstream v
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a commit to branch wheezy
in repository tzdata.
commit 4b55a9ab023aaa129bcbfb0e47e0773b19dfe02b
Author: Emilio Pozuelo Monfort
Date: Sun Nov 6 11:12:30 2016 +0100
Release to wheezy-security
---
debian/chang
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a change to branch wheezy
in repository tzdata.
from 71c268e Release to wheezy-security
new eb649b8 New upstream version
new 514d42f Update templates and translations.
new 4b55a9
This is an automated email from the git hooks/post-receive script.
aurel32 pushed a commit to branch wheezy
in repository tzdata.
commit 514d42f50d22fcfd7c9fa3d962cfebe1093aa303
Author: Aurelien Jarno
Date: Sat Nov 5 23:44:36 2016 +0100
Update templates and translations.
---
debian/chang
This is an automated email from the git hooks/post-receive script.
sthibault pushed a change to branch sid
in repository glibc.
from a5a376f hurd: Drop spurious pthread_spin_lock aliases
new fd76a49 hurd: Restore march version _pthread_spin_lock
The 1 revisions listed above as
This is an automated email from the git hooks/post-receive script.
sthibault pushed a commit to branch sid
in repository glibc.
commit fd76a49313eb7dbe51a86304e067be5913c0b190
Author: Samuel Thibault
Date: Sun Nov 6 13:39:07 2016 +0100
hurd: Restore march version _pthread_spin_lock
[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
19 matches
Mail list logo
