82576EB datasheet(22/34 Pages) INTEL

22 / 34 page

Errata - Intel® 82576EB GbE Controller

Intel® 82576EB GbE Controller

Revision: 2.85

Specification Update

September 2012

4. Internal Copper PHY: Test Equipment May Report Master/Slave Device Doesn't Correctly Implement

Master/Slave Resolution

Problem:

When the internal Copper PHY is operating in 1000 Mbps forced slave mode, illegal data

may be detected from the device during the transition from 10 Mbps mode (auto

negotiation) to 1000 Mbps mode after master/slave resolution is complete.

Implication: Test equipment checking for compliance of Master/Slave resolution may report failures

when the device is in Force Slave mode. In Forced Slave mode, the device should not

transmit any 1000 Mbps signals, which it is does not. However some test equipment

looks for any activity sent from the device in forced slave mode and considers this a

failure instead of looking for valid 1000 Mbps signals. Therefore, the illegal data may

results in failures reported by test equipment.

Internal validation shows the device compiles with IEEE 802.3 Table 40-5; for all

configurations, the device resolves to the correct defined mode

Workaround: None.

Status:

A1, A2 NoFix

▼ Return to Summary

5. Internal Copper PHY: Auto-MDX Improperly Implements Sample Timer

Problem:

The Auto-Crossover State Machine (Auto-MDIX) has two states: MDI_MODE and MDI-

X_MODE. The time that should be spent in each mode is defined as a multiple of a

pseudo-random number and a sample timer, which is defined to be 62 ms ± 2 ms.

A violation occurs in ~10% of the runs.

Implication: The time that the PHY is in MDI mode will have a slight deviation from the specified

definition.

Workaround: None.

Status:

A1, A2 NoFix

▼ Return to Summary

6. SCTP CRC Check Incorrect

Problem:

For SCTP CRC check; if the SCTP packet is smaller than 64 bytes and padding is added,

the SCTP CRC calculation is wrong.

Implication: The 82576 could incorrectly indicate the SCTP CRC as incorrect.

Workaround: If a 64-byte SCTP packet is received and the 82576 indicates the SCTP CRC is wrong

(RDESC.ERRORS.L4E is set), the driver should re-calculate the CRC.

Status:

A1, A2 NoFix

▼ Return to Summary

7. TLP: Poisoned TLP Reported In All Functions Instead Of Only Target

Problem:

A fatal message is incorrectly sent in response to a poisoned Transaction Layer Packet

(TLP).

Implication: The 82576 treats all poisoned memory requests as non-function specific. Instead of

reporting in the target function, a fatal error is reported in all functions.

82576EB Datasheet(PDF) 22 Page - Intel Corporation

82576EB Datasheet(HTML) 22 Page - Intel Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Datasheet Download

Link URL