L2以太网控制器是什么

Revision6.
9December2014IntelEthernetController82571EB/82572EI/82571GB/82571GISpecificationUpdateNetworkingDivision(ND)iiLegalNolicense(expressorimplied,byestoppelorotherwise)toanyintellectualpropertyrightsisgrantedbythisdocument.
Inteldisclaimsallexpressandimpliedwarranties,includingwithoutlimitation,theimpliedwarrantiesofmerchantability,fitnessforaparticularpurpose,andnon-infringement,aswellasanywarrantyarisingfromcourseofperformance,courseofdealing,orusageintrade.
Thisdocumentcontainsinformationonproducts,servicesand/orprocessesindevelopment.
Allinformationprovidedhereissubjecttochangewithoutnotice.
ContactyourIntelrepresentativetoobtainthelatestforecast,schedule,specificationsandroadmaps.
Theproductsandservicesdescribedmaycontaindefectsorerrorswhichmaycausedeviationsfrompublishedspecifications.
Copiesofdocumentswhichhaveanordernumberandarereferencedinthisdocumentmaybeobtainedbycalling1-800-548-4725orbyvisitingwww.
intel.
com/design/literature.
htm.
IntelandtheIntellogoaretrademarksofIntelCorporationintheU.
S.
and/orothercountries.
*Othernamesandbrandsmaybeclaimedasthepropertyofothers.
2014IntelCorporation.
iii82571/82572SpecificationUpdateRevisionsRevisionRevisionDescription1.
0Jan2004Initialrelease.
1.
1Jan2004AddedErratum16;Sightings4-6.
1.
2Feb2004AddedErratum17-18;AddedDeviceIdentificationandMechanical1.
3Mar2004AddedB-1errata.
1.
4Apr2004Addederratum23and24.
Addedsteppinginformationonsummaryofchangestable.
1.
5May2004Removedreferencesto82570EI.
UpdatedErratum#14.
1.
6Jun2004Addederratum#30.
Movedsightings#1,2,3,6,7,and8toerratum#21,25,26,27,28,and29,respectively.
Removedsighting#4.
1.
7Jul2004Fixedthesummaryoftablechanges.
Appendedupdatedschematics.
1.
8Jan2005RemovederratathatwerefixedforC0.
AddednewerratafoundonC0.
Added82572EIinformation.
1.
9Jun2005RemovederratafixedforC0.
AddednewerrataforD0.
2.
0Sep2005Addederrata48through75,sightings15through18andspecificationclarifications4,5&6.
2.
1Feb2006Removedallpre-productioncompleted/fixeditemsandrenumberedtheremainingitems;addedSpecificationChange1;addedErrata35,36&37;movedinformationaboutSpecificationClarification6—"On-DieCableDischargeEventprotectionmaynotbesufficient"todesignguide;changedSighting17toErrata37;removedSighting18:itwascausedbyatestsetupissue;clarifiedsomewording.
2.
2Jun2006AddedSpecificationChange#2(iSCSIHeaderSplitNotSupported)andChange#3(EEPROMInitialization).
AddedErrata38-44.
AddedSpecificationClarifications#6.
2.
3Nov2006AddedErrata45-56andSpecificationClarification8.
3.
0March2007AddedErrata57-64andSpecificationClarification9;correcteddevicenamesinMMnumbertable;addedalternativeworkaroundforerrata#7;addeddefinitionfor"image"intable2.
4.
0October2007AddedErrata65-67.
5.
0January2008AddedErrata68andSpecificationClarifications10&11.
6.
0December2008AddedSpecificationChange4.
AddedErrata69,70,71,72and73;addedSpecificationClarifications12and13:updatedErrata7,18,and66.
6.
1April2009AddedErrata74;addedinformationtoECCCorrectionEnableinSpecification4;6.
2June2009AddedSpecificationClarification14.
6.
3July2010AddedErrata:75-77;updatedErrata41,68,and69;addedSpecificationClarifications15-166.
4January2012AddedSpecificationChanges5and6.
UpdatedErrata39and65.
AddedErrata78and79.
AddedSpecificationClarification17.
AddedSoftwareClarification1.
6.
5January2012AddedSpecificationsChanges7and8.
UpdatedErrata76.
UpdatedSpecificationClarification16.
AddedSWClarification2.
6.
6August2013AddedSpecificationChange9.
AddedErratum80.
6.
7June2014Updatedrevisionhistory.
6.
8November2014UpdatedErratum#77.
AddedErratum#81.
6.
9December2014AddedanotetoErratum#77.
ivNOTE:Thispageintentionallyleftblank.
1Introduction—82571/825721.
0IntroductionThisdocumentappliestoboththeIntel82571EBand82572EIGigabitEthernetcontrollers.
Theyarecommonlyreferredtoasthedevice.
Anyinformationthatappliestoonlyoneisnotedassuch.
Thisdocumentisanupdatetopublishedspecifications.
Specificationdocumentsforthisproductinclude:82571EB/82572EIGigabitEthernetControllerDatasheet,IntelCorporation82571EB/82572EIGigabitEthernetControllerDesignGuide,IntelCorporationPCIe*FamilyofGigabitEthernetControllersSoftwareDeveloper'sManual,IntelCorporationThisdocumentisintendedforhardwaresystemmanufacturersandsoftwaredevelopersofapplications,operatingsystemsortools.
ItmaycontainSpecificationChanges,Errata,andSpecificationClarifications.
Allproductdocumentsaresubjecttofrequentrevisionandnewordernumberswillapply.
Newdocumentsmaybeadded.
Besureyouhavethelatestinformationbeforefinalizingyourdesign.
1.
1ProductCodeandDeviceIdentificationProductCodes:JLX540EB,JLX540AT2,JLX540BT2andJLX540AT1Thefollowingtablesanddrawingsdescribethevariousidentifyingmarkingsoneachdevicepackage:82571/82572—Introduction2Table1-1MarkingsTable1-2RevisionIDDeviceSteppingTopMarkingQ-SpecificationNotes82571EBD0(leadfree)JL82571EBQ866EngineeringSamples82571EBD0HL82571EBQ864EngineeringSamples82572EID0(leadfree)JL82572EIQ867EngineeringSamples82572EID0HL82572EIQ865EngineeringSamples82571EBD0(leadfree)JL82571EBN/AProduction82571EBD0HL82571EBN/AProduction82572EID0(leadfree)JL82572EIN/AProduction82572EID0HL82572EIN/AProduction82571EBD1HL82571EBN/AProduction82571EBD1(leadfree)JL82571EBN/AProduction82571EID1HL82571EIN/AProduction82571EID1(leadfree)JL82571EIN/AProduction82571GBD1(leadfree)JL82571GBN/AProduction82571GID1(leadfree)JL82571GIN/AProductionNote:Thedevicescanalsohavea"82571GB"or"82572GI"marking(insteadof"82571EB"or"82572EI");the82571GBand82572GIdevicesareusedonlyonIntelnetworkinterfaceadapters.
The82571GBisfunctionallyequivalenttothe82571EBandthe82572GIisfunctionallyequivalenttothe82572EI.
DeviceVendorIDDeviceIDRevisionID*82571EBD0/D1(copperapplications)8086105E682571EBD0/D1(fiberapplications)8086105F682571EBD0/D1(SERDESbackplaneapplications)80861060682572EID0/D1(copperapplications)8086107D682572EID0/D1(fiberapplications)8086107E682572EID0/D1(SERDESbackplaneapplications)8086107F6*=RevisionIDislocatedatConfigaddress0x8bits7:03Introduction—82571/82572Table1-3MMNumbers1.
2MarkingDiagramFigure1-1Example82571EB/82572EIIdentifyingMarksNote:Lead-freepartsuse"JL"(vs.
"HL")astheprefixfortheproductcode.
The"Q"designatorreferstotheQSpecificationnumberinthetableabove.
Note:Thedevicescanalsohavea"82571GB"or"82572GI"marking(insteadof"82571EB"or"82572EI").
The82571GBand82572GIdevicesareusedonlyonIntelnetworkinterfaceadapters.
The82571GBisfunctionallyequivalenttothe82571EBandthe82572GIisfunctionallyequivalenttothe82572EI.
Note:ThereisnochangeforpartslistedasD1.
TherearenoForm,FitorFunctionchangestothissilicon.
Intelanticipatesnoimpacttocustomers.
ThisisaninternalpackagechangetoprovideamaterialsolutionthatisRoHScompliant.
Intelhasqualifiedandcertifiedthischangeinthesamewayitdoesforallproductssuppliedtocustomers.
ProductTrayMM#TapeandReelMM#JLX540EB906871JLX540EB910815JLX540AT2917469JLX540AT2917470JLX540BT2920903920904JLX540AT192477182571/82572—Introduction41.
3NomenclatureUsedInThisDocumentThisdocumentusesvariousdefinitions,codesandabbreviationstodescribetheSpecificationChanges,Errata,Sightingsand/orSpecificationClarificationsthatapplytothelistedsilicon/steppings:Table1-4DefinitionsNameDescriptionSpecificationChangesModificationstothecurrentpublishedspecifications.
Thesechangeswillbeincorporatedinthenextreleaseofthespecifications.
ErrataDesigndefectsorerrors.
Erratamaycausedevicebehaviortodeviatefrompublishedspecifications.
Hardwareandsoftwaredesignedtobeusedwithanygivensteppingmustassumethatallerratadocumentedforthatsteppingarepresentonalldevices.
SightingsObservedissuesarethosebelievedtobeerratabuthavenotbeencompletelyconfirmedorrootcaused.
TheintentionofdocumentingsightingsistoproactivelyinformusersofobservedbehaviorsorissuesSightingsmayevolvetoerrataormayberemovedasnon-issuesafterinvestigationcompletes.
SpecificationClarificationsGreaterdetailorfurtherhighlightsconcerningaspecification'simpacttoacomplexdesignsituation.
Theseclarificationswillbeincorporatedinthenextreleaseofthespecifications.
DocumentationChangesTypos,errors,oromissionsfromthecurrentpublishedspecifications.
Thesechangeswillbeincorporatedinthenextreleaseofthespecifications.
A1,B1,etc.
Steppingtowhichthestatusapplies.
DocDocumentchangeorupdatethatwillbeimplemented.
FixThiserratumisintendedtobefixedinafuturesteppingofthecomponent.
FixedThiserratumhasbeenpreviouslyfixed.
NoFixTherearenoplanstofixthiserratum.
EvalPlanstofixthiserratumareunderevaluation.
RedChangeBar/orBoldThisItemiseithernewormodifiedfromthepreviousversionofthedocument.
5HardwareSightings,Clarifications,Changes,UpdatesandErrata—82571/825722.
0HardwareSightings,Clarifications,Changes,UpdatesandErrataSeeSection1.
3foranexplanationofterms,codes,andabbreviations.
Table2-1SummaryofHardwareSightings,Clarifications,ChangesandErrata;ErrataIncludeSteppingsSpecificationClarificationsStatus1.
DisableAutoMDI-XforForced100BASE-TXOperation.
N/A2.
RequestWillNotBeTreatedasCompletionAbort(CA)whentheProgrammingModelBytesEnableisViolated.
N/A3.
System-LevelEMITestCanBeAffectedby490MHzHarmonicSeenIn10Base-TWaveformSpectrum.
N/A4.
MDIReturnLossIsMarginalNear40MHzat115ohmLoad.
N/A5.
PCIeOutputDriverAmplitudeCanBeSetIncorrectlybytheEEPROM.
N/A6.
OnlyOnePortCanBeDisabledataTime;LANDisable(LAN0_DIS_N&LAN1_DIS_N)—82571Only.
N/A7.
ManageabilityModesNotAvailableWhenSystemIsinS5Statewhen"devicepowerdown"IsActivatedandAPMIsDisabledN/A8.
ManageabilitynotsupportedonSMBus1N/A9.
SupportforWOLConcurrentlyonBothPortsN/A10.
LEDModesBasedOnLINKSpeedOnlyWorkinCopper(InternalPHY)Mode.
N/A11.
THERM_Dp(D4)andTHEMR_Dn(D5)areReservedandShouldNotBeUsed.
N/A12.
TCPSegmentationOffloadOperationswithBothTransmitQueuesEnabledN/A13.
WhenPort0andPort1AreConnectedBack-to-Back,thePHYShouldBeResetAsPartoftheDriverInitializationToAvoidLinkFailures.
N/A14.
PCIe:CompletionTimeoutMechanismComplianceN/A15.
CriticalSession(KeepPHYLinkUp)ModeDoesNotBlockAllPHYResetsCausedbyPCIeResets.
N/A16.
ReceiverDetectionCircuitDesignandEstablishedLinkWidthN/A17.
UseofWakeonLANTogetherwithManageabilityN/A18.
DynamicLEDModesCanOnlyBeUsedinanActiveLowConfiguration.
N/A82571/82572—HardwareSightings,Clarifications,Changes,UpdatesandErrata6SpecificationClarificationsStatus19.
CTRL.
SLUShouldbeSetbySoftwareFollowingDeviceReset.
N/ASpecificationChangesStatus1.
SMBusOperationat1MhzIsNotSupported(400kHzOperationNotAffected)N/A2.
iSCSIHeaderSplitFeatureIsNotSupportedN/A3.
TheEEPROMInitializationControl2bit(word0Fh)bit7isReservedandMustBeSetTo0N/A4.
82571EBECCProtectionEnable0x1100N/A5.
UpdatestoPBANumberEEPROMWordFormatN/A6.
UpdatestoPXE/iSCSIEEPROMWordsN/A7.
UsingTCPSegmentationOffloadwithIPv6N/A8.
UpdateDefinitionofSWEEPROMPortIdentificationLEDBlinking(Word0x4)N/A9.
PXEVLANConfigurationN/AErrataStatus1.
WhenTwoFunctionsHaveDifferingMAX_PAYLOAD_SIZE,theDeviceMightUsetheLargerValueForAllFunctions.
D-Step;NoFix2.
UpstreamAttempttoReconfigurethePCIeLinkByMovingtheLinkTrainingStatusStateMachine(LTSSM)FromRecoverytoConfigurationWillCausea"LinkDown"Event.
D-Step;NoFix3.
WhenUsingSerialOverLAN,theDevice'sPowerStateCanBeAmbiguous.
D-Step;NoFix4.
PCIeDifferential-andCommon-ModeReturnLossIsHigherThanSpecifiedValue.
D-Step;NoFix5.
SerDesTransmitDifferentialReturnLossIsHigherThanSpecifiedValue.
D-Step;NoFix6.
SerDesIsUnabletoAcquireSyncfromOrderedSetsBeginningwith/K28.
1/.
D-Step;NoFix7.
DeviceTransmitOperationMightHaltinTCPSegmentationOffload(TSO)ModewhenMultipleRequests(MULR)AreEnabled.
D-Step;NoFix8.
IDE-RedirectPersistentRetransmissionInconsistencyD-Step;NoFix9.
SMBusTransactionsMightBeNACKed(NotACKnowledged)underIDEandSMBusStress.
D-Step;NoFix10.
I2CTransactions:WhenWorkingwithBusSpeeds400KHzorHigher,theBusMightHangWhentheMasterReadsMoreBytesthantheSlaveReported.
D-Step;NoFix11.
SOLTimeoutCharacterControlByteInEEPROMImageDoesNotFunction.
D-Step;NoFix12.
IncorrectNumberofRetransmissionsofLink-DownAlertD-Step;NoFix13.
DeviceDoesNotSupportPCIeActiveStatePowerManagementL1State(ASPML1).
D-Step;NoFixTable2-1SummaryofHardwareSightings,Clarifications,ChangesandErrata;ErrataIncludeSteppings7HardwareSightings,Clarifications,Changes,UpdatesandErrata—82571/82572ErrataStatus14.
XOFFfromPartnerCanPreventFlow-Control(XON/XOFF)Transmission.
D-Step;NoFix15.
MissedRXPacketsD-Step;NoFix16.
TxStopsDuringHostManagementStressin10MbpsHalf-DuplexD-Step;NoFix17.
DeviceOverwritesPortALAAtoDefaultValueDuetoPortBSoftwareResetD-Step;NoFix18.
EnablingOrDisablingRSSintheMiddleofReceivedPacketsMayStopReceiveFlow.
D-Step;NoFix19.
PacketswithIPV6TunneledinIPV4andwithaCertainValueofLastIPOptionsWillHaveanIncorrectRSSHashValue.
D-Step;NoFix20.
FormedandInvalid/C/CodeHandlingontheSerDesInterfaceD-Step;NoFix21.
FalseDetectionofanidle_matchConditionontheSerDesInterface.
D-Step;NoFix22.
AbilityMatchandAcknowledgeMatchontheSerDesInterfaceD-Step;NoFix23.
FrameswithAlignmentErrorsD-Step;NoFix24.
Inter-FrameSpacing(10/100Half-DuplexModeOnly)D-Step;NoFix25.
Auto-CrossSampleTimer(PHY-relatedIssue)D-Step;NoFix26.
FirmwareResetOccurswhenPerformingTransactionswithaLowInterpacketGap(IPG)UsingFastManagementLink(FML)at8MHz.
D-Step;NoFix27.
10base-TLinkPulseHitstheTemplateMaskDuetoVoltageRipple/Glitch.
D-Step;NoFix28.
10base-TTP_IDLTemplateFailureD-Step;NoFix29.
BMCFragmentsSentthroughTwoDifferentSMBusPortsAreSentOverLANasaSinglePacket.
D-Step;NoFix30.
FrameswithVariationsinthePreambleAreRejected(CopperOnly).
D-Step;NoFix31.
ReceptionofUndersizedFramesAffectsGoodFrameReception.
D-Step;NoFix32.
PacketLength-RelatedIssuesD-Step;NoFix33.
WhenMANC.
EN_XSUM_FILTERisNotEnabled,ReceivedPacketswithWrongUDPChecksumAreTransferredtoBMC.
D-Step;NoFix34.
DeviceSendsOnlyOneXOFFEveniftheLinkPartnerHasTimedOutandItIsStillCongested.
D-Step;NoFix35.
WhenWakeonLAN(WoL)IsDisabled,theDeviceConsumesMoreThantheSpecified20mA.
D-Step;NoFix36.
TheDeviceDoesNotCorrectlyHandleReceivedNullifiedTransactionLayerPackets(TLP).
D-Step;NoFix37.
LinkDownDuringReceiveFlowMayCauseDataCorruption.
D-Step;NoFix38.
IncorrectPCIeConfigurationsCanBeSetbyEarlierVersionsofdev_starterEEPROMImages(v5.
8andbelow).
D-Step;NoFixTable2-1SummaryofHardwareSightings,Clarifications,ChangesandErrata;ErrataIncludeSteppings82571/82572—HardwareSightings,Clarifications,Changes,UpdatesandErrata8ErrataStatus39.
PacketsReceivedwithanL2+L3HeaderLengthGreaterthan256BytesCanIncorrectlyReportaChecksumError.
D-Step;NoFix40.
PCIeBusCanHaltuponD3/L1EntryifThereAreLessThan16PostedData(PD)FlowControlCredits(=256bytememorywrites).
D-Step;NoFix41.
WhenAPMEnable(WOL)isNotSetintheEEPROM,itCanAffecttheFirmwareLoadandPCIeConfigurations.
D-Step;NoFix42.
TrafficonSMBusWhileLinkisDownCausesFirmwareReset.
D-Step;NoFix43.
SOLStressDataIntegrityFailswithIDERStress.
D-Step;NoFix44.
The82571EB/82572EIPCIeTransmitDifferentialVoltageAmplitudeis1.
4V(Maximumof1.
5V)fortheFirst15msofTransmission.
D-Step;NoFix45.
ManageabilitySoftwareHaltswhenSMBusSlaveAddressisSetto0x00.
D-Step;NoFix46.
RxPacketNotificationTimeoutDoesNotResetAfterMasterReadsFragment.
D-Step;NoFix47.
BMCConfigurationCommandsareDiscardedWhenThereisHeavyManageabilityTrafficLoad.
D-Step;NoFix48.
DuplicateFragmentsMightBeSenttotheBMC.
D-Step;NoFix49.
MemoryBufferLeaksUnderHeavySMBusTrafficLoad.
D-Step;NoFix50.
FirstTwoBytesofaRxPacketForwardedtotheBMCMightBeDropped,DegradingPerformance.
D-Step;NoFix51.
SMBusMightHangiftheBMCisResetintheMiddleofaTransaction.
D-Step;NoFix52.
CertainMalformedIPV6ExtensionHeadersarenotProcessedCorrectlybytheDevice.
D-Step;NoFix53.
CompletionwithCAorURStatusisConsideredMalformed.
D-Step;NoFix54.
HMACCalculationForRMCP+SessionEstablishmentisIncorrect.
D-Step;NoFix55.
SOLPayloadFailstoActivatewithEncryptionActivationBitSetWhenSessionwasNotEstablishedwithEncryption.
D-Step;NoFix56.
UserPasswordNotBeingUsed(InsteadoftheKg)whenCalculatingtheSIK.
D-Step;NoFix57.
FirmwareResetsWhileLinkIsDown.
D-Step;NoFix58.
IntegrityValueinRMCP+sessionestablishmentD-Step;NoFix59.
UsernameinRAKP1MessageMustBePaddedto16Bytes.
D-Step;NoFix60.
DeviceAcceptsInvalidUserNamewhenRMCP+SessionOwner.
D-Step;NoFix61.
ConfiguringRMCP+PasswordfromtheBMCD-Step;NoFix62.
"UpdateUserPassword"CommandIncorrectlyAcceptsLessThan20BytesofData.
D-Step;NoFix63.
ByteEnables2and3AreNotSetonMSIWrites.
D-Step;NoFixTable2-1SummaryofHardwareSightings,Clarifications,ChangesandErrata;ErrataIncludeSteppings9HardwareSightings,Clarifications,Changes,UpdatesandErrata—82571/82572ErrataStatus64.
WakeupEventOccursonMagicPacketthatDoesn'tPassAddressFilter.
D-Step;NoFix65.
PCIe:SKPOrderedSetResetsTrainingSequence(TS)CounterD-Step;NoFix66.
InternalCopperPHY:TestEquipmentMayReportMaster/SlaveDeviceDoesn'tCorrectlyImplementMaster/SlaveResolution.
D-Step;NoFix67.
82571EB-82572EIImproperlyImplementstheAuto-NegotiationAdvertisementRegister.
D-Step;NoFix68.
PCIe:ReceptionofCompletionThatShouldBeDroppedMayOccasionallyResultInDeviceHangorDataCorruption.
D-Step;NoFix69.
ReceivePacketDelayedWhenUsingRDTRorRADVRegister.
D-Step;NoFix70.
82571/82572OverwritesTransmitDescriptorsInInternalBuffer.
D-Step;NoFix71.
LinkIndication:LEDRemainsOnInD3PowerStateInSerDesMode.
D-Step;NoFix72.
PCIe:MissingReplayDuetoRecoveryDuringTLPTransmissionD-Step;NoFix73.
PCIe:LTSSMMovesfromL0toRecoveryOnlyWhenReceivingTS1/TS2onAllLanes.
D-Step;NoFix74.
MissingInterruptFollowingICRReadD-Step;NoFix75.
TxPacketLostAfterPHYSpeedChangeUsingAuto-negotiationD-Step;NoFix76.
TxDataCorruptionWhenUsingTCPSegmentationOffloadD-Step;NoFix77.
PCIe:ExtendedPCIe"HotReset"CanLeadtoaFirmwareHang.
D-Step;NoFix78.
SerDes:RXCW.
RxConfigInvalidSetIncorrectlyD-Step;NoFix79.
PCIe:SpuriousSDP/STPCausesPacketstobeDropped.
D-Step;NoFix80.
CRC8FieldsofAnalogInitializationStructuresintheEEPROMImagearenotCheckedbytheDevice.
D-Step;NoFix81.
Incorrect64-bitStatisticsCounterValue.
D-Step;NoFixTable2-1SummaryofHardwareSightings,Clarifications,ChangesandErrata;ErrataIncludeSteppings82571/82572—SpecificationClarifications103.
0SpecificationClarifications1.
DisableAutoMDI-XforForced100BASE-TXOperation.
Clarification:LinkmayfailifAutoMDI-Xisenabledduringforced100BASE-TXmodeoperation.
Sincethedevicedoesnotdisablethisfunctionautomatically,thedrivermustperformthisstep.
AutoMDI-XcanbedisabledbyclearingPHYREG18.
12.
Intel'ssoftwaredrivershavebeenimplementedinthisway.
Document:PCIe*FamilyofGigabitEthernetControllersSoftwareDeveloper'sManual.
2.
RequestWillNotBeTreatedasCompletionAbort(CA)whentheProgrammingModelBytesEnableisViolated.
Clarification:ThePCIExpressspecificationallowsadevicetonotacceptcertainrequests.
Thisisunderthe"programmingmodel"cases.
ThedeviceneedstoissueaCompletionAborterrorifthespecificrequestviolatestheprogrammingmodel.
Aspartofitsprogrammingmodel,thedevicedoesnotsupportwriteswithbyteenablestospecificmemoryaddresses.
ThesewriteswillbefullyexecutedandwillnotbetreatedasCompletionAbort.
"CSRwriteswithpartialbytesenables"willbeexecutedinspecificaddressranges.
Thisscenariowillnotoccurwhenusingthedevicedriver.
Thisfunctionalityisalsonotneededforthenormaloperationofthedesign.
Thiscanbeavoidedbyhavingnopartialbytesenablewritingtothedevice.
3.
System-LevelEMITestCanBeAffectedby490MHzHarmonicSeenIn10Base-TWaveformSpectrum.
Clarification:ThisisnotaviolationofanyIEEEspecification.
Thisharmonicmay,however,contributetoEMI(electro-magneticinterference)inasystem-levelcheckatthisfrequency.
Thereisnoimpactonsystem-levelperformance.
11SpecificationClarifications—82571/825724.
MDIReturnLossIsMarginalNear40MHzat115ohmLoad.
Clarification:Returnlossfor115ohmloadismarginal(GigabitIEEEspecificationSection40.
8.
3.
1)nearthefrequencyof40MHz.
Returnlossisacceptablethroughouttherestofthefrequencyspectrumandconformstothe10Base-Tand100Base-TXspecificationlimits.
IEEEconformanceismarginal.
Thereisnoimpactonsystem-levelperformance.
5.
PCIeOutputDriverAmplitudeCanBeSetIncorrectlybytheEEPROM.
Clarification:OlderversionsoftheEEPROMimages(basedondev_starterimageversion5.
6orolder)thatsupportManageabilitymodes(ASF,Passthrough,andSuperPassthrough)cansetthePCIeamplitudetoanincorrectvalue.
ThelatestversionsofEEPROMimages(basedondev_starterversion5.
10ornewer)arerequiredtoproperlysetthePCIeoutputdriveramplitude.
IfEEPROMswiththeManageabilitymodesenabledhavebeenused,pleasecontactyouIntelrepresentativetoensureyouhavethelatestEEPROMimagerequiredforyoursystem.
IfyouneedanupdatedEEPROMimage,itcanbeobtainedfromyourIntelrepresentative.
ReturnlossspeclinePointofmarginality82571/82572—SpecificationClarifications126.
OnlyOnePortCanBeDisabledataTime;LANDisable(LAN0_DIS_N&LAN1_DIS_N)—82571Only.
Clarification:ThesepinscannotbothbelowatthesametimesincethiswoulddisablebothLANports,whichisnotavalidoperatingmode.
7.
ManageabilityModesNotAvailableWhenSystemIsinS5Statewhen"devicepowerdown"IsActivatedandAPMIsDisabledClarification:Ifthefollowingconfigurationisset,thePHYispowereddownandpreventsanEthernetlinkfrombeingestablishedinS5.
Therefore,themanageabilitymodeisnotavailablewhenthesystemisintheS5statebecausethereisnoEthernetlink.
Forthe82571EB:EEPROMword0x14/24(InitializationControl3)andAPMEnable(bit10)arebothsetto'0'.
Dev_starterEEPROMdefaultissetto'1'Forthe82572EI:EEPROMword0x24(InitializationControl3)andAPMEnable(bit10)arebothsetto'0'.
Dev_starterEEPROMdefaultissetto'1'Forthe82571EBand82572EI:ThefollowingEEPROMsettingsareleftattheirdefaultvalues:PHY/Serdespowerdownisenabled.
EEPROMword0x0F(InitializationControl2),PHYpower-down(bit6)andSerDespower-down(bit2)aresetto1.
DevicePowerdownisenabled:EEPROMWord0x1E(DeviceRevisionID),Devicepowerdowndisable(bit15)issetto'1'.
Dev_starterEEPROMdefaultissetto'1'VoltageRegulatorsshutisdisabled:EEPROMWord0xA(InitializationControlWord1),EE_VR_Power_Down(bit7)issetto'0'.
Dev_starterEEPROMdefaultissetto'0'InordertohavethemanageabilityavailableinS5,"devicepowerdown"inEEPROMWord0x1E(DeviceRevisionID)(bit15)mustbedisabledbysettingthisbitto'0'.
EEPROMsbasedondev_starterimage5.
10havethissettingdisabledbydefault.
Earlierversionshadthisbitenabled.
Note:Alldev_starterEEPROMimageshaveAPMenabled.
8.
ManageabilitynotsupportedonSMBus1Clarification:ManageabilityonSMBus1isnotsupported.
Thiswillbereflectedinthenextreleaseof82571/82572/631xESB/632xxESBSystemManageabilityGuide.
13SpecificationClarifications—82571/825729.
SupportforWOLConcurrentlyonBothPortsClarification:IfWOLisenabledonbothportsofthe82571EB,thenitispossible,intheD3state,forthedevicetodrawmorethanthePCIBusPowerManagementInterfaceSpecificationRevision1.
1valueof375mAonthe3.
3Auxvoltagerail.
Inordertoalwaysmeetthisspecification,onlyoneportshouldbeenabledforWOLinthe82571EB.
IntelDriverslimittheuseofWOLtoPort0(PortA)ofthe82571EB.
10.
LEDModesBasedOnLINKSpeedOnlyWorkinCopper(InternalPHY)Mode.
Clarification:LEDmodes(asdefinedinTable5-26inPCIe*GbEControllersOpenSourceSoftwareDeveloper'sManual)basedonLINKspeedworkonlyincoppermode,notSerDesmode.
ThisincludesthemodesLINK_10/1000,LINK100/1000,LINK_10,LINK_100,LINK_1000andCOLLISION.
DesignsusingSerDesmodesrequiringaLinkupindicationshoulduseLINK_UPorLINK/ACTIVITYnotLINK_1000.
UsingthesemodesresultsinnoissuesinusingtheLEDstoproperlyindicatethelinkisup.
11.
THERM_Dp(D4)andTHEMR_Dn(D5)areReservedandShouldNotBeUsed.
Clarification:InSection3.
11andTable32intheIntel82571&82572GigabitEthernetControllerDatasheet,arereferencestosignalsTHERM_Dp(D4)andTHEMR_Dn(D5).
ThesepinsareRESERVEDandshouldnotbeusedinanydesign.
Thesepinsshouldbeleftunconnected(floating).
12.
TCPSegmentationOffloadOperationswithBothTransmitQueuesEnabledClarification:WhenusingTCPSegmentationOffload(TSO)withbothTransmitQueuesenabled,bits6:0"COUNT"intheTARC0(0x03840)andTARC1(0x3940)registermustbesetto1forproperoperation.
FailuretosetCOUNT=1canresultintheTransmitflowofthe82571/82572haltingunexpectedly.
13.
WhenPort0andPort1AreConnectedBack-to-Back,thePHYShouldBeResetAsPartoftheDriverInitializationToAvoidLinkFailures.
Clarification:IfthePHYisnotreset,thenbothportsmightstarttheAuto-MDI-Xprotocolbehavioratthesameexacttime.
Therefore,bothportswillgetthesamePseudoRandomtimeoutofapower-onreset.
Asaresult,82571/82572—SpecificationClarifications14eachportpowersupwiththesameconfigurationofMDI/MDIX.
Iftheyarebothswitchingatthesameexacttime,linkdoesnotoccursinceRXactivityisneverdetectedonthereceiver(thedeviceturnsofftheRXcircuitontheTXpathsoasnottofalselyestablishlinkfromitsownlinkpulses).
Onreset,orwhenphysicallyconnectingthePHYtoanotherdevice,thepseudorandomtimeoftheportisresetandisdifferentfromtheotherport,thusenablingthelinktobeestablished.
Otherfactors,suchascablelengthandsiliconvariationscanhaveaneffectonhowclosethetimingsare,buttheonlytimeitisanissueiswhentheconnectionsareback-to-backonthesame82571.
14.
PCIe:CompletionTimeoutMechanismComplianceClarification:IfthelatencyforPCIecompletionsinasystemisabove21msandthePCIecompletiontimeoutmechanismisenabled,therecanbeunpredictablesystembehavior.
The82571EB/82572EIcomplieswiththePCIe1.
0aspecificationforthecompletiontimeoutmechanism.
ThePCIe1.
0aspecificationprovidesatimeoutrangebetween50sto50mswithastrongrecommendationthatitbeatleast10ms.
The82571EB/82572EIusesarangeof21-42ms.
Thecompletiontimeoutvalueinasystemmustbeabovetheexpectedmaximumlatencyforcompletionsinthesysteminwhichthe82571EB/82572EIisinstalled.
Thiswillensurethatthe82571EB/82572EIreceivesthecompletionsfortherequestsitsendsout,avoidingacompletiontimeoutscenario.
Ifthelatencyforcompletionsisabove21ms,thiscanresultinthedevicetimingoutpriortoacompletionreturning.
Intheeventofacompletiontimeout,perdirectioninthePCIespecification,thedeviceassumestheoriginalcompletionislost,andresendstheoriginalrequest.
Inthiscondition,ifthecompletionfortheoriginalrequestarrivesatthe82571EB/82572EIdevices,thiswillresultintwocompletionsarrivingforthesamerequest,whichmaycauseunpredictablesystembehavior.
Therefore,ifthePCIecompletionlatencyforasystemcannotbeguaranteedtobelowerthan21ms,thePCIecompletiontimeoutmechanismshouldbedisabledbysettingtheGCR.
Disable_timeout_mechanism.
FormoredetailsonCompletionTimeoutoperationinthe82571EB/82572EIrefertotheIntel82571EB/82572EIControllerDatasheetandthePCIe*GbEControllersOpenSourceSoftwareDeveloper'sManual.
15.
CriticalSession(KeepPHYLinkUp)ModeDoesNotBlockAllPHYResetsCausedbyPCIeResets.
Clarification:D3->D0transitionwillcauseaPHYreseteveninKeepPHYLinkUpmode.
WhenCriticalSessionMode(KeepPHYLinkUp)isenabled(viatheSMBUSManagementControlcommand),PCIeresetsshouldnotcauseaPHYreset.
However,thefollowingeventwillstillcauseaPHYreset:TransitionfromD3toD0withoutageneralPCIereset,i.
e.
PMCSR[1:0]ischangedfrom11to00byaconfigurationwrite.
LossoflinkcancausealossoftheMNGsession.
Theseeventsdonotnormallyoccurduringarebootcycle,soitisexpectedthatnoeffectwillbeseeninmostcircumstances.
15SpecificationClarifications—82571/8257216.
ReceiverDetectionCircuitDesignandEstablishedLinkWidthClarification:The82571receiverdetectioncircuitwasdesignedaccordingtothePCIeSpecificationRev.
1.
1,whichrequiresthatanun-terminatedreceiverhaveaninputimpedanceofatleast200Kohm.
PCIeSpecificationRev.
2.
0allowstheinputimpedancetobeaslowas1Kohmatinputvoltagesintherange-150–0mVanddoesnotspecifyaminimuminputimpedancebelow-150mV.
Asaresult,apowered-downreceiverlanewithlowinputimpedanceatnegativevoltagescouldbecomplianttoRev2.
0andyetbefalselydetectedbythe82571asaterminatedlane.
Thisisnormallynotanissuesinceanyconnectedlanesshouldbeproperlyterminatedwithin5msafterfundamentalresetaccordingtothePCIeSpecification.
However,therearesomechipsetdevicesthatrequiresignificantlymoretimetopreparetheterminationandexpectthelinkpartnertoremainintheLTSSMDetectstateaslongasnoneofthelanesareterminated.
Whenusedwithsuchdevices,the82571mightfalselydetectareceiverononeormorelanesandleavetheDetectstate.
Thiscanleadtonotestablishingalinkorestablishingalinkthatislessthanfullwidth.
Inthiscase,itisrecommendedthat:1.
IfsomeofthePCIelanesarenotconnected,theLane_WidthfieldinthePCIeInitConfiguration3EEPROMwordshouldbeprogrammedtomatchtheactualwidthoftheconnectionanda.
AHotResetshouldbeperformedafteralinkhasbeenestablishedinordertoforcethe82571todetectthereceiversagainwhentheyareproperlyterminated.
Asaresult,afull-widthlinkcanbeestablished.
17.
UseofWakeonLANTogetherwithManageabilityTheWakeupFilterControlRegister(WUFC)containstheNoTCObit,whichaffectsthebehaviorofthewakeupfunctionalitywhenmanageabilityisinuse.
Notethat,ifmanageabilityisnotenabled,thevalueofNoTCOhasnoeffect.
WhenNoTCOcontainsthehardwaredefaultvalueof0b,anyreceivedpacketthatmatchesthewakeupfilterswillwakethesystem.
Thiscouldcauseunintendedwakeupsincertainsituations.
Forexample,ifDirectedExactWakeupisusedandthemanageabilitysharesthehost'sMACaddress,IPMIpacketsthatareintendedfortheBMCwakesthesystem,whichmightnotbetheintendedbehavior.
WhenNoTCOissetto1b,anypacketthatpassesthemanageabilityfilter,evenifitalsoiscopiedtothehost,isexcludedfromthewakeuplogic.
Thissolvesthepreviousproblem,sinceIPMIpacketsdonotwakethesystem.
However,withNoTCO=1b,broadcastpackets,includingbroadcastmagicpackets,donotwakethesystemsincetheypassthemanageabilityfiltersandarethereforeexcluded.
EffectsofNoTCOSettings:WoLNoTCOSharedMACAddressUnicastPacketBroadcastPacketMagicPacket0b-OKOKMagicPacket1bYNowakeNowakeMagicPacket1bNOKNowake82571/82572—SpecificationClarifications16TheIntelWindowsdriverssetNoTCObydefault.
18.
DynamicLEDModesCanOnlyBeUsedinanActiveLowConfiguration.
InanyofthedynamicLEDmodes(FILTER_ACTIVITY,LINK/ACTIVITY,COLLISION,ACTIVITY,PAUSED),LEDblinkingshouldonlybeenablediftheLEDsignalisconfiguredasanactivelowoutput.
19.
CTRL.
SLUShouldbeSetbySoftwareFollowingDeviceReset.
Asdocumented,theCTRL.
SLUbitisclearedduringresetandthensetto1bduringEEPROMauto-loadiftheAPM_EnableEEPROMbitis1b.
Alsoasdocumented,theAPM_Enablebitisinword0x14/0x24andisnotreadfollowingadeviceresetinitiatedbysoftwarewritingtoCTRL.
RST.
Therefore,CTRL.
SLUisnotautomaticallysetfollowingasoftwaredevicereset.
Thisbitshouldbeexplicitlysetbysoftwareinordertoestablishalink.
Exceptions:Ifmanageabilityisenabled,CTRL.
SLUissetautomatically.
IfaPHYresetisperformedafteradevicereset,CTRL.
SLUissetautomatically.
DirectedExact0bYWakeevenifMNGpacket.
NowaytotalktoBMCwithoutwakinghost.
N/ADirectedExact0bNOKN/ADirectedExact1b-OKN/A17SpecificationChanges—82571/825724.
0SpecificationChanges1.
SMBusOperationat1MhzIsNotSupported(400kHzOperationNotAffected)OperationoftheSMBusat1MHzisnotsupported.
OperationatthestandardSMBusfrequency(400kHz)isnotaffectedandissupported.
TheoperationfrequencyissetbytheEEPROM.
2.
iSCSIHeaderSplitFeatureIsNotSupportedTheextendedRxandRxwrite-backdescriptorsareaffected.
ThisinformationsupercedestheinformationinthePCIeFamilyofGigabitEthernetControllersSoftwareDeveloper'sManual,Section3.
2.
6.
5.
Thefollowingtablesreflectthechanges:PKTTYPE(bit19:16):ThePKTTYPEfielddefinesthetypeofthepacketthatwasdetectedbythedevice.
Ittriestofindthemostcomplexmatchuntilitlocatesthemostcommonone,asshowninthePacketTypetablebelow:Note:Payloaddoesnotmeanrawdata,butcanbealsoanunsupportedheader.
Note:IfthereisanNFSheaderinthepackets,itcanbeseeninthepackettypefield.
PacketTypeDescription0x0MAC,(VLAN/SNAP)Payload0x1MAC,(VLAN/SNAP)Ipv4,Payload0x2MAC,(VLAN/SNAP)Ipv4,TCP/UDP,payload0x3MAC(VLAN/SNAP),Ipv4,Ipv6,payload0x4MAC(VLAN/SNAP),Ipv4,Ipv6,TCP/UDP,payload0x5MAC(VLAN/SNAP),Ipv6,payload0x6MAC(VLAN/SNAP),Ipv6,TCP/UDP,payload0x8MAC,(VLAN/SNAP)Ipv4,TCP/UDP,NFS,payload0xAMAC(VLAN/SNAP),Ipv4,Ipv6,TCP/UDP,NFS,payload0xCMAC(VLAN/SNAP),Ipv6,TCP/UDP,NFS,payload82571/82572—SpecificationChanges18Packettypessupportedbythepacketsplit:The82571/82572providesheadersplitforthefollowingpackettypes.
Otherpackettypesarepostedsequentiallyinthebuffersofthepacketsplitreceivebuffers.
Asaresultofthisspecificationchange,bits5:0oftheReceiveFilterControlRegisterarenowreserved.
PacketTypeDescriptionHeaderSplit0x0MAC,(VLAN/SNAP)PayloadNo0x1MAC,(VLAN/SNAP)Ipv4,PayloadSplitheaderafterL3iffragmentedpackets0x2MAC,(VLAN/SNAP)Ipv4,TCP/UDP,payloadSplitheaderafterL4ifnotfragmented,otherwisetreataspackettype10x3MAC(VLAN/SNAP),Ipv4,Ipv6,payloadSplitheaderafterL3ifeitherIpv4orIpv6indicatesafragmentedpacket0x4MAC(VLAN/SNAP),Ipv4,Ipv6,TCP/UDP,payloadSplitheaderafterL4ifIpv4notfragmentedandifIpv6doesnotincludefragmentextensionheader,otherwisetreataspackettype30x5MAC(VLAN/SNAP),Ipv6,payloadSplitheaderafterL3iffragmentedpackets0x6MAC(VLAN/SNAP),Ipv6,TCP/UDP,payloadSplitheaderafterL4ifIpv6doesnotincludefragmentextensionheader,otherwisetreataspackettype50x8MAC,(VLAN/SNAP)Ipv4,TCP/UDP,NFS,payloadSplitheaderafterL5ifnotfragmented,otherwisetreataspackettype10xAMAC(VLAN/SNAP),Ipv4,Ipv6,TCP/UDP,NFS,payloadSplitheaderafterL5ifIpv4notfragmentedandifIpv6doesnotincludefragmentextensionheader,otherwisetreataspackettype30xCMAC(VLAN/SNAP),Ipv6,TCP/UDP,NFS,payloadSplitheaderafterL5ifIpv6doesnotincludefragmentextensionheader,otherwisetreataspackettype5FieldBit(s)InitialValueDescriptionReserved5:00Reserved.
Shouldbewrittenwith0toensurefuturecompatibility.
NFSW_DIS60NFSWritedisableDisablefilteringofNFSwriterequestheaders.
NFSR_DIS70NFSReaddisableDisablefilteringofNFSreadreplyheaders.
NFS_VER9:800NFSVersion00NFSversion201NFSversion310NFSversion411ReservedforfutureuseIPv6_dis100IPv6disable.
DisableIPv6packetfilteringIP6Xsum_dis110IPv6XsumdisableDisableXSUMonIPv6packets19SpecificationChanges—82571/825723.
TheEEPROMInitializationControl2bit(word0Fh)bit7isReservedandMustBeSetTo0TheEEPROMInitializationControl2(word0Fh)bit7isreservedandmustbesetto0.
DocumentsaffectedbythischangearethePCIeFamilyofEthernetGigabitControllersSoftwareDevelopersManualandthe82571EB/82572EIEEPROMInformationGuide.
4.
82571EBECCProtectionEnable0x1100ThePacketBufferhasECCprotectionandusesaregisterataddress0x1100tocontroltheoperationoftheECC:FieldBit(s)InitialValueDescriptionACKDIS120ACKacceleratedisableWhenthisbitissetOPHIRwillnotaccelerateinterruptonTCPACKpackets.
ACKD_DIS130ACKdataDisable1–OPHIRwillrecognizeACKpacketsaccordingtotheACKbitintheTCPheader+No–CPdata0-OPHIRwillrecognizeACKpacketsaccordingtotheACKbitonly.
ThisbitisrelevantonlyiftheACKDISbitisnotset.
IPFRSP_DIS140IPFragmentSplitDisableWhenthisbitissettheheaderofIPfragmentedpacketswillnotbeset.
EXSTEN150ExtendedstatusEnable,WhentheEXSTENbitissetorwhenthePacketSplitreceivedescriptorisused,OPHIRwritestheextendedstatustotheRxdescriptor.
IPv6_ExdIS160IPv6ExtensionHeaderDisable,ChickenbittodisabletheIPv6extensionheadersparsingforXSUMoffload,HeadersplitandFiltering:0–parseandrecognizeallowedIPV6extensionheaders(Hop-by-Hop,DestinationOptions,andRouting)1–donotrecognizeaboveextensionheadersNEW_IPV6_EXT_DIs170NewIPv6ExtensionHeader,ChickenbittodisablethemobilityIPv6extensionheadersparsing,requiredforRSS:0–parseandrecognizeIPV6"homeaddressoption"and"rout2"extensionheadersforRSSfunction1–IfanIPv6packetincludeseitheraHome-Address-OptionoraRouting-Header-Type-2,thentheTcpIPv6ExandIPv6Exfunctionsarenotused.
82571/82572—SpecificationChanges20The82571-82572supports256KBTCPpackets;however,eachbufferislimitedto64KBsincethedatalengthfieldinthetransmitdescriptorisonly16bits.
Thisrestrictionincreasesdriverimplementationcomplexityiftheoperatingsystempassesdownascatter/gatherelementgreaterthan64KBinlength.
Thiscanbeavoidedbylimitingtheoffloadsizeto64KB.
5.
UpdatestoPBANumberEEPROMWordFormatChange:PBANumberModule—Word0x8-0x9Thenine-digitPrintedBoardAssembly(PBA)numberusedforIntelmanufacturedNetworkInterfaceCards(NICs)isstoredinEEPROM.
ThroughthecourseofhardwareECOs,thesuffixfieldisincremented.
Thepurposeofthisinformationistoenablecustomersupport(oranyuser)toidentifytherevisionlevelofaproduct.
Networkdriversoftwareshouldnotrelyonthisfieldtoidentifytheproductoritscapabilities.
PBAnumbershaveexceededthelengththatcanbestoredasHEXvaluesintwowords.
FornewerNICs,thehighwordinthePBANumberModuleisaflag(0xFAFA)indicatingthattheactualPBAisstoredinaseparatePBAblock.
ThelowwordisapointertothestartingwordofthePBAblock.
FieldBit(s)InitialValueDescriptionECCErrorCounter31:200x000IncrementedoneachECCerrordetection,clearedbywritingtobit1ofthisregister.
Reserved191Reservedwriteto1ECCDisableFromEEPROM18LoadedfromEEPROMword0x10/0x20bit5Read-only.
LoadedfromEEPROM.
Whenset,disablesECCgenerationanderrorcorrection.
ECCCSRaccessenable171Whenset,enableECCgenerationanderrorcorrectiononCSRaccesstothePacketBuffer.
Reserved161Reserved.
Writeto1ECCerroraddress15:40xFFFContainsthePacketBufferaddressofthemostrecentECCerror.
Outofresetthisisset0xfff(invalidvalue)Alsosetto0xfffbywritingtobit1ofthisregister.
ThisfieldisforDebugonly.
Reserved30Reserved.
Writeto0ECCinterruptenable20Whenset,enablesthesettingofICRbit5ondetectionofanECCerrorECCStatisticClear10Writing1tothisbitclearstheerrorcounteranderroraddressfieldsECCCorrectionEnable00Whenset,enablessinglebitECCerrorcorrection.
Whenclear,ECCerrorswillbedetected,butnotcorrected.
Intelrecommendsthatthisbitbeenabled.
21SpecificationChanges—82571/82572ThefollowingtableshowstheformatofthePBANumberModulefieldfornewproducts.
ThefollowingprovidestheformatofthePBAblock;pointedtobyword0x9above:ThenewPBAblockcontainsthecompletePBAnumberandincludesthedashandthefirstdigitofthe3-digitsuffixwhichwerenotincludedpreviously.
Eachdigitisrepresentedbyitshexadecimal-ASCIIvalues.
ThefollowingshowsanexamplePBAnumber(inthenewstyle):OlderNICshavePBAnumbersstartingwith[A,B,C,D,E]andarestoreddirectlyinwords0x8-0x9.
ThedashinthePBAnumberisnotstored;noristhefirstdigitofthe3-digitsuffix(thefirstdigitisalways0bforolderproducts).
ThefollowingexampleshowsaPBAnumberstoredinthePBANumberModulefield(intheoldstyle):6.
UpdatestoPXE/iSCSIEEPROMWordsGigabitMainSetupOptionsWord0x30,0x34.
Seethefollowingtable.
PBANumberWord0x8Word0x9G23456-003FAFAPointertoPBABlockWordOffsetDescription0x0LengthinwordsofthePBABlock(defaultis0x6)0x1.
.
.
0x5PBANumberstoredinhexadecimalASCIIvalues.
PBANumberWordOffset0WordOffset1WordOffset2WordOffset3WordOffset4WordOffset5G23456-00300064732333435362D303033Specifies6wordsG23456-003PBANumberByte1Byte2Byte3Byte4E23456-003E2345603BitsNameDefaultDescription15:13Reserved.
Mustbe0x0.
82571/82572—SpecificationChanges2212:10FSDBits12-10controlforcingspeedandduplexduringdriveroperation.
Validvaluesare:000b=Auto-negotiate.
001b=.
100Mb/shalfduplex.
010b=100Mb/shalfduplex.
011b=Notvalid(treatedas000b).
100b=Notvalid(treatedas000b).
101b=.
100Mb/sfullduplex.
110b=100Mb/sfullduplex.
111b=1000Mb/sfullduplex.
Note:Onlyapplicableforcopper-basedadapters.
Notapplicableto10GbE.
Defaultvalueis000b.
9LWSLegacyOSWakeupSupport(ForX540-basedadaptersonly).
Ifsetto1b,theagentenablesPMEintheadapter'sPCIconfigurationspaceduringinitialization.
Thisallowsremotewakeupunderlegacyoperatingsystemsthatdon'tnormallysupportit.
Notethatenablingthismakestheadaptertechnicallynon-compliantwiththeACPIspecification,whichiswhythedefaultisdisabled.
Mustbesetto0bfor1GbEand10GbEadapters.
0b=Disabled(default).
1b=Enabled.
8DSMDisplaySetupMessage.
Ifthebitissetto1b,the"PressControl-S"messageisdisplayedafterthetitlemessage.
Defaultvalueis1b.
7:6PTPromptTime.
Thesebitscontrolhowlongthe"PressControl-S"setuppromptmessageisdisplayed,ifenabledbyDIM.
00b=2seconds(default).
01b=3seconds.
10b=5seconds.
11b=0seconds.
Note:TheCtrl-Smessageisnotdisplayedif0secondsprompttimeisselected.
5DisableiSCSISetupMenu0x0ThiscontrolstheiSCSIinitmessage(Ctrl+Dmenuprompt)wheniSCSIisdisabled.
WheniSCSIoptionROMisdisabledandthisbitissetto1b,theinitmessageisnotdisplayedfortheport.
WheniSCSIoptionROMisdisabledandthisbitissetto0b,theinitmessageisdisplayedfortheport.
WheniSCSIoptionROMisenabled,thisbitdoesnotmattersincetheinitmessageisdisplayedfortheport.
4:3DBSDefaultBootSelection.
Thesebitsselectwhichdeviceisthedefaultbootdevice.
ThesebitsareonlyusediftheagentdetectsthattheBIOSdoesnotsupportbootorderselectionoriftheMODEfieldofword31hissettoMODE_LEGACY.
00b=Networkboot,thenlocalboot(default)01b=Localboot,thennetworkboot10b=Networkbootonly11b=LocalbootonlyBitsNameDefaultDescription23SpecificationChanges—82571/82572Bits2:0aredefinedasfollows:7.
UsingTCPSegmentationOffloadwithIPv6WhenusingTCPSegmentationOffloadofIPv6packetswithtwotransmitqueues,thefollowingsettingsmustbeused:ProgramIPCSOequaltoTUCSOinthecontextdescriptor.
SetIXSMinadditiontoTXSMinthedatadescriptor(s).
IntelWindowsandLinuxdrivers(e1000e)useonlyonetransmitqueueforthisdevice.
8.
UpdateDefinitionofSWEEPROMPortIdentificationLEDBlinking(Word0x4)DriversoftwareprovidesamethodtoidentifyanexternalportonasystemthroughacommandthatcausestheLEDstoblink.
Basedonthesettinginword0x4,theLEDdriversshouldblinkbetweenSTATE1andSTATE2whenaportidentificationcommandisissued.
Bit(s)ValuePortStatusCLP(Combo)ExecutesiSCSIBootOptionROMCTRL-DMenuFCoEBootOptionROMCTRL-DMenu2:00PXEPXEDisplaysportasPXE.
AllowschangingtoBootDisabled,iSCSIPrimaryorSecondary.
DisplaysportasPXE.
AllowschangingtoBootDisabled,FCoEenabled.
1BootDisabledNONEDisplaysportasDisabled.
AllowschangingtoiSCSIPrimary/Secondary.
DisplaysportasDisabled.
AllowschangingtoFCoEenabled.
2iSCSIPrimaryiSCSIDisplaysportasiSCSIPrimary.
AllowschangingtoBootDisabled,iSCSISecondary.
DisplaysportasiSCSI.
AllowschangingtoBootDisabled,FCoEenabled.
3iSCSISecondaryiSCSIDisplaysportasiSCSISecondary.
AllowschangingtoBootDisabled,iSCSIPrimary.
DisplaysportasiSCSIAllowschangingtoBootDisabled,FCoEenabled.
4FCoEFCOEDisplaysportasFCoE.
AllowschangingporttoBootDisabled,iSCSIPrimaryorSecondary.
DisplaysportasFCoEAllowschangingtoBootDisabled.
7:5ReservedSameasdisabled.
Sameasdisabled.
Sameasdisabled.
82571/82572—SpecificationChanges24Whenword0x4isequalto0xFFFFor0x0000,theblinkingbehaviorrevertstoadefault.
Table4-1LEDBlinkStateControl9.
PXEVLANConfigurationTable4-2PXEVLANConfigurationPointer—0x003CBitDescription15:12ControlforLED30000bor1111b:DefaultLEDblinkingoperationisused.
0010b=DefaultinSTATE1+LEDisONinSTATE2.
0011b=DefaultinSTATE1+LEDisOFFinSTATE2.
0100b=LEDisONinSTATE1+DefaultinSTATE2.
0101b=LEDisONinSTATE1+LEDisONinSTATE2.
0110b=LEDisONinSTATE1+LEDisOFFinSTATE2.
0111b=LEDisOFFinSTATE1+DefaultinSTATE2.
1000b=LEDisOFFinSTATE1+LEDisONinSTATE2.
1001b=LEDisOFFinSTATE1+LEDisOFFinSTATE2.
Allothervaluesarereserved.
11:8ControlforLED2-sameencodingasforLED3.
7:4ControlforLED1-sameencodingasforLED3.
3:0ControlforLED0-sameencodingasforLED3.
BitsFieldDefaultDescription15:0PXEVLANConfigurationPointer0x0ThepointercontainsoffsetofthefirstNVMwordofthePXEVLANconfigblock25SpecificationChanges—82571/82572Table4-3PXEVLANConfigurationSectionSummaryTableTable4-4VLANBlockSignature—0x0000Table4-5VersionandSize—0x0001Table4-6Port0VLANTag—0x0002Table4-7Port1VLANTag—0x0003WordOffsetWordNameDescription0x0000VLANBlockSignatureASCII'V','L'0x0001VersionandSizeContainsversionandsizeofstructure0x0002Port0VLANTagVLANtagvalueforfirstportofthecontroller,containsPCP,CFIandVIDfields.
Value0meansnoVLANconfiguredforport.
0x0004Port1VLANTagVLANtagvalueforsecondportofthecontroller,containsPCP,CFIandVIDfields.
Value0meansnoVLANconfiguredforport.
BitsFieldDefaultDescription15:0VLANBlockSignature0x4C56ASCII'V','L'BitsFieldNameDefaultDescription15:8SizeTotalsizeinbytesofsection7:0Version0x01Versionofthisstructure.
Shouldbesetto1BitsFieldNameDefaultDescription15:13Priority(0-7)0x0Priority0-712Reserved0x0Always011:0VLANID(1-4095)0x0VLANID(1-4095)BitsFieldNameDefaultDescription15:13Priority(0-7)0x0Priority0-712Reserved0x0Always011:0VLANID(1-4095)0x0VLANID(1-4095)82571/82572—Errata265.
0Errata1.
WhenTwoFunctionsHaveDifferingMAX_PAYLOAD_SIZE,theDeviceMightUsetheLargerValueForAllFunctions.
Problem:MAX_PAYLOAD_SIZEisprogrammedperfunction.
IftwoPCIefunctionshavedifferentMAX_PAYLOAD_SIZE,thedevicemightusethelargervalueforallfunctions.
TheusagemodelforthedeviceistohaveallfunctionsusethesameMAX_PAYLOAD_SIZE.
Implication:Thereisnoimpactonthefunctionalflow.
Workaround:None.
Status:NoFix:Therearenoplanstofixthiserratum.
2.
UpstreamAttempttoReconfigurethePCIeLinkByMovingtheLinkTrainingStatusStateMachine(LTSSM)FromRecoverytoConfigurationWillCausea"LinkDown"Event.
Problem:ThedevicewillnotmoveitsLTSSMfromRecoverytoConfigurationwhenitreceivesTrainingSequences(TS)withonly"lanenumber"settoPAD.
Implication:IftheupstreamcomponenttriestoreconfigurethelinkbymovingtheLTSSMfromtheRecovery.
IdlestatetotheConfigurationstate(sendingTS1swithonly"lanenumber"settoPAD),thelinkwillfailandtheunitswillgotoDetectstates,causinga"linkdown"event.
Workaround:Theupstreamcomponentshouldnotapplythisoption.
27Errata—82571/82572Status:NoFix:Therearenoplanstofixthiserratum.
3.
WhenUsingSerialOverLAN,theDevice'sPowerStateCanBeAmbiguous.
Problem:ThesamephysicallineisallocatedforSMBusAlertandforS0PowerIndication.
InSerial-Over-LAN(SOL),bothareneededbymanageabilityfirmware,whichtreatstheseindicationsasseparate.
ForLOMscontainingSOL,thelineisusedforSMBusAlert.
Implication:Therearetwoimplications:SOLbehaviormightbeconfusedbecauseanSMBusAlertmightbeconsideredasapowerstateindicationSOLcannotascertainwhenapowerstatechangehasoccurredWorkaround:None.
StatusNoFix:Therearenoplanstofixthiserratum.
4.
PCIeDifferential-andCommon-ModeReturnLossIsHigherThanSpecifiedValue.
Problem:ThePCIetransmitter'sdifferentialreturnlossisupto-9dBinsteadofthe-10dBrequirement.
APCIeEngineeringChangeNoticesets-10dBastherequirementinsteadoftheprevious-15dBinthebase1.
0aspecification.
ThePCIereceiver'sworst-measureddifferentialreturnlossisupto-7.
7dBinsteadofthe-10dBrequirement.
Implication:Theout-of-specificationreturnlossaddsnoisetotheTXtransmissionline.
Workaround:None.
Status:Therearenoplanstofixthiserratum.
82571/82572—Errata285.
SerDesTransmitDifferentialReturnLossIsHigherThanSpecifiedValue.
Problem:TheSerDestransmitter'sdifferentialreturnlossisupto-9dBinsteadofthe-10dBrequirement.
APCIeEngineeringChangeNoticesets-10dBastherequirementinsteadoftheprevious-15dBinthebase1.
0aspecification.
Implication:Theout-of-specificationreturnlossaddsnoisetotheTXtransmissionline.
Workaround:None.
Status:NoFix:Therearenoplanstofixthiserratum.
6.
SerDesIsUnabletoAcquireSyncfromOrderedSetsBeginningwith/K28.
1/.
Problem:DeviceSerDesisunabletoacquiresyncfromorderedsetsbeginningwith/K28.
1/.
Ifthelinkpartnerdidnottransmitanyothercharactersthatcontain"commas"otherthan/K28.
1/,thedevicewillnotattainsync.
Implication:Artificialtestingofthisportionofthestandardwillproducefailures.
Workaround:None.
Status:NoFix:Therearenoplanstofixthiserratum.
7.
DeviceTransmitOperationMightHaltinTCPSegmentationOffload(TSO)ModewhenMultipleRequests(MULR)AreEnabled.
Problem:TheDeviceTransmitflowstopsandthedevicehangswhenoperatinginTSOwithMULRenabled.
29Errata—82571/82572Implication:WhenoperatinginTCPSegmentationOffloadmodeandwithMultipleRequestenabled,oneofthetwoworkaroundslistedbelowmustbeinplaceortheTransmitFlowwillstopunexpectedly.
Workaround:Thedrivermustensurethatthefirstdescriptorpointstothe(L2+L3+L4)Headerandatleasttwobytesofthedata(payload).
ThishasbeenimplementedintheInteldrivers.
ThisworkaroundmustbeappliedbeforeactivatingTSOwhenMULR=1.
Alternatively,register0x3940"TARC1"bit22canbesetatinitializationtimetoworkaroundthisissue.
Status:NoFix:Therearenoplanstofixthiserratum.
8.
IDE-RedirectPersistentRetransmissionInconsistencyProblem:Whensendingthe"StartIDERedirection"messagefromaremotemanagementconsole,a"NumRetransmits"valueofzeroshoulddefineapersistentretransmissionof"StartIDERedirection"messagesuntillinkisachieved.
Thedevicetransmitsonlyone"StartIDERedirection"message.
Implication:Usingthevalueofzeroisequivalenttousingthevalueofone.
Workaround:UseanumericvalueofNumRetransmitsthatisnotzeroorone.
Status:NoFix:Therearenoplanstofixthiserratum.
9.
SMBusTransactionsMightBeNACKed(NotACKnowledged)underIDEandSMBusStress.
Problem:IDEandSMBusstressmightcauseasmallpercentage(hw.
mac_type==e1000_82571){/*activatetheworkaround*/adapter->hw.
laa_is_present=1;/*HoldacopyoftheLAAinRAR[14]Thisisdonesothat*betweenthetimeRAR[0]getsclobberedandthetimeit*getsfixed(ine1000_watchdog),theactualLAAisinone*oftheRARsandnoincomingpacketsdirectedtothisport*aredropped.
EventaullytheLAAwillbeinRAR[0]and*RAR[14]*/e1000_rar_set(&adapter->hw,adapter->hw.
mac_addr,E1000_RAR_ENTRIES-1);}Periodically,forexampleinthedriverswatchdogfunction,RAR(0)shouldbeupdatedwiththechangedLAAasitmayhavebeenrewrittenbyaresetonPortB.
/*With82571controllers,LAAmaybeoverwrittenduetocontroller*resetfromtheotherport.
SettheappropriateLAAinRAR[0]*/if(adapter->hw.
mac_type==e1000_82571&&adapter->hw.
laa_is_present)e1000_rar_set(&adapter->hw,adapter->hw.
mac_addr,0);Inteldriverssharesomecommonfunctions,whichhavebeenadaptedtothisissue:e1000_rar_set()isusedtoupdatetheRARregisters.
Nochangesarerequiredtoadapttothisissue,butitisthefunctionusedbythefollowingfunctions.
e1000_init_rx_addrs()isusedtoinitializethereceiveaddressregistersbyupdatingRAR(0)andclearingtheremainingRARs.
IthasbeenadaptedtoreserveaspotfortheredundantLAA.
voide1000_init_rx_addrs(structe1000_hw*hw){uint32_ti;uint32_trar_num;/*Setupthereceiveaddress.
*/e1000_rar_set(hw,hw->mac_addr,0);rar_num=E1000_RAR_ENTRIES;/*ReserveaspotfortheLocallyAdministeredAddresstoworkaround*an82571issueinwhicharesetononeportwillreloadtheMACon*theotherport.
*/if((hw->mac_type==e1000_82571)&&(hw->laa_is_present==TRUE))35Errata—82571/82572rar_num-=1;/*Zeroouttheother15receiveaddresses.
*/for(i=1;inum_mc_addrs=mc_addr_count;/*ClearRAR[1-15]*/num_rar_entry=E1000_RAR_ENTRIES;/*ReserveaspotfortheLocallyAdministeredAddresstoworkaround*an82571issueinwhicharesetononeportwillreloadtheMACon*theotherport.
*/if((hw->mac_type==e1000_82571)&&(hw->laa_is_present==TRUE))num_rar_entry-=1;for(i=rar_used_count;iEnablingOrDisablingRSSintheMiddleofReceivedPacketsMayStopReceiveFlow.
Problem:EnablingRSSconsistsofsettingboththeMultipleReceiveQueuesEnablebitinMRQCandthePacketChecksumDisablebitinRXCSUM.
ChangingthesesettingswhilethereisdatainthereceivedataFIFOcouldcausethereceiveDMAtohang.
TheremaybedatapresentinthereceivedataFIFOevenbeforethedriverinitializationisexecutedifthemanageabilityfirmwareroutessomepacketstothehostusingMANC2H.
Implication:Nodatareceived.
Workaround:ThedrivershouldimplementthefollowingsequenceduringinitializationifRSSisused:SetPBS[31]todisablethereceiveFIFO.
PerformasoftwareresettoclearthereceiveFIFO.
SetupRSS.
WriteRDFHS=(PBA[5:0]<<7)-1ClearPBS[31].
ClearRDFHS.
SetRCTL.
ENtoenablepacketreceptionStatus:NoFix:Therearenoplanstofixthiserratum.
19.
PacketswithIPV6TunneledinIPV4andwithaCertainValueofLastIPOptionsWillHaveanIncorrectRSSHashValue.
Problem:WhenIPV6-tunneled-in-IPV4packetsarereceived,IPoptionwithdataispresent,andthelastbyteofIPoptionis0x08,anincorrectvalueofRSShash(itwillbe0x0),queue,andCPUnumbersmaybecalculated.
Implication:WhenworkingwithRSS,theplatformusestheRSShashtodoTCPcontextlookupandhasnowayofrecoveringiftheRSShashvalueisincorrect.
Inthiscase,itwilldropthepacket,andpossiblyresettheconnection.
Inaddition,thispacketmaybedirectedtoawrongqueueandwrongCPU.
37Errata—82571/82572Workaround:IfRSShashvalueis0andPKTTYPE=3,4,9or0xA,checkIPlength.
Ifoptionsarepresent,donotindicateanRSShashvaluetothestack.
TheTCPstackwillcalculatetheRSShashvalueforaTCPpacket,whichwillpreventitfrombeingdropped.
ThishasbeenimplementedintheInteldrivers.
Status:NoFix:Therearenoplanstofixthiserratum.
20.
FormedandInvalid/C/CodeHandlingontheSerDesInterfaceProblem:ThedevicerespondsimproperlytocertaininvalidsequencesontheSerDesinterface,whichincludecommacharactersdifferentthank28.
5orsymbolswithinverteddisparity.
Implication:Thedevicemay:Achievelinkwhenitshouldn'tMaynotrestartauto-negotiationwhenitshouldInnormaloperationthecommausedisk28.
5;inverteddisparityshouldnothappenonanormalsystem.
Workaround:None.
Status:NoFix:Therearenoplanstofixthiserratum.
21.
FalseDetectionofanidle_matchConditionontheSerDesInterface.
Problem:Theidle_matchfunctionisusedduringtheauto-negotiationprocessfor1000BASE-Xapplications(SerDes).
Thisfunctioncontinuouslyindicateswhetherthreeconsecutive/I/orderedsetshavebeenreceivedanditisobservedwhenmovingfromIDLE_DETECTstatetoLINK_OKstatewithintheauto-negotiationstatemachine.
Thoughtherearenotthreeconsistent/I/symbols(thatis,thereissomecombinationof/I/andothersymbols),thedevicecanincorrectlysettheidlematchtotrue.
82571/82572—Errata38Implication:Thisfailureshouldnotbeseeninnormal-usecaseswheretherearemanyconsecutive/I/symbolsintheauto-negotiationprocess.
However,iftheerroneouscaseoccurs,theauto-negotiationwillcontinueandlockonthenext/I/pattern.
Workaround:NoneStatus:NoFix:Therearenoplanstofixthiserratum.
22.
AbilityMatchandAcknowledgeMatchontheSerDesInterfaceProblem:Inthe1000BSE-Xstatemachine,thedevicedoesnotresetitsmatchcountuponreceptionof/I/orderedsetsinbetween/C/orderedsets.
Implication:None:Innormaloperation,thespecificsequencesdonotoccur.
Workaround:NoneStatus:NoFix:Therearenoplanstofixthiserratum.
23.
FrameswithAlignmentErrorsProblem:Thedevicediscardsaframewithextrabits.
AccordingtoIEEE802.
32002Section4.
2.
4.
2.
1,aframecontaininganon-integernumberofoctetsshouldbetruncatedtothenearestoctetboundary.
Afterthetestframeistruncated,theresultingframeshouldbeacceptedasavalidframe.
Implication:Thedeviceimproperlydiscardsframes.
Thisconditionoccursrarelyinnormaloperation.
Workaround:NoneStatus:NoFix:Therearenoplanstofixthiserratum.
39Errata—82571/8257224.
Inter-FrameSpacing(10/100Half-DuplexModeOnly)Problem:Inthe10/100half-duplexmode(only),thedeviceusesmorethan6.
4sforinterFrameSpacingPart1.
ItdoesnotforcecollisionsaccordingtotheIEEE802.
3standard.
Implication:Insteadoffollowing802.
3andinitiatingtransmissionindependentofcarriersenseduringinterFrameSpacingPart2,carriersensewillstillcauseadeferralandnotcauseaforcedcollision.
Workaround:NoneStatus:NoFix:Therearenoplanstofixthiserratum.
25.
Auto-CrossSampleTimer(PHY-relatedIssue)Problem:TheAuto-CrossoverStateMachine(Auto-MDIX)hastwostates:MDI_MODEandMDI-X_MODE.
Thetimethatshouldbespentineachmodeisdefinedasanintegermultipleofapseudo-randomnumberandasampletimer,whichisdefinedtobe62±2ms.
ThePHYissometimeswaitingforanon-integermultiplicationofthe62±2ms—asdefinedbythespecification.
Implication:NoneWorkaround:NoneStatus:NoFix:Therearenoplanstofixthiserratum.
26.
FirmwareResetOccurswhenPerformingTransactionswithaLowInterpacketGap(IPG)UsingFastManagementLink(FML)at8MHz.
Problem:AsinglefirmwareresetoccurswhenFML8MHztransactionsaredeliveredwithanInter-Packet-Gap(IPG)smallerthan20uSec.
Duetospeedandmemorylimitations,buffersofBMCframesbeingarrangedintoEthernetpacketsareincorrectlyreleased.
Asaresult,amemoryerror(Nullpointerexception)occurs.
82571/82572—Errata40Implication:Performanceimpact.
TheBMCmustretrythecorruptedtransaction.
Workaround:TheBMCshouldnottransmitwithanIPGlowerthan30usec.
Status:NoFix:Therearenoplanstofixthiserratum.
27.
10base-TLinkPulseHitstheTemplateMaskDuetoVoltageRipple/Glitch.
Problem:The10base-Tlinkpulsetouchesthetemplateduetovoltageripple/glitch.
Implication:Compliancewiththespecificationisnotcomplete,however,thereisnoeffectatsystemlevel.
Workaround:None.
41Errata—82571/82572Status:NoFix:Therearenoplanstofixthiserratum.
28.
10base-TTP_IDLTemplateFailureProblem:The10base-TTP_IDLwaveformfailsthetemplatetestwithtwisted-pairmodelcombinedwithtestload2.
Implication:Thereisnotfullspecificationcompliance.
Thereisnoimpactonsystemlevelperformance.
Workaround:None.
Status:NoFix:Therearenoplanstofixthiserratum.
29.
BMCFragmentsSentthroughTwoDifferentSMBusPortsAreSentOverLANasaSinglePacket.
Problem:WhentheBMCsendssequentialfragmentsoftwopackets,usingdifferentSMBusportsofthedevice,theyarelinkedandtransmittedasonepacket.
Implication:BMCcannotsendtwonon-synchronizedpacketsovertwoports.
Workaround:BMCshouldsendonlyonepacketatatime.
Status:NoFix:Therearenoplanstofixthiserratum.
82571/82572—Errata4230.
FrameswithVariationsinthePreambleAreRejected(CopperOnly).
Problem:Thedevice(oncopperimplementationsonly)rejectsframesthatcontainerrorsinthepreamble.
Implication:Thedevicedoesnotaccepttheframewithapreambledifferentthanthenormalstream(555…55D).
Workaround:None—therejectionofframeswithanerrorinthepreambledoesnotinterferewiththereceptionofvalidframesprecedingorfollowingtheframecontainingtheerror.
Status:NoFix:Therearenoplanstofixthiserratum.
31.
ReceptionofUndersizedFramesAffectsGoodFrameReception.
Problem:Ifthedevicereceivesaone-bytefragment,thenthefollowingfirst-receivedframewillbediscarded.
Implication:Afterreceivingaframewithaone-bytefragment,thedevicerejectsthefollowingfirst-receivedframe.
Workaround:None;thisframewillberecoveredinahigher-protocollevel.
Status:NoFix:Therearenoplanstofixthiserratum.
32.
PacketLength-RelatedIssuesProblem:Thedevicedoesnotreportalengtherrorifanincomingundersizedoroversizedpacketpassesthefiltercriteria.
Thedevicedoesnottruncatethepadfromframeswithalengthfieldrangingfrom0x0000to0x002d.
Implication:Thedevicedoesn'tchecktheEthernetlengthfieldtoverifythatthelengthofthepacketsmatchesthevalueinthelengthfield.
PacketswithincorrectlengthfieldvaluesarenotdiscardednorreportedasrequiredbySection4.
3.
2ofIEEE802.
32002.
43Errata—82571/82572Also,thedevicedoesnottruncatethepadfromframeswithalengthfieldrangingfrom0x0000to0x002d.
Workaround:None;boththedataandthepadportionarehandledbythehigherlayers.
Status:NoFix:Therearenoplanstofixthiserratum.
33.
WhenMANC.
EN_XSUM_FILTERisNotEnabled,ReceivedPacketswithWrongUDPChecksumAreTransferredtoBMC.
Problem:ReceivedpacketswithwrongUDPchecksumshouldbesilentlydiscarded.
UDPchecksumfilteringcouldbedonebyhardwareorbyfirmware.
Whenthehardwarefilteringoptionisdisabled,thatis,MANC.
EN_XSUM_FILTER(MACCSR0x5820bit23)isde-asserted,firmwarefailstodropthepacketandpassesittoBMC.
Implication:BMCwillreceivepacketswithincorrectUDPchecksum.
Workaround:MANC.
EN_XSUM_FILTERshouldbeasserted(configurableinEEPROMwords0x4D/0x5Dbit7).
Status:NoFix:Therearenoplanstofixthiserratum.
34.
DeviceSendsOnlyOneXOFFEveniftheLinkPartnerHasTimedOutandItIsStillCongested.
Problem:WhenFlowControlisenabled,thedeviceshouldperiodicallysendXOFFpacketsaslongasitiscongestedtopreventthelinkpartnerfromsendingdataandtopreventpacketloss.
TheperiodoftheXOFFpacketsdependsontheXOFFtimeoutnumber.
ThedevicesendsonlyoneXOFFpacketpercongestionregardlessofitscongestionstatus.
Implication:InFlowControlmode,whenthedeviceiscongestedforatimethatexceedstheXOFFtimeoutnumber,theremaybesomepacketloss.
ThelinkpartnerwillwaittheXOFFtimeoutandthencontinuetosenddata.
Inthiscase,ifthedeviceisstillcongested,thepacketwillbelost.
ThereceptionofthelinkpartnerdatawillcausethedevicetoresendaXOFFpacketandthelinkpartnerwillstoptransmissionagain.
82571/82572—Errata44Workaround:SetthemaximumtimeoutnumberintheXOFFpacketstoreducetheprobabilitythatthedevicewillstillbecongestedafterthetimeout.
Status:NoFix:Therearenoplanstofixthiserratum.
35.
WhenWakeonLAN(WoL)IsDisabled,theDeviceConsumesMoreThantheSpecified20mA.
Problem:WhenWakeonLan(Wol)isdisabledandexternalvoltageregulatorsareused(asrecommended),thedevicehasbeenmeasuredconsumingupto100mA.
ThisisaviolationofthePCIeanddevicespecifications.
Implication:Thespecificationisforoperationwithinternalregulators,whichwouldallowthemtobeshutdown,thusreducingpowerconsumption.
Sincetherecommendeddesignusesexternalregulators,thedevicewilloperatecorrectly,butpowerconsumptionisgreaterthanspecified.
Workaround:None.
Status:NoFix:Therearenoplanstofixthiserratum.
36.
TheDeviceDoesNotCorrectlyHandleReceivedNullifiedTransactionLayerPackets(TLP).
Problem:WhenareceivedTLP-end-framingsymbolisEDB,andtheLCRCisthelogicalNOTofthecalculatedCRC(NullifiedTLP),itshouldbe"silently"discarded,thatis,withoutsettinganyerrorflags.
ThedevicediscardstheTLPcorrectly,butitalsosetsaBadTLPerrorandsendsaNAKDLLP.
Implication:NullifiedTLPisrarelyseenintypicaloperation.
IfthedevicereceivesanullifiedTLP,itwillsendaBadTLPerrormessageandwillsendaNAKtothenullifiedTLP.
Thiscausesare-transmissionofTLP'sthatweresentafterit(thesequencenumberisnotincrementedafteranullifiedTLP).
Thisshouldnotaffectnormaloperationsince,afterthere-transmission,trafficwillcontinuenormally.
Workaround:None.
45Errata—82571/82572Status:NoFix:Therearenoplanstofixthiserratum.
37.
LinkDownDuringReceiveFlowMayCauseDataCorruption.
Problem:Whenthelinkfailsinthemiddleofareceivedpacket,theendofthepacketmaynotbesetandthenextpacket,afterthelinkisrestored,combineswiththepreviouspacket.
Implication:OnepacketwithcorruptdatamaybereceivedwithagoodCRCindication.
Workaround:Asoftwarereset,afterthelinkisdown,willremovethepacketthatwasinterruptedbythelinkfailure.
ThisactionhasbeenimplementedintheInteldrivers.
Status:NoFix:Therearenoplanstofixthiserratum.
38.
IncorrectPCIeConfigurationsCanBeSetbyEarlierVersionsofdev_starterEEPROMImages(v5.
8andbelow).
Problem:PCIeconfigurationscanbesetincorrectlybyEEPROMdev_starterimagesversion5.
8orolderImplication:ThefollowingaretheissuesthatcanbeseenasresultofthePCIeconfigurationsnotbeingloadedcorrectly:PCIeTXDifferentialVoltageamplitude:Increasedto~1.
35Vto1.
4Vinsteadofamaxof1.
2V.
SystemimpactwillvarybasedontheupstreamPCIedevices'tolerancetoahigheramplitude.
AbsoluteDeltaofDCCommon:DuringL0andElectrical-IdletheDeltawillincreasetoapproximately300mVfrom100mV.
Thisshouldnothaveanyfunctionalimpact.
Apower-savingfeature:WheninElectrical-IdleforthePCIebus,Receiveisnotenabled.
Workaround:UseanEEPROMimagebasedondevstarterversion.
5.
9orabove.
Status:FixedinEEPROMdevstarterversion.
5.
9andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
82571/82572—Errata4639.
PacketsReceivedwithanL2+L3HeaderLengthGreaterthan256BytesCanIncorrectlyReportaChecksumError.
Problem:L2/L3packetswithlong/multiplenextheaderextensionsincorrectlyreportaReceivechecksumerrorwhenthelengthfromDestinationAddress(DA)tothebeginningoftheTCP/UDPheaderisgreaterthan256bytes.
Implication:Areceivechecksumerrorcanincorrectlybereportedbythedevice,evenifthereisnochecksumerror.
Workaround:Whenthedriverreceivesapacketwithachecksumerrorreportedbythehardware,softwareshouldchecktheL2/L3headerlength.
IftheL2/L3headerlengthis256bytesorgreater,softwareshouldverifythechecksum.
TheIntelWindows*andLinux*driversaddressthisissuebypassingpacketswithbadchecksumstothestackfordiscardorrecheck.
Status:NoFix:Therearenoplanstofixthiserratum.
40.
PCIeBusCanHaltuponD3/L1EntryifThereAreLessThan16PostedData(PD)FlowControlCredits(=256bytememorywrites).
Problem:ThedevicePCIetransmitbuswillhaltwhenenteringD3/L1powerstatesiftheupstreamdeviceissueslessthan16PostedDataFlowControlcredits.
Implication:PCIebusstopswithnocommunicationtotheupstreamdeviceWorkaround:UpstreamPCIedevicemustissueatleast16PDtypecredits.
Status:NoFix:Therearenoplanstofixthiserratum.
47Errata—82571/8257241.
WhenAPMEnable(WOL)isNotSetintheEEPROM,itCanAffecttheFirmwareLoadandPCIeConfigurations.
Problem:Ifallofthefollowingconfigurationsettingsaretrue:Forthe82571EB:EEPROMword0x14/24(InitializationControl3),APMEnable(bit10)arebothsetto0b.
Dev_starterEEPROMdefaultissetto1b.
Forthe82572EI:EEPROMword0x24(InitializationControl3),APMEnable(bit10)issetto0b.
Dev_starterEEPROMdefaultissetto1b.
ForbothdevicesPHY/Serdespowerdownisenabled.
EEPROMword0x0F(InitializationControl2),PHYPowerDown(bit6)andSerDesPowerDown(bit2)aresetto1bDevicepowerdownisenabled:EEPROMWord0x1E,DevicePowerDownEnable(bit15)issetto1b.
Dev_starterEEPROMdefaultissetto1bVoltageregulatorsshutisdisabled:EEPROMWord0xA(InitializationControlWord1),EE_VR_Power_Down(bit7)issetto0b.
Dev_starterEEPROMdefaultissetto0bThen,ifPERST#isstillassertedbythesystemaftertheEEPROMautoread,whichoccurswithLAN_PWR_GOOD,configurationsthatshouldbeloadedfromtheEEPROMmightnotbeloaded.
Implication:Devicemightnotfunctionproperly.
Workaround:WhenAPMisdisabledonbothports,de-assertthedevicePower-DownEnablebit(EEPROMWord0x1E,bit15).
Status:NoFix.
42.
TrafficonSMBusWhileLinkisDownCausesFirmwareReset.
Problem:IftheEthernetlinkisdownandtrafficissenttothedeviceviatheSMBus,thefirmwarecanberesetandthedataislost.
Implication:ThefirmwareresetwillcausethelossofthepreviousstateanddisconnectopenRMCPsessions.
82571/82572—Errata48Workaround:FixedinEEPROMdevstarterimageversion5.
10andabove.
Thisfirmwarewilldiscardpacketssentwhilethelinkisdownaftertimeout.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
Status:FixedinEEPROMdevstarterversion5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
43.
SOLStressDataIntegrityFailswithIDERStress.
Problem:UnderheavySOLstress,alongwithnormalIDERstress,aboutoneinevery3x106SOLbytesforwardedtotheHostiscorrupted.
NocorruptionoccurswithSoLalone.
Implication:BytessentbyremotecontrollermaycauseunpredictableresultsinthecontrolledHost.
Workaround:None.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
44.
The82571EB/82572EIPCIeTransmitDifferentialVoltageAmplitudeis1.
4V(Maximumof1.
5V)fortheFirst15msofTransmission.
Problem:WhenthePCIeTXstartstransmittingafterPERST#de-assertion,thefirst15mswillbeatapproximately1.
4V(maximumof1.
5V).
Afterthis,thevoltagewillbeconfiguredtothecorrectvalueofapproximately1.
1V.
Implication:PCIeTXdifferentialvoltagewillexceedthespecificationduringthistime.
Workaround:NoneStatus:NoFix.
49Errata—82571/8257245.
ManageabilitySoftwareHaltswhenSMBusSlaveAddressisSetto0x00.
Problem:AttemptingtoconfigureonlyoneSMBusslaveaddressintheEEPROMbysettingtheotheraddressto0x00haltsmanageabilitysoftware.
Implication:Thesecondslaveaddresscannotbe"disabled.
"TheBMCwillgetanotificationaftereventsonthesecondLANport.
Ifthenotificationtimeoutissetto"no-timeout,"thenotificationswillcontinueindefinitelyanddegradeBMCperformance.
Workaround:Noworkaround.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
46.
RxPacketNotificationTimeoutDoesNotResetAfterMasterReadsFragment.
Problem:PacketsarefragmentedtobesentovertheSMBustotheBMC.
"Notificationtimeout"issetinEEPROM.
IfafragmentisnotreadbytheBMCbeforethetimeoutexpires,therestofthepacketwillbedropped.
Thetimeoutcounterisnotresetaftereveryfragmentisread,soiftheentirepacketisnotreadbeforetimeoutexpires,thelastfragmentswillbedropped.
Implication:Timeoutcanbesetbetween1msand255ms.
PacketscanonlybereadbytheBMCiftheyarecompletelyreadwithinthatinterval.
TheexpectedbehaviorwouldbetoresetthetimeoutcounteraftereveryBMCreadtransaction.
Workaround:Noworkaround.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
82571/82572—Errata5047.
BMCConfigurationCommandsareDiscardedWhenThereisHeavyManageabilityTrafficLoad.
Problem:WhenthereisheavyRxtraffictotheBMC,configurationcommandssenttothedevicearenotaccepted.
Implication:DenialofService—theBMCmaynotbeabletochangethedevice'sconfiguration(forexample,disableRxunderARPattack).
Workaround:Noworkaround.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
48.
DuplicateFragmentsMightBeSenttotheBMC.
Problem:IftheBMCsendstwoSMBusreadtransactionswithashortdelay,thesamefragmentmaybeforwardedtwice.
Implication:PacketsmaybeforwardedtotheBMCinseveralfragments.
DuplicateswillcausepacketstoarrivecorruptedontheBMCside.
Workaround:Noworkaround.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
49.
MemoryBufferLeaksUnderHeavySMBusTrafficLoad.
Problem:Firmwarememorypools,dedicatedforSMBustransaction,leakunderheavyTxandRxtrafficuntilunabletoforwardethernetpackets.
Implication:Normalmanageabilitytraffic,suchasKVMandPingwillhaltinlessthan15minutes.
51Errata—82571/82572Workaround:Thereisnoworkaround.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
50.
FirstTwoBytesofaRxPacketForwardedtotheBMCMightBeDropped,DegradingPerformance.
Problem:UnderheavyRxtraffic,thefirsttwobytesofapacketsentovertheSMBuscanbedropped.
Implication:TheBMCwillattempttorecoverpacketsbycomparingbytesreceivedwiththeoriginalpacketlength.
Thisprocessslowsperformance.
Workaround:Noworkaround.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
51.
SMBusMightHangiftheBMCisResetintheMiddleofaTransaction.
Problem:Whenthefollowingconditionsexist:ThedeviceisinthemiddleofanSMBusslavetransaction.
TheSMBusmasterabortsthetransactionwhentheclockishigh.
Thedeviceisholdingthedatalow.
Thedevicedoesn'treleasethedataline(becausetheclockishigh)andtheSMBusmastercannotstartanewtransaction(dataislow)soSMBushangs.
Implication:WhentheBMCisresetinthemiddleofatransactionasdescribedabove,itcannotrenewtheSMBusconnectionwiththedeviceorwithanyotherSMBusnodesharingthesameline.
Workaround:SMBusmastershouldimplementsomemeansofreleasingthelineafterreset.
Forexample,toggletheclockatleast9timessotheslavecancompletethetransaction.
82571/82572—Errata52Status:NoFix52.
CertainMalformedIPV6ExtensionHeadersarenotProcessedCorrectlybytheDevice.
Problem:CertainmalformedIPV6extensionheadersarenotprocessedcorrectlybythedevice.
Implication:PossibledevicereceivehangifthesemalformedIPV6headersarereceived.
Workaround:Setbit16(IPv6_ExdIS)intheRFCTLregistertodisabletheprocessingofreceivedIPV6extensionheaders.
Notethatwiththisbitset,HWwillnolongeroffloadthereceivechecksumscorrectlyforincomingframeswithIPV6extensionheaders,andSWwillneedtoaccountforthis.
ThisissueisaddressedincurrentIntelsoftwaredevicedrivers.
Status:NoFix.
53.
CompletionwithCAorURStatusisConsideredMalformed.
Problem:IfthedevicereceivesacompletionwithCA(CompleterAbort)orUR(UnsupportedRequest)status,ndanall-zerolengthfield,itwillrecognizethecompletionasamalformedcompletion.
AccordingtothePCIespecification,thiscompletionisnotmalformed.
Implication:Ifenabled,anerrormessagewillbesentupstream(fatal/non-fatal,asimpliedbytheseverityofamalformedTLPerror).
DefaultisfatalWorkaround:None.
Status:NoFix53Errata—82571/8257254.
HMACCalculationForRMCP+SessionEstablishmentisIncorrect.
Problem:Thedevicedoesnotincludethe"Nameonlylookup"bitintheRAKPOpenSessionrequest.
Implication:IfaRMCP+utilitysetsthisbit,theresultingHMACcalculationfortheutilityandthecontrollerwillnotmatchandthesessionestablishmentprocesswillfail.
Workaround:Setthe'Nameonlylookup'bittozero(0).
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
55.
SOLPayloadFailstoActivatewithEncryptionActivationBitSetWhenSessionwasNotEstablishedwithEncryption.
Problem:IfaRMCP+sessionwasestablishedbythedevice,andtheActivatePayloadcommandissentwithbit7ofByte3(EncryptionActivation)settoa1(one),thecontrollershouldignoreitbecauseencryptionwasnotnegotiated;insteaditfailstoactivatethepayload.
Implication:Ifusinga3rdpartyutilitysuchasIPMItoolandthedeviceisconfiguredtobethesessionowner,aSOLsessioncannotbeestablished.
Workaround:Setthisbitonlyifencryptionwasnegotiated.
Status:FixedinEEPROMdevstarterversion5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
56.
UserPasswordNotBeingUsed(InsteadoftheKg)whenCalculatingtheSIK.
Problem:Whilethecontrolleristhesessionowner,whencalculatingtheSIK,itdoesnotusetheuserpasswordinplaceoftheKg,ascalledforintheIPMI2.
0specification.
82571/82572—Errata54Implication:Ifusinga3rdpartyutilitysuchasIPMItoolandthedeviceisconfiguredtobethesessionowner,asessioncannotbeestablishedifapasswordisusedandtheKgisNULL.
Workaround:UseNULLpasswordandNULLKg,oralwaysconfigureaKg.
Status:FixedinEEPROMdevstarterversion5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
57.
FirmwareResetsWhileLinkIsDown.
Problem:FirmwareresetswhenaBMCattemptstosendmorethanonepacketwhilethelinkisdown.
Implication:Ifthelinkislostandmorethanonepacketisattemptedtobetransmitted,anyconfigurationtheBMCperformed(suchasautomaticARPresponseMACandIPAddress)willbelostwhentheresetofthefirmwareoccurs.
Workaround:TheBMCcanissuetheReadStatusCommandtodetermineifthelinkhasbeenlost.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
58.
IntegrityValueinRMCP+sessionestablishmentProblem:Incorrectcreation/validationoftheintegrityvalueinRMCP+sessionestablishment.
Implication:Whenthe82571EB/82572EIisthesessionowner,theRMCP+sessionestablishmentprocessusestheincorrectkeyforthecalculationandvalidationoftheRAKPintegritycheckvalue.
The82571EB/82572EIusestheSIKinsteadoftheK1key(pleaserefertotheIPMI2.
0specificationformoreinformationonRAKPmessagesandkeys).
TheIntelRedirectionSDKhasthesamedefectinit;assuch,aRMCP+sessioncanbeproperlyestablishedusingtheSDK,howeverotherutilitiessuchasIPMItoolwillfailwhenasessionisestablishedduetotheintegritycheckfailure.
Workaround:RMCP+sessionestablishmentcanbemodifiedintheuser'sRMCP+utilitytomatchtheerrorwithinthe82571.
55Errata—82571/82572Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
59.
UsernameinRAKP1MessageMustBePaddedto16Bytes.
Problem:Ifthe82571EB/82572EIistheRMCP+sessionowner,theusernameintheRAKP1messagemustbepaddedto16bytes,orthesessionestablishmentwillfail.
Implication:AnyattempttoestablishaRMCP+sessionwhenthe82571EB/82572EIisthesessionownerwillfailiftheusernameisnotzeropaddedto16bytes,despitethefactthattheusernamelengthispartofthemessage.
Workaround:TheRMCP+softwaremustensurethattheusernameintheRAKP1messageiszeropaddedto16bytes.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
60.
DeviceAcceptsInvalidUserNamewhenRMCP+SessionOwner.
Problem:Whenthe82571EB/82572EIisthesessionowner,theRMCP+sessionestablishmentprocessincorrectlyacceptsaninvalid(unconfigured)usernameaspartofthesessionestablishmentprocessifthe"NameOnlyLookup"bitisnotsetinRAKP1message.
Implication:Thisisapossiblesecuritybreach;ifthisbitisnotsettheuser,isnotvalidatedatall.
Workaround:EnsuretheRMCP+sessionestablishmentprocessfortheuser'sapplicationsetsthe"NameOnlyLookup"bit.
Status:FixedinEEPROMdevstarterversion5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
82571/82572—Errata5661.
ConfiguringRMCP+PasswordfromtheBMCProblem:ConfiguringtheRMCP+passwordfromtheBMC(viatheSMBus/FMLconnection)requiresasystemresetinordertotakeeffect.
Implication:IftheBMCconfiguresapasswordusingthe"UpdateUserPassword"command,the82571EB/82572EImustberesetinorderforthenewsettingtobeused.
Workaround:Thereisnowork-aroundforthisissue.
Status:FixedinEEPROMdevstarterversion.
5.
12andabove.
ContactyourIntelrepresentativetoensureyouhavethelatestEEPROMrelease.
62.
"UpdateUserPassword"CommandIncorrectlyAcceptsLessThan20BytesofData.
Problem:The"UpdateUserPassword"commandincorrectlyacceptslessthan20bytesofuserpassworddata.
Implication:Ifthe"UpdateUserPassword"commandisusedovertheSMBus/FMLconnectionanddoesnotzeropadtheUserPasswordfieldofthecommandtoafull20bytes,thecommandwillbeaccepted,howeverthepasswordstoredmaybecorruptedwithintheEEPROMimagewhereitisstored,makingitimpossibletoproperlyestablishaSOL/IDERRMCP+session.
Workaround:TheBMCmustensurethepasswordfieldofthe"UpdateUserPassword"iszeropaddedto20bytes.
Status:NoFix.
63.
ByteEnables2and3AreNotSetonMSIWrites.
Problem:MSI(formatcodedefinitionMessageSignalInterrupts)writesonthe82571EBwillnothavetheuppertwoByteEnables(BE)set.
Implication:ThePCIspecificationrequiresByteEnables2and3tobeseteventhoughthatdatawillalwaysbezero.
Becausethe82571/82572doesnotsettheseByteEnables,MSIwritesfailtogenerateinterruptson57Errata—82571/82572systemswithchipsetsthathavebeendesignedtorequiretheseBytesEnablestobeset.
ThiserrataonlyapplieswhenMSIissupportedandenabledbythesystemandOS.
Workaround:None,AslongasMSIisbeingused,ByteEnables2and3willnotbeset.
Status:NoFix.
64.
WakeupEventOccursonMagicPacketthatDoesn'tPassAddressFilter.
Problem:The82571/82572receivesamagicpacketthatdidn'tpassaddressfiltering.
The82571/82572willgenerateawakeupeventatthenextpacketifthenextreceivedpacket(non-magicpacket)isacceptedaccordingtotheaddressfilteringscheme.
Implication:The82571/82572maywakethesystemonanon-wakeuppacket.
Workaround:None.
Status:Nofix.
65.
PCIe:SKPOrderedSetResetsTrainingSequence(TS)CounterProblem:IfaSKPorderedsetisreceivedduringaTS1orTS2sequence,theTScounteriscleared.
Thiswillgenerallynotbeaproblemsincetheupstreamdeviceshouldtransmitatleast16TS2orderedsets,andthe82571/82572onlyneedstodetecteightconsecutiveTS2orderedsetstocompletetheRecoveryprocess,soasingleresetofthecounterwillnotcauseafailure.
Afailurecanoccuriftheupstreamdeviceisnon-compliantandtransmitsfewerthan16TS2orderedsets.
Inthiscase,the82571/82572couldfailtocompletetheRecoveryprocessandthenthePCIelinkwouldgodown.
Implication:ThereshouldbenofailurewhentheupstreamdevicefunctionsaccordingtothePCIespec.
Iftheupstreamdeviceisnon-compliant,thisissuecouldresultinaSurpriseDownerror.
Workaround:None.
82571/82572—Errata58Status:NoFix66.
InternalCopperPHY:TestEquipmentMayReportMaster/SlaveDeviceDoesn'tCorrectlyImplementMaster/SlaveResolution.
Problem:WhentheinternalCopperPHYisoperatingin1000Mbpsforcedslavemode,illegaldatamaybedetectedfromthedeviceduringthetransitionfrom10Mbpsmode(autonegotiation)to1000Mbpsmodeaftermaster/slaveresolutioniscomplete.
Implication:TestequipmentcheckingforcomplianceofMaster/SlaveresolutionmayreportfailureswhenthedeviceisinForceSlavemode.
InForcedSlavemode,thedeviceshouldnottransmitany1000Mbpssignals,whichitisdoesnot.
Howeversometestequipmentlooksforanyactivitysentfromthedeviceinforcedslavemodeandconsidersthisafailureinsteadoflookingforvalid1000Mbpssignals.
Therefore,theillegaldatamayresultsinfailuresreportedbytestequipment.
InternalvalidationshowsthedevicecompileswithIEEE802.
3Table40-5;forallconfigurations,thedeviceresolvestothecorrectdefinedmodeWorkaround:None.
Status:NoFix67.
82571EB-82572EIImproperlyImplementstheAuto-NegotiationAdvertisementRegister.
Problem:The82571EB-82572EIimproperlytransmitstheLinkCodeWordduetoawritetoregister4.
TheLinkCodeWordimproperlyswitchimmediately,whichcorrespondstoawritetoregister4.
LinkCodeWordbitsbehavedasrequiredwiththefollowingnotes.
Implication:Bits4.
7and4.
8:Alwayssetinthebasepagetransmission.
Bit4.
9:Thisbitrepresents100BASE-T4supportbythelocaldevice.
The82571EB-82572EIdoesnotsupportT4.
ItisunlikelythattheAuto-Negotiationfeatureofthe82571EB-82572EIwouldbeusedinanimplementationtoadvertisethepresenceofaseparateT4physicaldevicewithinthesystemimplementation.
Therefore,thefactthatthisdevicedoesnotallowT4tobeadvertisedisinsignificant.
Bit4.
15:The82571EB-82572EIalwayssupportsNextPage(regardlessthevalueofbit4.
15).
Whenbit4.
15issetto"one,"the82571EB-82572EIrequiresRegister7(ANNextPageTransmitRegister)tobe59Errata—82571/82572writtentocompletetheNextPageExchange.
Inthiscasehowever,the82571EB-82572EI'sNextPagesdonotcorrespondtoRegister7,butcontainvalid1000BASE-TNextPages.
Workaround:Anywritetoregister4shouldbefollowedwitharestartofAuto-Negotiationbysettingbit0.
9.
Status:NoFix68.
PCIe:ReceptionofCompletionThatShouldBeDroppedMayOccasionallyResultInDeviceHangorDataCorruption.
Problem:Thiserratumcanoccurwhenthe82571/82572PCIereceivesacompletionthatshouldbedropped,whilethe82571/82572isstartinganewrequestwiththesameTAGasthecompletion.
Onanerror-freePCIelink,thissituationshouldneveroccursincethe82571/82572doesnotassertasecondrequestwiththesametagasanoutstandingrequest.
Errorsthatcouldcausethisfailure:TheTAGofacompletioniscorruptedduetonoiseontheline.
ThiscompletionpacketwillbedroppedduetoLCRCerror,butitcouldcauseafailureif,bychance,anewrequestisassertedwiththecorruptedTAGvalueatthesametime.
Onsomeplatforms,ithasbeenobservedthatwhentheupstreamswitchporttransitionsthelinktoL0s,the82571/82572occasionallyrespondswithaNAKasaresultofnoiseontheline.
ThisNAKcouldcauseacompletiontobereplayed.
The82571/82572willdroptheduplicatepacketbasedonthesequencenumber.
However,thefailurecouldoccurifanewrequestisbeingassertedwiththesameTAGastheduplicatecompletion.
AnedgecaseofACKtimersresultsinareplayofacompletion.
Thiscouldcausethesamecaseasabove.
Implication:Whenthefailureoccurs,theactualcompletiondatafromthenewrequestwillbecorrupt.
Theimplicationsofthiscorruptionofthereaddatadependonthetypeofrequestthe82571/82572wasstartingtosendandaredescribedbelow:TXdescriptorwithTSO—82571/82572offloadmachinemayhang.
TXdataorTxdescriptorwithoutoffload—82571/82572willtransmitapacketonthenetworkwithinvaliddatabutavalidCRC.
RXdescriptor—82571/82572willDMAareceivepackettothewrongMemoryaddress.
Workaround:DisablingL0sintheswitchporttowhichthe82571/82572isconnectedwillpreventtheduplicatecompletionscausedbyL0s.
Keepingbit13"ACK/NACKScheme",word0x1A"PCIeInitializationConfiguration3"setto0intheEEPROMimagewillminimizethechancesofanACKtimeout.
82571/82572—Errata60Status:NoFix.
69.
ReceivePacketDelayedWhenUsingRDTRorRADVRegister.
Problem:WhenusingtheRDTRand/orRADVtimermechanisms,therecouldbeasituationwherethewrite-backtimerisincorrectlydisabled,whichpreventsthewrite-backofareceivedescriptoruntilanotherpacketarrives.
Implication:Nopacketlosswilloccur.
Theremayhowever,bealargedelaybetweenthetimeanRxpacketisreceivedinthedeviceandthetimethedescriptoriswrittenbacktomemory,andfinallyaninterruptgenerated.
Workaround:ItisrecommendedthattheRDTRandRADVregistersnotbeusedformoderatingRxinterrupts.
ThepreferredsolutionistousetheInterruptThrottlingRegister;ITR.
Status:NoFix70.
82571/82572OverwritesTransmitDescriptorsInInternalBuffer.
Problem:Thiserratumoccurswhentheinternaltransmitdescriptorbufferisnearlyfullofdescriptors.
Ifthefreespaceinthisbufferissmallerthanthesystemcacheline,thecalculationofthesizeofthedescriptorfetchmaybeincorrect.
Implication:Corruptionofthetransmitdescriptorring;cancauseasystemcrash.
Inmostapplications,thedescriptorswillbewrittenbackassoonasthedatahasbeenreadandtheywillnotbeaccumulatingintheinternalbuffer,thereforethisissuewillnotbeseen.
However,inanapplicationwheresystemeventssuchasPCIeFlowControlpreventtheimmediatewrite-backofdescriptors,thedescriptorbuffercouldfillupandthisissuecouldbeseen.
Workaround:ThedrivershouldkeeptrackofthedifferencebetweentheTransmitheadandtailandmakesurethedifferencebetweentailandheadisnevermorethanthevalueshownbelow.
CachelineMaximumValue(TDT-TDH)32Bytes6261Errata—82571/82572Status:NoFix71.
LinkIndication:LEDRemainsOnInD3PowerStateInSerDesMode.
Problem:TheLEDmightremainoninD3powerstatewhenSerDespowerdownisenabled(EEPROMword0xF,bit2;registerCTRL_EXT0x0018,bit18).
IfalinkisestablishedwhenthedeviceentersD3powerstateandtheLEDmodeisprogrammedtoreflectLINKindication,theLEDremainsoneventhoughtheSerDesinterfacepowersdown.
Implication:LEDincorrectlyreflectslinkisupwhenthereisnolink(asSerDesispoweredoff).
Workaround:SetCTRL.
LRST(0x0000,bit3)beforeputtingafunctioninD3.
ThisbringsthelinkdownandturnsofftheLED;thisbitisreloadedfromtheEEPROMwhenthedevicetransitionsbacktoD0.
Status:NoFix.
Therearenoplanstofixthiserratum.
72.
PCIe:MissingReplayDuetoRecoveryDuringTLPTransmissionProblem:IfthereplaytimerexpiresduringthetransmissionofaTLP,andtheLTSSMmovesfromL0toRecoveryduringthetransmissionofthesameTLP,theexpectedreplaydoesnotoccur.
Additionally,ifthereplaytimerisdisabled,nofurtherreplayswilloccurunlessaNAKisreceived.
Implication:Thissituationshouldnotoccurduringnormaloperation.
Ifitdoesoccurwhiletheupstreamswitchiswaitingforareplay,theresultcouldbeaSurpriseDownerror.
Workaround:None.
Status:Nofixplanned.
64Bytes60128Bytes56256Bytes4882571/82572—Errata6273.
PCIe:LTSSMMovesfromL0toRecoveryOnlyWhenReceivingTS1/TS2onAllLanes.
Problem:AccordingtothePCIespecification,theLTSSMshouldmovefromL0toRecoveryifaTS1orTS2orderedsetisreceivedonanyconfiguredLane.
TheOphirLTSSMonlymovesfromL0toRecoveryifaTS1orTS2orderedsetisreceivedonallconfiguredlanes.
Implication:ThissituationshouldnotoccurduringnormaloperationsincetheupstreamswitchwilltransmittheTS1orTS2orderedsetsonalllanesatthesametime.
Ifitdoesoccurduetoabrokenlane,theresultcouldbeaSurpriseDownerror.
Workaround:None.
Status:Noplannedfix74.
MissingInterruptFollowingICRReadProblem:IftheInterruptCauseRegister(ICR)isreadwhenatleastonebitissetintheinterruptmaskregisterandINT_ASSERTEDis0,anewinterrupteventoccurringonthesameclockcycleastheICRreadisignored.
Implication:Missedinterruptsleadingtodelaysinrespondingtointerruptevents.
Specifically,thiscancauseadelayinprocessingareceivedpacket.
Typically,theICRisonlyreadinresponsetoaninterruptsothisproblemwouldnotoccur.
However,whenusinglegacyinterruptsandsharinginterruptsbetweendevices,thesoftwaremaypollallthedevicestofindthesourceoftheinterrupt,includingthosedevicesthatdidnotassertaninterrupt.
Theremayalsobeothersituationsinnon-InteldriverswhereICRispolledevenwhennointerrupthasbeenasserted.
Workaround:IfreadingICRwhenthereisnoactiveinterruptcannotbeavoided,clearthemaskregister(bywriting0xfffffffftoIMC)beforereadingICR.
NotethatinthiscasetheICRwillbeclearedwhenreadevenifINT_ASSERTEDis0.
Status:Noplannedfix63Errata—82571/8257275.
TxPacketLostAfterPHYSpeedChangeUsingAuto-negotiationProblem:IfthePHYestablishesalinkat10/100Mb/sandthenauto-negotiationisre-startedandalinkisestablishedat1Gb/swithoutresettingthePHYinbetween,thefirstone-to-threeTxpacketsprovidedbytheMACmightnotbetransmitted.
Implication:Thissituationisgenerallyseenduringtestingwherethespeedofthelinkpartnerisintentionallychanged.
Duringnormaloperation,thepacketlosscouldoccurifthecablewasmovedtoadifferentport.
Inmostcases,thehigherlayerswouldhandlethepacketlossanditwouldnotbevisibletotheenduser.
Workaround:Ifitiscriticalthatnopacketsbelost,thesoftwaredrivercanbemodifiedtoperformaPHYreseteachtimeitisnotifiedofaspeedchange.
Status:Noplannedfix76.
TxDataCorruptionWhenUsingTCPSegmentationOffloadProblem:WhenusingTSO,asituationcanoccurwhereaPCIeMRdrequestisrepeatedwiththesameaddress,resultingindatacorruption.
AttheendoftheTCPpacket,theTxDMAhangsbecausethelengthdoesn'tmatch.
Thiscanonlyoccurwhenthefollowingaretrue:Thefirstbufferofthepacketislargerthan[3*(max_read_request-4)].
Thereisa4KBboundarywithin64bytesfollowingtheendoftheheaderbytesinthebuffer.
Implication:PossibledatacorruptionsinceaTCPpacketistransmittedcontainingthewrongdatabutwiththecorrectchecksum.
DatatransmissionhaltsastheTxDMAmoduleentersahangstate.
Workaround:Thefailurecanbeavoidedbyensuringatleastoneofthefollowing:Thebuffercontainingtheheadersshouldnotbelargerthan[3*(max_read_request-4)].
Tomeetthisrequirementevenfortheminimumvalueof128bytesformax_read_request,thebuffershouldnotbelargerthan372bytes.
Thealignmentofthebuffercontainingtheheadersshouldbesuchthatthereisno4KBboundarywithin64bytesfollowingtheendoftheheaderbytes.
AssumingstandardEthernet/IP/TCPheadersof54bytes,thismeansthatthebuffershouldnotstart54-118bytesbefore82571/82572—Errata64a4KBboundary.
Forexample,128-bytealignmentforthisbuffercouldbeusedtofulfillthiscondition.
ThisproblemhasnotbeenreportedwhenusinganIntelLinux*orWindows*driver.
Currentanalysisshowsitisveryunlikelyforasituationtoexistthatwouldcausethe82571/82572tobeatriskfortheerratawhenusingtheIntelLinuxorWindowsdrivers.
Status:Noplannedfix77.
PCIe:ExtendedPCIe"HotReset"CanLeadtoaFirmwareHang.
Problem:APCIehotresetpreventsthefirmwarefromaccessinginternalregisters,includingtheregistersusedtoaccesstheEEPROM.
WhenanextendedPCIeHotReset(onesecondorlonger)occurswhilethefirmwareisattemptingtoinitializeitselfbyreadingtheEEPROM,thefirmwarehangs.
ThisfailureoccursonlywhenusingNoMNGEEPROMimagesifaHotResetoccurswithinabouttwomsafteraneventthattriggersexecutionofthefirmware.
Specifically,thisfailurehasbeenobservedwhenanextendedHotResetoccursassoonasthePCIelinkisestablishedfollowingaPCIelinkdownevent.
Implication:PHYinitializationfromtheEEPROMisperformedbyfirmware,soifthefirmwarehangs,theinitializationisnotperformedandtheEthernetlinkmightnotoperatecorrectly.
Additionally,thesoftwaredrivermightfailtoloadsincetheCFG_DONEisnotset.
Withspecifichardwareandoperatingsystemconfigurations,the82571/82572mightceasetorespondoverthePCIebustothehostenvironmentafterasystemreboot.
Thisbehaviorcanbehighlytimingdependentandmightnotbeobservedinallsystemconfigurations.
Workaround:Anyofthefollowing:HotResetsshouldhaveadurationoflessthan950mstopreventafirmwarehang.
ItispreferablethatHotResetsbeasshortaspossibletominimizeinterferencewiththefirmwareexecution.
AddadelayofatleastseveralmsbetweenestablishingaPCIelinkandstartingHotReset.
UsingamanageabilityEEPROMimageaslongastheEEPROMdevicecanaccommodateanimagesizelargerthan16KB.
Note:Ifmoreinformationisneeded,contactyourIntelrepresentative.
Status:Noplannedfix65Errata—82571/8257278.
SerDes:RXCW.
RxConfigInvalidSetIncorrectlyProblem:Whenthedevicehasbeenreceivingacontinuousstreamof/C/orderedsetsforanextendedperiodoftime,theRXCW.
RxConfigInvalidmaybesetastheresultofaninternalFIFOoverflowevenifalltheinputsymbolsarevalid.
Implication:Falseindicationofinvalidsymbolsmaycausethedrivertodisablethelinkwhenthereisreallynoproblem.
Workaround:SoftwarethatusestheRxConfigInvalidbitshouldaccountforthisbehavior.
Forexample,whentheRxConfigbitisconsistently1b,itwouldbereasonabletoignoretheRxConfigInvalidbit.
Inteldriversaddressthiserratumforthedevicebylookingtoseeifthe82571-82572hasSyncandInvalidbitsetthenreadRXCWseveraltimes,ifSyncandConfigbothareconsistently1thenignoreInvalidbitandrestartAutoneg.
ThisisdonewhenlinkisdownanddriveristryingtodetermineifthelinksupportAutoNegotiationbylookingfor/C/orderedsetandif/C/orderedsetsareseenthenAutoNegotiationisenabled(TXCW.
ANE)totryanlinkupviaAutoNegotiation.
Status:Noplannedfix79.
PCIe:SpuriousSDP/STPCausesPacketstobeDropped.
Problem:WhenaspuriousSDPorSTPsymbolisreceivedwithoutacorrespondingENDsymbol,thealignmentofthereceiveddatapresentedtothelinklayermightbeincorrect.
Inthiscase,anyfollowingDLLPsorTLPsaredropped.
ThissituationcontinuesuntilthereisanENDsymbolreceivedthatisnotimmediatelyfollowedbyanSDPorSTPsymbol.
ThisissueonlyoccurswhenthePCIelinkwidthisx1orx2.
Implication:Usually,thisissuecausesnothingmorethanareplayofafewTLPs.
The82571-82572recoversfromthissituationautonomously.
Ifthe82571-82572isconnectedtoanICH7,aspuriousSDPorSTPsymbolthatoccursjustbeforeenteringL1couldcauseahangofthePCIelinksincetheICH7doesnotinsertSOSwhentransmittingPM_Request_ACKDLLPs,sothe82571-82572doesnotreceivethemandneverentersL1.
Workaround:Ifthe82571-82572isconnectedtoanICH7,ASPML1shouldbedisabled.
Otherwise,noworkaroundisrequired.
82571/82572—Errata66Status:Noplannedfix.
67Errata—82571/8257280.
CRC8FieldsofAnalogInitializationStructuresintheEEPROMImagearenotCheckedbytheDevice.
Problem:Section6.
4oftheDatasheetdescribestheanaloginitializationstructures.
TheCRC8fieldsofthesestructuresarenotcheckedbythedevice.
TheCRC_DISEEPROMbit(word0x23,bit6)mustbesetto1b.
Implication:Usually,thisissuecausesnothingmorethanareplayofafewTLPs.
The82571-82572recoversfromthissituationautonomously.
Ifthe82571-82572isconnectedtoanICH7,aspuriousSDPorSTPsymbolthatoccursjustbeforeenteringL1couldcauseahangofthePCIelinksincetheICH7doesnotinsertSOSwhentransmittingPM_Request_ACKDLLPs,sothe82571-82572doesnotreceivethemandneverentersL1.
Workaround:Ifthe82571-82572isconnectedtoanICH7,ASPML1shouldbedisabled.
Otherwise,noworkaroundisrequired.
Status:Noplannedfix.
82571/82572—Errata6881.
Incorrect64-bitStatisticsCounterValue.
Problem:Asdocumentedinthedatasheet,the64-bitstatisticscountersareclearedwhenreadingtheupper32-bitregister.
Asaresult,anyincrementstothecounterthatoccurredbetweenreadingthelower32-bitregisterandreadingtheupper32-bitregisterarelost.
Thisappliestothefollowingstatisticscounters:GoodOctetsReceivedGoodOctetsTransmittedTotalOctetsReceivedTotalOctetsTransmittedImplication:Thecountervaluescouldbeslightlylowerthantheactualnumberofoctetsreceivedortransmitted.
Workaround:Tominimizetheprobabilityofthisissueoccurring,readthecountersasinfrequentlyaspossible.
(At1Gb/s,theoctetcounterscannotsaturateinlessthan4675years.
)Also,ensurethattheupper32-bitregisterisreadassoonaspossibleafterreadingthelower32-bitregister.
Topreventanylossofinformation,ignoretheupper32-bitregisterandtreatthelower32-bitregisterasa32-bitcounterthatisnotclearedbyreadandwrapstozerowhenitreachesitsmaximumvalue.
Readthiscounteratleastonceevery30secondsandmaintainthehighportionofthecounterinsoftwarebyincrementingiteachtimethehardwarecountervaluehaswrappedsincethepreviousread.
Status:Noplannedfix.
69SoftwareClarifications—82571/825726.
0SoftwareClarifications1.
WhileInTCPSegmentationOffload,EachBufferisLimitedto64KB.
The82571-82572supports256KBTCPpackets;however,eachbufferislimitedto64KBsincethedatalengthfieldinthetransmitdescriptorisonly16bits.
Thisrestrictionincreasesdriverimplementationcomplexityiftheoperatingsystempassesdownascatter/gatherelementgreaterthan64KBinlength.
Thiscanbeavoidedbylimitingtheoffloadsizeto64KB.
InvestigationhasconcludedthattheincreaseindatatransfersizedoesnotprovideanynoticeableimprovementsinLANperformance.
Asaresult,Intelnetworksoftwaredriverslimitthedatatransfersizeinalldriversto64KB.
PleasenotethatLinuxoperatingsystemsonlysupport64KBdatatransfers.
ForfurtherdetailsabouthowIntelnetworksoftwaredriversaddressthisissue,refertoTechnicalAdvisoryTA-191.
2.
SerialInterfacesProgrammedByBitBangingWhenbit-bangingonaserialinterface(suchasSPI,I2C,orMDIO),itisoftennecessarytoperformconsecutiveregisterwriteswithaminimumdelaybetweenthem.
However,simplyinsertingasoftwaredelaybetweenthewritescanbeunreliableduetohardwaredelaysontheCPUandPCIeinterfaces.
Thedelayatthefinalhardwaremightbelessthanintendedifthefirstwriteisdelayedbyhardwaremorethanthesecondwrite.
Topreventsuchproblems,aregisterreadshouldbeinsertedbetweenthefirstregisterwriteandthesoftwaredelay,i.
e.
"write","read","softwaredelay.
"82571/82572—SoftwareClarifications70NOTE:Thispageintentionallyleftblank.