On Tue, Nov 26, 2013 at 03:31:06PM +1100, NeilBrown wrote: > The stack trace in the previous email seemed to suggest that a process was > blocking inside a wake_up call, but it wasn't at all conclusive. And I've > seen a few wake_ups in other stack traces which seem to be connected with > other deadlock. Probably some sort of co-incidence.
It appears stuck in some paravirt clock layer.. or just a lucky hit. I never run on (para)virt if I can help it, so I'm not much help there. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
