Errata
Intel
®
Core™2 Extreme Quad-Core Processor QX6000
Δ
Sequence and
37
Intel
®
Core™2 Quad Processor Q6000
Δ
Sequence
Specification Update
AK45.
Values for LBR/BTS/BTM will be Incorrect after an Exit from SMM
Problem:
After a return from SMM (System Management Mode), the CPU will
incorrectly update the LBR (Last Branch Record) and the BTS (Branch Trace
Store), hence rendering their data invalid. The corresponding data if sent out
as a BTM on the system bus will also be incorrect.
Note: This issue would only occur when one of the 3 above mentioned debug support
facilities are used.
Implication:
The value of the LBR, BTS, and BTM immediately after an RSM operation
should not be used.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AK46.
Shutdown/VMX-Abort Condition May Disable Non-Bootstrap
Processors
Problem:
When a logical processor encounters an error resulting in shutdown or VMX-
Abort, non-bootstrap processors in the package may be unexpectedly
disabled.
Implication:
Non-bootstrap logical processors in the package that have not observed the
error condition may be disabled and may not respond to INIT#, SMI#, NMI#,
SIPI or other events.
Workaround:
When this erratum occurs, RESET# must be asserted to restore multi-core
functionality.
Status:
For the steppings affected, see the Summary Tables of Changes.
AK47.
SYSCALL Immediately after Changing EFLAGS.TF May Not Behave
According to the New EFLAGS.TF
Problem:
If a SYSCALL instruction follows immediately after EFLAGS.TF was updated
and IA32_FMASK.TF (bit 8) is cleared, then under certain circumstances
SYSCALL may behave according to the previous EFLAGS.TF.
Implication:
When the problem occurs, SYSCALL may generate an unexpected debug
exception, or may skip an expected debug exception.
Workaround:
Mask EFLAGS.TF by setting IA32_FMASK.TF (bit 8).
Status:
For the steppings affected, see the Summary Tables of Changes.
AK48.
Code Segment Limit/Canonical Faults on RSM May be Serviced before
Higher Priority Interrupts/Exceptions
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
