From: "Christopher S. Aker" <caker@theshore.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
peter.spamcatcher@rimuhosting.com
Subject: Re: [uml-devel] SKAS race condition status?
Date: Tue, 25 Oct 2005 16:37:51 -0500 [thread overview]
Message-ID: <435EA5AF.30406@theshore.net> (raw)
In-Reply-To: <200510251958.14798.blaisorblade@yahoo.it>
Blaisorblade wrote:
> After some researches, it seems that the matching errata document is this one:
>
> http://www.intel.com/design/xeon/specupdt/302402.htm
>
> which would imply you have a 64-bit enabled processor...
>
> Note 1: that's not the only document matching, but the other is for 64-bit
> processors too
>
> Note 2: I couldn't match steppings between those docs and cpuinfo...
OK. I matched up some purchase orders with Intel part numbers:
BX80546KG3200FU <-- model 4
BX80546KG3200EU <-- model 3 (I think)
I'll start disabling HyperThreading on hosts that crash next.
-Chris
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-10-25 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 22:50 [uml-devel] SKAS race condition status? Christopher S. Aker
2005-10-25 16:44 ` Christopher S. Aker
2005-10-25 16:57 ` Christopher S. Aker
2005-10-25 17:58 ` Blaisorblade
2005-10-25 21:37 ` Christopher S. Aker [this message]
2005-10-25 21:58 ` Peter
2005-10-25 22:10 ` Christopher S. Aker
2005-10-25 22:25 ` Peter
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=435EA5AF.30406@theshore.net \
--to=caker@theshore.net \
--cc=blaisorblade@yahoo.it \
--cc=peter.spamcatcher@rimuhosting.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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