On Fri, 2014-01-24 at 22:26 +0100, Guy Martin wrote: > On Fri, 24 Jan 2014 22:07:23 +0100 > Jeroen Roovers <jer@xxxxxxxxxx> wrote: > > > On Fri, 24 Jan 2014 21:44:51 +0100 > > Rolf Eike Beer <eike-kernel@xxxxxxxxx> 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? Thanks, James -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
