From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: Re: 3.12.8 is doing nasty things
Date: Wed, 26 Feb 2014 17:06:28 +0100 [thread overview]
Message-ID: <1708632.M6uBEiBPM4@eto> (raw)
In-Reply-To: <BLU0-SMTP13B63E01B4FA0E673CD81997800@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
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 #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-26 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 20:44 3.12.8 is doing nasty things Rolf Eike Beer
2014-01-24 21:07 ` Jeroen Roovers
2014-01-24 21:26 ` Guy Martin
2014-01-25 22:30 ` James Bottomley
2014-01-25 22:40 ` Rolf Eike Beer
2014-02-11 15:30 ` Rolf Eike Beer
2014-02-13 6:37 ` Rolf Eike Beer
2014-02-15 7:47 ` Rolf Eike Beer
2014-02-25 17:13 ` Rolf Eike Beer
2014-02-26 14:26 ` Aw: " Helge Deller
2014-02-26 16:00 ` John David Anglin
2014-02-26 16:06 ` Rolf Eike Beer [this message]
2014-02-26 19:20 ` Jeroen Roovers
2014-02-26 19:33 ` John David Anglin
2014-02-26 19:32 ` Aaro Koskinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1708632.M6uBEiBPM4@eto \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox