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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.20.1703020006260.1113@math.ut.ee>
Date:   Thu, 2 Mar 2017 00:06:41 +0200 (EET)
From:   Meelis Roos <mroos@...ux.ee>
To:     Thomas Gleixner <tglx@...utronix.de>
cc:     Linux Kernel list <linux-kernel@...r.kernel.org>, x86@...nel.org,
        Peter Zijlstra <peterz@...radead.org>
Subject: Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP
 on cpu 1

> > 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.

-- 
Meelis Roos (mroos@...ux.ee)