Summary Tables of Changes
16
Intel
®
Core™2 Extreme Quad-Core Processor QX6000
Δ
Sequence and Intel
®
Core™2 Quad Processor Q6000
Δ
Sequence
Specification Update
NO
B3
G0
Plan
ERRATA
AK109
X
Fixed
CPUID Reports Certain Features/Parameters Incorrectly
when HT Technology is Disabled
AK110
X
X
No Fix
VTPR Write Access During Event Delivery May Cause an
APIC-Access VM Exit
AK111
X
No Fix
BIST Failure After Reset
AK112
X
X
No Fix
Performance Monitoring Event FP_MMX_TRANS_TO_MMX
May Not Count Some Transitions
AK113
X
X
No Fix
Instruction Fetch May Cause a Livelock During Snoops of the
L1 Data Cache
AK114
X
X
No Fix
Use of Memory Aliasing with Inconsistent Memory Type may
Cause a System Hang or a Machine Check Exception
AK115
X
X
No Fix
A WB Store Following a REP STOS/MOVS or FXSAVE May
Lead to Memory-Ordering Violations
AK116
X
X
No Fix
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 Interruptibility-State Field
AK117
X
X
No Fix
Using Memory Type Aliasing with Cacheable and WC
Memory Types May Lead to Memory Ordering Violations
AK118
X
X
No Fix
VM Exit due to Virtual APIC-Access May Clear RF
AK119
X
X
No Fix
RSM Instruction Execution under Certain Conditions May
Cause Processor Hang or Unexpected Instruction Execution
Results
AK120
X
Fixed
NMIs May Not Be Blocked by a VM-Entry Failure
AK121
X
X
No Fix
Benign Exception after a Double Fault May Not Cause a
Triple Fault Shutdown
AK122
X
X
No Fix
IA32_MC1_STATUS MSR Bit[60] Does Not Reflect Machine
Check Error Reporting Enable Correctly
AK123
X
X
No Fix
A VM Exit Due to a Fault While Delivering a Software
Interrupt May Save Incorrect Data into the VMCS
AK124
X
X
No Fix
A VM Exit Occurring in IA-32e Mode May Not Produce a VMX
Abort When Expected
AK125
X
X
No Fix
A Page Fault May Not be Generated When the PS bit is set
to “1” in a PML4E or PDPTE
AK126
X
X
No Fix
Not-Present Page Faults May Set the RSVD Flag in the Error
Code
AK127
X
X
No Fix
VM Exits Due to “NMI-Window Exiting” May Be Delayed by
One Instruction
AK128
X
X
No Fix
FP Data Operand Pointer May Be Incorrectly Calculated After
an FP Access Which Wraps a 4-Gbyte Boundary in Code
That Uses 32-Bit Address Size in 64-bit Mode
AK129
X
X
No Fix
A 64-bit Register IP-relative Instruction May Return
Unexpected Results
