From: Andi Kleen <ak@suse.de>
To: Keith Owens <kaos@sgi.com>
Cc: Ashok Raj <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org,
"Brendan Trotter" <btrotter@gmail.com>
Subject: Re: NMI problems with Dell SMP Xeons
Date: Wed, 7 Jun 2006 14:13:00 +0200 [thread overview]
Message-ID: <200606071413.00990.ak@suse.de> (raw)
In-Reply-To: <6799.1149680860@ocs3.ocs.com.au>
On Wednesday 07 June 2006 13:47, Keith Owens wrote:
> Andi Kleen (on Wed, 7 Jun 2006 10:01:40 +0200) wrote:
> >
> >>
> >> Two ways:
> >>
> >> (1) Boot with a kernel with CONFIG_ACPI=n, so the OS only finds 2 cpus
> >> in the MPT instead of the 4 listed by ACPI.
> >>
> >> (2) The kernel has ACPI=y, but is booted with maxcpus=2.
> >>
> >> In both cases, send_IPI_allbutself() with IPI 2 or an NMI will result
> >> in a hard reset.
> >
> >Sounds both like a "Don't do that when it hurts" . I know some people
> >have religious issues with ACPI, but it's simple a fact that many
> >modern boxes don't work correctly in obvious or subtle ways without it.
>
> Building a kernel without ACPI is silly nowadays. But even with ACPI,
> booting with a restricted maxcpus and sending IPI 2 or NMI as broadcast
> will kill these boxes. maxcpus is a valid option.
Yes, I'm not opposed to using *_sequence on cpu_online_map here. Please send a patch.
-Andi
next prev parent reply other threads:[~2006-06-07 12:13 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 [this message]
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=200606071413.00990.ak@suse.de \
--to=ak@suse.de \
--cc=ashok.raj@intel.com \
--cc=btrotter@gmail.com \
--cc=kaos@sgi.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 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.