Dear Bruce
I booted the system with Kernel 2.6.30 and made a 'lspci'. If I interpret the
output correct the ASPM is already disabled. With this kernel
Version I had the checksum error.
00:1c.3 Class 0604: Device 8086:27d6 (rev 02)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: fdc00000-fdcfffff
Prefetchable memory behind bridge: 00000000fdb00000-00000000fdbfffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 unlimited
ExtTag- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal+
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+
TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency
L0 <256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
DLActive+ BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+
Surpise+
Slot # 13, PowerLimit 10.000000; Interlock- NoCompl-
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power-
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+
Interlock-
Changed: MRL- PresDet+ LinkState+
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal+ PMEIntEna-
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [80] MSI: Mask- 64bit- Count=1/1 Enable+
Address: fee0100c Data: 4189
Capabilities: [90] Subsystem: Device 8086:27d6
Capabilities: [a0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pcieport-driver
But there is another issue which I do not understand. This document (
ftp://download.intel.com/design/network/applnots/ap475.pdf ) describes how to
connect a PC82573 chip to an EEPROM and how to specify the MAC address in this
memory (word 0 to 2). Now I am confused if you say that this feature was never
available for the PC82573 chip.
I also booted the test device with Kernel 2.6.37 and because the MAC address is
not read from the EEPROM (word 0 to 2) it leads to the invalid MAC addres
00:00:00:00:00:00 or in some cases to a random number and the driver does not
get initialized
e1000e: Intel(R) PRO/1000 Network Driver - 1.2.7-k2
e1000e: Copyright (c) 1999 - 2010 Intel Corporation.
e1000e 0000:02:00.0: Disabling ASPM L1
e1000e 0000:02:00.0: PCI->APIC IRQ transform: INT A -> IRQ 17
e1000e 0000:02:00.0: setting latency timer to 64
e1000e 0000:02:00.0: irq 40 for MSI/MSI-X
e1000e 0000:02:00.0: Disabling ASPM L0s
e1000e 0000:02:00.0: Warning: detected DSPD enabled in EEPROM
e1000e 0000:02:00.0: (unregistered net_device): Invalid MAC Address:
00:00:00:00:00:00
e1000e: probe of 0000:02:00.0 failed with error -5
Where do I have to specify the MAC address that the PC82573E chip works with
the driver of Kernel 2.6.37?
Martin
-----Ursprüngliche Nachricht-----
Von: Allan, Bruce W [mailto:[email protected]]
Gesendet: Dienstag, 5. April 2011 01:08
An: Mangard Martin; Lindsay, Morgan N; [email protected]
Cc: Rajagopal, Ramadurai
Betreff: RE: Alternate MAC address support disabled for 82573 ?
The issue with the bad checksum should be resolved in 2.6.37 by disabling ASPM
L1 on the 82573 (confirm with 'lspci -s <bus:slot.function> -vvv' run as root
where <bus:slot.function> is the device address of the NIC or remove the -s
option to see all PCI devices). From what I understand, alternate MAC
addresses where never supposed to be supported on 82573 and it was a bug in the
driver that allowed it before ca. 2.6.35.
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
