From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rolf Eike Beer Subject: Re: 3.12.8 is doing nasty things Date: Thu, 13 Feb 2014 07:37:55 +0100 Message-ID: <8596393.NVJnYl104a@caliban.sf-tec.de> References: <2696873.HIAXvrDslF@caliban.sf-tec.de> <2638727.5eeStlFCSi@caliban.sf-tec.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart25784955.jI7LQO5N9V"; micalg="pgp-sha1"; protocol="application/pgp-signature" To: linux-parisc@vger.kernel.org Return-path: In-Reply-To: <2638727.5eeStlFCSi@caliban.sf-tec.de> List-ID: List-Id: linux-parisc.vger.kernel.org --nextPart25784955.jI7LQO5N9V Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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. Eike --nextPart25784955.jI7LQO5N9V Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEABECAAYFAlL8aEkACgkQXKSJPmm5/E4bmQCcDyXNCgsGNJW1mgfJ7nEBsXdx BN8AoI+pSfxoVeGs/F0m5zDPvvGErd1d =oZRA -----END PGP SIGNATURE----- --nextPart25784955.jI7LQO5N9V--