On Tue, Jan 30, 2018 at 10:03:17PM +0100, Thomas Gleixner wrote:
> On Mon, 29 Jan 2018, Paul E. McKenney wrote:
>
> > On Mon, Jan 29, 2018 at 01:57:38AM -0800, Paul E. McKenney wrote:
> > > On Mon, Jan 29, 2018 at 09:20:48AM +0100, Sebastian Sewior wrote:
> > > > On 2018-01-26 14:09:17 [-0800], Paul E. McKenney wrote:
> > > > > find this one. ;-) But it did pass rcutorture testing for a great
> > > > > many
> > > > > years, didn't it? :-/
> > > >
> > > > It started to trigger better (or at all) on our test box with
> > > > modprobe kvm_intel preemption_timer=n
> > > >
> > > > on the host kernel so maybe a completely unrelated change helped to
> > > > trigger this.
> > >
> > > Good point!
> > >
> > > And testing continues, currently at 108 hours of TREE01 without any
> > > waylayed timers, so looking good! ;-)
> > >
> > > Just kicked off another 70 hours worth.
> >
> > And those completed without incident for a total of 178 hours. I believe
> > we can call this one fixed. Thank you all!!!
> >
> > One question... Is the patch shown below needed, or is this just yet
> > another case of me being confused? (The lack of it is not triggering,
> > but...)
>
> See commit 26456f87aca7
Got it, thank you! I will remove my patch from my queue.
Thanx, Paul
