Table of Contents
Advertisement
Errata
The snoop makes the RFO appear to have missed cache. Although the RFO appears
to have missed the cache, the ECC error code is not cleared and the L2 cache control
logic to fails to communicate that the RFO has completed. The processor does not
see that the RFO has completed and will hang.
Implication: When this erratum occurs, the processor will hang. Intel has not been able to
reproduce this erratum with commercial software.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
27.
System Hang Due to Uncorrectable Error and Bus Lock Combination
Problem:
When the following events occur:
• The L2 cache receives a speculative load request from the processor just as it is
starting to process a split load lock,
• The speculative load gets cancelled but only after it receives an uncorrectable
error, and
• Bus Lock is asserted for the split load lock and the first half of the split load lock
goes out on the system bus,
The first half of the load completes, but the uncorrectable error seen earlier prevents
the dispatch of the second half of the split load lock and the processor will hang with
lock asserted.
Implication: When this erratum occurs, the processor will hang.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
28.
Incorrect
IA32_MC1_ADDR Register
Problem:
The address of an L1 tag parity error is latched one clock cycle too late resulting in
the wrong address being logged in IA32_MC1_ADDR register.
Implication: When this erratum occurs, the wrong address may be logged in IA32_MC1_ADDR
register in response to an L1 tag parity error.
Workaround:
None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
29.
REP MOV Instruction with Overlapping Source and Destination May
Result in Data Corruption
Problem:
When fast strings are enabled and a REP MOV instruction is used to move a string
and the source and destination strings overlap by 56 bytes or less, data corruption
may occur.
Specification Update
Address
for
an
L1
Tag Parity Error
Is
Logged in
39
Advertisement
Table of Contents
