On Mon, 2014-07-07 at 18:41 -0700, dormando wrote:

Mostly there, but I think we hit what might be a new bug.. The machines
which crashed every few days previously have been stable for weeks.

however I had one machine running the new kernel in a larger cluster
elsewhere; we had a network event and the one machine on the new kernel
panic'ed in ipv4_dst_destroy, but what looks like a new path. Sadly I've
had to halt the rollout :( All of the older unfixed kernels survived this
particular network event.

Unfortunately this is still on 3.10, due to a bad softirq regression in
3.14 I've not had time to track down. I applied all of your patches for
what wasn't already in 3.10. The only other change I made was to un-revert
62713c4b6bc10c2d082ee1540e11b01a2b2162ab - which I'd been keeping reverted
as it was making crashes much more frequent.

Hmm, always give patch title or a valid sha1 commit, this one is not in
David trees, so its hard to tell.