Reference Number: 323372-015
Intel® Xeon® Processor 5600
Series
Specification Update
August 2013
2Intel® Xeon® Processor 5600 Series
Specification Update August 2013
Legal Lines and Discla ime rs
INFORMA TION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED,
BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS
PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER,
AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELA TING T O SALE AND/OR USE OF INTEL PRODUC TS INCLUDING
LIABILITY OR WARRANTIES RELATING TO FITNES S FOR A P ARTICULAR PURPOSE, MERCHANT ABILITY, OR INFRINGEMENT OF ANY
PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY
APPLICA TION IN WHICH THE FAILURE OF THE INTEL PRODUCT COUL D CREA TE A SITUATION WHERE PERSONAL INJU RY OR DEA TH
MAY OCCUR.
A “Mission Critical Application” is any application in which failure of the Intel Prod uct co uld res ult, dire ctl y or ind i rectly, in personal
injury or death. SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU
SHALL INDEMNIFY AND HOLD INTEL AND ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS,
OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE
A T T ORNEYS' FEES ARISING OUT OF, DIRE CTLY OR IND IRECTLY, ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJUR Y, OR DEATH
ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS SUBCON TRACTOR WAS
NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained
by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm%20
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the
absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel reserves these for future
definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The
information here is subject to change without notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to
deviate from published specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
All products, platforms, dates, and figures specified are preliminary based on current expectations, and are subject to change
without notice. All dates specified are target dates, are provided for planning purposes only and are subject to change.
This document contains info rmation on products i n the design phase of development. Do not finalize a design with this information.
Revised information will be published when the product is available. Verify with your local sales office that you have the latest
datasheet befo re finalizing a design .
Intel processor numbers are not a measure of performance. Proc essor numbers d ifferentiate features within e ach processo r family,
not across different processor families. See http://www.intel.com/products/processor_number for details
See the http://processorfinder.intel.com/ or contact your Intel representative for more information.
Hyper-Threading Technology requires a computer system with a processor supporting HT Technology and an HT Technology-
enabled chipse t, BIOS and operating system. Performance will vary de pe ndi ng on the specific har dware and softw are you use. F o r
more information including details on which processors support HT Technology, see http://www.intel.com/technology/platform-
technology/hyper-threading/index.htm.
Intel® Turbo Boost Technology requires a PC with a processor with Intel Turbo Boost Technology capability. Intel Turbo Boost
Technology performance varies depending on hardware, software and overall system configuration. Check with your PC
manufacturer on whether your system delivers Intel Turbo Boost Technology.For more information, see http://www.intel.com/
technology/turboboost.
Intel, X eon, Pentiu m, Celeron, Intel Enh anced SpeedStep Technology, Intel Core, the Intel logo are trademarks of Intel Corpor ation
in the U. S. and other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2013, Intel Corporation. All Rights Reserved.
Intel® Xeon® Processor 5600 Series 3
Specification Update, August 2013
Contents
Revision History...............................................................................................................5
Preface ..............................................................................................................................6
Identification Information ................................................................................................8
Summary Table of Changes..........................................................................................12
Errata Summary..............................................................................................................13
BIOS ACM AND SINIT ACM Errata Summary ..............................................................18
BIOS ACM Errata............................................................................................................58
SINIT ACM Errata............................................................................................................60
Specification Changes...................................................................................................61
Specification Clarifications...........................................................................................62
Documentation Changes...............................................................................................63
§
Intel® Xeon® Processor 5600 Series 4
Specification Update, August 2013
Intel® Xeon® Processor 5600 Series 5
Specification Update August 2013
Revision History
Doc ID Revision Description Date
323372 -001 • Initial Release March 2010
-002 • Added Errata BD91 through BD94 April 2010
-003 • Added Errata BD95 through BD98 May 2010
-004 • Added Errata BD99 through BD102. July 2010
-005 • Added Note 20 to Table 2. Updated Microcode Update Information. August 2010
-006 • Added Erratum BD103. Updated ErratumBD40 September 2010
-007 • Added Errata BD104 through BD106. Included Microcode Update
Table December 2010
-008 • Added Errata BD107 and BD108. Added BIOS ACM and SINIT ACM
Errata. January 2011
-009 • Added Errata BD109 through BD115 February 2011
-010 • Added Erratum BD116. Updated Table 2. April 2011
-011 • Updated Table 3 & 4 September 2011
-012 • Added Erratum BD117. Added SINIT ACM Erratum BD1 December 2011
-013 • Added Errata BD118 through BD121 May 2012
-014 • Added Errata BD122 through BD127 Nov 2012
-015 • Added Errata BD131-136 August 2013
Intel® Xeon® Processor 5600 Series 6
Specification Update August 2013
Preface
This document is an update to the specifications contained in the Affected Documents
able below. This document is a compilation of device and documentation errata,
specification clarifications and changes. It is intended for hardware system
manufacturers and software developers of applications, operating systems, or tools.
Information types defined in Nomenclature are consolidated into the specification
update and are no longer published in other documents.
This document may also contain information that was not previously published.
Affected Documents
Related Documents
Notes:
1. Document is available publicly at http://developer.intel.com.
Document Title Notes1
Intel® Xeon® Processor 5600 Series Datasheet Volume 1 & 2 323369 & 323370
Document Title Location Notes
Intel® 64 and IA-32 Architectures Software Developer's Manual
Volume 1: Basic Architecture
Volume 2A: Instruction Set Reference, A-M
Volume 2B: Instruction Set Reference, N-Z
Volume 3A: System Programming Guide, Part 1
Volume 3B: System Programming Guide, Part 2
253665
253666
253667
253668
253669
2
Intel® 64 and IA-32 Architectures Optimization Reference Manual 248966 2
Intel® Virtualization Technology Specification for Directed I/O
Architecture Specification D51397-001 2
Intel® Xeon® Processor 5600 Series 7
Specification Update August 2013
Nomenclature
S-Spec Number is a five-digit code used to identify products. Products are
differentiated by their unique characteristics, e.g., core speed, L2 cache size, package
type, etc. as described in the processor identification information table. Read all notes
associated with each S-Spec number.
Errata are design defects or errors. These may cause the processor behavior to deviate
from published specifications. Hardware and software designed to be used with any
given stepping must assume that all errata documented for that stepping are present
on all devices.
Specification Changes are modifications to the current published specifications.
These changes will be incorporated in the next release of the specification.
Specification Clarifications describe a specification in greater detail or further
highlight a specification’ s impact to a complex design situation. These clarifications will
be incorporated in any new release of the specification.
Documentation Changes include typographical errors, omissions, or incorrect
information from the current published specifications. These will be incorporated in the
next release of the specification.
Note: Errata remain in the specification update throughout the product’s life cycle, or until a
particular stepping is no longer commercially available. Under these circumstances,
errata remov ed from the specification update are archiv ed and available upon request.
Specification changes, specification clarifications, and documentation changes are
removed from the sightings report and/or specification update when the appropriate
changes are made to the appropriate product specification or user documentation.
Intel® Xeon® Processor 5600 Series 8
Specification Update August 2013
Identification Information
Component Identification
The Intel® Xeon® Processor 5600 Series stepping can be identified by the following
register contents.
Notes:
1. The Extended Fami ly, bits [27:20] are use d in co njunction with the Family C ode, spec ific in bit s [11:8],
to indicate whether the processor belongs to the Intel386, Intel486, Pentium, Pentium Pro, Pentium 4,
or Intel® Core™ processor family.
2. The Extended Model, bits [19:16] in conjunction with the Model Number, specified in bits [7:4], are
used to identify the model of the processor within the processor family.
3. The Processor Type, specified in bits [13:12] indicates whether the processor is an original OEM
processor, an OverDrive processor, or a dual processor (capable of being used in a dual processor
system).
4. The Family Code corresponds to bits [11:8] of the EDX register after RESET, bits [11:8] of the EAX
register after the CPUID instruction is executed with a 1 in the EAX register, and the generation field of
the Device ID register accessible through Boundary Scan.
5. The Model Number c orresponds to bits [7:4] of the EDX register after RESET, bits [7:4] of the EAX
register after the CPUID instruction is executed with a 1 in the EAX register, and the model field of the
Device ID regist er access ible through Boundary Scan.
6. The Stepping ID in bits [3:0] indicate s the revision number of that model. See Table 2 for th e processor
stepping ID number in the CPUID information.
When EAX is initialized to a value of ‘1’, the CPUID instruction returns the Extended
Family, Extended Model, Processor Type, Family Code, Model Number, and Stepping ID
in the EAX register. Note that the EDX processor signature value after reset is
equivalent to the processor signature output value in the EAX register.
Cache and TLB descriptor parameters are provided in the EAX, EBX, ECX and EDX
registers after the CPUID instruction is executed with a 2 in the EAX register.
Table 1. Intel® Xeon® Processor 5600 Series Signature/Version
Reserved Extended
Family1Extended
Model2Reserved Processor
Type3Family
Code4Model
Number5Stepping
ID6
31:28 27:20 19:16 15:14 13:12 11:8 7:4 3:0
0000000
0b 0010b 00b 0110 1100b XXXXb
Intel® Xeon® Processor 5600 Series 9
Specification Update August 2013
Component Marking
The Intel® X eon® Processor 5600 Series can be identified by the following component
markings:
Figure 1. Processor Top-side Markings (Example)
Table 2. Intel® Xeon® Processor 5600 Series Identification (Sheet 1 of 2)
S-Spec
Number Steppin
gCPUID1
Core Frequency (GHz) 18/
Intel QuickPath
Interconnect (GT/s) /
DDR3 (MHz) / DDR3L
(MHz)
Available
bins of Intel
Turbo Boost
Technology
Cache
Size
(MB)
TDP
(W) Notes
SLBVX B-1 0x000206C2 3.46 / 6.40 / 1333 / 1333 1/1/1/1/2/2 12 130 20
SLBVY B-1 0x000206C2 3.60 / 6.40 / 13 33 / 1333 na/na/1/1/
2/2 12 130 21
SLBZ7 B-1 0x000206C2 2.93 / 5.86 / 10 66 / 1066 na/na/1/1/
2/2 12 130 22
SLBV5 B-1 0x000206C2 3.33 / 6.40 / 13 33 / 1333 1/1/1/1/2/2 12 130 4
SLBV9 B-1 0x000206C2 3.46 / 6.40 / 13 33 / 1333 na/na/1/1/
2/2 12 130 5
SLBYL B-1 0x000206C2 3.06 / 6.40 / 1333 / 1333 2/2/2/2/3/3 12 95 23
SLBYK B-1 0x000206C2 3.20 / 6.40 / 13 33 / 1333 na/na/2/2/
3/3 12 95 24
SLBV7 B-1 0x000206C2 2.93 / 6.40 / 13 33 / 1333 2/2/2/2/3/3 12 95 6
SLBV A B-1 0x000206C2 3.06 / 6.40 / 1333 / 1333 na/na/2/2/
3/3 12 95 9,19
SLBV6 B-1 0x000206C2 2.80 / 6.40 / 13 33 / 1333 2/2/2/2/3/3 12 95 7
SLBV3 B-1 0x000206C2 2.66 / 6.40 / 13 33 / 1333 2/2/2/2/3/3 12 95 8
SLBZ8 B-1 0x000206C2 2.53 / 5.86 / 13 33 / 1333 1/1/2/2/3/3 12 80 25
SLBWZ B-1 0x000206C2 2.40 / 5.86 / 13 33 / 1333 1/1/2/2/3/3 12 80 26
Intel® Xeon® Processor 5600 Series 10
Specification Update August 2013
Notes:
1. CPUID is 0000206Csh, where ‘s’ is the stepping number.
2. This is a Intel® Xeon® Processor 5600 Series with 60W TDP (Thermal Design Power) with elevated
NEBS thermal profile.
3. This is a Intel® Xeon® Processor 5600 Series with 40W TDP (Thermal Design Power) with elevated
NEBS thermal profile.
4. This is an Intel® Xeon Processor X5680.
5. This is an Intel® Xeon Processor X5677.
6. This is an Intel® Xeon Processor X5670.
7. This is an Intel® Xeon Processor X5660.
8. This is an Intel® Xeon Processor X5650.
9. This is an Intel® Xeon Processor X5667.
10. This is an Intel® Xeon Processor E5640.
11. This is an Intel® Xeon Processor E5630
12. This is an Intel® Xeon Processor E5620
13. This is an Intel® Xeon Processor L5640.
14. This is an Intel® Xeon Processor L5630.
15. This is an Intel® Xeon Processor L5609.
16. This is an Intel® Xeon Processor L5638.
17. This is an Intel® Xeon Processor L5618.
18. The core frequency reported in the p roces sor brand string is rounded to 2 deci mal dig its. (For example,
core frequency of 2.6666, repeating 6, is reported as @2.67 in bran d s tring. Core frequ ency of 2.1333,
is reported as @2.13 in brand string.)
19. The Brand String for the Intel® Xeon Processor X5667 contains the value 3.07 when the actual
processor core frequency is 3.066 Ghz.
20. This is an Intel® Xeon Processor X5690.
21. This is an Intel® Xeon Processor X5687.
22. This is an Intel® Xeon Processor X5647.
23. This is an Intel® Xeon Processor X5675.
24. This is an Intel® Xeon Processor X5672.
25. This is an Intel® Xeon Processor E5649.
26. This is an Intel® Xeon Processor E5645.
27. This is an Intel® Xeon Processor E5607.
28. This is an Intel® Xeon Processor E5606.
29. This is an Intel® Xeon Processor E5603.
30. This is an Intel® Xeon Processor L5645.
31. This is an Intel® Xeon Processor L5639.
SLBZ9 B-1 0x000206C2 2.26 / 4.80 / 1066 / 1066 na 8 80 27
SLC2N B-1 0x000206C2 2.13 / 4.80 / 1066 / 1066 na 8 80 28
SLC2F B-1 0x000206C2 1.60 / 4.80 / 1066 / 1066 na 4 80 29
SLBVC B-1 0x000206C2 2.66 / 5.86 / 1066 / 1066 na/na/1/1/2/
212 80 10
SLBVB B-1 0x000206C2 2.53 / 5.86 / 1066 / 1066 na/na/1/1/2/
212 80 11
SLBV4 B-1 0x000206C2 2.40 / 5.86 / 1066 /1066 na/na/1/1/2/
212 80 12
SLBVW B-1 0x000206C2 2.40 / 5.86 / 1333 / 1333 2/2/3/3/4/4 12 60 30
SLBZJ B-1 0x000206C2 2.13 / 5.86 / 1333 / 1333 2/2/3/3/4/4 12 60 31
SLBV8 B-1 0x000206C2 2.26 / 5.86 / 1333 / 1333 2/2/3/3/4/4 12 60 13
SLBWY B-1 0x000206C2 2.00 / 5.86 / 1333 / 1333 1/1/2/2/3/3 12 60 16
SLBVD B-1 0x000206C2 2.13 / 5.86 / 1066 / 1066 na/na/1/1/2/
212 40 14
SLBVJ B-1 0x000206C2 1.86 / 4.80 / 1066 / 1066 na 12 40 15
SLBX3 B-1 0x000206C2 1.86 / 5.86 / 1066 / 1066 na/na/1/1/2/
312 40 17
Table 2. Intel® Xeon® Processor 5600 Series Identification (Sheet 2 of 2)
S-Spec
Number Steppin
gCPUID1
Core Frequency (GHz) 18/
Intel QuickPath
Interconnect (GT/s) /
DDR3 (MHz) / DDR3L
(MHz)
Available
bins of Intel
Turbo Boost
Technology
Cache
Size
(MB)
TDP
(W) Notes
Intel® Xeon® Processor 5600 Series 11
Specification Update August 2013
32.
Intel® Xeon® Processor 5600 Series 12
Specification Update August 2013
Summary Table of Changes
The table included in this section indicate the errata, Specification Changes,
Specification Clarifications, or Document Changes which apply to the Intel® Xeon®
Processor 5600 Series. Intel may fix some of the errata in a future stepping of the
component, and account for the other outstanding issues through documentation or
specification changes as noted.
Definitions are listed below for terminology used in the Summary Tables below.
Affected Stepping Column:
X: Errata exists in the stepping indicated. Specification Change or Specification
Clarification that applies to this stepping.
Blank: This erratum is fixed, or does not exist, in the listed stepping. Specification
Change does not apply to listed stepping.
Status Column:
No Fix: There are no plans to fix this erratum.
Plan Fix: This erratum may be fixed in a future stepping of the product.
Fixed: This erratum has been fixed.
A change bar to the left of the table row indicates this erratum is either new or has
been modified from the previous revision of this document.
Intel® Xeon® Processor 5600 Series 13
Specification Update August 2013
Errata Summary
Table 3. Errata Summary Table (Sheet 1 of 5)
Errata
Number
Steppings Status ERRATA
B-1
BD1 X No Fix The Processor may Report a #TS Instead of a #GP Fault
BD2 X No Fix REP MOVS/STOS Executing wi th F ast String s Enabled and Cross ing Pa ge Boundaries
with Inconsistent Memory T ypes may use an Incorrect Data Size or Lead to Memory-
Ordering Violations
BD3 X No Fix Code Segment Limit/Canonical F aults on RSM May be Serviced before Higher Priorit y
Interrupts/Exceptions and May Push the Wrong Address Onto the Stack
BD4 X No Fix Performance Monitor SSE Retired Instructions May Return Incorrect Values
BD5 X No Fix Premature Execution of a Load Operation Prior to Exception Handler Invocation
BD6 X No Fix MOV To/From Debug Registers Causes Debu g Exception
BD7 X No Fix Incorrect Address Computed For Last Byte of FXSAVE/FXRSTOR Image Leads to
Partial Memory Update
BD8 X No Fix Values for LBR/BTS/BTM will be Incorrect after an Exit from SMM
BD9 X No Fix Single Step Interrupts with Floating Point Exception Pending May Be Mishandled
BD10 X No Fix Fault on ENTER Instruction May Result in Unexpected Values on Stack Frame
BD11 X No Fix IRET under Certain Conditions May Cause an Unexpected Alignment Check
Exception
BD12 X No Fix General Protection Fault (#GP) for Instructions Greater than 15 Bytes May be
Preempted
BD13 X No Fix General Protection (#GP) Fault May Not Be Signaled on Data Segment Limit
Violation ab ove 4-G Limit
BD14 X No Fix LBR, BT S, B TM May Report a Wrong Address when an Ex ception/Inte rrupt Oc curs in
64-bit Mode
BD15 X No Fix MCi_Status Overflow Bi t Ma y Be Incorrect ly S et on a Single In stance of a D TLB Error
BD16 X No Fix Debug Exception Flags DR6.B0-B3 Flags May be Incorrect for Disabled Breakpoints
BD17 X No Fix MONITOR or CLFLUSH on the Local XAPIC's Address Space Results in Hang
BD18 X No Fix Corruption of CS Segment Register During RSM While Tr ansit ioning Fro m R eal Mod e
to Protected Mode
BD19 X No Fix A VM Exit on MWAIT May Incorrectly Report the Monitoring Hardware as Armed
BD20 X No Fix Performance Monitor Event SEGMENT_REG_LOADS Counts Inaccurately
BD21 X No Fix #GP on Segment Selector Descriptor that Straddles Canonical Boundary May Not
Provide Correct Exception Error Code
BD22 X No Fix Improper P arit y Erro r Signale d in the IQ F o llowing Reset When a Code Breakpoint i s
Set on a #GP Instruction
BD23 X No Fix An Enabled Debug Breakpoint or Single Step Trap May Be Taken after MOV SS/POP
SS Instruction if it is Followed by an Instruction That Signals a Floating Point
Exception
BD24 X No Fix IA32_MPERF Counter Stops Counting During On-Demand TM1
BD25 X No Fix Intel® QuickPath Memory Controller May Hang Due to Uncorrectable ECC Errors
Occurring on Both Channels in Mirror Channel Mode
BD26 X No Fix Simultaneous Correctable ECC Errors on Different Memory Channels With Patrol
Scrubbing Enabled May Result in Incorrect Information Being Logged
BD27 X No Fix The Memory Controller tTHRO T_OPRE F Timings May be Violated During Self Refres h
Entry
Intel® Xeon® Processor 5600 Series 14
Specification Update August 2013
BD28 X No Fix Synchronous Reset of IA32_APERF/IA32_MPERF Counters on Overflow Does Not
Work
BD29 X No Fix Disabling Thermal Monitor While Processor is Hot, Then Re-enabling, May Result in
Stuck Core Operating Ratio
BD30 X No Fix Writing the Local Vector Table (LVT) when an Interrupt is Pending May Cause an
Unexpected Interrupt
BD31 X No FIx Faulting MMX Instruction May Incorrectly Update x87 FPU Tag Word
BD32 X No Fix xAPIC Timer May Decrement Too Quickly Following an Automatic Reload While in
Periodic Mode
BD33 X No Fix Reported Memory Type May Not Be Used to Access the VMCS and Referenced Data
Structures
BD34 X No Fix B0-B3 Bits in DR6 For Non-Enabled Breakpoints May be Incorrectly Set
BD35 X No Fix Core C6 May Clear Previously Logged TLB Errors
BD36 X No Fix Changing the Memory Type for an In-Use Page Translation May Lead to Memory-
Ordering Violations
BD37 X No Fix A String Instruction that Re-maps a Page May Encounter an Unexpected Page Fault
BD38 X No Fix Infinite Stream of Interrupts May Occur if an ExtINT Delivery Mode Interrupt is
Received while All Cores in C6
BD39 X No Fix Two xAPIC Timer Event Interrupts May Unexpectedly Occur
BD40 X No Fix EOI Transaction May Not be Sent if Software Enters Core C6 During an Interrupt
Service Routine
BD41 X No Fix FREEZE_WHILE_SMM Does Not Prevent Event From Pending PEBS During SMM
BD42 X No Fix APIC Error “Received Illegal Vector” May be Lost
BD43 X No Fix DR6 May Contain Incor rect Information When the First Ins truction After a MOV S S,r/
m or POP SS is a Store
BD44 X No Fix An Uncorrectable Error Logged in IA32_CR_MC2_STATUS May also Result in a
System Hang
BD45 X No Fix IA32_PERF_GLOBAL_CTRL MSR May be Incorrectly Initialized
BD46 X No Fix ECC Errors Can Not be Injected on Back-to-Back Writes
BD47 X No Fix Performance Monitor Counter INST_RETIRED.STORES May Count Higher than
Expected
BD48 X No Fix Sleeping Cores May Not be Woken Up on Logical Cluster Mode Broadcast IPI Using
Destination Field Instead of Shorthand
BD49 X No Fix Faulting Executions of FXRSTOR May Update State Inconsistently
BD50 X No Fix Failing DIMM ID May be Incorrect in the 2DPC Configuration When Mirroring is
Enabled
BD51 X No Fix ISSUEONCE Bit in MC_SCRUB_CONTROL Register Does Not Work Correctly
BD52 X No Fix Memory Aliasing of Code Pages May Cause Unpredictable System Behavior
BD53 X No Fix Performance Monitor Counters May Count Incorrectly
BD54 X No Fix Memory Thermal Throttling May Not Work as Expected in Lockstep Channel Mode
BD55 X No Fix Simultaneous Accesses to the Processor via JTAG and PECI May Cause Unexpected
Behavior
BD56 X No Fix Performance Monitor Ev ent O ffcore_re spons e_0 (B7H) Does Not C ount NT Stor es to
Local DRAM Correctly
BD57 X No Fix EFLAGS Discrepancy o n Page F aults and on EPT- Induced VM Exits after a Translation
Change
Table 3. Errata Summary Table (Sheet 2 of 5)
Errata
Number
Steppings Status ERRATA
B-1
Intel® Xeon® Processor 5600 Series 15
Specification Update August 2013
BD58 X No Fix System May Hang if MC_CHANNEL_{0,1,2}_MC_DIMM_INIT_CMD.DO_ZQCL
Commands Are Not Issued in Increasing Populated DDR3 Rank Order
BD59 X No Fix Package C3/C6 Transitions When Memory 2x Refresh is Enabled May Result in a
System Hang
BD60 X No Fix Back to Back Uncorrected Machine Check Errors May Overwrite
IA32_MC3_STATUS.MSCOD
BD61 X No Fix Corrected Errors With a Yellow Error Indication May be Overwritten by Other
Corrected Errors
BD62 X No Fix Performance Monitor Events DCACHE_CACHE_LD and DCACHE_CACHE_ST May
Overcount
BD63 X No Fix Performance Monitor Events INSTR_RETIRED and MEM_INST_RETIRED May Count
Inaccurately
BD64 X No Fix A Page Fault May Not be Generated When the PS bit is set to "1" in a PML4E or
PDPTE
BD65 X No Fix Uncacheable Access to a Monitored Address Range May Prevent Future Triggering of
the Monitor Hardware
BD66 X No Fix Intel® Interconnect BIST (Intel® IBIST) R esults May be Additi onally Rep orted After
a GETSEC[WAKEUP] or INIT-SIPI Sequence
BD67 X No Fix Pending x87 FPU Exceptions (#MF) May be Signaled Earlier Than Expected
BD68 X No Fix VM Exits Due to “NMI-Window Exiting” May Be De layed by One Instruction
BD69 X No Fix Multiple Performance Monitor Interrupts are Possible on Overflow of
IA32_FIXED_CTR2
BD70 X No Fix C-State Autodemotion May be too Aggressive Under Certain Configurations and
Workloads
BD71 X No Fix LBRs May Not be Initialized During Power-On Reset of the Processor
BD72 X No Fix Multiple Per formance Monito r Interrup ts are Possible on Overflow of Fixed Coun ter 0
BD73 X No Fix VM Exits Due to LIDR/LGDT/SIDT/SGDT Do Not Report Correct Operand Size
BD74 X No Fix Performance Monitoring Eve nts STORE_BLOCKS.NO T_STA and ST ORE _BLOC KS .STA
May Not Count Events Correctly
BD75 X No Fix Storage of PEBS Record Delayed Following Execution of MOV SS or STI
BD76 X No Fix Performance Monitoring Event FP_MMX_TRANS_TO_MMX May Not Count Some
Transitions
BD77 X No Fix The PECI Bu s May be Tri-stated After System Reset
BD78 X No Fix LER MSRs May Be Unreliable
BD79 X No Fix APIC Timer CCR May Report 0 in Periodic Mode
BD80 X No Fix LBR, BTM or BTS Records May have Incorrect Branch From Information After an
Intel Enhanced SpeedStep Technology Transition, T-states, C1E, or Adaptive
Thermal Throttling
BD81 X No Fix PEBS Records Not Created For FP-A ssists Events
BD82 X No Fix MSR_TURBO_RATIO_LIMIT MSR May Return Intel® Turbo Boost Technology Core
Ratio Multipliers for Non-Existent Core Configurations
BD83 X No Fix L1 Cache Uncorrected Errors May be Recorded as Correctable in 16K Mode
BD84 X No Fix Extra APIC Timer Interrupt May Occur During a Write to the Divide Configuration
Register
BD85 X No Fix PECI Reads of Machine Check MSRs in the Processor Core May Not Function
Correctly
BD86 X No Fix The Combination of a Page-Split Lock Access And Data Accesses That Are Split
Across Cacheline Boundaries May Lead to Proces sor Livelock
Table 3. Errata Summary Table (Sheet 3 of 5)
Errata
Number
Steppings Status ERRATA
B-1
Intel® Xeon® Processor 5600 Series 16
Specification Update August 2013
BD87 X No Fix Package C6 Transitions May Cause Memory Bit Errors to be Observed
BD88 X No Fix FP Data Operand Pointer May Be Incorrectly Calculated After an FP Access Which
Wraps a 4-Gbyte Boundary in Code That Uses 32-Bit Address Size in 64-bit Mode
BD89 X No Fix FP Data Operand Pointer May Be Incorrectly Calculated After an FP Access Which
Wraps a 64-Kbyte Boundary in 16-bit Code
BD90 X No Fix Spurious PROCHOT# Assertion During Warm Reset May Hang the Processor
BD91 X No Fix TSC Values When Observed Cross-Socket May Be Out of Sync After a Warm Reset
BD92 X No Fix Changes to Reserved Bits for Some Non-Architectural MSR’s May Cause
Unpredictable System Behavior
BD93 X No Fix Persistent Stream of Correctable Memory ECC Errors May Result in Unexpected
Behavior
BD94 X No Fix IO_SMI Indication in SMRAM State Save Area May Be Lost
BD95 X No Fix Failing DIMM ID May Be Incorrect When Mirroring is Enabled
BD96 X No Fix PECI Reads to Machine Check Registers May Return Unexpected Data
BD97 X No Fix FSW May Be Corrupted If an x87 Store Instruction Causes a Pag e Fault in VMX Non-
Root Operation
BD98 X No Fix Sensitivity in Clocking Circuitry May Result in Unpredictable System Behavior
BD99 X No Fix Accesses to a VMCS May Not Operate Correctly If CR0.CD is Set on Any Logical
Processor of a Core
BD100 X No Fix Performance Monitor Events for Hardware Prefetches Which Miss The L1 Data Cache
May be Over Counted
BD101 X No Fix Parallel VMX entries and exits the DTLB is not flushed
BD102 X No Fix VM Exit May Incorrectly Clear IA32_PERF_GLOBAL_CTRL [34:32]
BD103 X No Fix VM Entry May Omit Consistency Checks R elated to Bit 14 (BS) of th e Pendin g Debug
Exception Field in Guest-State Area of the VMCS
BD104 X No Fix Package C6 Transitions May Result in Single and Multi-Bit Memory Errors
BD105 X No Fix Execution of VMPTRLD May Corrupt Memory If Current-VMCS Pointer is Invalid
BD106 X No Fix PerfMon Ove rflow Status Can Not be Cleared Af ter Certain Conditio ns Hav e Occurred
BD107 X No Fix An Unexpected P age F ault or EPT Violation Ma y Occur After AnotherLogical Process or
Creates a Valid Translation for a Page
BD108 X No Fix L1 Data Cache Errors May be Logged With Level Set to 1 Instead of 0
BD109 X No Fix Executing The GETSEC Instruction While Throttling May Result in a Processor Hang
BD110 X No Fix PerfMon Event LOAD_HIT_PRE.SW_PREFETCH May Overcount
BD111 X No Fix Successive Fixe d Counter Overflows May be Discarded
BD112 X No Fix #GP May be Signaled When Invalid VEX Prefix Precedes Conditional Branch
Instructions
BD113 X No Fix A Logical Processor May Wake From Shutdown State When Branch-Trace Messages
or Branch-Trace Stores Are Enabled
BD114 X No Fix Task Switch to a TSS With an Inaccessible LDTR Descriptor May Cause Unexpected
Faults
BD115 X No Fix Package C6 Exit with Memory in Self-Refresh When Using DDR3 RDIMM Memory
May Lead to a System Hang
BD116 X No Fix .MCIP Bit Not Checked on SENTER or ENTERACCS
BD117 X No Fix Unexpected Load May Occur on Execution of Certain Opcodes
Table 3. Errata Summary Table (Sheet 4 of 5)
Errata
Number
Steppings Status ERRATA
B-1
Intel® Xeon® Processor 5600 Series 17
Specification Update August 2013
BD118 X No Fix Successive Fixed Counter Overflows May be Discarded
BD119 X No Fix VM Exits Due to “NMI-Window Exiting” May Not Occur Following a VM Entry to the
Shutdown State
BD120 X No Fix Execution of INVVPID Outside 64-Bit Mode Cannot In validate Translations For 64-Bit
Linear Addresses
BD121 X No Fix A Combination of Data Accesses That Are Split Across Cacheline Boundaries May
Lead to a Processor Hang
BD122 X No Fix PerfMon Ove rflow Status Can Not be Cleared Af ter Certain Conditio ns Hav e Occurred
BD123 X No Fix Package C6 C-State Exit May Result in Uncorrectable Memory Errors
BD124 X No Fix VMRESUME May Omit Check of Revision Identifier of Linked VMCS
BD125 X No Fix An INIT Signal May Cause Unpredictable Behavior After a VMXOFF
BD126 X No Fix APIC Timer Interrupts May be Lost During Core C3
BD127 X No Fix MCI_ADDR May be Incorrect For Cache Parity Errors
BD128 X No Fix APIC Timer Interrupt May be Lost
BD129 X No Fix REP MOVS/STOS Ex ecuting with Fast Strings Enabled and Cr ossing P age Boundaries
with Inconsistent Memory T ypes may use an Incorrect Data Size or Lead to Memory-
Ordering Violations
BD130 X No Fix CR0.CD Is Ignored in VM X Operation
BD131 X No Fix Sensitivity in Execution Unit Clock Circuitry on a small subset of Intel® Xeon®
processor X5675, X5690 and X5687 May Result in Unpredictable System Behavior
BD132 X No Fix Virtual-APIC Page Accesses With 32-Bit PAE Paging May Cause a System Crash
BD133 X No Fix EPT Violations May Report Bits 11:0 of Guest Linear Address Incorrectly
BD134 X No Fix IA32_VMX_VMCS_ENUM MSR (48AH) Does Not Properly Report The Highest Index
Value Used For VMCS Encoding
BD135 X No Fix The Upper 32 Bits of CR3 May be Incorrectly Used With 32-Bit Paging
BD136 X No Fix The Corrected Error Count Overflow Bit in IA32_ MC0_STATUS is Not Updated After
a UC Error is Logged
Table 3. Errata Summary Table (Sheet 5 of 5)
Errata
Number
Steppings Status ERRATA
B-1
Intel® Xeon® Processor 5600 Series 18
Specification Update August 2013
BIOS ACM AND SINIT ACM Errata
Summary
Table 4. BIOS ACM Errata Table
Number ACM Release Status ERRATA Description
1.0 1.1 1.2
BD1 X Fixed BIOS ACM May Report an Incorrect TXT.ERRORCODE in Multiprocessor
Configurations
BD2 X Fixed BIOS ACM Reset TPM Auxiliary Indices Function Not Available\
BD3 X Fixed If Processor is Reset Without Resetting The IOH With Secrets in Memory, The
BIOS ACM Will Hand-off to BIOS With Memory Locked
BD4 X X Plan Fix BIOS ACM SCHECK May Set TPM Locality 0 to Inactive Status
BD5 X Fixed If BIOS policy Autopromotion Fails, TXT.ACMCRASHCODE And TXT.ACMSTATUS
May Have Incorrect Values
BD6 X Fixed The BIOS ACM May Write Error Codes to Th e Wrong Register
BD7 X X Plan Fix NPW BIOS ACMs May Allow Launch of an MLE When The Launch Control Policy
Disallows NPW Launch
BD8 X X Plan Fix TPM PCR17 Not Extended with BIOS ACM values
BD9 X X Plan Fix BIOS ACM May Exit to BIOS with TPM locality 3 activated
Table 5. SINIT ACM Errata Table
Number ACM Release Status ERRATA Description
1.0 1.1 1.2
BD1 X Fixed SINIT Buffer Overflow Vulnerability
Intel® Xeon® Processor 5600 Series 19
Specification Update August 2013
Specification Changes
Specification Clarifications
Documentation Changes
Number Specification Changes
No new Specification Changes in this Specification Update Revision
Number Specification Clarifications
No new Specification Clarifications in this Specification Update Revision
Number Documentation Changes
No new Documentation Changes in this Specification Update Revision
Intel® Xeon® Processor 5600 Series 20
Specification Update August 2013
Errata
BD1. The Processor may Report a #TS Instead of a #GP Fault
Problem: A jump to a busy TSS (Task-State Segment) may cause a #TS (invalid TSS exception)
instead of a #GP fault (general protection exception).
Implication: Operation systems that access a busy TSS may get invalid TSS fault instead of a #GP
fault. Intel has not observed this erratum with any commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD2. REP MOVS/STOS Executing with Fast Strings Enabled and Crossing
Page Boundaries with Inconsistent Memory Ty pes may use an
Incorrect Data Size or Lead to Memory-Ordering Violations
Problem: Under certain conditions as described in the Software Developers Manual section "Out-
of-Order Stores For String Operations in Pentium 4, Intel Xeon, and P6 Family
Processors" the processor performs REP MOVS or REP STOS as fast strings. Due to this
erratum fast string REP MOVS/REP STOS instructions that cross page boundaries from
WB/WC memory types to UC/WP/WT memory types, may start using an incorrect data
size or may observe memory ordering violations.
Implication: Upon crossing the page boundary the following may occur, dependent on the new page
memory type:
• UC the data size of each write will now always be 8 bytes, as opposed to the
original data size.
• WP the data size of each write will now always be 8 bytes, as opposed to the
original data size and there may be a memo ry orde ring violation.
• WT there may be a memory ordering violation.
Workaround: Software should avoid crossing page boundaries from WB or WC memory type to UC,
WP or WT memory type within a single REP MOVS or REP STOS instruction that will
execute with fast strings enabled.
Status: For the steppings affected, see the Summary Table of Changes.
BD3. Code Segment Limit/Canonical Faults on RSM May be Serviced before
Higher Priority Interrupts/Exceptions and May Push the Wrong
Address Onto the Stack
Problem: Normally, when the processor encounters a Segment Limit or Canonical Fault due to
code execution, a #GP (General Protection Exception) fault is generated after all higher
priority Interrupts and exceptions are serviced. Due to this erratum, if RSM (Resume
from System Management Mode) returns to execution flow that results in a Code
Segment Limit or Canonical Fault, the #GP fault may be serviced before a higher
priority Interrupt or Exception (for example, NMI (Non-Maskable Interrupt), Debug
break(#DB), Machine Check (#MC), and so forth). If the RSM attempts to return to a
non-canonical address, the address pushed onto the stack for this #GP fault may not
match the non-canonical address that caused the fault.
Intel® Xeon® Processor 5600 Series 21
Specification Update August 2013
Implication: Operating systems may observe a #GP fault being serviced before higher priority
Interrupts and Exceptions. Intel has not observed this erratum on any commercially
available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD4. Performance Monitor SSE Retired Instructions May Return Incorrect
Values
Problem: Performance Monitoring counter SIMD_INST_RETIRED (Event: C7H) is used to track
retired SSE instructions. Due to this err atum, the processor ma y also count oth er types
of instructions resulting in higher than expected values.
Implication: Performance Monitoring counter SIMD_INST_RETIRED may report count higher than
expected.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD5. Premature Execution of a Load Operation Prior to Exception Handler
Invocation
Problem: If any of the below circumstances occur, it is possible that the load portion of the
instruction will have executed before the exception handler is entered.
• If an instruction that performs a memory load causes a code segment limit
violation.
• If a waiting X87 floating-point (FP) instruction or MMX™ technology (MMX)
instruction that performs a memory load has a floating-point exception pending.
• If an MMX or SSE/SSE2/SSE3/SSSE3 extensions (SSE) instruction that performs a
memory load and has either CR0.EM=1 (Emulation bit set), or a floating-point Top-
of-S tack (FP TOS) not equal to 0, or a DNA exception pending.
Implication: In normal code execution where the target of the load operation is to write back
memory there is no impact from the load being prematurely executed, or from the
restart and subsequent re-execution of that instruction by the exception handler. If the
target of the load is to uncached memory that has a system side-effect, restarting the
instruction may cause unexpected system behavior due to the repetition of the side-
effect. Particularly, while CR0.TS [bit 3] is set, a MOVD/MOVQ with MMX/XMM register
operands may issue a memory load before getting the DNA exception.
Workaround: Code which performs loads from memory that has side-effects can effectively
workaround this behavior by using simple integer-based load instructions when
accessing side-effect memory and by ensuring that all code is written such that a code
segment limit violation cannot occur as a part of reading from side-effect memory.
Status: For the steppings affected, see the Summary Table of Changes.
BD6. MOV To/From Debug Registers Causes Debug Ex ception
Problem: When in V86 mode, if a MOV instruction is executed to/from a debug registers, a
general-protection exception (#GP) should be generated. However, in the case when
the general detect enable flag (GD) bit is set, the observed behavior is that a debug
exception (#DB) is generated instead.
Intel® Xeon® Processor 5600 Series 22
Specification Update August 2013
Implication: With debug-register protection enabled (i.e., the GD bit set), when attempting to
execute a MOV on debug registers in V86 mode, a debug exception will be generated
instead of the expected general-protection fault.
Workaround: In general, operating systems do not set the GD bit when they are in V86 mode. The
GD bit is generally set and used by debuggers. The debug exception handler should
check that the exception did not occur in V86 mode before continuing. If the exception
did occur in V86 mode, the exception may be directed to the general-protection
exception handler.
Status: For the steppings affected, see the Summary Table of Changes.
BD7. Incorrect Address Computed For Last Byte of FXSAVE/FXRSTOR
Image Leads to Partial Memory Update
Problem: A partial memory state save of the 512-byte FXSAVE image or a partial memory state
restore of the FXRSTOR image may occur if a memory address exceeds the 64 KB limit
while the processor is operating in 16-bit mode or if a memory address exceeds the
4 GB limit while the processor is operating in 32-bit mode.
Implication: FXSAVE/F XRSTOR will incur a #GP fault due to the memory limit violation as expected
but the memory state may be only partially saved or restored.
Workaround: Software should avoid memory accesses that wrap around the respective 16-bit and
32-bit mode memory limits.
Status: For the steppings affected, see the Summary Table of Changes.
BD8. Values for LBR/BTS/BTM will be Incorrect after an Exit from SMM
Problem: After a return from SMM (System Management Mode), the CPU will incorrectly update
the LBR (Last Branch Record) and the BTS (Branch Trace Store), hence rendering their
data invalid. The corresponding data if sent out as a BTM on the system bus will also be
incorrect.
Note: This issue would only occur when one of the 3 above mentioned debug support
facilities are used.
Implication: The value of the LBR, BTS, and BTM immediately after an RSM operation should not be
used.
Workaround: None identified
Status: For the steppings affected, see the Summary Table of Changes.
BD9. Single Step Interrupts with Floating Point Exception Pending May Be
Mishandled
Problem: In certain circumstances, when a floating point exception (#MF) is pending during
single-step execution, processing of the single-step debug exception (#DB) may be
mishandled.
Implication: When this erratum occurs, #DB will be incorrectly handled as follows:
• #DB is signaled before the pending higher priority #MF (Interrupt 16)
• #DB is generated twice on the same instruction
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 23
Specification Update August 2013
BD10. Fault on ENTER Instruction May Result in Unexpected Values on Stack
Frame
Problem: The ENTER instruction is used to create a procedure stack frame. Due to this erratum,
if execution of the ENTER instruction results in a fault, the dynamic storage area of the
resultant stack frame may contain unexpected values (that is, residual stack data as a
result of processing the fault).
Implication: Data in the created stack frame may be altered following a fault on the ENTER
instruction. Please refer to "Procedure Calls For Block-Structured Languages" in
Intel® 64 and IA-32 Architectures Software Developer's Manual, Volume 1: Basic
Architecture, for information on the usage of the ENTER instructions. This erratum is
not expected to occur in ring 3. Faults are usually processed in ring 0 and stack switch
occurs when transferring to ring 0. Intel has not observed this erratum on any
commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD11. IRET under Certain Conditions May Cause an Unexpected Alignment
Check Exception
Problem: In IA-32e mode, it is possible to get an Alignment Check Exception (#AC) on the IRET
instruction even though alignment checks were disabled at the start of the IRET. This
can only occur if the IRET instruction is returning from CPL3 code to CPL3 code. IRETs
from CPL0/1/2 are not affected. This erratum can occur if the EFLAGS value on the
stack has the AC flag set, and the interrupt handler's stack is misaligned. In IA-32e
mode, RSP is aligned to a 16-byte boundary before pushing the stack frame.
Implication: In IA-32e mode, under the conditions given above, an IRET can get a #AC even if
alignment checks are disabled at the start of the IRET. This erratum can only be
observed with a software generated stack frame.
Workaround: Software should not generate misaligned stack frames for use with IRET.
Status: For the steppings affected, see the Summary Table of Changes.
BD12. General Protection Fault (#GP) for Instructions Greater than 15 Bytes
May be Preempted
Problem: When the processor encounters an instruction that is greater than 15 bytes in length, a
#GP is signaled when the instruction is decoded. Under some circumstances, the #GP
fault may be preempted by another lower priority fault (for example, Page F au lt (#PF)).
However, if the preempting lower priority faults are resolved by the operating system
and the instruction retried, a #GP fault will occur.
Implication: Software may observe a lower-priority fault occurring before or in lieu of a #GP fault.
Instructions of greater than 15 bytes in length can only occur if redundant prefixes are
placed before the instruction.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD13. General Protection (#GP) Fault May Not Be Signaled on Data Segment
Limit Violation above 4-G Limit
Problem: In 32-bit mode, memory accesses to flat data segments (base = 00000000h) that
occur above the 4G limit (0ffffffffh) may not signal a #GP fault.
Intel® Xeon® Processor 5600 Series 24
Specification Update August 2013
Implication: When such memory accesses occur in 32-bit mode, the system may not issue a #GP
fault.
Workaround: Software should ensure that memory accesses in 32-bit mode do not occur above the
4G limit (0ffffffffh).
Status: For the steppings affected, see the Summary Table of Changes.
BD14. LBR, BTS, BTM May Report a Wrong Address when an Exception/
Interrupt Occurs in 64-bit Mode
Problem: An exception/interrupt event should be transparent to the LBR (Last Branch Record),
BTS (Branch Trace Store) and BTM (Branch Trace Message) mechanisms. However,
during a specific boundary condition where the exception/interrupt occurs right after
the execution of an instruction at the lower canonical boundary (0x00007 FFFFFFF FFFF)
in 64-bit mode, the LBR return registe rs will save a wrong return address wi th bits 63
to 48 incorrectly sign extended to all 1's. Subsequent BTS and BTM operations which
report the LBR will also be incorrect.
Implication: LBR, BTS and BTM may report incorrect information in the event of an exception/
interrupt.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD15. MCi_Status Overflow Bit May Be Incorrectly Set on a Single Instance
of a DTLB Error
Problem: A single Data Translation Look Aside Buffer (DTLB) error can incorrectly set the
Overflow (bit [62]) in the MCi_Status register. A DTLB error is indicated by MCA error
code (bits [15:0]) appearing as binary value, 000x 0000 0001 0100, in t he MCi_Status
register.
Implication: Due to this erratum , the Overflow bit in the MCi_Status register may not be an accur ate
indication of multiple occurrences of DTLB errors. There is no other impact to normal
processor functionality.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD16. Debug Exception Flags DR6.B0-B3 Flags May be Incorrect for Disabled
Breakpoints
Problem: When a debug exception is signaled on a load that crosses cache lines with data
forwarded from a store and whose corresponding breakpoint enable flags are disabled
(DR7.G0-G3 and DR7.L0-L3), the DR6.B0-B3 flags may be incorrect.
Implication: The debug exception DR6.B0-B3 flags may be incorrect for the load if the
corresponding breakpoint enable flag in DR7 is disabled.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD17. MONITOR or CLFLUSH on the Loca l XAPIC's Address Space Results in
Hang
Problem: If the target linear address range for a MONITOR or CLFLUSH is mapped to the local
xAPIC's address space, the processor will hang.
Implication: When this erratum occurs, the processor will hang. The local xAPIC's address space
must be uncached. The MONITOR instruction only functions correctly if the specified
Intel® Xeon® Processor 5600 Series 25
Specification Update August 2013
linear address range is of the type write-back. CLFLUSH flushes data from the cache.
Intel has not observed this erratum with any commercially available software.
Workaround: Do not execute MONITOR or CLFLUSH instructions on the local xAPIC address space.
Status: For the steppings affected, see the Summary Table of Changes.
BD18. Corruption of CS Segment Register During RSM While Transitioning
From Real Mode to Protected Mode
Problem: During the transition from real mode to protected mode, if an SMI (System
Management Interrupt) occurs between the MOV to CR0 that sets PE (Protection
Enable, bit 0) and the first FAR JMP, the subsequent RSM (Resume from System
Management Mode) may cause the lower two bits of CS segment register to be
corrupted.
Implication: The corruption of the bottom two bits of the CS segment register will have no impact
unless software explicitly examines the CS segment register between enabling
protected mode and the first FAR JMP. Intel® 64 and IA-32 Architectures Software
Developer’s Manual Volume 3A: System Programming Guide, Part 1, in the section
titled "Switching to Protected Mode" recommends the FAR JMP i mmediately follows the
write to CR0 to enable protected mode. Intel has not observed this erratum with any
commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD19. A VM Exit on MWAIT May Incorrectly Report the Monitoring Hardware
as Armed
Problem: A processor write to the address range armed by the MONITOR instruction may not
immediately trigger the monitoring hardware. Consequently, a VM exit on a later
MWAIT may incorrectly report the monitoring hardware as armed, when it should be
reported as unarmed due to the write occurring prior to the MWAIT.
Implication: If a write to the range armed by the MONITOR instruction occurs between the
MONITOR and the MWAIT, the MWAIT instruction may start executing before the
monitoring hardware is triggered. If the MWAIT instruction causes a VM exit, this could
cause its exit qualification to incorrectly report 0x1. In the recommended usage model
for MONITOR/MWAIT, there is no write to the range armed by the MONITOR instruction
between the MONITOR and the MWAIT.
Workaround: Software should never write to the address range armed by the MONITOR instruction
between the MONITOR and the subsequent MWAIT.
Status: For the steppings affected, see the Summary Table of Changes.
BD20. Performance Monitor Event SEGMENT_REG_LOADS Counts
Inaccurately
Problem: The performance monitor event SEGMENT_REG_LOADS (Event 06H) counts
instructions that load new values into segment registers. The v alue of the count ma y be
inaccurate.
Implication: The performance monitor event SEGMENT_REG_LOADS may reflect a count higher or
lower than the actual number of events.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 26
Specification Update August 2013
BD21. #GP on Segment Selector Descriptor that Straddles Canonical
Boundary May Not Provide Correct Exception Error Code
Problem: During a #GP (General Protection Ex ception), the processor pushes an error code on to
the exception handler’s stack. If the segment selector descriptor straddles the
canonical boundary, the error code pushed onto the stack may be incorrect.
Implication: An incorrect error code may be pushed onto the stack. Intel has not observed this
erratum with any commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD22. Improper Parity Error Signaled in the IQ Following Reset When a Code
Breakpoint is Set on a #GP Instruction
Problem: While coming out of cold reset or exiting from C6, if the processor encounters an
instruction longer than 15 bytes (which causes a #GP) and a code breakpoint is
enabled on that instruction, an IQ (Instruction Queue) parity error may be incorrectly
logged resulting in an MCE (Machine Check Exception).
Implication: When this erratum occurs, an MCE may be incorrectly signaled.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD23. An Enabled Debug Breakpoint or Single Step Trap May Be Taken after
MOV SS/POP SS Instruction if it is Followed by an Instruction That
Signals a Floating Point Exception
Problem: A MOV SS/POP SS instruction should inhibit all interrupts including debug breakpoints
until after execution of the following instruction. This is intended to allow the sequential
execution of MOV SS/POP SS and MOV [r/e]SP, [r/e]BP instructions without having an
inv alid stack during interrupt handling. However, an enabled debug breakpoint or single
step trap may be taken after MOV SS/POP SS if this instruction is followed by an
instruction that signals a floating point exception rather than a MOV [r/e]SP, [r/e]BP
instruction. This results in a debug exception being signaled on an unexpected
instruction boundary since the MOV SS/POP SS and the followi ng instruction should be
executed atomically.
Implication: This can result in incorrect signaling of a debug exception and possibly a mismatched
Stack Segment and Stack Pointer. If MOV SS/POP SS is not followed by a MOV [r/e ]SP,
[r/e]BP, there may be a mismatched Stack Segment and Stack Pointer on any
exception. Intel has not observed this erratum with any commercially available
software or system.
Workaround: As recommended in the Intel® 64 and IA-32 Intel® Architectures Software Developer’s
Manual, the use of MOV SS/POP SS in conjunction with MOV [r/e]SP, [r/e]BP will avoid
the failure since the MOV [r/e]SP, [r/e]BP will not generate a floating point exception.
Developers of debug tools should be aware of the potential incorrect debug event
signaling created by this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD24. IA32_MPERF Counter Stops Counting During On-Demand TM 1
Problem: According to the Intel® 64 and IA-32 Architectures Software Developer’s Manual
Volume 3A: System Programming Guide, the ratio of IA32_MPERF (MSR E7H) to
IA32_APERF (MSR E8H) should reflect actual performance while TM1 or on-demand
throttling is activ ated. Due to this err atu m, IA32_MPERF MSR stops counting while TM1
Intel® Xeon® Processor 5600 Series 27
Specification Update August 2013
or on-demand throttling is activated, and the ratio of the two will indicate higher
processor performance than actual.
Implication: The incorrect ratio of IA32_APERF/IA32_MPERF can mislead software P-state
(performance state) management algorithms under the conditions described above. It
is possible for the Operating S ystem to observ e higher processor utilization than actual,
which could lead the OS into raising the P-state. During TM1 activation, the OS P-state
request is irrelevant and while on-demand throttling is enabled, it is expected that the
OS will not be changing the P-state. This erratum should result in no practical
implication to software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD25. Intel® QuickPath Memory Controller May Hang Due to Uncorrectable
ECC Errors Occurring on Both Channels in Mirror Channel Mode
Problem: If an uncorrectable ECC error or parity error occurs on the mirrored channel before an
uncorrectable ECC error or parity error on the other channel can be resolved, the Intel
QuickPath Memory Controller will hang without an uncorrectable ECC or parity error
being logged.
Implication: The processor may hang and not report the error when uncorrectable ECC or parity
errors occur in close proximity on both channels in a mirrored channel pair. No
uncorrectable ECC or parity error will be logged in the machine check banks.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD26. Simultaneous Correctable ECC Errors on Different Memory Channels
With Patrol Scrubbing Enabled May Result in Incorrect Information
Being Logged
Problem: When a correctable patrol scrub ECC error occurs simultaneously with a correctable
system read ECC error on different memory channels, IA32_MCi_STATUS and
IA32_MCi_MISC should log the system read error. Due to this erratum IA32_MCi_MISC
may incorrectly contain the patrol scrub error information and the IA32_MCi_ADDR
may not be correct.
Implication: IA32_MCi_MISC and IA32_MCi_STATUS information may be inconsistent.
IA32_MCi_ADDR may be incorrect.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD27. The Memory Controller tTHROT_OPREF Timings May be Violated
During Self Refresh Entry
Problem: During self refresh entry, the memory controller may issue more refreshes than
permitted by tTHROT_OPREF (bits 29:19 in MC_CHANNEL_{0,1,2}_REFRESH_TIMING
CSR).
Implication: The intention of tTHROT _OPREF is to limit current. Since current supply conditions near
self refresh entry are not critical, there is no measurable impact due to this erratum.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 28
Specification Update August 2013
BD28. Synchronous Reset of IA32_APERF/IA32_MPERF Counters on
Overflow Does Not Work
Problem: When either the IA32_MPERF or IA32_APERF MSR (E7H, E8H) increments to its
maximum value of 0xFFFF_FFFF_FFFF_FFFF, both MSRs are supposed to synchronously
reset to 0x0 on the next clock. This synchronous reset does not work. Instead, both
MSRs increment and overflow independently.
Implication: Software can not rely on synchronous reset of the IA32_APERF/IA32_MPERF registers.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD29. Disabling Thermal Monitor While Processor is Hot, Then Re-enabling,
May Result in Stuck Core Operating Ratio
Problem: If a processor is at its TCC (Thermal Control Circuit) activation temperature and then
Thermal Monitor is disabled by a write to IA 32_MISC_ENABLES MSR (1A0H) bit [3], a
subsequent re-enable of Thermal Monitor will result in an artificial ceiling on the
maximum core P-state. The ceiling is based on the core frequency at the time of
Thermal Monitor disable. This condition will only correct itself once the processor
reaches its TCC activation temperature again.
Implication: Since Intel requires that Thermal Monitor be enabled in order to be operating within
specification, this erratum should never be seen during normal operation.
Workaround: Software should not disable Thermal Monitor during processor operation.
Status: For the steppings affected, see the Summary Table of Changes.
BD30. Writing the Local Vector Table (LVT) when an Interrupt is Pending
May Cause an Un expected Interrup t
Problem: If a local interrupt is pending when the LVT entry is written, an interrupt may be taken
on the new interrupt vector even if the mask bit is set.
Implication: An interrupt may immediately be generated with the new vector when a LVT entry is
written, even if the new LVT entry has the mask bit set. If there is no Interrupt Service
Routine (ISR) set up for that vector the system will GP fault. If the ISR does not do an
End of Interrupt (EOI) the bit for the v ector will be left set in the in-service register and
mask all interrupts at the same or lower priority.
Workaround: Any vector programmed into an LVT entry must have an ISR associated with it, even if
that vector was programmed as masked. This ISR routine must do an EOI to clear any
unexpected interrupts that may occur. The ISR associated with the spurious vector
does not generate an EOI, therefore the spurious vector should not be used when
writing the LVT.
Status: For the steppings affected, see the Summary Table of Changes.
BD31. Faulting MMX Instruction May Incorrectly Update x87 FPU Tag Word
Problem: Under a specific set of conditions, MMX stores (MOVD, MOVQ, MOVNTQ, MASKMOVQ)
which cause memory access faults (#GP, #SS, #PF, or #AC), may incorrectly update
the x87 FPU tag word regist er.
This erratum will occur when the following additional conditions are also met.
• The MMX store instruction must be the first MMX instruction to operate on x87 FPU
state (that is, the x87 FP tag word is not already set to 0x0000).
Intel® Xeon® Processor 5600 Series 29
Specification Update August 2013
• For MOVD, MOVQ, MOVNTQ stores, the instruction must use an addressing mode
that uses an index register (this condition does not apply to MASKMOVQ).
Implication: If the erratum conditions are met, the x87 FPU tag word register may be incorrectly set
to a 0x0000 value when it should not have been modified.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD32. xAPIC Timer May Decrement Too Quickly Following an Automatic
Reload While in Periodic Mode
Problem: When the xAPIC Timer is automatically reloaded by counting down to zero in periodic
mode, the xAPIC Timer may slip in its synchronization with the external clock. The
xAPIC timer may be shortened by up to one xAPIC timer tick.
Implication: When the xAPIC Timer is automatically reloaded by counting down to zero in periodic
mode, the xAPIC Timer may slip in its synchronization with the external clock. The
xAPIC timer may be shortened by up to one xAPIC timer tick.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD33. Rep orted Memory Type May Not Be Used to Access the VMCS and
Referenced Data Structures
Problem: Bits 53:50 of the IA32_VMX_BASIC MSR report the memory type that the processor
uses to access the VMCS and data structures referenced by pointers in the VMCS. Due
to this erratum, a VMX access to the VMCS or referenced data structures will instead
use the memory type that the MTRRs (memory-type range registers) specify for the
physical address of the access.
Implication: Bits 53:50 of the IA32_VMX_BASIC MSR report that the WB (write-back) memory type
will be used but the processor may use a different memory type.
Workaround: Software should ensure that the VMCS and referenced data structures are located at
physical addresses that are mapped to WB memory type by the MTRRs.
Status: For the steppings affected, see the Summary Table of Changes.
BD34. B0-B3 Bits in DR6 For Non-Enabled Breakpoints May be Incorrectly Set
Problem: Some of the B0-B3 bits (breakpoint conditions detect flags, bits [3:0]) in DR6 may be
incorrectly set for non-enabled breakpoints when the following sequence happens:
1. MOV or POP instruction to SS (Stack Segment) selector;
2. Next instruction is FP (Floating Point) that gets FP assist
3. Another instruction after the FP instruction completes successfully
4. A breakpoin t occurs due to eithe r a data breakpoint on the preceding instruction or
a code breakpoint on the next instruction.
Due to this erratum a non-enabled breakpoint triggered on step 1 or step 2 may be
reported in B0-B3 after the breakpoint occurs in step 4.
Implication: Due to this erratum, B0-B3 bits in DR6 may be incorrectly set for non-enabled
breakpoints.
Workaround: Software should not execute a floating point instruction directly after a MOV SS or POP
SS instruction.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 30
Specification Update August 2013
BD35. Core C6 May Clear Previously Logged TLB Errors
Problem: Following an exit from core C6, previously logged TLB (Translation Lookaside Buffer)
errors in IA32_MCi_STATUS may be cleared.
Implication: Due to this erratum, TLB errors logged in the associated machine check bank prior to
core C6 entry may be cleared. Provided machine check exceptions are enabled, the
machine check exception handler can log any uncorrectable TLB errors prior to core C6
entry. The TLB marks all detected errors as uncorrectable.
Workaround: As long as machine check exceptions are enabled, the machine check exception
handler can log the TLB error prior to core C6 entry. This will ensure the error is logged
before it is cleared.
Status: For the steppings affected, see the Summary Table of Changes.
BD36. Changing the Memory Type for an In-Use Page Translation May Lead
to Memory-Ordering Violations
Problem: Under complex micro-architectural conditions, if softw are changes the memory type for
data being actively used and shared by multiple threads without the use of semaphores
or barriers, software may see load operations execute out of order.
Implication: Memory ordering may be violated. Intel has not observed this erratum with any
commercially available software.
Workaround: Software should ensure pages are not being actively used before requesting their
memory type be changed.
Status: For the steppings affected, see the Summary Table of Changes.
BD37. A String Instruction that Re-maps a Page May Encounter an
Unexpected Page Fault
An unexpected page fault (#PF) may occur for a page under the following conditions:
• The paging structures initially specify a valid translation for the page.
• Software modifies the paging structures so that there is no v alid tr anslation for the
page (for example, by clearing to 0 the present bit in one of the paging-structure
entries used to translate the page).
• An iteration of a string instruction modifies the paging structures so that the
translation is again a valid tr anslation for the page (e.g., by setting to 1 the bit that
was cleared earlier).
• A later iteration of the same string instruction loads from a linear address on the
page.
Problem: Software did not invalidate TLB entries for the page between the first modification of
the paging structures and the string instruction. In this case, the load in the later
iteration may cause a page fault that indicates that there is no translation for the page
(for example, with bit 0 clear in the page-fault error code, indicating that the fault was
caused by a not-present page).
Implication: Software may see an unexpected page fault that indicates that there is no translation
for the page. Intel has not observed this erratum with any commercially available
software or system.
Workaround: Software should not update the paging structures with a string instruction that
accesses pages mapped the modified paging structures.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 31
Specification Update August 2013
BD38. Infinite Stream of Interrupts May Occur if an ExtINT Delivery Mode
Interrupt is Received while All Cores in C6
Problem: If all logical processors in a core are in C6, an ExtINT delivery mode interrupt is
pending in the xAPIC and interrupts are blocked with EFLAGS.IF=0, the interrupt will
be processed after C6 wakeup and after interrupts are re-enabled (EFLAGS.IF=1).
However, the pending interrupt event will not be cleared.
Implication: Due to this erratum, an infinite stream of interrupts will occur on the core servicing the
external interrupt. Intel has not observed this erratum with any commercially available
software/system.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD39. Two xAPIC Timer Event Interrupts May Unexpectedly Occur
Problem: If an xAPIC timer event is enabled and while counting down the current count reaches
1 at the same time that the processor thread begins a transition to a low power C-
state, the xAPIC may generate two interrupts instead of the expected one when the
processor returns to C0.
Implication: Due to this erratum, two interrupts may unexpectedly be generated by an xAPIC timer
event.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD40. EOI Transaction May Not be Sent if Software Enters Core C6 During an
Interrupt Service Routine
Problem: If core C6 is entered after the start of an interrupt service routine but before a write to
the APIC EOI (End of Interrupt) register, and the core is woken up by an event other
than a fixed interrupt source the core ma y drop the EOI transaction the next time APIC
EOI register is written and further interrupts from the same or lower priority level will
be blocked.
Implication: EOI transactions and interrupts may be blocked when core C6 is used during interrupt
service routines. Intel has not observed this erratum with any commercially available
software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD41. FREEZE_WHILE_SMM Does Not Prevent Event From Pending PEBS
During SMM
Problem: In general, a PEBS record should be generated on the first count of the event after the
counter has overflowed. However, IA32_DEBUGCTL_MSR.FREEZE_WHILE_SMM (MSR
1D9H, bit [14]) prevents performance counters from counting during SMM (System
Management Mode). Due to this erratum, if
1. A performance counter overflowed before an SMI
2. A PEBS record has not yet been generated because another count of th e ev ent has
not occurred
3. The monitored event occurs during SMM
then a PEBS record will be saved after the next RSM instruction.
Intel® Xeon® Processor 5600 Series 32
Specification Update August 2013
When FREEZE _ WH I LE _S M M i s se t, a PEBS should not be generated until the event
occurs outside of SMM.
Implication: A PEBS record may be saved after an RSM instruction due to the associated
performance counter detecting the monitored event during SMM; even when
FREEZE _W H I LE_SMM is set.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD42. APIC Error “Received Illegal Vector” May be Lost
Problem: APIC (Advanced Programmable Interrupt Controller) may not update the ESR (Error
Status Register) flag R eceived Illegal Vector bit [6] properly when an illegal vector error
is received on the same internal clock that the ESR is being written (as part of the
write-read ESR access flow). The corresponding error interrupt will also not be
generated for this case.
Implication: Due to this erratum, an incoming illegal vector error may not be logged into ESR
properly and may not generate an error interrupt.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD43. DR6 May Contain Incorrect Information When the First Instruction
After a MOV SS,r/m or POP SS is a Store
Problem: Normally, each instruction clears the changes in DR6 (Debug Status Register) caused
by the previous instruction. However, the instruction following a MOV SS,r/m (MOV to
the stack segment selector) or POP SS (POP stack segment selector) instruction will
not clear the changes in DR6 because data breakpoints are not tak en immediately after
a MOV SS,r/m or POP SS instruction. Due to this erratum, any DR6 changes caused by
a MOV SS,r/m or POP SS instruction may be cleared if the following instruction is a
store.
Implication: When this erratum occurs, incorrect information may exist in DR6. This erratum will not
be observed under normal usage of the MOV SS,r/m or POP SS instructions (that is,
following them with an instruction that writes [e/r]SP). When debugging or when
developing debuggers, this behavior should be noted.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD44. An Uncorrectable Error Logged in IA32_CR_MC2_STATUS May also
Result in a System Hang
Problem: Uncorrectable errors logged in IA32_CR_MC2_STATUS MSR (409H) may also result in a
system hang causing an Internal Timer Error (MCACOD = 0x0400h) to be logged in
another machine check bank (IA32_MCi_STATUS).
Implication: Uncorrectable errors logged in IA32_CR_MC2_ST ATUS can further cause a system hang
and an Internal Timer Error to be logged.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD45. IA32_PERF_GLOBAL_CTRL MSR May be Incorrectly Initialized
Problem: The IA32_PERF_GLOBAL_CTRL MSR (38FH) bits [34:32] may be incorrectly set to 7H
after reset; the correct value should be 0H.
Intel® Xeon® Processor 5600 Series 33
Specification Update August 2013
Implication: The IA32_PERF_GLOBAL_CTRL MSR bits [34:32] may be incorrect after reset
(EN_FIXED_CTR{0, 1, 2} may be enabled).
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD46. ECC Errors Can Not be Injected on Back-to-Back Writes
Problem: ECC errors should be injected on every write that matches the address set in the
MC_CHANNEL_{0,1,2}_ADDR_MATCH CSRs. Due to this erratum if there are two back-
to-back writes that match MC_CHANNEL_{0,1,2}_ADDR_MAT CH, the 2nd write will not
have the error injected.
Implication: The 2nd back-to-back write that matches MC_CHANNEL_{0,1,2}_ADDR_MATCH will
not have the ECC error properly injected. Setting
MC_CHANNEL_{0,1,2}_ADDR_MATCH to a specific address will reduce the chance of
being impacted by this erratum.
Workaround: Only injecting errors to specific address should reduce the chance on being impacted by
this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD47. P erformance Monitor C ounter INST_RETIRED.STORES May Count
Higher than Expected
Problem: Performance Monitoring counter INST_RETIRED.STORES (Event: C0H) is used to track
retired instructions which contain a store operation. Due to this erratum, the processor
may also count other types of instructions including WRMSR and MFENCE.
Implication: P erformance Monitoring counter INST_RETIRED.STO RES may report counts higher than
expected.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD48. Sleeping Cores May Not be Woken Up on Logical Cluster Mode
Broadcast IPI Using Destination Field Instead of Shorthand
Problem: If software sends a logical cluster broadcast IPI using a destination shorthand of 00B
(No Shorthand) and writes the cluster portion of the Destination Field of the Interrupt
Command Register to all ones while not using all 1s in the mask portion of the
Destination Field, target cores in a sleep state that are identified by the mask portion of
the Destination Field may not be woken up. This erratum does not occur if the
destination shorthand is set to 10B (All Including Self) or 11B (All Excluding Self).
Implication: When this erratum occurs, cores which are in a sleep state may not wake up to handle
the broadcast IPI. Intel has not observed this erratum with any commercially available
software.
Workaround: Use destination shorthand of 10B or 11B to send broadcast IPIs.
Status: For the steppings affected, see the Summary Table of Changes.
BD49. Faulting Executions of FXRSTOR May Update State Inconsistently
Problem: The state updated by a faulting FXRSTOR instruction may vary from one execution to
another.
Intel® Xeon® Processor 5600 Series 34
Specification Update August 2013
Implication: Software that relies on x87 state or SSE state following a faulting execution of
FXRSTOR may behave inconsistently.
Workaround: Software handling a fault on an execution of FXRSTOR can compensate for execution
variability by correcting the cause of the fault and executing FXRSTOR again.
Status: For the steppings affected, see the Summary Table of Changes.
BD50. Failing DIMM ID May be Incorrect in the 2DPC Configuration When
Mirroring is Enabled
Problem: When redundancy is lost in the 2DPC (2 DIMMs Per Channel) configuration,
MC_SMI_SPARE_DIMM_ERROR_STATUS CSR bits [13:12]
(REDUNDANCY_LOSS_FAILING_DIMM) may indicate the incorrect failing DIMM ID. The
2DPC configuration is indicated when MC_CHANNEL_{0,1}_DIMM_INIT_PARAMS CSR
bit [24] (THREE_DIMMS_PRESENT) is 0.
Implication: The failing DIMM ID may be reported incorrectly in the 2DPC configuration when
mirroring is enabled. The 3DPC configuration is not affected.
Workaround: Only use the value in bit [13] to determine the failing DIMM ID in the non-3PDC
configurations when mirroring is enabled. This workaround will show correct results for
both the 1DPC and 2DPC configurations.
Status: For the steppings affected, see the Summary Table of Changes.
BD51. ISSUEON CE Bit in MC_SCRUB_CONTROL Re gister Does Not Work
Correctly
Problem: When ISSUEONCE (bit [25]) in the MC_SCRUB_CONTROL register (Device 3, Function
2, Offset 4CH) is set, the memory controller should issue one patrol scrub. Due to this
erratum, scrubbing requests continue to be issued.
Implication: ISSUEONCE bit in MC_SCRUB_CONTROL register does not work correctly.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD52. Memory Aliasing of Code Pages May Cause Unpredictable System
Behavior
Problem: The type of memory aliasing contributing to this erratum is the case where two
different logical processors have the same code page mapped with two different
memory types. Specifically, if one code page is mapped by one logical processor as
write-back and by another as uncacheable and certain instruction fetch timing
conditions occur, the system may experience unpredictable behavior.
Implication: The type of memory aliasing contributing to this erratum is the case where two
different logical processors have the same code page mapped with two different
memory types. Specifically, if one code page is mapped by one logical processor as
write-back and by another as uncacheable and certain instruction fetch timing
conditions occur, the system may experience unpredictable behavior.
Workaround: Code pages should not be mapped with uncacheable and cacheable memory types at
the same time.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 35
Specification Update August 2013
BD53. Performance Monitor Counters May Count Incorrectly
Problem: Under certain circumstances, a general purpose performance counter, IA32_PMC0-4
(C1H – C4H), may count at core frequency or not count at all instead of counting the
programmed event.
Implication: The Performance Monitor Counter IA32_PMCx may not properly count the programmed
event. Due to the requirements of the workaround there may be an interruption in the
counting of a previously programmed event during the programming of a new event.
Workaround: Before programming the performance event select registers, IA32_PERFEVTSELx MSR
(186H – 189H), the internal monitoring hardware must be cleared. This is
accomplished by first disabling, saving valid events and clearing from the select
registers, then programming three event values 0x4300D2, 0x4300B1 and 0x4300B5
into the IA32_PERFEVTSELx MSRs, and finally continuing with new event programming
and restoring previous programming if necessary. Each performance counter,
IA32_PMCx, must have its corresponding IA 32_PREFEVT SELx MSR p rogramm ed with at
least one of the event values and must be enabled in IA32_PERF_GLOBAL_CTRL MSR
(38FH) bits [3:0]. All three values must be written to either the same or different
IA32_PERFEVTSELx MSRs before programming the performance counters. Note that
the performance counter will not increment when its IA32_PERFEVTSELx MSR has a
value of 0x4300D2, 0x4300B1 or 0x4300B5 because those values have a zero UMASK
field (bits [15:8]).
Status: For the steppings affected, see the Summary Table of Changes.
BD54. Memory Thermal Throttling May Not Work as Expected in Lockstep
Channel Mode
Problem: Thermal Throttling on a channel that is in lockstep mode affects all channels in order to
maintain lockstep requirements. If throttling parameters are modified at different times
during runtime, throttling on one channel is likely to be out of phase with throttling on
other channels. Throttling which is out of phase will result in more throttling than
anticipated. If the throttling duty cycle exceeds 50%, certain phase relationships can
result in persistent memory traffic blockage.
Implication: Runtime modification of throttling parameters may result in a system hang.
Workaround: Since Thermal Throttling on one channel affects all channels while in lockstep mode,
throttling should only be applied to one channel.
Status: For the steppings affected, see the Summary Table of Changes.
BD55. Simultaneous Accesses to the Processor via JTAG and PECI May Cause
Unexpected Behavior
Problem: JTAG commands that are executed at the same time as a PECI (Platform Environment
Control Interface) access may cause unexpected behavior. In addition the PECI
command may take longer to complete or may not complete.
Implication: The processor could be left in an unexpected state and any software or firmware doing
PECI writes may time out.
Workaround: Ensure that PECI commands are not executed while using JTAG.
Status: For the steppings affected, see the Summary Table of Changes.
BD56. Performance Monitor Event Offcore_response_0 (B7H) Does Not
Count NT Stores to Local DRAM Correctly
Problem: When a IA32_PERFEVTSELx MSR is programmed to count the Offcore_response_0
event (Event:B7H), selections in the OFFCORE_RSP_0 MSR (1A6H) determine what is
Intel® Xeon® Processor 5600 Series 36
Specification Update August 2013
counted. The following two selections do not provide accur ate counts when counting NT
(Non-Temporal) Stores:
• OFFCORE_RSP_0 MSR bit [14] is set to 1 (LOCAL_DRAM) and bit [7] is set to 1
(OTHER): NT Stores to Local DRAM are not counted when they should have been.
OFFCORE_RSP_0 MSR bit [9] is set to (OTHER_CORE_HIT_SNOOP) and bit [7] is set to
1 (OTHER): NT Stores to Local DRAM are counted when they should not have been.
Implication: The counter for the Offcore_response_0 event may be incorrect for NT stores.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD57. EFLAGS Discrepancy on Page Faults and on EPT-Induced VM Exits
after a Translation Change
Problem: This erratum is regarding the case where paging structures are modified to change a
linear address from writable to non-writable without software performing an
appropriate TLB invalidation. When a subsequent access to that address by a specific
instruction (ADD, AND, BTC, BTR, BTS, CMPXCHG, DEC, INC, NEG, NOT, OR, ROL/ROR,
SAL/SAR/SHL/SHR, SHLD, SHRD , SUB, XOR, and XADD) causes a page fault or an EPT-
induced VM exit, the v alue saved for EFLAGS ma y incorrectly contain the arithmetic flag
values that the EFLAGS register would have held had the instruction completed without
fault or VM exit. For page faults, this can occur even if the fault causes a VM exit or if
its delivery causes a nested fault.
Implication: None identified. Although the EFLAGS value saved by an affected event (a page fault or
an EPT-induced VM exit) may contain incorrect arithmetic flag values, Intel has not
identified software that is affected by this erratum. This erratum will have no further
effects once the original instruction is restarted because the instruction will produce the
same results as if it had initially completed without fault or VM exit.
Workaround: If the handler of the affected events inspects the arithmetic portion of the saved
EFLAGS value, then system software should perform a synchronized paging structure
modification and TLB invalidation.
Status: For the steppings affected, see the Summary Table of Changes.
BD58. System May Hang if
MC_CHANNEL_{0,1,2}_MC_DIMM_INIT_CMD.DO_ZQCL Commands
Are Not Issued in Increasing Populated DDR3 Rank Order
Problem: ZQCL commands are used during initialization to calibrate DDR3 termination. A ZQCL
command can be issued by writing 1 to the
MC_CHANNEL_{0,1,2}_MC_DIMM_INIT_CMD.DO_ZQCL (Device 4,5,6, Function 0,
Offset 15, bit[15]) field and it targets the DDR3 rank specified in the RANK field
(bits[7:5]) of the same register. If the ZQCL commands are not issued in increasing
populated rank order then ZQ calibration may not complete, causing the system to
hang.
Implication: Due to this erratum the system may hang if writes to the
MC_CHANNEL_{0,1,2}_MC_DIMM_INIT_CMD.DO_ZQCL field are not in increasing
populated DDR3 rank order.
Workaround: A BIOS code change has been identified and may be implemented as a workaround for
this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 37
Specification Update August 2013
BD59. Package C3/C6 Transitions When Memory 2x Refresh is Enabled May
Result in a System Hang
Problem: If ASR_PRESENT (MC_CHANNEL_{0,1,2}_REFRESH_THROTTLE_SUP PORT CSR
function 0, offset 68H, bit [0], Auto Self Refresh Present) is clear which indicates that
high temperature operation is not supported on the DRAM, the memory controller will
not enter self-refresh if software has REF_2X_NOW (bit 4 of the MC_CLOSED_LOOP
CSR, function 3, offset 84H) set. This scenario may cause the system to hang during
C3/C6 entry.
Implication: Failure to enter self-refresh can delay C3/C6 power state transitions to the point that a
system hang may result with CATERR being asserted. REF_2X_NOW is used to double
the refresh rate when the DRAM is operating in extended temperature range. The
ASR_PRESENT was intended to allow low power self refresh with DRAM that does not
support automatic self refresh.
Workaround: It is possible for Intel provided BIOS reference code to contain a workaround for this
erratum. Please refer to the latest version of the BIOS memory Reference Code and
release notes.
Status: For the steppings affected, see the Summary Table of Changes.
BD60. Back to Back Uncorrected Machine Check Errors May Overwrite
IA32_MC3_STATUS.MSCOD
Problem: When back-to-back uncorrected machine check errors occur that would both be logged
in the IA32_MC3_STATUS MSR (40CH), the IA32_MC3_STATUS.MSCOD (bits [31:16])
field may reflect the status of the most recent error and not the first error. The rest of
the IA32_MC3_STATUS MSR contains the information from the first error.
Implication: Software should not rely on the value of IA32_MC3_STATUS.MSCOD if
IA32_MC3_STATUS.OVER (bit [62]) is set.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD61. Corrected Errors With a Yellow Error Indication May be Overwritten by
Other Corrected Errors
Problem: A corrected cache hierarchy data or tag error that is reported with
IA32_MCi_STATUS.MCACOD (bits [15:0]) with value of 000x_0001_xxxx_xx01 (where
x stands for zero or one) and a yellow threshold-based error status indication (bits
[54:53] equal to 10B) may be overwritten by a corrected error with a no tracking
indication (00B) or green indication (01B).
Implication: Corrected errors with a yellow threshold-based error status indication may be
overwritten by a corrected error without a yellow indication.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD62. Performance Monitor Events DCACHE_CACHE_LD and
DCACHE_CACHE_ST May Overcount
Problem: The performance monitor events DCACHE_CACHE_LD (Event 40H) and
DCACHE_CACHE_ST (Event 41h) count cacheable loads and stores that hit the L1
cache. Due to this erratum , in addition to counting the completed loads and stores, the
counter will incorrectly count speculative loads and stores that were aborted prior to
completion.
Intel® Xeon® Processor 5600 Series 38
Specification Update August 2013
Implication: The performance monitor events DCACHE_CACHE_LD and DCACHE_CACHE_ST may
reflect a count higher than the actual number of events.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD63. Performance Monitor Events INSTR_RETIRED and
MEM_INST_RETIRED May Count Inaccurately
Problem: The performance monitor event INSTR_RETIRED (Event C0H) should count the number
of instructions retired, and MEM_INST_ RETIRED (Event 0BH) should count the number
of load or store instructions retired. However, due to this erratum, they may
undercount.
Implication: The performance monitor event INSTR_RET IRED and MEM_INST_RETIRED may reflect
a count lower than the actual number of events.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD64. A Page Fault May Not be Generated When the PS bit is set to "1" in a
PML4E or PDPTE
Problem: On processors supporting Intel® 64 architecture, the PS bit (Page Size, bit 7) is
reserved in PML4Es and PDPTEs. If the translation of the linear address of a memory
access encounters a PML4E or a PDPTE with PS set to 1, a page fault should occur. Due
to this erratum, PS of such an entry is ignored and no page fault will occur due to its
being set.
Implication: Software may not operate properly if it relies on the processor to deliver page faults
when reserved bits are set in paging-structure entries.
Workaround: Software should not set bit 7 in any PML4E or PDPTE that has Present Bi t (Bit 0) set to
"1".
Status: For the steppings affected, see the Summary Table of Changes.
BD65. Uncacheable Access to a Monitored Ad dress Range May Prevent
Future Triggering of the Monitor Hardware
Problem: It is possible that an address range which is being monitored via the MONITOR
instruction could be written without triggering the monitor hardware. A read from the
monitored address range which is issued as uncacheable (for example having the
CR0.CD bit set) may prevent subsequent writes from triggering the monitor hardware.
A write to the monitored address range which is issued as uncacheable, may not trigger
the monitor hardware and may prevent subsequent writes from triggering the monitor
hardware.
Implication: The MWAIT instruction will not exit the optimized power state and resume progr am flow
if the monitor hardware is not triggered.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD66. Intel® Interconnect BIST (Intel® IBIST) Results May be Additionally
Reported After a GETSEC[WAKEUP] or INIT-SIPI Sequence
Problem: BIST results should only be reported in EAX the first time a logical processor wakes up
from the Wait-For-SIPI state. Due to this erratum, Intel® Interconnect BIST (Intel®
Intel® Xeon® Processor 5600 Series 39
Specification Update August 2013
IBIST) Intel results may be additionally reported after INIT-SIPI sequences and when
waking up RLP’s from the SENTER sleep state using the GETSEC[WAKEIUP] command.
Implication: An INIT-SIPI sequence may show a non-zero value in EAX upon wakeup when a zero
value is expected. RLP’s waking up for the SENTER sleep state using the
GETSEC[WAKEUP] command may show a different value in EAX upon wakeup than
before going into the SENTER sleep state.
Workaround: If necessary software may save the value in EAX prior to launching into the secure
environment and restore upon wakeup and/or clear EAX after the INIT-SIPI sequence.
Status: For the steppings affected, see the Summary Table of Changes.
BD67. Pending x87 FPU Exceptions (#MF) May be Signaled Earlier Than
Expected
Problem: x87 instructions that trigger #MF normally service interrupts before the #MF. Due to
this erratum, if an instruction that triggers #MF is executed while Enhanced Intel
SpeedStep® Technology transitions, Intel® Turbo Boost Technology transitions, or
Thermal Monitor events occur, the pending #MF may be signaled before pending
interrupts are serviced.
Implication: Software may be observed #MF being-signaled before pending interrupts are serviced.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD68. VM Exits Due to “NMI-Window Exiting” May Be Delayed by One
Instruction
Problem: If VM entry is executed with the “NMI-window exiting” VM-execution control set to 1, a
VM exit with exit reason “NMI window” should occur before execution of any instruction
if there is no virtual-NMI blocking, no blocking of events by MOV SS, and not blocking
of events by STR. If VM entry is made with no virtual-NMI blocking but with blocking of
events by either MOV SS or STI, such a VM exit should occur after execution of one
instruction in VMX non-root operation. Due to this err atum, the VM exit may be delayed
by one additional instruction.
Implication: VMM software using “NMI-window exiting” for NMI virutalization should generally be
unaffected, as the erratum causes at most a one-instruction delay in the injection of a
virtual NMI, which is virtually asynchronous. The erratum may affect VMMs relying on
deterministic delivery of the affected VM exits.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD69. Multiple Performance Monitor Interrupts are Possible on Overflow of
IA32_FIXED_CTR2
Problem: When multiple performance counters are set to generate interrupts on an overflow and
more than one counter overflows at the same time, only one interrupt should be
generated. However, if one of the counters set to generate an interrupt on overflow is
the IA32_FIXED_CTR2 (MSR 30BH) counter, multiple interrupts may be generated
when the IA32_FIXED_CTR2 overflows at the same time as any of the other
performance counters.
Implication: Multiple counter overflow interrupts may be unexpectedly generated.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 40
Specification Update August 2013
BD70. C-State Autodemotion May be too Aggressive Under Certain
Configurations and Workloads
Problem: The C-state autodemotion feature allows the processor to make intelligent power and
performance tradeoffs regarding the OS-requested C-state. Under certain operating
system and workload specific conditions, the C-state auto-demotion feature may be
overly aggressive in demoting OS C-sate requests to a C-sate with higher power and
lower exit latency.
Implication: This aggressive demotion can result in higher platform power under idle conditions.
Workaround: None identified
Status: For the steppings affected, see the Summary Table of Changes.
BD71. LBRs May Not be Initialized During Power-On Reset of the Processor
Problem: If a second reset is initiated during the power-on processor reset cycle, the LBRs (Last
Branch Re cords) may not be properly initialized.
Implication: Due to this erratum, debug software may not be able to rely on the LBRs out of power-
on reset.
Workaround: Ensure that the processor has completed its power-on reset cycle prior to initiating a
second reset.
Status: For the steppings affected, see the Summary Table of Changes.
BD72. Multiple Performance Monitor Interrupts are Possible on Overflow of
Fixed Counter 0
Problem: The processor can be configured to issue a PMI (performance monitor interrupt) upon
overflow of the IA32_FIXED_CTR0 MSR (309H). A single PMI should be observed on
overflow of IA32_FIXED_CTR0, however multiple PMIs are observed when this erratum
occurs. This erratum only occurs when IA32_FIXED_CTR0 overflows and the processor
and counter are configured as follows:
• Intel Hyper-Threading Technology is enabled
• IA32_FIXED_CTR0 local and global controls are enabled
• IA32_FIXED_CTR0 is set to count events only on its own thread
(IA32_FIXED_CTR_CTRL MSR (38DH) bits[2] = ‘0)
• PMIs are enabled on IA32_FIXED_CTR0 (IA32_FIXED_CTR_ CTRL MSR bit[3] = ‘1)
• Freeze_on_PMI feature is enabled (IA32_DEBUGCTL MSR (1D9H) bit[12] = ‘1)
Implication: When this erratum occurs there may be multiple PMIs observed when
IA32_FIXED_CTR0 overflows.
Workaround: Disable the FREEZE_PERFMON_ON_PMI feature in IA32_DEBUGCTL MSR (1D9H)
bit[12].
Status: For the steppings affected, see the Summary Table of Changes.
BD73. VM Exits Due to LIDR/LGDT/SIDT/SGDT Do Not Report Correct
Operand Size
Problem: When a VM exit occurs due to a LIDT, LGDT, SIDT, or SGDT instruction with a 32-bit
operand, bit 11 of the VM-exit instruction information field should be set to 1. Due to
this erratum, this bit is instead cleared to 0 (indicating a 16-bit operand).
Intel® Xeon® Processor 5600 Series 41
Specification Update August 2013
Implication: Virtual-machine monitors cannot rely on bit 11 of the VM-exit instruction information
field to determine the operand size of the instruction causing the VM exit.
Workaround: Virtual-machine monitor software may decode the instruction to determine operand
size.
Status: For the steppings affected, see the Summary Table of Changes.
BD74. Performance Monitoring Events STORE_BLOCKS.NOT_STA and
STORE_BLOCKS.STA May Not Count Events Correctly
Problem: Performance Monitor Events STORE_BLOCKS.NOT_STA and STORE_BLOCKS.STA
should only increment the count when a load is blocked by a store. Due to this err atum,
the count will be incremented whenever a load hits a store, whether it is blocked or can
forward. In addition this event does not count for specific threads correctly.
Implication: If Intel Hyper-Threading Technology is disabled, the Performance Monitor events
STORE_BLOCKS.NOT_STA and STORE_BLOCKS.STA may indicate a higher occurrence
of loads blocked by stores than have actually occurred. If Intel Hyper-Threading
Technology is enabled, the counts of loads blocked by stores may be unpredictable and
they could be higher or lower than the correct count.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD75. Storage of PEBS Record Delayed Following Execution of MOV SS or STI
Problem: When a performance monitoring counter is configured for PEBS (Precise Event Based
Sampling), overflow of the counter results in storage of a PEBS record in the PEBS
buffer. The information in the PEBS record represents the state of the next instruction
to be executed following the counter overflow. Due to this erratum, if the counter
overflow occurs after execution of either MOV SS or STI, storage of the PEBS record is
delayed by one instruction.
Implication: When this erratum occurs, software may observe storage of the PEBS record being
delayed by one instruction following execution of MOV SS or STI. The state information
in the PEBS record will also reflect the one instruction delay.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD76. Performance Monitoring Event FP_MMX_TRANS_TO_MMX May Not
Count Some Transitions
Problem: Performance Monitor Event FP_MMX_TRANS_TO_MMS (Event CCH, Umask 01H) counts
transitions from x87 Floating Point (FP) to MMXTM instructions. Due to this erratum, if
only a small number of MMX instructions (including EMMS) are executed immediately
after the last FP instruction, a FP to MMX transition may not be counted.
Implication: The count value for Performance Monitoring Event FP_MMX_TRANS_TO_MMX may be
lower than expected. The degree of undercounting is dependent on the occurrences of
the erratum condition while the counter is active. Intel has not observed this erratum
with any commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 42
Specification Update August 2013
BD77. The PECI Bus May be Tri-stated After System Reset
Problem: During power-up, the processor may improperly assert the PECI (Platform Environment
Control Interface) pin. This condition is cleared as soon as Bus Clock starts toggling.
However, if the PECI host (also referred to as the master or originator) incorrectly
determines this asserted state as another PECI host initiating a transaction, it may
release control of the bus resulting in a permanent tri-state condition.
Implication: Due to this erratum, the PECI host may incorrectly determine that it is not the bus
master and consequently PECI commands initiated by the PECI software layer may
receive incorrect/inv alid responses.
Workaround: To workaround this erratum the PECI host should pull the PECI bus low to initiate a
PECI transaction.
Status: For the steppings affected, see the Summary Table of Changes.
BD78. LER MSRs May Be Unreliable
Problem: Due to certain internal processor events, updates to the LER (Last Exception Record)
MSRs, MSR_LER_FROM_LIP (1DDH) and MSR_L ER_TO_LIP (1DEH), may happen when
no update was expected.
Implication: The values of the LER MSRs may be unreliable.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD79. APIC Timer CCR May Report 0 in Periodic Mode
Problem: In periodic mode the APIC timer CCR (current-count register) is supposed to be
automatically reloaded from the initial-count register when the count reaches 0,
consequently software would never be able to observe a value of 0. Due to this
erratum, softw are ma y read 0 from the CCR when the timer h as counted down and is in
the process of re-arming.
Implication: Due to this erratum, an unexpected value of 0 may be read from the APIC timer CCR
when in periodic mode.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD80. LBR, BTM or BTS Records May have Incorrect Branch From
Information After an Intel Enhanced SpeedStep Technology
Transition, T-states, C1E, or Adaptive Thermal Throttling
Problem: The “Form” address associated with the LBR (Last Branch Record), BTM (Branch Trace
Message) or BTS (Branch Trace Store) may be incorrect for the first branch after an
Enchanced Intel® SpeedStep Technology transition, T-states, C1E (C1 Enhanced), or
Adaptive Thermal Throttling.
Implication: When the LBRs, BTM or BTS are enabled, some records may have incorrect branch
“From” addresses for the first branch after an Enchanced Intel SpeedStep Technology
transition, T-states, C1E, or Adaptive Thermal Throttling.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 43
Specification Update August 2013
BD81. PEBS Records Not Created For FP-Assists Events
Problem: When a performance monitor counter is configured to count FP_ASSISTS (Event: F7H)
and to trigger PEBS (Precise Event Based Sampling), the processor does not create a
PEBS record when the counter overflows.
Implication: FP_ASSISTS events cannot be used for PEBS.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD82. MSR_TURBO_RATIO_LIMIT MSR May Return Intel® Turbo Boost
Technology Core Ratio Multipliers for Non-Existent Core
Configurations
Problem: MSR_TURBO_RATIO_LIMIT MSR (1ADH) is designed to describe the maximum Intel
Turbo Boost Technology potential of the processor. On some processors, a non-zero
Intel Turbo Boost Technology value will be returned for non-existent core
configurations.
Implication: Due to this erratum, software using the MSR_TURBO_RATIO_LIMIT MSR to report Intel
Turbo Boost Technology processor capabilities may report erroneous results.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD83. L1 Cache Uncorrected Errors May be Recorded as Correctable in 16K
Mode
Problem: When the L1 Cache is oper ating in 16K redundant parity mode and a parity error occurs
on both halves of the duplicated cache on the same cacheline, an uncorrectable error
should be logged. Due to this erratum, the uncorrectable error will be recorded as
correctable, however a machine check exception will be appropriately taken in this
case.
Implication: Due to this erratum, the IA32_MCi_STATUS.UC bit will incorrectly contain a value of 0
indicating a correctable error.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD84. Extra APIC Timer Interrupt May Occur During a Write to the Divide
Configuration Register
Problem: If the APIC timer Divide Configuration Register (Offset 03E0H) is written at the same
time that the APIC timer Current Count Register (Offset 0390H) reads 1H, it is possible
that the APIC timer will deliver two interrupts.
Implication: Due to this erratum, two interrupts may unexpectedly be generated by an APIC timer
event.
Workaround: Software should reprogram the Divide Configur ation Register only when the APIC timer
interrupt is disarmed.
Status: For the steppings affected, see the Summary Table of Changes.
BD85. PECI Reads of Machine Check MSRs in the Processor Core May Not
Function Correctly
Problem: PECI reads which target machine check MSRs in the processor core may either be
directed to a different core than intended or report that the data is not available.
Intel® Xeon® Processor 5600 Series 44
Specification Update August 2013
Implication: PECI reads of machine check MSRs in the processor core may return incorrect data or
incorrectly report that data is not available for the requested core.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD86. The Combination of a Page-Split Lock Access And Data Accesses That
Are Split Across Cacheline Boundaries May Lead to Processor Livelock
Problem: Under certain complex microarchitectural conditions, the simultaneous occurrence of a
page-split lock and several data accesses that are split cacheline boundaries may lead
to processor livelock.
Implication: Due to this erratum, a livelock may occur that can only be terminated by a processor
reset. Intel has not observed this erratum with any commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD87. Package C6 Transitions May Cause Memory Bit Errors to be Observed
Problem: During Package C6 tr ansitions, internal signaling nois e may cause the D DRx_CKE signal
to become asserted during self-refresh. These assertions may result in memory bit
errors upon exiting from the package C6 state. Due to this erratum the DDRx_CKE
signals can be driven during times in which the DDR3 JEDEC specification requires that
they are idle.
Implication: DDRx_CKE signals can be driven during package C6 memory self-refresh creating an
invalid memory DRAM state. A system hang, memory ECC errors or unpredictable
system behavior may occur when exiting the package C6 state.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD88. FP Data Operand Pointer May Be Incorrectly Calculated After an FP
Access Which Wraps a 4-Gbyte Boundary in Code That Uses 32-Bit
Address Size in 64-bit Mode
Problem: The FP (Floating Point) Data Operand Pointer is the effective address of the operand
associated with the last non-control FP instruction executed by the processor. If an 80-
bit FP access (load or store) uses a 32-bit address size in 64-bit mode and the memory
access wraps a 4-Gbyte boundary and the FP environment is subsequently saved, the
value contained in the FP Data Operand Pointer may be incorrect.
Implication: Due to this erratum, the FP Data Operand P ointer may be incorrect. Wrapping an 80-bit
FP load around a 4-Gbyte boundary in this way is not a normal programming practice.
Intel has not observed this erratum with any commercially available software.
Workaround: If the FP Data Operand P ointer is used in a 64-bit operating system which ma y run code
accessing 32-bit addresses, care must be taken to ensure that no 80-bit FP accesses
are wrapped around a 4-Gbyte boundary.
Status: For the steppings affected, see the Summary Table of Changes.
BD89. FP Data Operand Pointer May Be Incorrectly Calculated After an FP
Access Which Wraps a 64-Kbyte Boundary in 16-bit Code
Problem: The FP (Floating Point) Data Operand Pointer is the effective address of the operand
associated with the last non-control FP instruction executed by the processor. If an 80-
bit FP access (load or store) occurs in a 16-bit mode other than protected mode (in
Intel® Xeon® Processor 5600 Series 45
Specification Update August 2013
which case the access will produce a segment limit violation), the memory access wrap
a 64-Kbyte boundary, and the FP environment is subsequently saved, the value
contained in the FP Data Operand Pointer may be incorrect.
Implication: Due to this erratum, the FP Data Operand P ointer may be incorrect. Wrapping an 80-bit
FP load around a segment boundary in this way is not a normal programming practice.
Intel has not observed this erratum with any commercially available software.
Workaround: If the FP Data Operand Pointer is used in an operating system which may run 16-bit FP
code, care must be taken to ensure that no 80-bit FP access are wrapped around a 64-
Kbyte boundary.
Status: For the steppings affected, see the Summary Table of Changes.
BD90. Spurious PROCHOT# Assertion During Warm Reset May Hang the
Processor
Problem: The processor may hang if there is a spurious PROCHOT# pin assertion during a warm
reset. The hang may occur even if the minimum hold time specification for PROCHOT#
is not met or voltage regulator based throttling is not enabled.
Implication: Due to this erratum the processor may hang if there is any spurious assertion of the
PROCHOT# pin during a warm reset.
Workaround: It is possible of the BIOS to contain a workaround for this erratum, to be used in
conjunction with a BIOS modification.
Status: For the steppings affected, see the Summary Table of Changes.
BD91. TSC Values When Observed Cross-Socket May Be Out of Sync After a
Warm Reset
Problem: In a two socket platform with package C6 enabled, the TSC (Time Stamp Counter)
cross-socket values should remain synchronous if the conditions specified in the
processor AC timing Waveforms Section of the Intel® Xeon 5600 Series EMTS
(Electrical Mechanical and Thermal Specifications) are met. Due to this erratum the
TSC may become out of sync between the processor packages after a warm reset even
if the Reset# de-assertion requirements are met.
Implication: Certain software applications that rely on hardware based TSC cross-socket
synchronization may not function correctly.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD92. Changes to Reserved Bits for Some Non-Architectural MSR’s May
Cause Unpredictable System Behavior
Problem: Under normal circumstances, an operation fails if it attempts to modify a reserved bit of
a model-specific register (MSR). Due to this erratum and for some non-architectural
MSRs, such an attempt may cause unpredictable system behavior.
Implication: Unpredictable system behavior may occur if software attempts to modify reserved bits
of some non-architectural MSRs. (Note that documentation of the WRMSR instruction
states that “Undefined or reserved bits in an MSR should be set to values previously
read.”)
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 46
Specification Update August 2013
BD93. Persistent Stream of Correctable Memory ECC Errors May Result in
Unexpected Behavior
Problem: When Demand and/or Patrol Scrub are enabled along with Write Major Mode, and a
persistent stream of correctable memory ECC errors occurs, the processor may exhibit
unexpected behavior.
Implication: A system hang or unpredictable system behavior might be observed due to this
erratum. Intel has not observ ed this erratum with any commercially available software.
Workaround: It is possible for the Intel provided Memory reference code to contain a workaround for
this erratum. The workaround disables Write Major Mode when Demand and/or Patrol
Scrub are enabled, which eliminates the potential for this erratum to occur.
Status: For the steppings affected, see the Summary Table of Changes.
BD94. IO_SMI Indication in SMRAM State Save Area May Be Lost
Problem: The IO_SMI bit (bit 0) in the IO state field at SMRAM offset 7FA4H is set to “1” by the
processor to indicate a System Management Interrupt (SMI) is either taken
immediately after a successful I/O instruction or is taken after a successful iteration of
a REP I/O instruction. Due to this erratum, the setting of the IO_SMI bit may be lost.
This may happen under a complex set of internal conditions with Intel® Hyper-
Threading Technology enabled and has not been observed with commercially available
software.
Implication: Due to this erratum, SMI handlers may not be able to identify the occurrence of I/O
SMIs.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD95. Failing DIMM ID May Be Incorrect When Mirroring is Enabled
Problem: When redundancy is lost in Mirroring mode, the failing DIMMs cannot be identified
correctly if MC_SMI_SPARE_DIMM_ERROR_STATUS CSR bits [13:12]
(REDUNDANCY_LOSS_FAILING_DIMM) are 00b.
Implication: When the bits [13:12] in the MC_SMI_SPARE_DIMM_ERROR_STATUS CSR are 00b, the
failing DIMM may not be correctly identified.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD96. PECI Reads to Machine Check Registers May Return Unexpected Data
Problem: If BIOS disables one or more cores by writing to the CSR_DESIRED_CORES (De vice 0;
Function 0; Offset 80H), PECI (Platform Environment Control Interface) reads to
machine check registers may receive data from a core which was not the intended
target of the read or may receive unexpected data.
Implication: When one or more cores are disabled by the BIOS, PECI commands to read machine
check registers may return incorrect data and/or behave in an unpredictable manner.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 47
Specification Update August 2013
BD97. FSW May Be Corrupted If an x87 Store Instruction Causes a Page Fault
in VMX Non-Root Operation
Problem: The X87 FSW (FPU Status W ord) may be corrupted if execution of a floating-point store
instruction (FST, FSTP, FIST, FISTP, FISTTP) causes a page fault in VMX non-root
operation.
Implication: This erratum may result in unexpected behavior of software that uses x87 FPU
instructions.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD98. Sensitivity in Clocking Circuitry May Result in Unpredictable System
Behavior
Problem: On a subset of processors the clocking circuitry may be sensitive to fluctuations in Vtt
voltage during stressful testing and/or operating conditions and may result in
unpredictable system behavior.
Implication: This erratum may result in unpredictable system behavior.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD99. Accesses to a VMCS May Not Operate Correctly If CR0.CD is Se t on Any
Logical Processor of a Core
Problem: The VMX (virtual-machine extensions) are controlled by the VMCS (virtual-machine
control structure). If CR0.CD is set on any logical processor of a core, operations using
the VMCS may not function correctly. Such operations include the VMREAD and
VMWRITE instructions as well as VM entries and VM exits.
Implication: If CR0.CD is set on either logical processor in a core, the VMWRITE instruction may not
correctly update the VMCS and the VMREAD instruction may not return correct data.
VM entries may not load state properly and may not establish VMX controls properly.
VM exits may not save or load state properly.
Workaround: VMMs (Virtual-machine monitors) should ensure that CR0.CD is clear on all logical
processors of a core before entering VMX operation on any logical processor. Software
should not set CR0.CD on a logical processor if any logical processor of the same core is
in VMX operation. VMM software should prevent guest software from setting CR0.CD by
setting bit 30 in the CR0 guest/host mask field in every VMCS.
Status: For the steppings affected, see the Summary Table of Changes.
BD100. Performance Monitor Events for Hardware Prefetches Which Miss The
L1 Data Cache May be Over Counted
Problem: Hardware prefetches that miss the L1 data cache but cannot be processed immediately
due to resource conflicts will count and then retry. This may lead to incorrectly
incrementing the L1D_PREFETCH.MISS (event 4EH, umask 02H) event multiple times
for a single miss.
Implication: The count reported by the L1D_PREFETCH.MISS event may be higher than expected.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 48
Specification Update August 2013
BD101. Parallel VMX entries and exits the DTLB is not flushed
Problem: The DTLB ph ysicals are left intact, however, the physicals needs to be flushed to ensure
proper SMRR operation.
Implication: The DTLB physicals may contain SMM addresses even after exiting SMM.
Workaround: Software using SMM Transfer Monitor should insure that the DTLB is flushed prior to
parallel entries and exits.
Status: For the steppings affected, see the Summary Table of Changes.
BD102. VM Exit May Incorrectly Clear IA32_PERF_GLOBAL_CTRL [34:32]
Problem: If the “load IA32_PERF_GLOBAL_CTRL” VM-exit control is 1, a VM exit should load the
IA32_PERF_GLOBAL_CTRL MSR (38FH) from the IA32_PERF_GLOBAL_CTRL field in the
guest-state area of the VMCS. Due to this erratum, such a VM exit may instead clear
bits 34:32 of the MSR, loading only bits 31:0 from the VMCS.
Implication: All fixed-function performance counters will be disabled after an affected VM exit, even
if the VM exit should have enabled them based on the IA32_PERF_GLOBAL_CTRL field
in the guest-state area of the VMCS.
Workaround: A VM monitor that wants th e fixed-function performance counters to be enabled after a
VM exit may do one of two things: (1) clear the “load IA32_PERF_GLOBAL_CTRL” VM-
exit control; or (2) include an entry for the IA32_ PERF_GLOBAL_CTRL MSR in the VM-
exit MSR-load list.
Status: For the steppings affected, see the Summary Table of Changes.
BD103. VM Entry May Omit Consistency Checks Related to Bit 14 (BS) of the
Pending Debug Exception Field in Guest-State Area of the VMCS
Problem: Section “Checks on Guest Non-Register State” of Volume 3B specifies consistency
checks that VM entry should perform for bit 14 (BS, indicating a pending single-step
exception) of the pending debug exception field in guest-state area of the VMCS. These
checks enforce the consistency of that bit with other fields in the guest -state area. Due
to this erratum, VM entry may fail to perform these checks.
Implication: A logical processor may enter VMX non-root operation with a pending single-step
debug exception that not consistent other register state; this may result in unexpected
behavior. Intel has not observed this erratum with an y commercially av ailable software.
Workaround: When using VMW RITE to write to a field in the guest -state area, s oftware should e nsure
that the value written is consistent with the state of other guest-state fields.
Status: For the steppings affected, see the Summary Table of Changes.
BD104. Package C6 Transitions May Result in Single and Multi-Bit Memory
Errors
Problem: On a subset of processors, during package C6 transitions, internal circuit marginality
may cause DDR3 JEDEC specification violations. These violations may result in control
and data signal errors upon exiting from package C6 state.
Implication: Certain memory control signals may be incorrectly driven during package C6 memory
self-refresh. This can create an invalid memory DRAM state, system hang, reboot,
memory ECC errors or unpredictable system behavior. For systems with ECC memory,
Intel® Xeon® Processor 5600 Series 49
Specification Update August 2013
correctable/uncorrectable ECC errors may be logged in the IA32_MC8_STATUS MSR
(421H) with the uncorrectable errors resulting in a machine check exception.
Workaround: It is possible for the BIOS to contain a workaround for this erratum. Please refer to
Table 3, Intel® Xeon® Processor 5600 Series Microcode Update Guide for further
details.
Status: For the steppings affected, see the Summary Table of Changes.
BD105. Execution of VMPTRLD May Corrupt Memory If Current-VMCS Pointer
is Invalid
Problem: If the VMCLEAR instruction is executed with a pointer to the current-VMCS (virtual-
machine control structure), the current-VMCS pointer becomes invalid as expected. A
subsequent execution of the VMPTRLD (Load Pointer to Virtual-Machine Control
Structure) instruction may erroneously overwrite the four bytes at physical address
0000008FH.
Implication: Due to this erratum, the four bytes in system memory at physical address 0000008FH
may be corrupted.
Workaround: It is possible for BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD106. PerfMon Overflow Status Can Not be Cleared After Certain Conditions
Have Occurred
Problem: Under very specific timing conditions, if software tries to disable a PerfMon counter
through MSR IA32_PERF_GLOBAL_CTRL (0x38F) or through the per-counter event-
select (e.g. MSR 0x186) and the counter reached its overflow state very close to that
time, then due to this erratum the overflow status indication in MSR
IA32_PERF_GLOBAL_STAT (0x38E) may be left set with no way for software to clear it.
Implication: Due to this erratum, software may be unable to clear the PerfMon counter overflow
status indication.
Workaround: Software may avoid this erratum by clearing the PerfMon counter value prior to
disabling it and then clearing the overflow status indication bit.
Status: For the steppings affected, see the Summary Table of Changes.
BD107. An Unexpected Page Fault or EPT Violation May Occur After
AnotherLogical Processor Creates a Valid Translation for a Pa ge
Problem: An unexpected page fault (#PF) or EPT violation may occur for a page under the
following conditions:
• The paging structures initially specify no valid translation for the page.
• Software on one logical processor modifies the paging structures so thatthere is a
valid translation for the page (e.g., by setting to 1 the present bitin one of the
paging-structure entries used to translate the page).
• Software on another logical processor observ es this modification (e.g., byaccessing
a linear address on the page or by reading the modified paging structure entry and
seeing value 1 for the present bit).
• Shortly thereafter, software on that other logical processor performs astore to a
linear address on the page. In this case, the store may cause a page fault or EPT
violation that indicates that there is no translation for the page (e.g., with bit 0
clear in thepage-fault error code, indicating that the fault was caused by a not-
Intel® Xeon® Processor 5600 Series 50
Specification Update August 2013
present page). Intel has not observed this erratum with any commercially av ailable
software.
Implication: An unexpected page fault may be reported. There are no other side effects due to this
erratum.
Workaround: System software can be constructed to tolerate these unexpected page faults. See
Section “Propagation of P aging-Structu re Changes to Multiple Pro cessors” of Volume 3A
of IA-32 Intel® Architecture Software Developer's Manual, for recommendations for
software treatment of asynchronous paging-structure updates.
Status: For the steppings affected, see the Summary Table of Changes.
BD108. L1 Data Cache Errors May be Logged With Level Set to 1 Instead of 0
Problem: When an L1 Data Cache error is logged in IA32_MCi_STATUS[15:0], which is the MCA
Error Code Field, with a cache error type of the format 0000 0001 RRRR TTLL, the LL
field may be incorrectly encoded as 01b instead of 00b.
Implication: An error in the L1 Data Cache may report the same LL value as the L2 Cache. Software
should not assume that an LL value of 01b is the L2 Cache.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD109. Executing The GETSEC Instruction While Throttling May Result in a
Processor Hang
Problem: If the processor throttles due to either high temperature thermal conditions or due to
an explicit operating system throttling request (TT1) while executing GETSEC[SENTER]
or GETSEC[SEXIT] instructions, then under certain circumstances, the processor may
hang. Intel has not been observed this erratum with any commercially available
software.
Implication: P ossible hang during execution of GETSEC instruction.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD110. PerfMon Event LOAD_HIT_PRE.SW_PREFETCH May Overcount
Problem: PerfMon event LOAD_HIT_PRE.SW_PREFETCH (event 4CH, umask 01H) should count
load instructions hitting an ongoing software cache fill request initiated by a preceding
software prefetch instruction. Due to this erratum, this event may also count when
there is a preceding ongoing cache fill request initiated by a locking instruction.
Implication: PerfMon event LOAD_HIT_PRE.SW_PREFETCH may overcount.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD111. Successive Fixed Counter Overflows May be Discarded
Problem: Under specific internal conditions, when using Freeze PerfMon on PMI feature (bit 12 in
IA32_DEBUGCTL.Freeze_PerfMon_on_PMI, MSR 1D9H), if two or more PerfMon Fixed
Counters overflow very closely to each other, the overflow may be mishandled for some
of them. This means that the counter's overflow status bit (in
MSR_PERF_GLOBAL_STATUS, MSR 38EH) may not be updated properly; additionally,
PMI interrupt may be missed if software programs a counter in Sampling-Mode (PMI bit
is set on counter configuration).
Intel® Xeon® Processor 5600 Series 51
Specification Update August 2013
Implication: Successive Fixed Counter overflows may be discarded when Freeze PerfMon on PMI is
used.
— Software can avoid this by:
1. Avoid using Freeze PerfMon on PMI bit
2. Enable only one fixed counter at a time when using Freeze PerfMon on PMI
Status: For the steppings affected, see the Summary Table of Changes.
BD112. #GP May be Signaled When Invalid VEX Prefix Precedes Conditional
Branch Instructions
Problem: When a 2-byte opcode of a conditional branch (opcodes 0F8xH, for any value of x)
instruction resides in 16-bit code-segment and is associated with invalid VEX prefix, it
may sometimes signal a #GP fault (illegal instruction length > 15-bytes) instead of a
#UD (illegal opcode) fault.
Implication: Due to this erratum, #GP fault instead of a #UD may be signaled on an illegal
instruction.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD113. A Logical Processo r May Wake From Shutdown State When Branch-
Trace Messages or Branch-Trace Stores Are Enabled
Problem: Normally, a logical processor that entered the shutdown state will remain in that state
until a break event (NMI, SMI, INIT) occurs. Due to this erratum, if CR4.MCE (Machine
Check Enable) is 0 and a branch-trace message or branch-trace store is pending at the
time of a machine check, the processor may not remain in shutdown state. In addition,
if the processor was in VMX non-root operation when it improperly woke from
shutdown state, a subsequent VM exit may save a value of 2 into the activity -state field
in the VMCS (indicating shutdown) even though the VM exit did not occur while in
shutdown state.
Implication: This erratum ma y result in unexpected system behavior. If a VM exit saved a v alue of 2
into the activity-state field in the VMCS, the next VM entry will take the processor to
shutdown state.
Workaround: Software should ensure that CR4.MCE is set whenever IA32_DEBUGCTL MSR (60EH)
TR bit [6] is set.
Status: For the steppings affected, see the Summary Table of Changes.
BD114. Task Switch to a TS S With an Inaccessible LDTR Descriptor May Cause
Unexpected Faults
Problem: A task switch may load the LDTR (Local Descriptor Table Register) with an incorrect
segment descriptor if the LD T (Local Descriptor Table) segment selector in the new TSS
specifies an inaccessible location in the GDT (Global Descriptor Table).
Implication: Future accesses to the LDT may result in unpredictable system behavior.
Workaround: Operating system code should ensure that segment selectors used during task switches
to the GDT specify offsets within the limit of the GDT and that the GDT is fully paged
into memory.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 52
Specification Update August 2013
BD115. Package C6 Exit with Memory in Self-Refresh When Using DDR3
RDIMM Memory May Lead to a System Hang
Problem: When using DDR3 RDIMM memory and exiting from the C6 low power state with
memory in self-refresh the CS (Chip Select) signals may remain in tri-state during
tSTAB (CLK Stabilization time) thus violating the JEDEC Standard: Definition of the
SSTE32882 Registering Clock Driver with Parity and Quad Chip Selects for DDR3
RDIMM Applications. As detailed in the JEDEC specification the CS signals should
transition from tri-state to high to exit the Clock Stopped Po wer Down Mode.
Implication: When this erratum occurs the processor may hang.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD116. .MCIP Bit Not Checked on SENTER or ENTERACCS
Problem: When an ILP (Initiating Logical Processor) executes GETSEC with either the SENTER or
ENTERACCS leaf function, the processor should check the MCIP (Machine Check In
Progress) bit in the IA32_MCG_ST ATUS MSR (17AH) to determine if any machine check
exception is being processed. If a machine check is in progress the ILP should gener ate
a general protection ex ception. Du e to this erratum, the general protection exception is
not gene rated.
Implication: If GETSEC is executed with either the SENTER or ENTERACCS leaf function, and a
machine check exception is being processed, ILP will enter an authenticated execution
mode instead of generating a general protection exception.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD117. Unexpected Load May Occur on Execution of Certain Opcodes
Problem: If software executes an instruction with an opcode of the form 66 0F 38 8x (where x is
in the range 0 to 6), the processor may unexpectedly perform a load operation (the
data loaded is not used). The load occurs e ven if the instruction causes a VM exit or a
fault (including an invalid-opcode exception). If the VMXON instruction has been
executed successfully, the load is from the physical address in the VMXON pointer plus
408H; otherwise, it is from physical address 407H. The affected opcodes include the
INVEPT and INVVPID instructions as well as five invalid opcodes.
Implication: This erratum may cause incorrect side effects if the load accesses a memory-mapped
I/O device. Intel has not observed this erratum with any commercially available
system.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD118. Successive Fixed Counter Overflows May be Discarded
Problem: Under specific internal conditions, when using Freeze PerfMon on PMI feature (bit 12 in
IA32_DEBUGCTL.Freeze_PerfMon_on_PMI, MSR 1D9H), if two or more PerfMon Fixed
Counters overflow very closely to each other, the overflow may be mishandled for some
of them. This means that the counter's overflow status bit (in
MSR_PERF_GLOBAL_STATUS, MSR 38EH) may not be updated properly; additionally,
PMI interrupt may be missed if software programs a counter in Sampling-Mode (PMI bit
is set on counter configuration).
Intel® Xeon® Processor 5600 Series 53
Specification Update August 2013
Implication: Successive Fixed Counter overflows may be discarded when Freeze PerfMon on PMI is
used.
Workaround: Software can avoid th is by:
1. Avoid using Freeze PerfMon on PMI bit
2. Enable only one fixed counter at a time when using Freeze PerfMon on PMI
Status: For the steppings affected, see the Summary Table of Changes.
BD119. VM Exits Due to “NMI-Window Exiting” May Not Occur Following a VM
Entry to the Shutdown State
Problem: If VM entry is made with the “virtual NMIs” and “NMI-window exiting”, VM-execution
controls set to 1, and if there is no virtual-NMI blocking after VM entry, a VM exit with
exit reason “NMI window” should occur immediately after VM en try unless the VM entry
put the logical processor in the wait-for SIPI state. Due to this erratum, such VM exits
do not occur if the VM entry put the processor in the shutdown state.
Implication: A VMM may fail to deliver a virtual NMI to a virtual machine in the shutdown state.
Workaround: Before performing a VM entry to the shutdown state, software should check whether
the “virtual NMIs” and “NMI-window exiting” VM-exec ution controls are both 1. If they
are, software should clear “NMI-window exiting” and inject an NMI as part of VM entry.
Status: For the steppings affected, see the Summary Table of Changes.
BD120. Execution of INVVPID Outside 64-Bit Mode Cannot Invalidate
Translations For 64-Bit Linear Addresses
Problem: Executions of the INVVPID instruction outside 64-bit mode with the INVVPID type
“individual-address invalidation” ignore bits 63:32 of the linear add ress in the INV VPID
descriptor and invalidate translations for bits 31:0 of the linear address.
Implication: The INVVPID instruction may fail to invalidate translations for linear addresses that set
bits in the range 63:32. Because this erratum applies only to executions outside 64-bit
mode, it applies only to attempts by a 32-bit virtual-machine monitor (VMM) to
invalidate translations for a 64-bit guest. Intel has not observed this erratum with any
commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD121. A Combination of Data Accesses That Are Split Across Cacheline
Boundaries May Lead to a Processor Hang
Problem: Under certain complex micro-architectural conditions, closely spaced data accesses
that are split across cacheline boundaries may lead to a processor hang.
Implication: Due to this erratum, the processor ma y hang. This err atum has not been observ ed with
any gener al purpose operating systems.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD122. PerfMon Overflow Status Can Not be Cleared After Certain Conditions
Have Occurred
Problem: Under very specific timing conditions, if software tries to disable a PerfMon counter
through MSR IA32_PERF_GLOBAL_CTRL (0x38F) or through the per-counter event-
select (e.g. MSR 0x186) and the counter reached its overflow state very close to that
Intel® Xeon® Processor 5600 Series 54
Specification Update August 2013
time, then due to this erratum the overflow status indication in MSR
IA32_PERF_GLOAL_STAT (0x38E) may be left set with no way for software to clear it.
Implication: Due to this erratum, software may be unable to clear the PerfMon counter overflow
status indication.
Workaround: Software may avoid this erratum by clearing the PerfMon counter value prior to
disabling it and then clearing the overflow status indication bit.
Status: For the steppings affected, see the Summary Table of Changes.
BD123. Package C6 C-State Exit May Result in Uncorrectable Memory Errors
Problem: On a subset of processors, during package C6 C-State transitions, internal circuit
marginality may cause uncorrectable memory errors to occur on exiting Package C6 C-
State. The errors will be logged in IA32_MCi_STATUS MSR with MCACOD = 0x009F.
Workaround: Uncorrectable memory errors may cause a system reboot/shutdown.
Workaround: A BIOS code change has been identified and may be implemented as a workaround for
this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD124. VMRESUME May Omit Check of Revision Identifier of Linked VMCS
Problem: If the VMCS link pointer is valid in the VMCS, VM entry instructions should check that
the 32 bits referenced by that pointer contains the processor's VMCS revision identifier
and fail if it does not. Due to this erratum, VMRESUME may omit this check and thus
not cause VM entry to fail in some cases.
Implication: The revision identifier of the linked VMCS may not be chec ked. Intel has not observed
this erratum with any commercially available software.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD125. An INIT Signal May Cause Unpredictable Behavior After a VMXOFF
Problem: If software has used VMX-preemption timer and subsequently leaves VMX operation
This erratum may lead to unpredictable behavior, including a system hang. Intel has
not observed this erratum with any commercially available software.using VMXOFF,
then an INIT signal may result in unpredictable behavior.
Implication: This erratum may lead to unpredictable behavior, including a system hang. Intel has
not observed this erratum with any commercially available software.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD126. APIC Timer Interrupts May be Lost During Core C3
Problem: APIC timer interrupts intended to awaken from core C3 may be lost under certain
timing conditions.
Implication: Due to this erratum, a lost timer interrupt may cause the system to hang.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes
Intel® Xeon® Processor 5600 Series 55
Specification Update August 2013
BD127. MCI_ADDR May be Incorrect For Cache Parity Errors
Problem: In cases when a WBINVD instruction evicts a line containing an address or data parity
error (MCACOD of 0x124, and MSCOD of 0x10), the address of this error should be
logged in the MCi_ADDR register. Due to this erratum, the logged address may be
incorrect, even though MCi_Status.ADDRV (bit 63) is set.
Implication: The address reported in MCi_ADDR may not be correct for cases of a parity error found
during WBINVD execution.
Workaround: None Identified.
Status: For the steppings affected, see the Summary Table of Changes
BD128. APIC Timer Interrupt May be Lost
Problem: An APIC timer interrupt can be lost when it aligns precisely with an internal CPU
counter overflow condition (the overflow condition occurs once about every 90
minutes).
Implication: Due to this erratum, for certain programmed values of the APIC timer, the processor
may not recognize and service the interrupt.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes
BD129. REP MOVS/STOS Executing with Fast Strings Enabled and Crossing
Page Boundaries with Inconsistent Memory Ty pes may use an
Incorrect Data Size or Lead to Memory-Ordering Violations
Problem: Under certain conditions as described in the Software Developers Manual section “Out-
of-Order Stores For String Operations in Pentium 4, Intel Xeon, and P6 Family
Processors” the processor performs REP MOVS or REP STOS as fast strings. Due to this
erratum fast string REP MOVS/REP STOS instructions that cross page boundaries from
WB/WC memory types to UC/WP/WT memory types, may start using an incorrect data
size or may observe memory ordering violations.
Implication: Upon crossing the page boundary the following may occur, dependent on the new page
memory type:
• UC the data size of each write will now always be 8 bytes, as opposed to the
original data size.
• WP the data size of each write will now always be 8 bytes, as opposed to the
original data size and there may be a memo ry orde ring violation.
• WT there may be a memory ordering violation.
Workaround: Software should avoid crossing page boundaries from WB or WC memory type to UC,
WP or WT memory type within a single REP MOVS or REP STOS instruction that will
execute with fast strings enabled.
Status: For the steppings affected, see the Summary Table of Changes.
BD130. CR0.CD Is Ignored in VMX Operation
Problem: If CR0.CD=1, the MTRRs and PAT should be ignored and the UC memory type should
be used for all memory accesses. Due to this erratum, a logical processor in VMX
operation will operate as if CR0.CD=0 even if that bit is set to 1.
Intel® Xeon® Processor 5600 Series 56
Specification Update August 2013
Implication: Algorithms that rely on cache disabling may not function properly in VMX operation.
Workaround: Algorithms that rely on cache disabling should not be executed in VMX root operation.
Status: For the steppings affected, see the Summary Table of Changes.
BD131. Sensitivity in Execution Unit Clock Circuitry on a small subset of
Intel® Xeon® processor X5675, X5690 and X5687 May Result in
Unpredictable System Behavior
Problem: Under a complex set of internal and platform conditions, the execution unit on a small
subset of Intel® Xeon® processor X5675, X5690 and X5687 may not complete some
instructions correctly.
Implication: Due to this erratum, the execution unit may not complete some instructions correctly,
leading to unpredictable system behavior.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD132. Virtual-APIC Page Accesses With 32-Bit PAE Paging May Cause a
System Crash
Problem: If a logical processor has EPT (Extended Page Tables) enabled, is using 32-bit PAE
paging, and accesses the virtual-APIC page then a complex sequence of internal
processor micro-architectural events may cause an incorrect address translation or
machine check on either logical processor
Implication: This erratum may result in unexpected faults, an uncorrectable TLB error logged in
IA32_MCi_STATUS.MCACOD (bits [15:0]) with a value of 0000_0000_0001_xxxxb
(where x stands for 0 or 1), a guest or hypervisor crash, or other unpredictable system
behavior.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.
BD133. EPT Violations May Report Bits 11:0 of Guest Linear Address
Incorrectly
Problem: If a memory access to a linear address requires the processor to update an accessed or
dirty flag in a paging-structure entry and if that update causes an EPT violation, the
processor should store the linear address into the “guest linear address” field in the
VMCS. Due to this erratum, the processor may store an incorrect value into bits 11:0 of
this field. (The processor correctly stores the guest-physical address of the paging-
structure entry into the “guest-physical address” field in the VMCS.)
Implication: Software may not be easily able to determine the page offset of the original memory
access that caused the EPT violation. Intel has not observed this erratum to impact the
operation of any commercially available software.
Workaround: Software requiring the page offset of the original memory access address can derive it
by simulating the effective address computation of the instruction that caused the EPT
violation.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 57
Specification Update August 2013
BD134. IA 32_VMX_VMCS_ENUM MSR (48AH) Does Not Properly Rep ort T he
Highest Index Value Used For VMCS Encoding
Problem: IA32_VMX_VMCS_ENUM MSR (48AH) bits 9:1 report the highest index value used for
any VMCS encoding. Due to this erratum, the v alue 21 is returned in bits 9:1 although
there is a VMCS field whose encoding uses the index value 23.
Implication: Software that uses the value reported in IA32_VMX_VMCS_ENUM[9:1] to read and
write all VMCS fields may omit one field.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
BD135. The U pper 32 Bits of CR3 May be Incorrectly Used With 32-Bit Paging
Problem: When 32-bit paging is in use, the processor should use a page directory located at the
32-bit physical address specified in bits 31:12 of CR3; the upper 32 bits of CR3 should
be ignored. Due to this erratum, the processor will use a page directory located at the
64-bit physical address specified in bits 63:12 of CR3.
Implication: The processor may use an unexpected page directory or, if EPT (Extended Page Tables)
is in use, cause an unexpected EPT violation. This erratum applies only if software
enters 64-bit mode, loads CR3 with a 64-bit value, and then returns to 32-bit paging
without changing CR3. Intel has not observed this erratum with any commercially
available software.
Workaround: Software that has executed in 64-bit mode should reload CR3 with a 32-bit value
before returning to 32-bit paging.
Status: For the steppings affected, see the Summary Table of Changes.
BD136. The Corrected Error Count Overflow Bit in IA32_ MC0_STATUS is Not
Updated After a UC Error is Logged
Problem: When a UC (uncorrected) error is logged in the IA32_MC0_STATUS MSR (401H),
corrected errors will continue to update the lower 14 bits (bits 51:38) of the Corrected
Error Count. Due to this erratum, th e sticky coun t ov erflow bit (bit 52) of the Corrected
Error Count will not get updated after a UC error is logged.
Implication: The Corrected Error Count Overflow indication will be lost if the o verflow occurs after an
uncorrectable error has been logged.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
Intel® Xeon® Processor 5600 Series 58
Specification Update August 2013
BIOS ACM Errata
BD1. BIOS ACM May Report an Incorrect TXT.ERRORCODE in Multiprocessor
Configurations
Problem: In multiprocessor configurations, TXT.ERRORCODE error information may be lost across
BIOS ACM calls due to a synchronization problem.
Implication: In multiprocessor configurations, SINIT ACM errors may not be correctly reported in
TXT.ERRORCODE.
Workaround: Uniprocessor configurations are unaffected by this erratum. If the platform is changed
to a uniprocessor configuration, TXT.ERRORCODE will be reported accurately.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD2. BIOS ACM Reset TPM Auxiliary Indices Function Not Available\
Problem: Early server BIOS ACM releases do not support the new Reset TPM Auxiliary Indices
Function (ESI = 0x02).
Implication: Calls to the BIOS ACM Reset Auxiliary Indices function on affected ACM releases will
return control back to the caller without performing the function.
Workaround: None Identified.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD3. If Processor is Reset Without Resetting The IOH With Secrets in
Memory, The BIOS ACM Will Hand-off to BIOS With Memory Locked
Problem: The platform may assert reset only to the processor to change DDR speed or make
another configuration change. If cold reset or warm reset is asserted to the processor
with secrets in memory without resetting the IOH, the BIOS ACM will hand off to BIOS
with memory lo cked.
Implication: With memory locked, BIOS will be unable to initialize memory, resulting in boot failure.
Workaround: If RESET# is asserted to both the processor and the IOH, exposure to this erratum
does not exist.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD4. BIOS ACM SCHECK May Set TPM Locality 0 to Inactive Status
Problem: If BIOS has set TPM locality 0 to be active, BIOS ACM SCHECK may reset TPM locality 0
to inactive.
Implication: BIOS implementations that depend upon locality 0 active status to be preserved across
SCHECK may not behave as expected.
Workaround: BIOS can set TPM locality 0 to active after SCHECK if necessary.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD5. If BIOS policy Autopromotion Fails, TXT.ACMCRASHCODE An d
TXT.ACMSTATUS May Have Incorrect Values
Problem: If BIOS policy autopromotion fails, TXT.ACMCRASHCODE and TXT.SPAD may have
incorrect values.
Intel® Xeon® Processor 5600 Series 59
Specification Update August 2013
Implication: BIOS implementations depending upon TXT.ACMCRASHCODE or TXT.SPAD may not
identify BIOS policy autopromotion failure.
Workaround: None Identified.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD6. The BIOS ACM May Write Error Codes to The Wrong Register
Problem: The BIOS ACM may incorrectly write error codes to TXT.ERRORCODE (offset 0030h)
instead of TXT.BIOSACM.ERRORCODE (offset 0328h).
Implication: TXT.ERRORCODE may be overwritten with BIOS ACM error codes.
Workaround: None Identified.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD7. NPW BIOS ACMs May Allow Launch of an MLE When The Launch
Control Policy Disallows NPW Launch
Problem: With the affected NPW (Non-Production Worthy) BIOS ACMs, the Measured Launch
Environment (e.g., virtual machine monitor or operating system) may boot when the
MLE launch control policy disallows NPW boot.
Implication: Measured Launch Environments may boot wi th NPW BIOS ACMs even if the MLE launch
control policy disallows NPW boot.
Workaround: None Identified.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD8. TPM PCR17 Not Extended with BIOS ACM values
Problem: With the affected BIOS ACMs, TPM (Trusted Platform Module) Platform Configuration
Register PCR17 may not be extended with the BIOS ACM version or Non-Production
Worthy bit.
Implication: On platforms using the affected BIOS ACMs, software depending upon PCR17
attestation may not behave as expected.
Workaround: None Identified.
Status: For the steppings affected, see the BIOS ACM Errata Table.
BD9. BIOS ACM May Exit to BIOS with TPM locality 3 activated
Problem: In multiprocessor configurations, under certain race conditions the BIOS ACM may exit
to BIOS with TPM locality 3 activated.
Implication: If TPM locality 3 is left activated, BIOS will be unable to activate locality and trusted
boot will fail.
Workaround: Uniprocessor configurations are unaffected by this erratum. If the platform is changed
to a uniprocessor configuration, TPM locality 3 will not be activate d on exit to BIOS.
Status: For the steppings affected, see the BIOS ACM Errata Table.
Intel® Xeon® Processor 5600 Series 60
Specification Update August 2013
SINIT ACM Errata
BD1. SINIT Buffer Overflow Vulnerability
Problem: SINIT Authenticated Code Module (ACM) 1.0 is susceptible to a buffer overflow issue.
Implication: When Intel® Trusted Execution Technology measured launch is invoked using SINIT
Authenticated Code Module 1.0, the platform is susceptible to an OS kernel-level
exploit which may compromise certain SINIT ACM functionality.
Workaround: It is possible for a BIOS update and an updated SINIT ACM 1.1 to be used as a
workaround for this erratum. Previous SINIT ACM releases will no longer function with
the BIOS update.
Status: For the steppings affected, see the BIOS ACM Errata Table.
Intel® Xeon® Processor 5600 Series 61
Specification Update August 2013
Specification Changes
The Specification Changes listed in this section apply to the following documents:
• Intel® Xeon® Processor 5600 Series Datasheet Volumes 1 & 2
•
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic
Architecture
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A:
Instruction Set Reference Manual A-M
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B:
Instruction Set Reference Manual N-Z
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3A:
System Programmin g Gu ide
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3B:
System Programmin g Gu ide
Intel® Xeon® Processor 5600 Series 62
Specification Update August 2013
Specification Clarifications
The Specification Changes listed in this section apply to the following documents:
• Intel® Xeon® Processor 5600 Series Datasheet Volume 1 & 2
•
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic
Architecture
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A:
Instruction Set Reference Manual A-M
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B:
Instruction Set Reference Manual N-Z
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3A:
System Programmin g Gu ide
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3B:
System Programmin g Gu ide
Intel® Xeon® Processor 5600 Series 63
Specification Update August 2013
Documentation Changes
The Documentation Changes listed in this section apply to the following documents:
• Intel® Xeon® Processor 5600 Series Datasheet Volume 1 & 2
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 1: Basic
Architecture
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2A:
Instruction Set Reference Manual A-M
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 2B:
Instruction Set Reference Manual N-Z
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3A:
System Programmin g Gu ide
• Intel® 64 and IA-32 Architectures Software Developer’s Manual, Volume 3B:
System Programmin g Gu ide
All Documentation Changes will be incorporated into a future version of the appropriate
Processor documentation.
Note: Documentation changes for Intel® 64 and IA-32 Architecture Software
Developer's Manual volumes 1, 2A, 2B, 3A, and 3B will be posted in a separate
document, Intel® 64 and IA-32 Architecture Software Developer's Manual
Documentation Changes. Follow the link below to become familiar with this file.
http://developer.intel.com/products/processor/manuals/index.htm
Intel® Xeon® Processor 5600 Series 64
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 65
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 66
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 67
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 68
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 69
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 70
Specification Update August 2013
Intel® Xeon® Processor 5600 Series 71
Specification Update August 2013
