On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> On Tue, 3 Oct 2017, Thomas Gleixner wrote:
> > On Tue, 3 Oct 2017, Michael Ellerman wrote:
> > > Hmm, I tried that patch, it makes the warning go away. But then I
> > > triggered a deliberate hard lockup and got nothing.
> > >
> > > Then I went back to the existing code (in linux-next), and I still get
> > > no warning from a deliberate hard lockup.
> > >
> > > So seems there may be some more gremlins. Will test more in the morning.
> >
> > Hrm. That's weird. I'll have a look and send a proper patch series on top
> > of next.
>
> The major difference is that the reworked code utilizes
> watchdog_nmi_reconfigure() for both init and the sysctl updates, but I
> can't for my life figure out why that doesn't work.
I collected the changes which Linus requested along with the nmi_probe()
one and pushed them into:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/urgent
That's based on 4.13 final so it neither contains 4.14 nor -next material.
Thanks,
tglx
