From: Guy Martin <gmsoft@tuxicoman.be>
To: Jeroen Roovers <jer@gentoo.org>, Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: 3.12.8 is doing nasty things
Date: Fri, 24 Jan 2014 22:26:15 +0100 [thread overview]
Message-ID: <20140124222615.66cb0d2a@borg.lux.tuxicoman.be> (raw)
In-Reply-To: <20140124220723.5985ac4e@marga.jer-c2.orkz.net>
On Fri, 24 Jan 2014 22:07:23 +0100
Jeroen Roovers <jer@gentoo.org> wrote:
> On Fri, 24 Jan 2014 21:44:51 +0100
> Rolf Eike Beer <eike-kernel@sf-tec.de> wrote:
>
> > I reported that I saw strange things happening after upgrading to
> > 3.12.5. Meanwhile I upgraded to 3.12.8 and things became worse. I
> > regularly see processes to fail randomly. I can see this as I
> > somethimes get failures in my nagios because the SSH connection to
> > the watched host (only the watched one runs .8) fails.
>
> Confirmed with any kernel above 3.12.2 that I cared to test (I didn't
> test 3.12.3). The issues vary from illegal instructions to
> segmentation faults to double frees in userland, so it's basically a
> "random" thing. I can't say it's become "worse" after 3.12.5 (since I
> haven't kept per version statistics).
Same here, 3.12.5 was not behaving correctly and 3.12.8 was even worse.
With the later, I also experienced sshd segfault, python threading
segfault/hangs.
I quickly reverted to 3.12.4 which is far more stable.
Guy
next prev parent reply other threads:[~2014-01-24 21:26 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 [this message]
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
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=20140124222615.66cb0d2a@borg.lux.tuxicoman.be \
--to=gmsoft@tuxicoman.be \
--cc=eike-kernel@sf-tec.de \
--cc=jer@gentoo.org \
--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