47062 SR5650 Databook 2.00
© 2010 Advanced Micro Devices, Inc.
2-10
Proprietary
RAS Features
The ACS violations for ACS Source Validation and ACS Translation Blocking are recorded in the AER error log. Errors
due to IOMMU translation failures are not logged as ACS violations, but are logged as UR or CA depending on the error
type.
IOC may abort a non-posted request with UR status if it determines that the request will not hit system memory. Such
errors are pushed back into the PCIe core for logging. The IOC must abort potential peer-to-peer non-posted requests to
avoid a deadlock condition. For posted requests, the IOC can be configured to forward all non-decoded (non system
memory and non-peer-to-peer) posted requests up to the processor, which may abort the request and generate an MCA
error log.
For downstream completions with abort status coming back from the processor, error status is propagated to the endpoint
but no AER header information is logged in the chipset.
For upstream completions, error status is propagated up to the processor and AER information may be logged.
lists the types of errors that are detectable by the SR5650 AER implementation. For details, see the
PCI Express
2.0 Base Specification
.
The following error classes are NOT supported:
•
Receiver Overflow Error
•
Flow Control Error
•
Surprise Down Error
•
Receiver Error
2.5.5.3 IOMMU Error Reporting
The IOMMU specification defines a standard error logging facility that logs error events in system memory with register
status bits or interrupt notification to system software. The SR5650 fully supports the generation of logging events
following this standard.
2.5.5.4 HyperTransport™ Error Reporting
The HyperTransport specification defines various levels of error handling for link-related errors. The SR5650 supports
the detection of most error classes including protocol error, overflow error, and response error. The SR5650 also supports
notification of error conditions via fatal interrupts, non-fatal interrupts, or syncflood.
lists the types of errors supported by the error handling capabilities of the SR5650 for HyperTransport.
Table 2-2 Types of Errors Detectable by the SR5650 AER Implementation
Error Type
Error Class
ACS Violation
Uncorrectable – Fatal or Non-fatal
Unsupported Request
Uncorrectable – Fatal or Non-fatal
Malformed TLP
Uncorrectable – Fatal or Non-fatal
Unexpected Completion
Uncorrectable – Fatal or Non-fatal
Completer Abort
Uncorrectable – Fatal or Non-fatal
Completion Timeout
Uncorrectable – Fatal or Non-fatal
Poisoned TLP Received
Uncorrectable – Fatal or Non-fatal
Data Link Layer Protocol Error
Uncorrectable – Fatal or Non-fatal
ECRC Error
Uncorrectable – Fatal or Non-fatal
Replay Timeout
Correctable
REPLAY_NUM Rollover
Correctable
Bad DLLP
Correctable
Bad TLP
Correctable