Am Mittwoch 26 Februar 2014, 11:00:01 schrieben Sie: > On 2/26/2014 9:26 AM, Helge Deller wrote: >>>> After 2,5 days with 3.13.2 and 0576da2c08e3d332f1b0653030d28ab804585ab6 >>>> I have not yet seen a single random segfault. > >> > >> A short update on this: I am still running on that kernel and have not > >> seen a single random process crash since then. I'm willing to help in > >> debugging this if anyone tells me how, but I will now just revert that > >> patch from every new kernel to get a stable machine. > > > > On a debian-kernel linux-image-3.13-1-parisc64-smp (3.13.4-1) and the > > latest libc6 which Dave uploaded, I'm now seeing similiar issues which > > are most likely related: > > > > lsXX:~# dpkg-reconfigure locales > > Generating locales (this might take a while)... > > > > de_DE.ISO-8859-1...cannot map archive header: Invalid argument > > In my opinion, this is a glibc bug. The issue has been discussed before. > > I'm not seeing random segvs with 3.13.2 and later in general use. I > haven't reverted anything. > > The only random program failures that I see are thread related. There > are a bunch of failures > in the glibc testsuite, but these are not new. There was a message on > the console this morning about > reaching maximum lock depth 1024. This was probably from glibc > testsuite. There is a known > issue with locking in glib2.0 which sometimes causes dot to segv. > > If you are testing programs that use threads intensively, then I could > see that you might see problems. > > A TLS bug affecting thread local variables was recently fixed in gcc-4.8. I don't think this is the problem that I'm seeing. What crashed was things like make or ld which don't care for threads. Eike
Attachment:
signature.asc
Description: This is a digitally signed message part.
