On Thu, 24 Apr 2014, David Rientjes wrote: > > Well, if you have dmesg dump from panic that happens every other year, and > > you have to do post-mortem analysis on it, I am pretty sure you would love > > to be able to figure out how the stack traces would look like without > > inter-CPU interleaving. And I am pretty sure you wouldn't want to > > insert/enable a tracepoint and wait another two years for the bug to > > trigger again. > > Sounds like the appropriate fix would be to serialize stack dumping to the > kernel log.
That's rather difficult, as it can be done both from NMI and non-NMI contexts, and those are very hard to synchronize. -- Jiri Kosina SUSE Labs -- 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/
