mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jack F Vogel <jfv@bluesong.net>, Andi Kleen <ak@muc.de>,
	notting@redhat.com
Subject: Re: [PATCH] check nmi watchdog is broken
Date: Wed, 11 May 2005 13:33:49 +0200	[thread overview]
Message-ID: <17025.60829.58835.194099@alkaid.it.uu.se> (raw)
In-Reply-To: <20050511055540.GA27052@redhat.com>

Dave Jones writes:
 > My EM64T Dell Precision 470 seems to have problems both before
 > and after this change, though the behaviour changes.
 > 
 > With -rc3..
 > testing NMI watchdog ... CPU#1: NMI appears to be stuck (0)!
 > 
 > With -rc4...
 > Testing NMI watchdog ... CPU#4: NMI appears to be stuck (0)!
 > 
 > The CPU #'s are consistent across reboots (Ie, they're always the same).
 > Though the rc4 behaviour seems odd, as my CPUs are numbered 0-3.

There is known breakage in x86-64's nmi watchdog recently.
One of the problems is that the checking code inspects
all possible CPU numbers [0..NR_CPUS[ and not just the
ones actually present, which leads to false failure reports.

 > Bill (Cc'd) also reports that with -rc4, he sees around
 > a 10 second delay when it does that 'Testing NMI watchdog'
 > message.

And that's another of the known x86-64 breakages.

/Mikael

      reply	other threads:[~2005-05-11 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200505011704.j41H4SUQ021132@hera.kernel.org>
2005-05-11  5:55 ` Dave Jones
2005-05-11 11:33   ` Mikael Pettersson [this message]

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=17025.60829.58835.194099@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=ak@muc.de \
    --cc=davej@redhat.com \
    --cc=jfv@bluesong.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=notting@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®