From: Andi Kleen <ak@linux.intel.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: kan.liang@intel.com, linux-kernel@vger.kernel.org,
dzickus@redhat.com, mingo@kernel.org, akpm@linux-foundation.org,
babu.moger@oracle.com, atomlin@redhat.com,
torvalds@linux-foundation.org, peterz@infradead.org,
tglx@linutronix.de, eranian@google.com, acme@redhat.com,
stable@vger.kernel.org
Subject: Re: [PATCH] kernel/watchdog: fix spurious hard lockups
Date: Tue, 20 Jun 2017 16:00:02 -0700 [thread overview]
Message-ID: <20170620230002.GE23705@tassilo.jf.intel.com> (raw)
In-Reply-To: <4718a252-9515-626e-a69f-565f1c2bc589@redhat.com>
On Tue, Jun 20, 2017 at 06:34:23PM -0400, Prarit Bhargava wrote:
>
>
> On 06/20/2017 05:33 PM, kan.liang@intel.com wrote:
> > From: Kan Liang <Kan.liang@intel.com>
> >
> > Some users reported spurious NMI watchdog timeouts.
> >
> > We now have more and more systems where the Turbo range is wide enough
> > that the NMI watchdog expires faster than the soft watchdog timer that
> > updates the interrupt tick the NMI watchdog relies on.
> >
>
> Hmm ... odd that I haven't seen this. We're running a pretty wide
> variety of systems here. Do you have a reproducer? I'd like to see
> this occur on production HW.
It only happens on a few specific CPU SKUs with a very wide Turbo range.
Reproducer is typically some stress workload that turbos very high.
-Andi
next prev parent reply other threads:[~2017-06-20 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 21:33 [PATCH] kernel/watchdog: fix spurious hard lockups kan.liang
2017-06-20 22:03 ` Andrew Morton
2017-06-21 12:40 ` Liang, Kan
2017-06-21 13:47 ` Don Zickus
2017-06-21 14:10 ` Liang, Kan
2017-06-20 22:34 ` Prarit Bhargava
2017-06-20 23:00 ` Andi Kleen [this message]
2017-06-21 0:12 ` Prarit Bhargava
2017-06-21 21:02 ` Marc Herbert
2017-06-21 13:40 ` Don Zickus
2017-06-21 14:02 ` Liang, Kan
2017-06-28 11:40 ` Michal Hocko
2017-06-28 13:24 ` Liang, Kan
2017-06-28 14:29 ` Michal Hocko
2017-06-28 14:32 ` Liang, Kan
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=20170620230002.GE23705@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=babu.moger@oracle.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.