RAS Features
© 2010 Advanced Micro Devices, Inc.
47062 SR5650 Databook 2.00
Proprietary
2-11
End of chain error is not supported, since the end of the chain is on PCI Express instead HyperTransport.
2.5.5.5 Internal Parity Error Reporting
One register bit per memory macro is used to log parity errors. Values for those bits are persistent across a warm reset for
diagnostic purposes.
2.5.6 Interrupt Generation on Errors
Internal interrupts may be generated on the following error conditions:
•
PCI Express errors (fatal, non-fatal, or correctable)
•
HT errors (fatal or non-fatal)
•
IOMMU events
•
Internal parity error (fatal or non-fatal)
•
Internal parity error in the IOMMU cache (fatal, non-fatal, or correctable)
2.5.7 Poisoned Data Support
The SR5650 supports the propagation of poisoned data attributes (EP in PCIe and Data Error in HT) between PCI Express
endpoints and the processor for both host and DMA requests or responses. The SR5650 cannot actively mark a transaction
with a poisoned data attribute even if the transaction encounters an internal parity error. Received packets containing
ECRC errors are not marked as poisoned.
2.5.8 PCIe
®
Link Disable State
The SR5650 has the ability to put PCIe links into the disabled state as an error response in order to help stop data
movement within the system. Links which received fatal errors may be disabled. Also, a HyperTransport syncflood event
may be used to trigger all links to enter the disabled state.
Table 2-3 Types of HyperTransport™ Errors Supported by the SR5650
Error Type
Description
Response Error
Received incorrect response type such as tgtdone for read request, read response for flush, or size of
received data did not match size of requested data.
Overflow Error
Flow-control buffer overflow in the receiver. This is only mapped to a fatal or non-fatal error in HT1
mode. In HT3 mode, this maps onto a retry in the hope that when the packet is subsequently received,
there is space in the FCB. No interrupt will be generated in HT3 mode.
CRC Error
Periodic CRC error
Retry Error
Per-packet CRC error received
Retry Count Rollover
Per-packet CRC error counter overflowed. Non-fatal interrupt only.
Protocol Error
Protocol conditions detected in HT1 mode:
• Data count not matching header
• Invalid command encoding
• Invalid CTL encoding
• Incomplete header
• Unexpected data
Protocol conditions detected in HT3 mode
• Data count not matching header
• Invalid command encoding
• Invalid CTL encoding
• Incomplete header
• Unexpected data
• Unexpected CRC
• Missing CRC
• Non-NOP inserted command
• Inserted command without inserted command CTL encoding