All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
Date: Wed, 1 Mar 2017 18:07:11 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1703011801420.4005@nanos> (raw)
In-Reply-To: <alpine.LRH.2.20.1703011719350.22226@math.ut.ee>

On Wed, 1 Mar 2017, Meelis Roos wrote:

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

Thanks,

	tglx

  reply	other threads:[~2017-03-01 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 15:28 PPro arch_cpu_idle: NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Meelis Roos
2017-03-01 17:07 ` Thomas Gleixner [this message]
2017-03-01 20:47   ` Meelis Roos
2017-03-01 22:06   ` Meelis Roos
2017-03-01 22:34     ` Thomas Gleixner
2017-03-02 16:11       ` Thomas Gleixner
2017-03-02 19:40         ` Meelis Roos
2017-03-03 10:56         ` Thomas Gleixner
2017-03-03 10:58           ` Meelis Roos
2017-03-05 20:48           ` Meelis Roos
2017-03-05 23:19             ` Frederic Weisbecker
2017-03-06 11:42               ` Meelis Roos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1703011801420.4005@nanos \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.