Datasheet

Intel
®
82599 10 GbE Controller—Errata
32
23 ERR_COR Message TLPs Are not Sent for Advisory
Errors in D3
Problem:
If the 82599 is in D3 state, and if set to advisory non-fatal, an ERR_COR message is not sent for the
following errors: Unexpected Completion, Poisoned TLP, Completer Abort, and Unsupported Request.
Implication:
The 82599 is required by the PCIe specification to send error messages for all errors caused by a
received TLP when in D3hot. The 82599 violates this requirement.
Workaround:
Use ERR_NONFATAL instead of ERR_COR by not using advisory non-fatal. If advisory non-fatal is
required, no workaround is available.
Status: B0=Yes; NoFix
24 PCIe Bandwidth in Non-Optimal Gen1 2.5GT/s
Conditions Might Be Limited in Single Port
Configuration
Problem:
In systems configured to Gen1 2.5GT/s link-speed and to Max Payload Size of 128 bytes, the bandwidth
for upstream traffic is lower than expected. The problem is limited to single-port Rx traffic.
Implication:
With this combination, the receive traffic might suffer from bandwidth degradation.
Workaround:
Set Max Payload Size to 256 bytes in the platform/system BIOS.
Status: B0=Yes; NoFix
25 Bus Number and Device Number Are not Preserved
Through PCIe Reset
Problem:
A function supporting wake-up functionality from D3Cold must maintain its PME context. The 82599
does not maintain its requester ID, thus the PM_PME message sent after wake up has this field set to
zero.
Implication:
In case of a wakeup packet, the system will be awakened by the 82599, but it will not be aware of the
source of the wake up event if it relies on the Requestor ID field in the PM_PME message.