From: Jeff Golds <jgolds@resilience.com>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] AMD SMP capability sanity checking.
Date: Fri, 16 Nov 2001 16:33:35 -0800 [thread overview]
Message-ID: <3BF5B05F.9F727DD8@resilience.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0111162353140.32578-100000@Appserv.suse.de>
Dave Jones wrote:
>
> Burning out a fuse to make the switch from MP->XP may affect more
> than just the cpuid capabilities. The fact is _we don't know_
>
Right, so why assume it doesn't work?
> I've yet to see a socket 370 dual processormotherboard that
> I'd put faith in for a mission critical environment.
> "I had no problems" means _nothing_ when theres as few as 1 other
> user reporting SMP related problems with the same setup.
>
People with "true" SMP CPUs can have problems as well. Does this mean
SMP CPUs are not SMP capable? If only one person is having problems,
chances are there's a problem someplace. Could it be a faulty
motherboard? Mismatched CPUs? Bad memory? Bad CPU? Bad power
supply? There's an awful lot of variables here.
-Jeff
--
Jeff Golds
Sr. Software Engineer
jgolds@resilience.com
next prev parent reply other threads:[~2001-11-17 0:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 21:30 [PATCH] AMD SMP capability sanity checking Dave Jones
2001-11-16 19:42 ` Gérard Roudier
2001-11-16 21:41 ` Randy.Dunlap
2001-11-16 21:46 ` Dave Jones
2001-11-16 21:44 ` Dan Hollis
2001-11-16 22:02 ` Dave Jones
2001-11-16 21:46 ` Jeff Garzik
2001-11-16 21:59 ` Stefan Smietanowski
2001-11-16 22:11 ` Dave Jones
2001-11-16 22:37 ` Jeff Golds
2001-11-16 23:04 ` Dave Jones
2001-11-17 0:33 ` Jeff Golds [this message]
2001-11-17 0:39 ` Dave Jones
2001-11-17 0:59 ` Andreas Boman
2001-11-17 1:54 ` Mike Fedyk
2001-11-17 4:11 ` Nathan Walp
2001-11-17 4:59 ` Mark Orr
2001-11-16 23:40 ` Stefan Smietanowski
2001-11-16 23:47 ` Dave Jones
2001-11-17 1:05 ` Stefan Smietanowski
2001-11-17 1:09 ` Dan Hollis
2001-11-17 1:11 ` Dave Jones
2001-11-17 1:10 ` Dave Jones
2001-11-21 0:42 ` Pavel Machek
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=3BF5B05F.9F727DD8@resilience.com \
--to=jgolds@resilience.com \
--cc=davej@suse.de \
--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