From: Keith Owens <kaos@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de, "Brendan Trotter" <btrotter@gmail.com>
Subject: Re: NMI problems with Dell SMP Xeons
Date: Wed, 07 Jun 2006 14:49:11 +1000 [thread overview]
Message-ID: <6143.1149655751@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 23 May 2006 15:03:39 +1000." <8303.1148360619@kao2.melbourne.sgi.com>
Following a suggestion by Brendan Trotter, I ran some more tests to
track down the problem with sending NMI IPI on Dell Xeons.
BIOS Logical OS ACPI Cpus IPI 2 NMI IPI
Processor BIOS OS (APIC_DM_NMI)
Enabled Enabled 4 4 Not delivered Delivered as NMI
Enabled Disabled 4 2 Machine reset Machine reset
Disabled Enabled 2 2 Not delivered Delivered as NMI
Disabled Disabled 2 2 Not delivered Delivered as NMI
So the killer combination with this motherboard is when the BIOS knows
about logical processors but the OS does not. Sending IPI 2 or NMI IPI
with that combination kills the machine. Brendan suggested that the
BIOS is seeing the broadcast NMI on the logical processors which are
not under OS control and that the BIOS cannot cope.
Should we change the x86_64 send_IPI_allbutself() so it is only
delivered to cpus that the OS knows about, instead of doing a general
broadcast. That would prevent offline or hidden cpus being sent an
interrupt that they are not expecting. The failing case is
__send_IPI_shortcut, with a cfg of 0xc0c00.
next prev parent reply other threads:[~2006-06-07 4:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 9:08 NMI problems with Dell SMP Xeons Keith Owens
2006-05-22 23:56 ` Andi Kleen
2006-05-23 1:26 ` Keith Owens
2006-05-23 1:55 ` Andi Kleen
2006-05-23 2:02 ` Keith Owens
2006-05-23 2:21 ` Keith Owens
2006-05-23 5:03 ` Keith Owens
2006-06-07 4:49 ` Keith Owens [this message]
2006-06-07 7:20 ` Andi Kleen
2006-06-07 7:43 ` Keith Owens
2006-06-07 8:01 ` Andi Kleen
2006-06-07 11:47 ` Keith Owens
2006-06-07 12:13 ` Andi Kleen
2006-06-07 15:18 ` Brendan Trotter
2006-06-07 15:23 ` Andi Kleen
2006-06-07 18:47 ` Rajesh Shah
2006-06-08 0:41 ` Rajesh Shah
2006-06-08 0:46 ` Rajesh Shah
2006-06-08 5:11 ` Keith Owens
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=6143.1149655751@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=ak@suse.de \
--cc=btrotter@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox