22 Specification Update
HSD17. PCIe* Root-port Initiated Compliance State Transmitter Equalization Settings May be Incorrect
Problem: If the processor is directed to enter PCIe Polling.Compliance at 5.0 GT/s or 8.0 GT/s
transfer rates, it should use the Link Control 2 Compliance Preset/De-emphasis field
(bits [15:12]) to determine the correct de-emphasis level. Due to this erratum, when
the processor is directed to enter Polling.Compliance from 2.5 GT/s transfer rate, it
retains 2.5 GT/s de-emphasis values.
Implication: The processor may operate in Polling.Compliance mode with an incorrect transmitter
de-emphasis level.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
HSD18. PCIe* Controller May Incorrectly Log Errors on Transition to RxL0s
Problem: Due to this erratum, if a link partner transitions to RxL0s state within 20 ns of entering
L0 state, the PCIe controller may incorrectly log an error in “Correctable Error
Status.Receiver Error Status” field (Bus 0, Device 2, Function 0, 1, 2 and Device 6,
Function 0, offset 1D0H, bit 0).
Implication: Correctable receiver errors may be incorrectly logged. Intel has not observed any
functional impact due to this erratum with any commercially available add-in cards.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
HSD19. Unused PCIe* Lanes May Report Correctable Errors
Problem: Due to this erratum, during PCIe* link down configuration, unused lanes may report a
Correctable Error Detected in Bus 0, Device 1, Function 0-2, and Device 6, Function 0,
Offset 158H, Bit 0.
Implication: Correctable Errors may be reported by a PCIe controller for unused lanes.
Workaround: None identified.
Status: For the steppings affected, see the Summary Table of Changes.
HSD20. Accessing Physical Memory Space 0-640K through the Graphics Aperture May Cause Unpredictable System Behavior
Problem: The physical memory space 0-640K when accessed through the graphics aperture may
result in a failure for writes to complete or reads to return incorrect results.
Implication: A hang or functional failure may occur during graphics operation such as OGL or OCL
conformance tests, 2D/3D games and graphics intensive application.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status: For the steppings affected, see the Summary Table of Changes.