AT80573KJ1006M/SLBAQ [INTEL]
Microprocessor;
| 型号： | AT80573KJ1006M/SLBAQ |
| 厂家： | 
INTEL |
| 描述： | Microprocessor |
| 文件： | 总44页 (文件大小：212K) |
| 中文： | 中文翻译 | 下载： | 下载PDF数据表文档文件 |
Intel® Xeon® Processor 5200 Series
Specification Update
December 2010
Document Number: 318586-019
Legal Lines and Disclaimers
INFORMATION 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, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or
in nuclear facility applications.
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.
Hyper-Threading Technology requires a computer system with a processor supporting HT Technology and an HT Technology-enabled chipset, BIOS
and operating system. Performance will vary depending on the specific hardware and software you use. For more information including details on
which processors support HT Technology, see here
Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across
different processor families. See http://www.intel.com/products/processor_number for details.
The Intel® Xeon® Processor 5200 Series 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.
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 by visiting Intel's website at http://www.intel.com.
Intel, Intel Core, Celeron, Centrino, Pentium, Intel Xeon, Intel Enhanced SpeedStep Technology Intel Atom, Intel Hyper-Threading Technology, and the
Intel logo are trademarks of Intel Corporation in the U. S. and other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2007-2010, Intel Corporation. All Rights Reserved.
2
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Content
Revision History...............................................................................................................5
Preface ..............................................................................................................................6
Summary Tables of Changes..........................................................................................8
Identification Information..............................................................................................16
Errata...............................................................................................................................18
Specification Changes...................................................................................................41
Specification Clarifications...........................................................................................42
Documentation Changes...............................................................................................43
§
3
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Intel® Xeon® Processor 5200 Series
Specification Update
4
Revision History
Revision
Description
Initial Release - WDP_Public
Date
-001
-002
November 2007
Added Errata AY43 through AY50
Updated Erratum AY26
December 2007
January 2008
Updated Erratum AY18
Added Erratum AY51
-003
Added Spec Clarification AY1
-004
-005
-006
-007
Added Erratum AY52
January 2008
February 2008
March 2008
April 2008
Added Erratum AY53 and AY54
Updated Table 1to support L5238
Added Specification Clairification on TLB
Added Erratum AY55-AY57
Added L5240 to Table 1
-008
-009
May 2008
June 2008
Added Erratum AY58
Added Erratum AY59-64
Updated Table 1 for E-step Processor samples
Updated C & E step microcode
-010
July 2008
Updated notes in Table 1. Added Tcontrol Enabling Range and
removed actual Tcontrol values
-011
-012
Added Erratum AY65, AY66
August 2008
October 2008
Added Erratum AY67-AY70
Added Production E-step S-spec numbers to Table 1
Added Erratum AY71
Added Production E-step S-spec numbers to Table 1
-013
-014
November 2008
December 2008
Updated Erratum AY68
Added Erratum AY72
-015
-016
-017
Updated Erratum AY1
February 2009
May 2009
Updated Power information for X5260 and E5205
Added Erratum AY73
June 2009
No changes....released to keep in sync with other related
documents
-018
-019
December 2010
December 2010
Added Erratum AY74-AY76
5
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Preface
This document is an update to the specifications contained in the Affected Documents
table 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
Document Number/
Location
Document Title
Intel® Xeon® Processor 5200 Series Datasheet
318590
Related Documents
Document Number/
Location
Document Title
AP-485, Intel® Processor Identification and the CPUID Instruction
http://www.intel.com/
design/processor/
applnots/241618.htm
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
http://www.intel.com/
products/processor/
manuals/index.htm
Intel® 64 and IA-32 Architectures Software Developer’s Manual,
Volume 3A: System Programming Guide
Intel® 64 and IA-32 Architectures Software Developer’s Manual,
Volume 3B: System Programming Guide
Intel® 64 and IA-32 Intel Architecture Optimization Reference
Manual
http://www.intel.com/
design/processor/
specupdt/252046.htm
Intel® 64 and IA-32 Architectures Software Developer’s Manual
Documentation Changes
Intel® Xeon® Processor 5200 Series
Specification Update
6
Nomenclature
Errata are design defects or errors. These may cause the Intel® Xeon® Processor
5200 Series 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.
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.
Specification Changes are modifications to the current published specifications.
These changes will be incorporated in any new 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 typos, errors, or omissions from the current
published specifications. These will be incorporated in any new release of the
specification.
Note:
Errata remain in the specification update throughout the product’s lifecycle, or until a
particular stepping is no longer commercially available. Under these circumstances,
errata removed from the specification update are archived and available upon request.
Specification changes, specification clarifications and documentation changes are
removed from the specification update when the appropriate changes are made to the
appropriate product specification or user documentation (datasheets, manuals, and so
forth).
7
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Summary Tables of Changes
The following tables indicate the errata, specification changes, specification
clarifications, or documentation changes which apply to the Intel® Xeon® Processor
5200 Series product. 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. These tables uses the following notations:
Codes Used in Summary Tables
Stepping
X:
Errata exists in the stepping indicated. Specification Change or
Clarification that applies to this stepping.
(No mark)
or (Blank box):
This erratum is fixed in listed stepping or specification change
does not apply to listed stepping.
Page
(Page):
Page location of item in this document.
Status
Doc:
Document change or update will be implemented.
This erratum may be fixed in a future stepping of the product.
This erratum has been previously fixed.
Plan Fix:
Fixed:
No Fix:
There are no plans to fix this erratum.
Row
Change bar to left of table row indicates this erratum is either new or modified from the
previous version of the document.
Each Specification Update item is prefixed with a capital letter to distinguish the
product. The key below details the letters that are used in Intel’s microprocessor
Specification Updates:
A =
C =
D =
E =
F =
I =
Intel® Xeon® processor 7000 sequence
Intel® Celeron® processor
Intel® Xeon® processor 2.80 GHz
Intel® Pentium® III processor
Intel® Pentium® processor Extreme Edition and Intel® Pentium® D processor
Intel® Xeon® processor 5000 series
J =
K =
64-bit Intel® Xeon® processor MP with 1MB L2 cache
Mobile Intel® Pentium® III processor
Intel® Xeon® Processor 5200 Series
Specification Update
8
L =
M =
N =
O =
P =
Q =
Intel® Celeron® D processor
Mobile Intel® Celeron® processor
Intel® Pentium® 4 processor
Intel® Xeon® processor MP
Intel ® Xeon® processor
Mobile Intel® Pentium® 4 processor supporting Intel® Hyper-Threading Technology
(Intel® HT Technology) on 90-nm process technology
R =
S =
Intel® Pentium® 4 processor on 90 nm process
64-bit Intel® Xeon® processor with 800 MHz system bus (1 MB and 2 MB L2 cache
versions)
T =
U =
V =
W=
X =
Mobile Intel® Pentium® 4 processor-M
64-bit Intel® Xeon® processor MP with up to 8 MB L3 cache
Mobile Intel® Celeron® processor on.13 micron process in Micro-FCPGA package
Intel® Celeron® M processor
Intel® Pentium® M processor on 90 nm process with 2-MB L2 cache and Intel®
processor A100 and A110 with 512-KB L2 cache
Y =
Intel® Pentium® M processor
Z =
Mobile Intel® Pentium® 4 processor with 533 MHz system bus
AA =
Intel® Pentium® D processor 900 sequence and Intel® Pentium® processor Extreme
Edition 955, 965
AB =
AC =
AD =
AE =
AF =
AG =
AH =
AI =
Intel® Pentium® 4 processor 6x1 sequence
Intel® Celeron® processor in 478 pin package
Intel® Celeron® D processor on 65nm_process
Intel® Core™ Duo processor and Intel® Core™ Solo processor on 65 nm process
Intel® Xeon® processor LV
Intel® Xeon® processor 5100 series
Intel® Core™2 Duo/Solo Processor for Intel® Centrino® Duo Processor Technology
Intel® Core™2 Extreme processor X6800 and Intel® Core™2 Duo desktop processor
E6000 and E4000 sequence
AJ =
Intel® Xeon® processor 5300 series
AK =
Intel® Core™2 Extreme processor QX6000 sequence and Intel® Core™2 processor
Q6000 sequence
AL =
AM =
AN =
AO =
AP =
AQ =
AR =
AS =
Intel® Xeon® processor 7100 series
Intel® Celeron® processor 400 sequence
Intel® Pentium® processor
Intel® Xeon® processor 3200 series
Intel® Xeon® processor 3000 series
Intel® Pentium® desktop processor E2000 sequence
Intel® Celeron processor 500 series
Intel® Xeon® processor 7200, 7300 series
9
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
AT =
AV =
Intel® Celeron® processor 200 series
Intel® Core™2 Extreme Processor QX9650 Sequence and Intel® Core™2 Processor
Q9000 Sequence processor
AW = Intel® Core™ 2 Duo processor E8000 series
AX =
AY =
AZ=
Intel® Xeon® Processor 5400 Series
Intel® Xeon® Processor 5200 Series
Intel® Core™2 Duo Processor and Intel® Core™2 Extreme Processor on 45-nm
Process
AAA= Intel® Xeon® processor 3300 series
AAB= Intel® Xeon® E3110 Processor
AAC= Intel® Celeron® processor E1000 series
AAD= Intel® Core™ 2 extreme Processor OX9775
AAE= Intel® Atom™ Processor Z5xx series
AAF=
Intel® Atom™ Processor 200 series
AAG= Intel® Atom™ Processor N series
AAH= Intel® Atom™ Processor 300 series
AAI=
Intel® Xeon® Processor 7400 Series
Intel® Xeon® Processor 5200 Series
Specification Update
10
Errata Intel® Xeon® Processor 5200 Series (Sheet 1 of 4)
Stepping Stepping
Status
(Hardware
Fix?)
Number
ERRATA
C-0
E-0
AY1
AY2
X
X
No Fix
No Fix
EFLAGS Discrepancy on Page Faults After a Translation Change
INVLPG Operation for Large (2M/4M) Pages May be Incomplete under
Certain Conditions
X
X
X
X
Store to WT Memory Data May be Seen in Wrong Order by Two Subsequent
Loads
AY3
No Fix
AY4
AY5
X
X
X
X
No Fix
No Fix
Non-Temporal Data Store May be Observed in Wrong Program Order
Page Access Bit May be Set Prior to Signaling a Code Segment Limit Fault
Updating Code Page Directory Attributes without TLB Invalidation May
Result in Improper Handling of Code #PF
AY6
AY7
AY8
X
X
X
X
X
X
No Fix
No Fix
No Fix
Storage of PEBS Record Delayed Following Execution of MOV SS or STI
Performance Monitoring Event FP_MMX_TRANS_TO_MMX May Not Count
Some Transitions
A REP STOS/MOVS to a MONITOR/MWAIT Address Range May Prevent
Triggering of the Monitoring Hardware
AY9
X
X
No Fix
AY10
AY11
AY12
AY13
AY14
X
X
X
X
X
X
X
X
X
X
No Fix
No Fix
No Fix
No Fix
No Fix
Performance Monitoring Event MISALIGN_MEM_REF May Over Count
The Processor May Report a #TS Instead of a #GP Fault
Code Segment Limit Violation May Occur on 4 Gigabyte Limit Check
A Write to an APIC Register Sometimes May Appear to Have Not Occurred
Last Branch Records (LBR) Updates May be Incorrect after a Task Switch
REP MOVS/STOS Executing with Fast Strings Enabled and Crossing Page
Boundaries with Inconsistent Memory Types may use an Incorrect Data Size
or Lead to Memory-Ordering Violations.
AY15
X
X
No Fix
Upper 32 bits of 'From' Address Reported through BTMs or BTSs May be
Incorrect
AY16
AY17
X
X
X
X
No Fix
No Fix
Address Reported by Machine-Check Architecture (MCA) on Single-bit L2
ECC Errors May be Incorrect
Code Segment Limit/Canonical Faults on RSM May be Serviced before
Higher Priority Interrupts/Exceptions and May Push the Wrong Address Onto
the Stack
AY18
X
X
No Fix
AY19
AY20
X
X
X
X
No Fix
No Fix
Store Ordering May be Incorrect between WC and WP Memory Type
EFLAGS, CR0, CR4 and the EXF4 Signal May be Incorrect after Shutdown
Premature Execution of a Load Operation Prior to Exception Handler
Invocation
AY21
AY22
AY23
AY24
AY25
X
X
X
X
X
X
X
X
X
X
No Fix
No Fix
No Fix
No Fix
No Fix
Performance Monitoring Events for Retired Instructions (C0H) May Not Be
Accurate
Returning to Real Mode from SMM with EFLAGS.VM Set May Result in
Unpredictable System Behavior
CMPSB, LODSB, or SCASB in 64-bit Mode with Count Greater or Equal to
248 May Terminate Early
Writing the Local Vector Table (LVT) when an Interrupt is Pending May
Cause an Unexpected Interrupt
11
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Errata Intel® Xeon® Processor 5200 Series (Sheet 2 of 4)
Stepping Stepping
Status
(Hardware
Fix?)
Number
ERRATA
C-0
E-0
Pending x87 FPU Exceptions (#MF) Following STI May Be Serviced Before
Higher Priority Interrupts
AY26
AY27
X
X
No Fix
No Fix
VERW/VERR/LSL/LAR Instructions May Unexpectedly Update the Last
Exception Record (LER) MSR
X
X
AY28
AY29
X
X
X
X
No Fix
No Fix
INIT Does Not Clear Global Entries in the TLB
Split Locked Stores May not Trigger the Monitoring Hardware
Programming the Digital Thermal Sensor (DTS) Threshold May Cause
Unexpected Thermal Interrupts
AY30
AY31
X
X
X
X
No Fix
No Fix
Writing Shared Unaligned Data that Crosses a Cache Line without Proper
Semaphores or Barriers May Expose a Memory Ordering Issue
General Protection (#GP) Fault May Not Be Signaled on Data Segment Limit
Violation above 4-G Limit
AY32
AY33
AY34
AY35
AY36
X
X
X
X
X
X
X
X
X
X
No Fix
No Fix
Plan Fix
No Fix
No Fix
An Asynchronous MCE During a Far Transfer May Corrupt ESP
CPUID Reports Architectural Performance Monitoring Version 2 is
Supported, When Only Version 1 Capabilities are Available
B0-B3 Bits in DR6 May Not be Properly Cleared After Code Breakpoint
An xTPR Update Transaction Cycle, if Enabled, May be Issued to the FSB
after the Processor has Issued a Stop-Grant Special Cycle
Performance Monitoring Event IA32_FIXED_CTR2 May Not Function
Properly when Max Ratio is a Non-Integer Core-to-Bus Ratio
AY37
AY38
AY39
X
X
X
Fixed
No Fix
No Fix
X
X
Instruction Fetch May Cause a Livelock During Snoops of the L1 Data Cache
Use of Memory Aliasing with Inconsistent Memory Type may Cause a
System Hang or a Machine Check Exception
A WB Store Following a REP STOS/MOVS or FXSAVE May Lead to
Memory-Ordering Violations
AY40
AY41
AY42
X
X
X
X
No Fix
Fixed
VM Exit with Exit Reason "TPR Below Threshold" Can Cause the Blocking
by MOV/POP SS and Blocking by STI Bits to be Cleared in the Guest
Interruptability-State Field
Using Memory Type Aliasing with Cacheable and WC Memory Types May
Lead to Memory Ordering Violations
X
X
No Fix
VM Exit Caused by a SIPI Results in Zero Being Saved to the Guest RIP
Field in the VMCS
AY43
AY44
AY45
X
X
X
No Fix
Fixed
Fixed
NMIs May Not Be Blocked by a VM-Entry Failure
Partial Streaming Load Instruction Sequence May Cause the Processor to
Hang
Self/Cross Modifying Code May Not be Detected or May Cause a Machine
Check Exception
AY46
AY47
AY48
AY49
X
X
X
X
X
X
Not Fixed
Fixed
Data TLB Eviction Condition in the Middle of a Cacheline Split Load
Operation May Cause the Processor to Hang
Update of Read/Write (R/W) or User/Supervisor (U/S) or Present (P) Bits
without TLB Shootdown May Cause Unexpected Processor Behavior
Fixed
RSM Instruction Execution under Certain Conditions May Cause Processor
Hang or Unexpected Instruction Execution Results
Fixed
Intel® Xeon® Processor 5200 Series
Specification Update
12
Errata Intel® Xeon® Processor 5200 Series (Sheet 3 of 4)
Stepping Stepping
Status
(Hardware
Fix?)
Number
ERRATA
C-0
E-0
Benign Exception after a Double Fault May Not Cause a Triple Fault
Shutdown
AY50
AY51
AY52
X
X
X
X
X
X
No Fix
No Fix
No Fix
LER MSRs May be Incorrectly Updated
Short Nested Loops That Span Multiple 16-Byte Boundaries May Cause a
Machine Check Exception or a System Hang
IA32_MC1_STATUS MSR Bit[60] Does Not Reflect Machine Check Error
Reporting Enable Correctly
AY53
AY54
X
X
X
X
No Fix
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
A VM Exit Due to a Fault While Delivering a Software Interrupt May Save
Incorrect Data into the VMCS
AY55
AY56
AY57
AY58
X
X
X
X
X
X
X
X
No Fix
No Fix
No Fix
No Fix
A VM Exit Occurring in IA-32e Mode May Not Produce a VMX Abort When
Expected
IRET under Certain Conditions May Cause an Unexpected Alignment Check
Exception
VM Entry May Fail When Attempting to Set
IA32_DEBUGCTL.FREEZE_WHILE_SMM_EN
AY59
AY60
AY61
X
X
X
No Fix
No Fix
No Fix
VM Entry May Use Wrong Address to Access Virtual-APIC Page
INIT Incorrectly Resets IA32_LSTAR MSR
CPUID Instruction May Return Incorrect Brand String
Global Instruction TLB Entries May Not be Invalidated on a VM Exit or VM
Entry
AY62
AY63
AY64
X
X
X
X
No Fix
No Fix
No Fix
XRSTOR Instruction May Cause Extra Memory Reads
Enabling PECI via the PECI_CTL MSR Does Not Enable PECI and May
Corrupt the CPUID Feature Flags
Corruption of CS Segment Register During RSM While Transitioning From
Real Mode to Protected Mode
AY65
X
X
X
No Fix
LBR, BTS, BTM May Report a Wrong Address when an Exception/Interrupt
Occurs in 64-bit Mode
AY66
AY67
AY68
AY69
AY70
AY71
AY72
X
X
X
X
X
X
X
No Fix
No Fix
No Fix
No Fix
No Fix
No Fix
Plan Fix
The XRSTOR Instruction May Fail to Cause a General-Protection Exception
The XSAVE Instruction May Erroneously Modify Reserved Bits in the
XSTATE_BV Field
Store Ordering Violation When Using XSAVE
Memory Ordering Violation With Stores/Loads Crossing a Cacheline
Boundary
X
X
X
B0-B3 Bits in DR6 For Non-Enabled Breakpoints May be Incorrectly Set
Unsynchronized Cross-Modifying Code Operations Can Cause Unexpected
Instruction Execution Results
A Page Fault May Not be Generated When the PS bit is set to “1” in a
PML4E or PDPTE
AY73
X
X
No Fix
13
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Errata Intel® Xeon® Processor 5200 Series (Sheet 4 of 4)
Stepping Stepping
Status
(Hardware
Fix?)
Number
ERRATA
C-0
E-0
AY74
AY75
AY76
X
X
X
X
X
X
No Fix
No Fix
No Fix
Not-Present Page Faults May Set the RSVD Flag in the Error Code
VM Exits Due to “NMI-Window Exiting” May Be Delayed by One Instruction
A 64-bit Register IP-relative Instruction May Return Unexpected Results
Intel® Xeon® Processor 5200 Series
Specification Update
14
Specification Changes
Number
SPECIFICATION CHANGES
None for this revision of this specification update.
Specification Clarifications
Number
SPECIFICATION CLARIFICATIONS
Some Intel® Xeon® Processor X5200 Series Processors May Exhibit Higher Extended HALT State Power
Consumption Than Specified.
AY1
AY2
Clarification of TRANSLATION LOOKASIDE BUFFERS (TLBS) Invalidation
Documentation Changes
Number
DOCUMENTATION CHANGES
None for this revision of this specification update.
15
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Identification Information
Component Identification via Programming Interface
The Intel® Xeon® Processor 5200 Series stepping can be identified by the following
register contents:
Extended
Extended
Processor
Family
Model
Stepping
Reserved
31:28
Reserved
15:14
1
2
3
4
5
6
Family
Model
Type
Code
Number
ID
27:20
19:16
13:12
11:8
7:4
3:0
0000000b
0001b
00b
0110b
0111b
XXXXb
When EAX is initialized to a value of 1, the CPUID instruction returns the Extended
Family, Extended Model, Type, Family, Model and Stepping value 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.
Notes:
1.
The Extended Family, bits [27:20] are used in conjunction with the Family Code, specified in bits [11:8],
to indicate whether the processor belongs to the Intel386, Intel486, Pentium, Pentium Pro, Pentium 4,
or Intel® Core™ processor family.
2.
3.
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’s family.
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.
5.
6.
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.
The Model Number corresponds 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 register accessible through Boundary Scan.
The Stepping ID in bits [3:0] indicates the revision number of that model. See Table 2 for the processor
stepping ID number in the CPUID information.
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.
Intel® Xeon® Processor 5200 Series
Specification Update
16
Component Marking Information
Intel® Xeon® Processor 5200 Series stepping can be identified by the following
component markings:
Figure 1.
Processor Top-side Markings (Example)
Legend:
Mark Text (Production Mark):
3.33GHz/6M/1333
Intel ® Xeon®
SXXX XXXXX
GROUP1LINE1
GROUP1LINE2
GROUP1LINE3
GROUP1LINE4
GROUP1LINE5
GROUP1LINE1
GROUP1LINE2
GROUP1LINE3
GROUP1LINE4
GROUP1LINE5
i (M) © ’07 x52XX
(FPO)
LOTNO
S/N
Table 1.
Intel® Xeon® Processor 5200 Series Identification Information
Data
Bus
L2
Cache
Size
Thermal
Design
Power
(TDP)
Core
Freq
(GHz)
Processor
Number
Core
Stepping
1
CPUID
Notes
S-Spec
Freq
(MHz)
(MB)
SLANH
SLANJ
SLANG
SLAND
SLANF
SLANM
SLAS3
SLBAQ
SLBAR
SLBAS
SLBAU
SLBAV
SLBAY
SLBAW
SLBAT
SLBAZ
SLBB3
X5272
X5260
E5205
E5240
E5220
L5238
L5240
X5270
X5272
X5260
E5205
L5248
L5240
E5240
E5220
L5238
L5215
C-0
C-0
C-0
C-0
C-0
C-0
C-0
E-0
E-0
E-0
E-0
E-0
E-0
E-0
E-0
E-0
E-0
10676h
10676h
10676h
10676h
10676h
10676h
10676h
1067Ah
1067Ah
1067Ah
1067Ah
1067Ah
1067Ah
1067Ah
1067Ah
1067Ah
1067Ah
3.40
3.33
1.86
3
1600
1333
1066
1333
1333
1333
1333
1333
1600
1333
1066
1333
1333
1333
1333
1333
1066
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
80
80
65
65
65
35
40
80
80
80
65
55
40
65
65
35
20
2.33
2.67
3
3.50
3.40
3.33
1.86
3
3
3
2.33
2.66
1.86
Notes:
1.
Processors in the QDF/S-Spec column that begin with a Q are for qualification only. PPS Samples.
17
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Errata
AY1.
EFLAGS Discrepancy on Page Fault After 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, the value
saved for EFLAGS may incorrectly contain the arithmetic flag values that the EFLAGS
register would have held had the instruction completed without fault. 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 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 a page
fault.
Workaround: If the page fault handler 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 Tables of Changes.
AY2.
INVLPG Operation for Large (2M/4M) Pages May be Incomplete under
Certain Conditions
Problem:
The INVLPG instruction may not completely invalidate Translation Look-aside Buffer
(TLB) entries for large pages (2M/4M) when both of the following conditions exist:
"Address range of the page being invalidated spans several Memory Type Range
Registers (MTRRs) with different memory types specified "INVLPG operation is
preceded by a Page Assist Event (Page Fault (#PF) or an access that results in either A
or D bits being set in a Page Table Entry (PTE)).
Implication: Stale translations may remain valid in TLB after a PTE update resulting in unpredictable
system behavior. Intel has not observed this erratum with any commercially available
software.
Workaround: Software should ensure that the memory type specified in the MTRRs is the same for
the entire address range of the large page.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY3.
Store to WT Memory Data May be Seen in Wrong Order by Two
Subsequent Loads
Problem:
When data of Store to WT memory is used by two subsequent loads of one thread and
another thread performs cacheable write to the same address the first load may get the
data from external memory or L2 written by another core, while the second load will
get the data straight from the WT Store.
Implication: Software that uses WB to WT memory aliasing may violate proper store ordering.
Workaround: Do not use WB to WT aliasing.
Status:
For the steppings affected, see the Summary Tables of Changes.
Intel® Xeon® Processor 5200 Series
Specification Update
18
AY4.
Non-Temporal Data Store May be Observed in Wrong Program Order
Problem:
When non-temporal data is accessed by multiple read operations in one thread while
another thread performs a cacheable write operation to the same address, the data
stored may be observed in wrong program order (i.e. later load operations may read
older data).
Implication: Software that uses non-temporal data without proper serialization before accessing the
non-temporal data may observe data in wrong program order.
Workaround: Software that conforms to the Intel® 64 and IA-32 Architectures Software Developer's
Manual, Volume 3A, section "Buffering of Write Combining Memory Locations" will
operate correctly.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY5.
Page Access Bit May be Set Prior to Signaling a Code Segment Limit
Fault
Problem:
If code segment limit is set close to the end of a code page, then due to this erratum
the memory page Access bit (A bit) may be set for the subsequent page prior to
general protection fault on code segment limit.
Implication: When this erratum occurs, a non-accessed page which is present in memory and
follows a page that contains the code segment limit may be tagged as accessed.
Workaround: Erratum can be avoided by placing a guard page (non-present or non-executable page)
as the last page of the segment or after the page that includes the code segment limit.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY6.
Updating Code Page Directory Attributes without TLB Invalidation May
Result in Improper Handling of Code #PF
Problem:
Code #PF (Page Fault exception) is normally handled in lower priority order relative to
both code #DB (Debug Exception) and code Segment Limit Violation #GP (General
Protection Fault). Due to this erratum, code #PF may be handled incorrectly, if all of the
following conditions are met:
1. A PDE (Page Directory Entry) is modified without invalidating the corresponding
TLB (Translation Look-aside Buffer) entry
2. Code execution transitions to a different code page such that both
• The target linear address corresponds to the modified PDE
• The PTE (Page Table Entry) for the target linear address has an A
(Accessed) bit that is clear
3. One of the following simultaneous exception conditions is present following the
code transition
• Code #DB and code #PF
• Code Segment Limit Violation #GP and code #PF
Implication: Software may observe either incorrect processing of code #PF before code Segment
Limit Violation #GP or processing of code #PF in lieu of code #DB.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY7.
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
19
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
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 Tables of Changes.
AY8.
Performance Monitoring Event FP_MMX_TRANS_TO_MMX May Not
Count Some Transitions
Problem:
Performance Monitor Event FP_MMX_TRANS_TO_MMX (Event CCH, Umask 01H) counts
transitions from x87 Floating Point (FP) to MMX™ 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 Tables of Changes.
AY9.
A REP STOS/MOVS to a MONITOR/MWAIT Address Range May Prevent
Triggering of the Monitoring Hardware
Problem:
The MONITOR instruction is used to arm the address monitoring hardware for the
subsequent MWAIT instruction. The hardware is triggered on subsequent memory store
operations to the monitored address range. Due to this erratum, REP STOS/MOVS fast
string operations to the monitored address range may prevent the actual triggering
store to be propagated to the monitoring hardware.
Implication: A logical processor executing an MWAIT instruction may not immediately continue
program execution if a REP STOS/MOVS targets the monitored address range.
Workaround: Software can avoid this erratum by not using REP STOS/MOVS store operations within
the monitored address range.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY10.
Performance Monitoring Event MISALIGN_MEM_REF May Over Count
Problem:
Performance monitoring event MISALIGN_MEM_REF (05H) is used to count the number
of memory accesses that cross an 8-byte boundary and are blocked until retirement.
Due to this erratum, the performance monitoring event MISALIGN_MEM_REF also
counts other memory accesses.
Implication: The performance monitoring event MISALIGN_MEM_REF may over count. The extent of
the over counting depends on the number of memory accesses retiring while the
counter is active.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
Intel® Xeon® Processor 5200 Series
Specification Update
20
AY11.
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 Tables of Changes.
AY12.
Code Segment Limit Violation May Occur on 4 Gigabyte Limit Check
Problem:
Code Segment limit violation may occur on 4 Gigabyte limit check when the code
stream wraps around in a way that one instruction ends at the last byte of the segment
and the next instruction begins at 0x0.
Implication: This is a rare condition that may result in a system hang. Intel has not observed this
erratum with any commercially available software, or system.
Workaround: Avoid code that wraps around segment limit.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY13.
A Write to an APIC Register Sometimes May Appear to Have Not
Occurred
Problem:
With respect to the retirement of instructions, stores to the uncacheable memory-
based APIC register space are handled in a non-synchronized way. For example if an
instruction that masks the interrupt flag, for example, CLI is executed soon after an
uncacheable write to the Task Priority Register (TPR) that lowers the APIC priority, the
interrupt masking operation may take effect before the actual priority has been
lowered. This may cause interrupts whose priority is lower than the initial TPR, but
higher than the final TPR, to not be serviced until the interrupt enabled flag is finally
set, i.e. by STI instruction. Interrupts will remain pending and are not lost.
Implication: In this example the processor may allow interrupts to be accepted but may delay their
service.
Workaround: This non-synchronization can be avoided by issuing an APIC register read after the
APIC register write. This will force the store to the APIC register before any subsequent
instructions are executed. No commercial operating system is known to be impacted by
this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY14.
Last Branch Records (LBR) Updates May be Incorrect after a Task
Switch
Problem:
A Task-State Segment (TSS) task switch may incorrectly set the LBR_FROM value to
the LBR_TO value.
Implication: The LBR_FROM will have the incorrect address of the Branch Instruction.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY15.
REP MOVS/STOS Executing with Fast Strings Enabled and Crossing
Page Boundaries with Inconsistent Memory Types 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
21
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
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 memory ordering 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 Tables of Changes.
AY16.
Upper 32 bits of 'From' Address Reported through BTMs or BTSs May
be Incorrect
Problem:
When a far transfer switches the processor from 32-bit mode to IA-32e mode, the
upper 32 bits of the 'From' (source) addresses reported through the BTMs (Branch
Trace Messages) or BTSs (Branch Trace Stores) may be incorrect.
Implication: The upper 32 bits of the 'From' address debug information reported through BTMs or
BTSs may be incorrect during this transition.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY17.
Address Reported by Machine-Check Architecture (MCA) on Single-bit
L2 ECC Errors May be Incorrect
Problem:
When correctable Single-bit ECC errors occur in the L2 cache, the address is logged in
the MCA address register (MCi_ADDR). Under some scenarios, the address reported
may be incorrect.
Implication: Software should not rely on the value reported in MCi_ADDR, for Single-bit L2 ECC
errors.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY18.
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 (e.g. NMI (Non-Maskable Interrupt), Debug break(#DB),
Machine Check (#MC), etc.). 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 5200 Series
Specification Update
22
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 Tables of Changes.
AY19.
Store Ordering May be Incorrect between WC and WP Memory Type
Problem:
According to Intel® 64 and IA-32 Intel Architecture Software Developer's Manual,
Volume 3A "Methods of Caching Available", WP (Write Protected) stores should drain
the WC (Write Combining) buffers in the same way as UC (Uncacheable) memory type
stores do. Due to this erratum, WP stores may not drain the WC buffers.
Implication: Memory ordering may be violated between WC and WP stores.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY20.
EFLAGS, CR0, CR4 and the EXF4 Signal May be Incorrect after
Shutdown
Problem:
When the processor is going into shutdown due to an RSM inconsistency failure,
EFLAGS, CR0 and CR4 may be incorrect. In addition the EXF4 signal may still be
asserted. This may be observed if the processor is taken out of shutdown by NMI#.
Implication: A processor that has been taken out of shutdown may have an incorrect EFLAGS, CR0
and CR4. In addition the EXF4 signal may still be asserted.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY21.
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.
1. If an instruction that performs a memory load causes a code segment limit
violation.
2. If a waiting X87 floating-point (FP) instruction or MMX™ technology (MMX)
instruction that performs a memory load has a floating-point exception pending.
3. 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-Stack (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 Tables of Changes.
23
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
AY22.
Performance Monitoring Events for Retired Instructions (C0H) May
Not Be Accurate
Problem:
The INST_RETIRED performance monitor may miscount retired instructions as follows:
• Repeat string and repeat I/O operations are not counted when a hardware interrupt
is received during or after the last iteration of the repeat flow.
• VMLAUNCH and VMRESUME instructions are not counted.
• HLT and MWAIT instructions are not counted. The following instructions, if executed
during HLT or MWAIT events, are also not counted:
a) RSM from a C-state SMI during an MWAIT instruction.
b) RSM from an SMI during a HLT instruction.
Implication: There may be a smaller than expected value in the INST_RETIRED performance
monitoring counter. The extent to which this value is smaller than expected is
determined by the frequency of the above cases.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY23.
Returning to Real Mode from SMM with EFLAGS.VM Set May Result in
Unpredictable System Behavior
Problem:
Returning back from SMM mode into real mode while EFLAGS.VM is set in SMRAM may
result in unpredictable system behavior.
Implication: If SMM software changes the values of the EFLAGS.VM in SMRAM, it may result in
unpredictable system behavior. Intel has not observed this behavior in commercially
available software.
Workaround: SMM software should not change the value of EFLAGS.VM in SMRAM.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY24.
CMPSB, LODSB, or SCASB in 64-bit Mode with Count Greater or Equal
48
to 2 May Terminate Early
Problem:
In 64-bit Mode CMPSB, LODSB, or SCASB executed with a repeat prefix and count
greater than or equal to 248 may terminate early. Early termination may result in one of
the following.
• The last iteration not being executed
• Signaling of a canonical limit fault (#GP) on the last iteration
Implication: While in 64-bit mode, with count greater or equal to 248, repeat string operations
CMPSB, LODSB or SCASB may terminate without completing the last iteration. Intel
has not observed this erratum with any commercially available software.
Workaround: Do not use repeated string operations with RCX greater than or equal to 248
.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY25.
Writing the Local Vector Table (LVT) when an Interrupt is Pending
May Cause an Unexpected Interrupt
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
Intel® Xeon® Processor 5200 Series
Specification Update
24
not do an End of Interrupt (EOI) the bit for the vector 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 Tables of Changes.
AY26.
Pending x87 FPU Exceptions (#MF) Following STI May Be Serviced
Before Higher Priority Interrupts
Problem:
Interrupts that are pending prior to the execution of the STI (Set Interrupt Flag)
instruction are normally serviced immediately after the instruction following the STI. An
exception to this is if the following instruction triggers a #MF. In this situation, the
interrupt should be serviced before the #MF. Because of this erratum, if following STI,
an instruction that triggers a #MF is executed while STPCLK#, Enhanced Intel
SpeedStep Technology transitions or Thermal Monitor events occur, the pending #MF
may be serviced before higher priority interrupts.
Implication: Software may observe #MF being serviced before higher priority interrupts.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY27.
VERW/VERR/LSL/LAR Instructions May Unexpectedly Update the Last
Exception Record (LER) MSR
Problem:
The LER MSR may be unexpectedly updated, if the resultant value of the Zero Flag (ZF)
is zero after executing the following instructions
1. VERR (ZF=0 indicates unsuccessful segment read verification)
2. VERW (ZF=0 indicates unsuccessful segment write verification)
3. LAR (ZF=0 indicates unsuccessful access rights load)
4. LSL (ZF=0 indicates unsuccessful segment limit load)
Implication: The value of the LER MSR may be inaccurate if VERW/VERR/LSL/LAR instructions are
executed after the occurrence of an exception.
Workaround: Software exception handlers that rely on the LER MSR value should read the LER MSR
before executing VERW/VERR/LSL/LAR instructions.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY28.
INIT Does Not Clear Global Entries in the TLB
Problem:
INIT may not flush a TLB entry when:
• The processor is in protected mode with paging enabled and the page global enable
flag is set (PGE bit of CR4 register)
• G bit for the page table entry is set
• TLB entry is present in TLB when INIT occurs
Implication: Software may encounter unexpected page fault or incorrect address translation due to
a TLB entry erroneously left in TLB after INIT.
25
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Workaround: Write to CR3, CR4 (setting bits PSE, PGE or PAE) or CR0 (setting bits PG or PE)
registers before writing to memory early in BIOS code to clear all the global entries
from TLB.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY29.
Split Locked Stores May not Trigger the Monitoring Hardware
Problem:
Logical processors normally resume program execution following the MWAIT, when
another logical processor performs a write access to a WB cacheable address within the
address range used to perform the MONITOR operation. Due to this erratum, a logical
processor may not resume execution until the next targeted interrupt event or O/S
timer tick following a locked store that spans across cache lines within the monitored
address range.
Implication: The logical processor that executed the MWAIT instruction may not resume execution
until the next targeted interrupt event or O/S timer tick in the case where the
monitored address is written by a locked store which is split across cache lines.
Workaround: Do not use locked stores that span cache lines in the monitored address range.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY30.
Programming the Digital Thermal Sensor (DTS) Threshold May Cause
Unexpected Thermal Interrupts
Problem:
Software can enable DTS thermal interrupts by programming the thermal threshold
and setting the respective thermal interrupt enable bit. When programming DTS value,
the previous DTS threshold may be crossed. This will generate an unexpected thermal
interrupt.
Implication: Software may observe an unexpected thermal interrupt occur after reprogramming the
thermal threshold.
Workaround: In the ACPI/OS implement a workaround by temporarily disabling the DTS threshold
interrupt before updating the DTS threshold value.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY31.
Writing Shared Unaligned Data that Crosses a Cache Line without
Proper Semaphores or Barriers May Expose a Memory Ordering Issue
Problem:
Software which is written so that multiple agents can modify the same shared
unaligned memory location at the same time may experience a memory ordering issue
if multiple loads access this shared data shortly thereafter. Exposure to this problem
requires the use of a data write which spans a cache line boundary.
Implication: This erratum may cause loads to be observed out of order. Intel has not observed this
erratum with any commercially available software or system.
Workaround: Software should ensure at least one of the following is true when modifying shared
data by multiple agents:
• The shared data is aligned
• Proper semaphores or barriers are used in order to prevent concurrent data
accesses.
Status:
For the steppings affected, see the Summary Tables of Changes
Intel® Xeon® Processor 5200 Series
Specification Update
26
AY32.
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.
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 Tables of Changes.
AY33.
An Asynchronous MCE During a Far Transfer May Corrupt ESP
Problem:
If an asynchronous machine check occurs during an interrupt, call through gate, FAR
RET or IRET and in the presence of certain internal conditions, ESP may be corrupted.
Implication: If the MCE (Machine Check Exception) handler is called without a stack switch, then a
triple fault will occur due to the corrupted stack pointer, resulting in a processor
shutdown. If the MCE is called with a stack switch, e.g. when the CPL (Current Privilege
Level) was changed or when going through an interrupt task gate, then the corrupted
ESP will be saved on the new stack or in the TSS (Task State Segment), and will not be
used.
Workaround: Use an interrupt task gate for the machine check handler.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY34.
CPUID Reports Architectural Performance Monitoring Version 2 is
Supported, When Only Version 1 Capabilities are Available
Problem:
CPUID leaf 0Ah reports the architectural performance monitoring version that is
available in EAX[7:0]. Due to this erratum CPUID reports the supported version as 2
instead of 1.
Implication: Software will observe an incorrect version number in CPUID.0Ah.EAX [7:0] in
comparison to which features are actually supported.
Workaround: Software should use the recommended enumeration mechanism described in the
Architectural Performance Monitoring section of the Intel® 64 and IA-32 Architectures
Software Developer's Manual, Volume 3: System Programming Guide.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY35.
B0-B3 Bits in DR6 May Not be Properly Cleared After Code Breakpoint
Problem:
B0-B3 bits (breakpoint conditions detect flags, bits [3:0]) in DR6 may not be properly
cleared when the following sequence happens:
1. POP instruction to SS (Stack Segment) selector;
2. Next instruction is FP (Floating Point) that gets FP assist followed by code
breakpoint.
Implication: B0-B3 bits in DR6 may not be properly cleared.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
27
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
AY36.
An xTPR Update Transaction Cycle, if Enabled, May be Issued to the
FSB after the Processor has Issued a Stop-Grant Special Cycle
Problem:
According to the FSB (Front Side Bus) protocol specification, no FSB cycles should be
issued by the processor once a Stop-Grant special cycle has been issued to the bus. If
xTPR update transactions are enabled by clearing the IA32_MISC_ENABLES[bit 23] at
the time of Stop-Clock assertion, an xTPR update transaction cycle may be issued to
the FSB after the processor has issued a Stop Grant Acknowledge transaction.
Implication: When this erratum occurs in systems using C-states C2 (Stop-Grant State) and higher
the result could be a system hang.
Workaround: BIOS must leave the xTPR update transactions disabled (default).
Status:
For the steppings affected, see the Summary Tables of Changes.
AY37.
Performance Monitoring Event IA32_FIXED_CTR2 May Not Function
Properly when Max Ratio is a Non-Integer Core-to-Bus Ratio
Problem:
Performance Counter IA32_FIXED_CTR2 (MSR 30BH) event counts CPU reference
clocks when the core is not in a halt state. This event is not affected by core frequency
changes (e.g., P states, TM2 transitions) but counts at the same frequency as the
Time-Stamp Counter IA32_TIME_STAMP_COUNTER (MSR 10H). Due to this erratum,
the IA32_FIXED_CTR2 will not function properly when the non-integer core-to-bus
ratio multiplier feature is used and when a non-zero value is written to IA32_
FIXED_CTR2. Non-integer core-to-bus ratio enables additional operating frequencies.
This feature can be detected by IA32_PLATFORM_ID (MSR 17H) bit [23].
Implication: The Performance Monitoring Event IA32_FIXED_CTR2 may result in an inaccurate
count when the non-integer core-to-bus multiplier feature is used.
Workaround: If writing to IA32_FIXED_CTR2 and using a non-integer core-to-bus ratio multiplier,
always write a zero.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY38.
Instruction Fetch May Cause a Livelock During Snoops of the L1 Data
Cache
Problem:
A livelock may be observed in rare conditions when instruction fetch causes multiple
level one data cache snoops.
Implication: Due to this erratum, a livelock may occur. Intel has not observed this erratum with any
commercially available software.
Workaround: It is possible for BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY39.
Use of Memory Aliasing with Inconsistent Memory Type may Cause a
System Hang or a Machine Check Exception
Problem:
Software that implements memory aliasing by having more than one linear addresses
mapped to the same physical page with different cache types may cause the system to
hang or to report a machine check exception (MCE). This would occur if one of the
addresses is non-cacheable and used in a code segment and the other is a cacheable
address. If the cacheable address finds its way into the instruction cache, and the non-
cacheable address is fetched in the IFU, the processor may invalidate the non-
cacheable address from the fetch unit. Any micro-architectural event that causes
instruction restart will be expecting this instruction to still be in the fetch unit and lack
of it will cause a system hang or an MCE.
Implication: This erratum has not been observed with commercially available software.
Intel® Xeon® Processor 5200 Series
Specification Update
28
Workaround: Although it is possible to have a single physical page mapped by two different linear
addresses with different memory types, Intel has strongly discouraged this practice as
it may lead to undefined results. Software that needs to implement memory aliasing
should manage the memory type consistency.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY40.
A WB Store Following a REP STOS/MOVS or FXSAVE May 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 may perform REP MOVS or REP STOS as write combining
stores (referred to as "fast strings") for optimal performance. FXSAVE may also be
internally implemented using write combining stores. Due to this erratum, stores of a
WB (write back) memory type to a cache line previously written by a preceding fast
string/FXSAVE instruction may be observed before string/FXSAVE stores.
Implication: A write-back store may be observed before a previous string or FXSAVE related store.
Intel has not observed this erratum with any commercially available software.
Workaround: Software desiring strict ordering of string/FXSAVE operations relative to subsequent
write-back stores should add an MFENCE or SFENCE instruction between the string/
FXSAVE operation and following store-order sensitive code such as that used for
synchronization.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY41.
VM Exit with Exit Reason "TPR Below Threshold" Can Cause the
Blocking by MOV/POP SS and Blocking by STI Bits to be Cleared in the
Guest Interruptability-State Field
Problem:
As specified in Section, "VM Exits Induced by the TPR Shadow", in the Intel® 64 and
IA-32 Architectures Software Developer's Manual, Volume 3B, a VM exit occurs
immediately after any VM entry performed with the "use TPR shadow", "activate
secondary controls", and "virtualize APIC accesses" VM-execution controls all set to 1
and with the value of the TPR shadow (bits 7:4 in byte 80H of the virtual-APIC page)
less than the TPR-threshold VM-execution control field. Due to this erratum, such a VM
exit will clear bit 0 (blocking by STI) and bit 1 (blocking by MOV/POP SS) of the
interruptability-state field of the guest-state area of the VMCS (bit 0 - blocking by STI
and bit 1 - blocking by MOV/POP SS should be left unmodified).
Implication: Since the STI, MOV SS, and POP SS instructions cannot modify the TPR shadow, bits
1:0 of the interruptability-state field will usually be zero before any VM entry meeting
the preconditions of this erratum; behavior is correct in this case. However, if VMM
software raises the value of the TPR-threshold VM-execution control field above that of
the TPR shadow while either of those bits is 1, incorrect behavior may result. This may
lead to VMM software prematurely injecting an interrupt into a guest. Intel has not
observed this erratum with any commercially available software.
Workaround: VMM software raising the value of the TPR-threshold VM-execution control field should
compare it to the TPR shadow. If the threshold value is higher, software should not
perform a VM entry; instead, it could perform the actions that it would normally take in
response to a VM exit with exit reason "TPR below threshold".
Status:
For the steppings affected, see the Summary Tables of Changes.
29
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
AY42.
Using Memory Type Aliasing with Cacheable and WC Memory Types
May Lead to Memory Ordering Violations
Problem:
Memory type aliasing occurs when a single physical page is mapped to two or more
different linear addresses, each with different memory types. Memory type aliasing
with a cacheable memory type and WC (write combining) may cause the processor to
perform incorrect operations leading to memory ordering violations for WC operations.
Implication: Software that uses aliasing between cacheable and WC memory types may observe
memory ordering errors within WC memory operations. Intel has not observed this
erratum with any commercially available software.
Workaround: None identified. Intel does not support the use of cacheable and WC memory type
aliasing, and WC operations are defined as weakly ordered.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY43.
VM Exit Caused by a SIPI Results in Zero Being Saved to the Guest RIP
Field in the VMCS
Problem:
If a logical processor is in VMX non-root operation and in the wait-for-SIPI state, an
occurrence of a start-up IPI (SIPI) causes a VM exit. Due to this erratum, such VM exits
always save zero into the RIP field of the guest-state area of the virtual-machine
control structure (VMCS) instead of the value of RIP before the SIPI was received.
Implication: In the absence of virtualization, a SIPI received by a logical processor in the wait-for-
SIPI state results in the logical processor starting execution from the vector sent in the
SIPI regardless of the value of RIP before the SIPI was received. A virtual-machine
monitor (VMM) responding to a SIPI-induced VM exit can emulate this behavior
because the SIPI vector is saved in the lower 8 bits of the exit qualification field in the
VMCS. Such a VMM should be unaffected by this erratum. A VMM that does not emulate
this behavior may need to recover the old value of RIP through alternative means. Intel
has not observed this erratum with any commercially available software.
Workaround: VMM software that may respond to SIPI-induced VM exits by resuming the interrupt
guest context without emulating the non-virtualized SIPI response should (1) save
from the VMCS (using VMREAD) the value of RIP before any VM entry to the wait-for
SIPI state; and (2) restore to the VMCS (using VMWRITE) that value before the next
VM entry that resumes the guest in any state other than wait-for-SIPI.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY44.
NMIs May Not Be Blocked by a VM-Entry Failure
Problem:
The Intel® 64 and IA-32 Architectures Software Developer's Manual Volume 3B:
System Programming Guide, Part 2 specifies that, following a VM-entry failure during or
after loading guest state, "the state of blocking by NMI is what it was before VM entry."
If non-maskable interrupts (NMIs) are blocked and the "virtual NMIs" VM-execution
control set to 1, this erratum may result in NMIs not being blocked after a VM-entry
failure during or after loading guest state.
Implication: VM-entry failures that cause NMIs to become unblocked may cause the processor to
deliver an NMI to software that is not prepared for it.
Workaround: VMM software should configure the virtual-machine control structure (VMCS) so that
VM-entry failures do not occur.
Status:
For the steppings affected, see the Summary Tables of Changes.
Intel® Xeon® Processor 5200 Series
Specification Update
30
AY45.
Partial Streaming Load Instruction Sequence May Cause the Processor
to Hang
Problem:
Under some rare conditions, when multiple streaming load instructions (MOVNTDQA)
are mixed with non-streaming loads that split across cache lines, the processor may
hang.
Implication: Under the scenario described above, the processor may 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. However,
streaming behavior may be re-enabled by setting bit 5 to 1 of the MSR at address 0x21
for software development or testing purposes. If this bit is changed, then a read-
modify-write should be performed to preserve other bits of this MSR. When the
streaming behavior is enabled and using streaming load instructions, always consume
a full cache line worth of data and/or avoid mixing them with non-streaming memory
references. If streaming loads are used to read partial cache lines, and mixed with non-
streaming memory references, use fences to isolate the streaming load operations
from non-streaming memory operations.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY46.
Self/Cross Modifying Code May Not be Detected or May Cause a
Machine Check Exception
Problem:
If instructions from at least three different ways in the same instruction cache set exist
in the pipeline combined with some rare internal state, self-modifying code (SMC) or
cross-modifying code may not be detected and/or handled.
Implication: An instruction that should be overwritten by another instruction while in the processor
pipeline may not be detected/modified, and could retire without detection. Alternatively
the instruction may cause a Machine Check Exception. 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 Tables of Changes.
AY47.
Data TLB Eviction Condition in the Middle of a Cacheline Split Load
Operation May Cause the Processor to Hang
Problem:
If the TLB translation gets evicted while completing a cacheline split load operation,
under rare scenarios the processor may hang.
Implication: The cacheline split load operation may not be able to complete normally, and the
machine may hang and generate Machine Check Exception. 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 Tables of Changes.
AY48.
Update of Read/Write (R/W) or User/Supervisor (U/S) or Present (P)
Bits without TLB Shootdown May Cause Unexpected Processor
Behavior
Problem:
Updating a page table entry by changing R/W, U/S or P bits, even when transitioning
these bits from 0 to 1, without keeping the affected linear address range coherent with
all TLB (Translation Lookaside Buffers) and paging-structures caches in the processor,
in conjunction with a complex sequence of internal processor micro-architectural
events and store operations, may lead to unexpected processor behavior.
31
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Implication: This erratum may lead to livelock, shutdown or other unexpected processor behavior.
Intel has not observed this erratum with any commercially available software.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY49.
RSM Instruction Execution under Certain Conditions May Cause
Processor Hang or Unexpected Instruction Execution Results
Problem:
Problem: RSM instruction execution, under certain conditions triggered by a complex
sequence of internal processor micro-architectural events, may lead to processor hang,
or unexpected instruction execution results.
Implication: In the above sequence, the processor may live lock or hang, or RSM instruction may
restart the interrupted processor context through a nondeterministic EIP offset in the
code segment, resulting in unexpected instruction execution, unexpected exceptions or
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 Tables of Changes.
AY50.
Benign Exception after a Double Fault May Not Cause a Triple Fault
Shutdown
Problem:
According to the Intel® 64 and IA-32 Architectures Software Developer's Manual,
Volume 3A, "Exception and Interrupt Reference", if another exception occurs while
attempting to call the double-fault handler, the processor enters shutdown mode. Due
to this erratum, any benign faults while attempting to call double-fault handler will not
cause a shutdown. However Contributory Exceptions and Page Faults will continue to
cause a triple fault shutdown.
Implication: If a benign exception occurs while attempting to call the double-fault handler, the
processor may hang or may handle the benign exception. Intel has not observed this
erratum with any commercially available software.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY51.
LER MSRs May be Incorrectly Updated
Problem:
The LER (Last Exception Record) MSRs, MSR_LER_FROM_LIP (1DDH) and
MSR_LER_TO_LIP (1DEH) may contain incorrect values after any of the following:
• Either STPCLK#, NMI (NonMaskable Interrupt) or external interrupts
• CMP or TEST instructions with an uncacheable memory operand followed by a
conditional jump
• STI/POP SS/MOV SS instructions followed by CMP or TEST instructions and then by
a conditional jump
Implication: When the conditions for this erratum occur, the value of the LER MSRs may be
incorrectly updated.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
Intel® Xeon® Processor 5200 Series
Specification Update
32
AY52.
Short Nested Loops That Span Multiple 16-Byte Boundaries May Cause
a Machine Check Exception or a System Hang
Problem:
Under a rare set of timing conditions and address alignment of instructions in a short
nested loop sequence, software that contains multiple conditional jump instructions
and spans multiple 16-byte boundaries, may cause a machine check exception or a
system hang.
Implication: Due to this erratum, a machine check exception or a system hang may occur.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY53.
IA32_MC1_STATUS MSR Bit[60] Does Not Reflect Machine Check Error
Reporting Enable Correctly
Problem:
IA32_MC1_STATUS MSR (405H) bit[60] (EN- Error Enabled) is supposed to indicate
whether the enable bit in the IA32_MC1_CTL MSR (404H) was set at the time of the
last update to the IA32_MC1_STATUS MSR. Due to this erratum, IA32_MC1_STATUS
MSR bit[60] instead reports the current value of the IA32_MC1_CTL MSR enable bit.
Implication: IA32_MC1_STATUS MSR bit [60] may not reflect the correct state of the enable bit in
the IA32_MC1_CTL MSR at the time of the last update.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY54.
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
invalid 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 following 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 IA-32 Intel® Architecture 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 Tables of Changes.
AY55.
A VM Exit Due to a Fault While Delivering a Software Interrupt May
Save Incorrect Data into the VMCS
Problem:
If a fault occurs during delivery of a software interrupt (INTn) in virtual-8086 mode
when virtual mode extensions are in effect and that fault causes a VM exit, incorrect
data may be saved into the VMCS. Specifically, information about the software interrupt
33
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
may not be reported in the IDT-vectoring information field. In addition, the
Interruptability-state field may indicate blocking by STI or by MOV SS if such blocking
were in effect before execution of the INTn instruction or before execution of the VM-
entry instruction that injected the software interrupt.
Implication: In general, VMM software that follows the guidelines given in the section “Handling VM
Exits Due to Exceptions” of Intel® 64 and IA-32 Architectures Software Developer’s
Manual Volume 3B: System Programming Guide should not be affected. If the erratum
improperly causes indication of blocking by STI or by MOV SS, the ability of a VMM to
inject an interrupt may be delayed by one instruction.
Workaround: VMM software should follow the guidelines given in the section “Handling VM Exits Due
to Exceptions” of Intel® 64 and IA-32 Architectures Software Developer’s Manual
Volume 3B: System Programming Guide.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY56.
A VM Exit Occurring in IA-32e Mode May Not Produce a VMX Abort
When Expected
Problem:
If a VM exit occurs while the processor is in IA-32e mode and the “host address-space
size” VM-exit control is 0, a VMX abort should occur. Due to this erratum, the expected
VMX aborts may not occur and instead the VM Exit will occur normally. The conditions
required to observe this erratum are a VM entry that returns from SMM with the “IA-
32e guest” VM-entry control set to 1 in the SMM VMCS and the “host address-space
size” VM-exit control cleared to 0 in the executive VMCS.
Implication: A VM Exit will occur when a VMX Abort was expected.
Workaround: An SMM VMM should always set the “IA-32e guest” VM-entry control in the SMM VMCS
to be the value that was in the LMA bit (IA32_EFER.LMA.LMA[bit 10]) in the IA32_EFER
MSR (C0000080H) at the time of the last SMM VM exit. If this guideline is followed, that
value will be 1 only if the “host address-space size” VM-exit control is 1 in the executive
VMCS.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY57.
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 Tables of Changes.
AY58.
VM Entry May Fail When Attempting to Set
IA32_DEBUGCTL.FREEZE_WHILE_SMM_EN
Problem:
If bit 14 (FREEZE_WHILE_SMM_EN) is set in the IA32_DEBUGCTL field in the guest-
state area of the VMCS, VM entry may fail as described in Section “VM-Entry Failures
During or After Loading Guest State” of Intel® 64 and IA-32 Architectures Software
Developer’s Manual Volume 3B: System Programming Guide, Part 2. (The exit reason
will be 80000021H and the exit qualification will be zero.) Note that the
Intel® Xeon® Processor 5200 Series
Specification Update
34
FREEZE_WHILE_SMM_EN bit in the guest IA32_DEBUGCTL field may be set due to a
VMWRITE to that field or due to VM exit that occurs while
IA32_DEBUGCTL.FREEZE_WHILE_SMM_EN=1
a
Implication: A VMM will not be able to properly virtualize a guest using the FREEZE_WHILE_SMM
feature.
Workaround: It is possible for the BIOS to contain a workaround for this erratum. Alternatively, the
following software workaround may be used. If
a
VMM wants to use the
FREEZE_WHILE_SMM feature, it can configure an entry in the VM-entry MSR-load area
for the IA32_DEBUGCTL MSR (1D9H); the value in the entry should set the
FREEZE_WHILE_SMM_EN bit. In addition, the VMM should use VMWRITE to clear the
FREEZE_WHILE_SMM_EN bit in the guest IA32_DEBUGCTL field before every VM entry.
(It is necessary to do this before every VM entry because each VM exit will save that bit
as 1.) This workaround prevents the VM-entry failure and sets the
FREEZE_WHILE_SMM_EN bit in the IA32_DEBUGCTL MSR.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY59.
VM Entry May Use Wrong Address to Access Virtual-APIC Page
Problem:
When XFEATURE_ENABLED_MASK register (XCR0) bit 1 (SSE) is 1, a VM entry
executed with the "use TPR shadow" VM-execution control set to 1 may use the wrong
address to access data on the virtual-APIC page.
Implication: An affected VM entry may exhibit the following behaviors: (1) it may use wrong areas
of the virtual-APIC page to determine whether VM entry fails or whether it induces a VM
exit due to the TPR threshold; or (2) it may clear wrong areas of the virtual-APIC page.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY60.
INIT Incorrectly Resets IA32_LSTAR MSR
Problem:
In response to an INIT reset initiated either via the INIT# pin or an IPI (Inter Processor
Interrupt), the processor should leave MSR values unchanged. Due to this erratum
IA32_LSTAR MSR (C0000082H), which is used by the iA32e SYSCALL instruction, is
being cleared by an INIT reset.
Implication: If software programs a value in IA32_LSTAR to be used by the SYSCALL instruction and
the processor subsequently receives an INIT reset, the SYSCALL instructions will not
behave as intended. Intel has not observed this erratum in 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 Tables of Changes.
AY61.
CPUID Instruction May Return Incorrect Brand String
Problem:
When a CPUID instruction is executed with EAX = 8000_0002H, 8000_0003H, or
8000_0004H, the returned EAX, EBX, ECX, and/or EDX values may be incorrect.
Implication: When this erratum occurs, the processor may report an incorrect brand string.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY62.
Global Instruction TLB Entries May Not be Invalidated on a VM Exit or
VM Entry
Problem:
If a VMM is using global page entries (CR4.PGE is enabled and any present page-
directories or page-table entries are marked global), then on a VM entry, the
instruction TLB (Translation Lookaside Buffer) entries caching global page translations
35
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
of the VMM may not be invalidated. In addition, if a guest is using global page entries,
then on a VM exit, the instruction TLB entries caching global page translations of the
guest may not be invalidated.
Implication: Stale global instruction linear to physical page translations may be used by a VMM after
a VM exit or a guest after a VM entry.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY63.
XRSTOR Instruction May Cause Extra Memory Reads
Problem:
An XRSTOR instruction will cause non-speculative accesses to XSAVE memory area
locations containing the FCW/FSW and FOP/FTW Floating Point registers even though
the 64-bit restore mask specified in the EDX:EAX register pair does not indicate to
restore the x87 FPU state.
Implication: Page faults, data breakpoint triggers, etc. may occur due to the unexpected non-
speculative accesses to these memory locations.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY64.
Enabling PECI via the PECI_CTL MSR Does Not Enable PECI and May
Corrupt the CPUID Feature Flags
Problem:
Writing PECI_CTL MSR (Platform Environment Control Interface Control Register) will
not update the PECI_CTL MSR (5A0H), instead it may corrupt the CPUID feature flags.
Implication: Due to this erratum, PECI (Platform Environment Control Interface) will not be enabled
as expected by the software. In addition, due to this erratum, processor features
reported in ECX following execution of leaf 1 of CPUID (EAX=1) may be masked.
Software utilizing CPUID leaf 1 to verify processor capabilities may not work as
intended.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY65.
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 immediately 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 Tables of Changes.
Intel® Xeon® Processor 5200 Series
Specification Update
36
AY66.
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 (0x00007FFFFFFFFFFF)
in 64-bit mode, the LBR return registers will save a wrong return address with 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 Tables of Changes.
AY67.
The XRSTOR Instruction May Fail to Cause a General-Protection
Exception
Problem:
The XFEATURE_ENABLED_MASK register (XCR0) bits [63:9] are reserved and must be
0; consequently, the XRSTOR instruction should cause a general-protection exception if
any of the corresponding bits in the XSTATE_BV field in the header of the XSAVE/
XRSTOR area is set to 1. Due to this erratum, a logical processor may fail to cause such
an exception if one or more of these reserved bits are set to 1.
Implication: Software may not operate correctly if it relies on the XRSTOR instruction to cause a
general-protection exception when any of the bits [63:9] in the XSTATE_BV field in the
header of the XSAVE/XRSTOR area is set to 1.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY68.
The XSAVE Instruction May Erroneously Modify Reserved Bits in the
XSTATE_BV Field
Problem:
Bits 63:2 of the HEADER.XSTATE_BV are reserved and must be 0. Due to this erratum,
the XSAVE instruction may erroneously modify one or more of these bits.
Implication: If one of bits 63:2 of the XSTATE_BV field in the header of the XSAVE/XRSTOR area had
been 1 and was then cleared by the XSAVE instruction, a subsequent execution of
XRSTOR may not generate the #GP (general-protection exception) that would have
occurred in the absence of this erratum. Alternatively, if one of those bits had been 0
and was then set by the XSAVE instruction, a subsequent execution of XRSTOR may
generate a #GP that would not have occurred in the absence of this erratum.
Workaround: It is possible for the BIOS to contain a partial workaround for this erratum that
prevents XSAVE from setting HEADER.XSTATE_BV reserved bits. To ensure
compatibility with future processors, software should not set any XSTATE_BV reserved
bits when configuring the header of the XSAVE/XRSTOR save area.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY69.
Store Ordering Violation When Using XSAVE
Problem:
The store operations done as part of the XSAVE instruction may cause a store ordering
violation with older store operations. The store operations done to save the processor
context in the XSAVE instruction flow, when XSAVE is used to store only the SSE
context, may appear to execute before the completion of older store operations.
37
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Implication: Execution of the stores in XSAVE, when XSAVE is used to store SSE context only, may
not follow program order and may execute before older stores. Intel has not observed
this erratum with any commercially available software.
Workaround: None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY70.
Memory Ordering Violation With Stores/Loads Crossing a Cacheline
Boundary
Problem:
When two logical processors are accessing the same data that is crossing a cacheline
boundary without serialization, with a specific set of processor internal conditions, it is
possible to have an ordering violation between memory store and load operations.
Implication: Due to this erratum, proper load store ordering may not be followed when multiple
logical processors are accessing the same data that crosses a cacheline boundary
without serialization.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:
For the steppings affected, see the Summary Tables of Changes.
AY71.
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:
a. MOV or POP instruction to SS (Stack Segment) selector;
b. Next instruction is FP (Floating Point) that gets FP assist
c. Another instruction after the FP instruction completes successfully
d. A breakpoint occurs due to either 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 Tables of Changes.
AY72.
Unsynchronized Cross-Modifying Code Operations Can Cause
Unexpected Instruction Execution Results
Problem:
The act of one processor, or system bus master, writing data into a currently executing
code segment of a second processor with the intent of having the second processor
execute that data as code is called cross-modifying code (XMC). XMC that does not
force the second processor to execute a synchronizing instruction, prior to execution of
the new code, is called unsynchronized XMC. Software using unsynchronized XMC to
modify the instruction byte stream of a processor can see unexpected or unpredictable
execution behavior from the processor that is executing the modified code.
Implication: In this case, the phrase "unexpected or unpredictable execution behavior"
encompasses the generation of most of the exceptions listed in the Intel® Architecture
Software Developer's Manual Volume 3: System Programming Guide, including a
General Protection Fault (GPF) or other unexpected behaviors. In the event that
unpredictable execution causes a GPF the application executing the unsynchronized
XMC operation would be terminated by the operating system.
Workaround: In order to avoid this erratum, programmers should use the XMC synchronization
algorithm as detailed in the Intel Architecture Software Developer's Manual Volume 3:
System Programming Guide, Section: Handling Self- and Cross-Modifying Code.
Intel® Xeon® Processor 5200 Series
Specification Update
38
Status:
For the steppings affected, see the ”Summary Tables of Changes”.
AY73.
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 Bit (Bit 0) set to
“1”.
Status:
For the steppings affected, see the ”Summary Tables of Changes”.
AY74.
Not-Present Page Faults May Set the RSVD Flag in the Error Code
Problem:
An attempt to access a page that is not marked present causes a page fault. Such a
page fault delivers an error code in which both the P flag (bit 0) and the RSVD flag (bit
3) are 0. Due to this erratum, not-present page faults may deliver an error code in
which the P flag is 0 but the RSVD flag is 1.
Implication: Software may erroneously infer that a page fault was due to a reserved-bit violation
when it was actually due to an attempt to access a not-present page. Intel has not
observed this erratum with any commercially available software.
Workaround: Page-fault handlers should ignore the RSVD flag in the error code if the P flag is 0.
Status:
For the steppings affected, see the ”Summary Tables of Changes”
AY75.
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 no blocking of
events by STI. 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 erratum, the VM exit may be delayed
by one additional instruction.
Implication: VMM software using “NMI-window exiting” for NMI virtualization 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 Tables of Changes”.
AY76.
A 64-bit Register IP-relative Instruction May Return Unexpected
Results
Problem:
Under an unlikely and complex sequence of conditions in 64-bit mode, a register IP-
relative instruciton result may be incorrect.
Implication: A register IP-relative instruction result may be incorrect and could cause software to
read from or write to an incorrect memory location. This may result in an unexpected
page fault or unpredictable system behavior.
39
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the ”Summary Tables of Changes”.
Intel® Xeon® Processor 5200 Series
Specification Update
40
Specification Changes
The Specification Changes listed in this section apply to the following documents:
• Intel® Xeon® Processor 5200 SeriesDatasheet
There are no new Specification Changes in this Specification Update revision.
41
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Specification Clarifications
The Specification Clarifications listed in this section may apply to the following
documents:
• Intel® Xeon® Processor 5200 Series Datasheet.
• Intel® 64 and IA-32 Architectures Software Developer's Manual, Volume 3A:
System Programming Guide.
AY1.
Some Intel® Xeon® Processor X5200 Series Processors May Exhibit
Higher Extended HALT State Power Consumption Than Specified.
Issue:
The Intel® Xeon® Processor 5200 Series Processor Datasheet specifies a maximum
Extended HALT State (C1E) power consumption of 8W (refer to Table 7-2 in the
processor Datasheet). For initial production processors in the X5272 and X5260 Intel®
Xeon® processors the Extended HALT State power consumption may be up to 12W,
thus exceeding the specified amount found in the processor datasheet. This
specification exception may only be found on initial production processors with the
SLANJ and SLANH SSPEC processor identifiers.
The Intel® Xeon® Processor 5200 Series Datasheet.
AY2.
Clarification of TRANSLATION LOOKASIDE BUFFERS (TLBS)
Invalidation
Issue:
Section 10.9 INVALIDATING THE TRANSLATION LOOKASIDE BUFFERS (TLBS) of the
Intel® 64 and IA-32 Architectures Software Developer's Manual, Volume 3A: System
Programming Guide will be modified to include the presence of page table structure
caches, such as the page directory cache, which Intel processors implement. This
information is needed to aid operating systems in managing page table structure
invalidations properly.
Intel will update the Intel® 64 and IA-32 Architectures Software Developer's Manual,
Volume 3A: System Programming Guide in the coming months. Until that time, an
application note, TLBs, Paging-Structure Caches, and Their Invalidation (http://
www.intel.com/products/processor/manuals/index.htm), is available which provides
more information on the paging structure caches and TLB invalidation.
In rare instances, improper TLB invalidation may result in unpredictable system
behavior, such as system hangs or incorrect data. Developers of operating systems
should take this documentation into account when designing TLB invalidation
algorithms.
Intel® Xeon® Processor 5200 Series
Specification Update
42
Documentation Changes
The Documentation Changes listed in this section apply to the following documents:
• Intel® Xeon® Processor 5200 Series Datasheet
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
There are no new Documentation Changes in this Specification Update revision.
§
43
Intel® Xeon® Processor 5200 Series
SpecificationUpdate
Intel® Xeon® Processor 5200 Series
Specification Update
44
相关型号：
SI9130DB
5- and 3.3-V Step-Down Synchronous ConvertersWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9135LG-T1
SMBus Multi-Output Power-Supply ControllerWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9135LG-T1-E3
SMBus Multi-Output Power-Supply ControllerWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9135_11
SMBus Multi-Output Power-Supply ControllerWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9136_11
Multi-Output Power-Supply ControllerWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9130CG-T1-E3
Pin-Programmable Dual Controller - Portable PCsWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9130LG-T1-E3
Pin-Programmable Dual Controller - Portable PCsWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9130_11
Pin-Programmable Dual Controller - Portable PCsWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9137
Multi-Output, Sequence Selectable Power-Supply Controller for Mobile ApplicationsWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9137DB
Multi-Output, Sequence Selectable Power-Supply Controller for Mobile ApplicationsWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9137LG
Multi-Output, Sequence Selectable Power-Supply Controller for Mobile ApplicationsWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
SI9122E
500-kHz Half-Bridge DC/DC Controller with Integrated Secondary Synchronous Rectification DriversWarning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY
©2020 ICPDF网 联系我们和版权申明