Errata
54
Intel
®
Core™2 Extreme Quad-Core Processor QX6000
Δ
Sequence and Intel
®
Core™2 Quad Processor Q6000
Δ
Sequence
Specification Update
AK97.
Storage of PEBS Record Delayed Following Execution of MOV SS or
STI
Problem:
When a performance monitoring counter is configured for PEBS (Precise
Event Based Sampling), overflow of the counter results in storage of a PEBS
record in the PEBS buffer. The information in the PEBS record represents the
state of the next instruction to be executed following the counter overflow.
Due to this erratum, if the counter overflow occurs after execution of either
MOV SS or STI, storage of the PEBS record is delayed by one instruction.
Implication:
When this erratum occurs, software may observe storage of the PEBS record
being delayed by one instruction following execution of MOV SS or STI. The
state information in the PEBS record will also reflect the one instruction delay.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AK98.
Processor On Die Termination of BR1# and LOCK# Signals are
Incorrect
Problem:
On Die Termination control of BR1# and LOCK# signals are incorrect. BR#1
has its On Die Termination continuously enabled and LOCK# has its On Die
Termination continuously disabled.
Implication:
BR1# has its On Die Termination continuously enabled meaning the VOL
(Output Low Voltage) of this signal is expected to be higher than normal
losing potential margin for nominal VCCP. LOCK# has its On Die Termination
always disabled meaning the VOL of this signal is expected to be lower than
normal and could lead to signal degradation. Even if the BR1# and Lock#
terminations are always on or always off, VOL electrical specifications are not
violated. Intel has not observed any functional failure due to this erratum.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AK99.
Store Ordering May be Incorrect between WC and WP Memory Types
Problem:
According to
Intel
®
64 and IA-32 Architectures 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.
