public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 25 Jan 2014 23:40:06 +0100	[thread overview]
Message-ID: <38632185.Uo4SvuvNmB@caliban.sf-tec.de> (raw)
In-Reply-To: <1390689039.2275.52.camel@dabdike.int.hansenpartnership.com>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

Am Samstag, 25. Januar 2014, 14:30:39 schrieben Sie:
> On Fri, 2014-01-24 at 22:26 +0100, Guy Martin wrote:
> > 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.
> 
> This all sounds like a flushing problem.  I can't confirm with my
> pa8800 ... but that could be because the additional pa8800 flushes are
> masking the problem.  Could you try bisecting the parisc commits
> between .4 and .5 and see if there's a particular cause?

It's the one mmap fix, I see .5 being stable after reverting that fix.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-01-25 22:40 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 [this message]
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=38632185.Uo4SvuvNmB@caliban.sf-tec.de \
    --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