Specupdatevol 22
Specupdatevol 22
Specupdatevol 22
October 2012
v2.5
Revision History
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR
OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF
SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO
SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY,
OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life
saving, life sustaining, critical control or safety systems, or in nuclear facility applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented
subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or
otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights.
IMPORTANT - PLEASE READ BEFORE INSTALLING OR USING INTEL® PRE-RELEASE PRODUCTS.
Please review the terms at http://www.intel.com/netcomms/prerelease_terms.htm carefully before using any Intel® pre-release product, including any
evaluation, development or reference hardware and/or software product (collectively, “Pre-Release Product”). By using the Pre-Release Product, you
indicate your acceptance of these terms, which constitute the agreement (the “Agreement”) between you and Intel Corporation (“Intel”). In the event that
you do not agree with any of these terms and conditions, do not use or install the Pre-Release Product and promptly return it unused to Intel.
Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “undefined.” Intel reserves these for future
definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different
processor families. See http://www.intel.com/products/processor_number for details.
The 82577 GbE PHY may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current
characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Intel and Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
*Other names and brands may be claimed as the property of others.
Copyright © 2010-2012, Intel Corporation. All Rights Reserved.
2
Intel® 82579 GbE PHY Specification Update
This document applies to the Intel® 82579 GbE Ethernet PHY, incuding both the “LM and “V” versions.
This document is an update to a published specification, the Intel® 82579 Gigabit Ethernet Controller
Datasheet. It is intended for use by system manufacturers and software developers. All product
documents are subject to frequent revision, and new order numbers will apply. New documents may be
added. Be sure you have the latest information before finalizing your design.
Table 1 and Figure 1 describe the various identifying markings on each lead-free device package:
Table 1. Markings
WG82579LM C-0 MM# 909806 S LHA6 Tray 490 / Tray production RoHS
WG82579V C-0 MM# 909808 S LHA8 Tray 490 / Tray production RoHS
This document uses specific terms, codes, and abbreviations to describe changes, errata, sightings
and/or clarifications that apply to silicon/steppings. See Table 3 for a description.
Name Description
Specification Modifications to the current published specifications. These changes will be incorporated in the next release
Changes of the specifications.
Errata Design defects or errors. Errata may cause device behavior to deviate from published specifications.
Hardware and software designed to be used with any given stepping must assume that all errata documented
for that stepping are present on all devices.
Specification Greater detail or further highlights concerning a specification’s impact to a complex design situation. These
Clarifications clarifications will be incorporated in the next release of the specifications.
Documentation Typos, errors, or omissions from the current published specifications. These changes will be incorporated in
Changes the next release of the specifications.
Yes or No If the errata applies to a stepping, “Yes” is indicated for the stepping (for example: “A0=Yes” indicates errata
applies to stepping A0). If the errata does not apply to stepping, “No” is indicated (for example: “A0=No”
indicates the errata does not apply to stepping A0).
(No mark) or This erratum is fixed in listed stepping or specification change does not apply to listed stepping.
(Blank box)
Red Change This Item is either new or modified from the previous version of the document.
Bar/or Bold
DS Datasheet
See Section 1.2 for an explanation of terms, codes, and abbreviations used in the following tables and
discussions.
None active.
Clarification: When the 82579 is transmitting or receiving data the PCIe Clock signal is reduced to half
its normal level. This is normal for this device.
Clarification: Release 15.6 driver, supporting the 82579 PHY, introduced an issue where the LAN
becomes disabled in Device manager when the system resumes from Sx states. The PHY
could lock up due to an incorrect handling of the PHY shared semaphore. To resolve the
issue, the driver now takes control of the PHY semaphore before accessing a specific PHY
register. To ensure smooth transition in and out of Sx states, a HW reset to the driver Sx
resume flow was also added. The initial release for this resolution is available in Release
15.7.1.
Change: In the table in Section 6, for the Power on Test: “Measure magnetics center tap voltage,”
under Debug Suggestions, delete the following text: “Inspect the trace for the magnetics
center tap, if connected to the 82579 pin 6.” This action is not required.
Change: In Section 1.3-Overview, the Configuration/Proxy table and table footnote should read as
follows:
CONFIGURATION PROXY
System with Intel® ME enabled and in PP1 No Proxy Support (Intel® ME 7.0)
(S0 state) Intel® ME responds to ARP/NS requests (Only
†
Microsoft Windows 7* supported in Intel® ME 8.0)
®
Intel 82579 C0 PHY with NDIS
System with Intel® ME enabled and in PP2 (S0 Intel® ME responds to ARP/NS requests.
& Sx state)
†
Microsoft Windows 7*
Intel® 82579 C0 PHY with NDIS
† Microsoft Windows 7* does not require ARP offload support on platforms until Q4’11. Certification for
ARP/NS offload will be in Windows* Lab Kit (WLK) 1.6.
Change: Chapter 2, Figure 2 Intel 6 Series Express Chipset/82579 Interconnects; Chapter 16,
Figure 16-9; and Chapter 17, Figure 17-9 should appear as follows:
PCIe
Intel® PCH Intel® PHY
100nF
PETp[8:1] PERp
100nF PERn
PETn[8:1] 100nF
PERp[8:1] PETp
100nF PETn
PERn[8:1] +3.3VS
10k
CLKOUT_PCIE[7:0]P PE_CLKP
CLKOUT_PCIE[7:0]N PE_CLKN
PCIECLKRQ[7:0# CLK_REQ_N
0 ohm
EMPTY3
+3.3VM_LAN
10k
EMPTY
LAN_PHY_PWR_CTRL/
GPIO12 LAN_DISABLE_N
10k
EMPTY
+3.3VA
2.2k 2.2k
5% 5%
SML0DATA SMBDATA
SML0CLK SMBCLK
SMBus
1.3.5 Errata
Problem: The Intel® 82579 Gigabit Ethernet Controller may not meet the IEEE Std 802.3™-2008
specification (40.6.1.2.4) that states that the Tx Distortion must meet the following
criteria. “A PHY is considered to pass this test if the peak distortion is below 10mV for at
least 60% of the UI within the eye opening.” The 82579 may marginally fail this
requirement.
The TX distortion is less than 10 mV during the critical time when the signal is actually
sampled therefore no impact on system performance is observed with the 82579 due to
this marginality.
Workaround: None.
Status: NoFix
Problem: When in 100 Mbps/Half-Duplex only, the controller may show excessive packet loss.
Platforms may show dropped packets during ping test at 100 Mbps/Half-Duplex under all
OS's supported. Packet loss in the worst cases has been seen up to 50%. Upon
inspection, the majority of the dropped packets were found to be 200 bytes or less.
Any board with the 82579LM or 82579V, with driver release version 16.4 or older and
where the connection mode is 100 Mbps/half-duplex, could be affected by dropped
packets. This includes all driver versions released before July 17, 2011.
Note: The 1 Gbps and 10 Mbps modes, and the 100 Mbps/full-duplex are unaffected.
Implication: Platforms with the 82579LM or 82579V may show drop packets during ping test at
100Mbps/half-duplex under all OS's supported. Packet loss in the worst cases has been
up to 50%. Upon inspection, the majority of the dropped packets are found to be 200
bytes or less.
Root Cause: The MAC/PHY interface, when working in 100M/Half Duplex, was dropping packets.
When the MAC initiates K1 entrance (analogous to P1 state in the PCI Express
specification), it sends a K1 request and put its TX lanes into electrical idle (EI). When the
PHY receives the K1 request, it sends a K1 response and put its TX lanes into EI. When
the PHY gets a packet from the wire it starts sending a beacon signal for 10us. After
10usec, it begins searching for synchronization pattern. When the MAC senses activity on
its RX lines, it sends its beacon signal for 16us. After 16usec, it begins searching for
synchronization pattern.
The failed behavior is described in the following timing diagram showing the K1 exit
mechanism.
Problem: During system resume from SX states, the Intel 82579V Ethernet Controller erroneously
updates the device id in the PCIE configuration space to the 82579LM device Id, resulting
in a Windows Code 10 error message. The issue is caused due to a HW bug.
Implication: Not all platforms with 82579V will see this problem. Platforms configured with Win 8 O.S
are more susceptible to the issue and will experience the loss of LAN connectivity along
with Windows Code 10 error message in the device manager.
Root Cause: Run the SW utility available on the Intel portal at:
http://www.intel.com/support/go/network/82579v/nvramupdate.htm
Status: NoFix
§§