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: Tue, 25 Feb 2014 18:13:32 +0100	[thread overview]
Message-ID: <5116135.sX67MB4Kjr@caliban.sf-tec.de> (raw)
In-Reply-To: <1712740.zFjPFKGkFe@caliban.sf-tec.de>

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

Am Samstag, 15. Februar 2014, 08:47:06 schrieb Rolf Eike Beer:
> Am Donnerstag, 13. Februar 2014, 07:37:55 schrieb Rolf Eike Beer:
> > Am Dienstag, 11. Februar 2014, 16:30:08 schrieb Rolf Eike Beer:
> > > > Next week I'll try 3.13, but since it has the same changes I expect
> > > > the
> > > > same results.
> > > 
> > > I'm now on 3.13.2 and things are similar. While I did an initial test
> > > with
> > > 100 invocations of ssh which went flawlessly I now see random process
> > > errors again. Examples can be found here:
> > > http://my.cdash.org/index.php?project=Qsmtp&date=2014-02-11
> > > 
> > > Normally the reports should have arrived much earlier, but for an
> > > unknown
> > > reason the resolv.conf (generated by DHCP) was empty, I assume that the
> > > DHCP process has failed during while renewing the IP address. The
> > > segfaults during the build have not happened with the older kernel.
> > 
> > I can now confirm that the cache coherency fixes are _not_ the reason for
> > those failures I see. I have rebuild 3.13.2 without them and still see
> > random segfaults in my dashboards. I'll try the mmap() patch next.
> 
> 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.

Greetings,

Eike

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

  reply	other threads:[~2014-02-25 17:13 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 [this message]
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=5116135.sX67MB4Kjr@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