Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1

From	Meelis Roos <mroos@linux.ee>
Newsgroups	linux.kernel
Subject	Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
Date	2017-03-03 02:40 +0100
Message-ID	<tgKml-2cx-7@gated-at.bofh.it> (permalink)
References	<tgfiy-5AK-11@gated-at.bofh.it> <tgfVg-65H-17@gated-at.bofh.it> <tgnSN-3ew-11@gated-at.bofh.it> <tgnSN-3ew-9@gated-at.bofh.it> <tgDkR-63W-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

> > > > > This is on my trusty IBM PC365, dual Pentium Pro. 4.10 worked fine, 
> > > > > 4.10.0-09686-g9e314890292c and 4.10.0-10770-g2d6be4abf514 exhibit a 
> > > > > problem. Ocassionally NMI watchdog kicks in and discovers one of the 
> > > > > CPUs in LOCKUP. The system keeps running fine. The first lockup was 
> > > > > different, all the others were from arch_cpu_idle. Sometime ecey couple 
> > > > > of seconds (after some activity), sometimes nothing for a long time 
> > > > > (idle, no SSH logins).
> > > > 
> > > > The only watchdog related patch which hit after 4.10 is:
> > > > 
> > > >  8dcde9def5a1 kernel/watchdog.c: do not hardcode CPU 0 as the initial thread
> > > > 
> > > > Can you try to revert that for a start? I'm not seeing why it should be the
> > > > culprit from a quick glance, but ...
> > > 
> > > Reverting this patch does not help.
> > 
> > I did not expect that, but excluding it was a valid shot in the
> > dark. Thanmks for trying.
> > 
> > To be honest, I have no idea what causes that at the moment, but I will
> > come back to you tomorrow after thinking it through (with brain awake) how
> > to debug this.
> 
> Went through the related changes which came in during the merge window. One
> which affects the per cpu timers is: 914122c389d0
> 
> Can you try to revert that one please?

Reverted, no effect.

-- 
Meelis Roos (mroos@linux.ee)

Thread

Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Thomas Gleixner <tglx@linutronix.de> - 2017-03-01 18:10 +0100
  Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Thomas Gleixner <tglx@linutronix.de> - 2017-03-02 02:40 +0100
    Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Thomas Gleixner <tglx@linutronix.de> - 2017-03-02 19:10 +0100
      Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Meelis Roos <mroos@linux.ee> - 2017-03-03 02:40 +0100
      Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Meelis Roos <mroos@linux.ee> - 2017-03-03 12:00 +0100
      Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Thomas Gleixner <tglx@linutronix.de> - 2017-03-03 14:10 +0100
        Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Meelis Roos <mroos@linux.ee> - 2017-03-05 21:50 +0100
          Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Frederic Weisbecker <fweisbec@gmail.com> - 2017-03-06 00:30 +0100
            Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Meelis Roos <mroos@linux.ee> - 2017-03-06 12:50 +0100
  Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP  on cpu 1 Meelis Roos <mroos@linux.ee> - 2017-03-02 04:40 +0100

csiph-web