Table of Contents
Advertisement
Status:
For the steppings affected, see the Summary Tables of Changes.
AAZ74.
PCI Express x16 Port Logs Bad TLP Correctable Error When Receiving
a Duplicate TLP
Problem:
In the PCI Express 2.0 Specification a receiver should schedule an ACK and discard a
duplicate TLP (Transaction Layer Packet) before ending the transaction within the data
link layer. In the processor, the PCI Express x16 root port will set the Bad TLP status bit
in the Correctable Error Status Register (Bus 0; Device 1 and 6; Function 0; Offset
1D0h; bit 6) in addition to scheduling an ACK and discarding the duplicate TLP. Note:
The duplicate packet can be received only as a result of a correctable error in the other
end point (Transmitter).
Implication: The processor does not comply with the PCI Express 2.0 Specification. This does not
impact functional compatibility or interoperability with other PCIe devices.
Workaround:None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AAZ75.
PCI Express x16 Root Port Incorrectly NAK's a Nullified TLP
Problem:
In the processor, the PCI Express root port may NAK a nullified TLP (Transaction Layer
Packet). This behavior is a result of an incorrect DW (Double Word) enable generation
on the processors when packets end with EDB (End Bad Symbol). This also occurs only
if total TLP length <= 8 DW in which CRC (Cyclic Redundancy Check) check/framing
upstream checks will fail. This failure causes a NAK to be unexpectedly generated for
TLP's which have packets with inverted CRC and EDB's. The PCI-e specification revision
2.0 states that such cycles should be dropped and no NAK should be generated. The
processor should NAK a nullified TLP only when there is a CRC error or a sequence
check fail.
Implication: The processor does not comply with the PCI Express 2.0 Specification. This does not
impact functional compatibility or interoperability with other PCIe devices.
Workaround:None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AAZ76.
PCI Express Graphics Receiver Error Reported When Receiver With
L0s Enabled and Link Retrain Performed
Problem:
If the Processor PCI Express root port is the receiver with L0s enabled and the root port
itself initiates a transition to the recovery state via the retrain link configuration bit in
the 'Link Control' register (Bus 0; Device 1 and 6; Function 0; Offset B0H; bit 5), then
the root port may not mask the receiver or bad DLLP (Data Link Layer Packet) errors as
expected. These correctable errors should only be considered valid during PCIe
configuration and L0 but not L0s. This causes the processor to falsely report correctable
errors in the 'Device Status' register (Bus 0; Device 1 and 6; Function 0; Offset AAH;
bit 0) upon receiving the first FTS (Fast Training Sequence) when exiting Receiver L0s.
Under normal conditions there is no reason for the Root Port to initiate a transition to
Recovery. Note: This issue is only exposed when a recovery event is initiated by the
processor.
Implication: The processor does not comply with the PCI Express 2.0 Specification. This does not
impact functional compatibility or interoperability with other PCIe devices.
Workaround:None identified.
Status:
For the steppings affected, see the Summary Tables of Changes.
AAZ77.
Internal Parity Error May Be Incorrectly Signaled during C6 Exit
Problem:
In a complex set of internal conditions an internal parity error may occur during a Core
C6 exit.
36
Errata
Specification Update
Advertisement
Table of Contents
