Re: [patch 0/4] timer/nohz: Fix timer/nohz woes

[Thomas Gleixner]

On Fri, 5 Jan 2018, Paul E. McKenney wrote:
> But after more than 1,000 hours of test runs, split roughly evenly
> among the above three scenarios, there is no statistically significant
> difference in error rate among them.  This means that there is some
> other bug lurking somewhere, and having the same appearance (lost timer).
> Were you guys ever able to reproduce this via rcutorture?

No.

We'll setup more testing on Monday. Which of the tests fails or at least
exposes the highest failure rate?

Thanks,

	tglx