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:
signature.asc
Description: This is a digitally signed message part.
