Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754032AbdCBDfF (ORCPT ); Wed, 1 Mar 2017 22:35:05 -0500 Received: from smtp2.it.da.ut.ee ([193.40.5.67]:45495 "EHLO smtp2.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753947AbdCBDfA (ORCPT ); Wed, 1 Mar 2017 22:35:00 -0500 Date: Thu, 2 Mar 2017 00:06:41 +0200 (EET) From: Meelis Roos To: Thomas Gleixner cc: Linux Kernel list , x86@kernel.org, Peter Zijlstra Subject: Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 805 Lines: 19 > > 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@linux.ee)