From: Keith Owens <kaos@sgi.com>
To: "Brendan Trotter" <btrotter@gmail.com>
Cc: "Andi Kleen" <ak@suse.de>, "Ashok Raj" <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: NMI problems with Dell SMP Xeons
Date: Thu, 08 Jun 2006 15:11:15 +1000 [thread overview]
Message-ID: <6888.1149743475@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 07 Jun 2006 15:18:57 GMT." <b1ebdcad0606070818l3024b264k89f6cd37ccb0b6f7@mail.gmail.com>
"Brendan Trotter" (on Wed, 7 Jun 2006 15:18:57 +0000) wrote:
>Hi,
>
>On 6/7/06, Keith Owens <kaos@sgi.com> wrote:
>> This problem is not KDB specific, although that is where it was first
>> noticed. Any code that sends a broadcast IPI 2 or an NMI IPI will
>> crash these Dell boxes when there is a mismatch between the cpus known
>> to the BIOS and the cpus known to the OS.
>
>I missed this (broadcast IPI 2 causing problems)...
It turns out that there is an uncommented hack in x86_64's version of
__prepare_ICR().
case NMI_VECTOR:
icr |= APIC_DM_NMI;
break;
That hack is not in i386, which means that IPI 2 does different things
in i386 vs. x86_64 mode on the same hardware. I am still tracking down
all the differences before doing a clean up patch that makes i386 and
x86_64 behave the same.
prev parent reply other threads:[~2006-06-08 5:11 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
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 [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=6888.1149743475@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=ak@suse.de \
--cc=ashok.raj@intel.com \
--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