Thanks Jesse for your reply. See my comments below..

On 07/19/2010 06:24 PM, Brandeburg, Jesse wrote:
> 
> 
> On Sun, 18 Jul 2010, Fabio Varesano wrote:
> 
>> Hi guys,
>>
>> me and some other Archlinux users who upgraded to 2.6.34 kernel are
>> having problems with e1000e probing which results in no eth0 available.
>>
>> See https://bbs.archlinux.org/viewtopic.php?pid=793385
>>
>> I read at
>> http://sourceforge.net/mailarchive/forum.php?thread_name=DDC57477F5D6F845A0DDCB99D3C4812D0CA6A93F56%40orsmsx510.amr.corp.intel.com&forum_name=e1000-devel
>> that it could have something to do with the BIOS not being updated.
>> Unfortunately I do have to most recent BIOS version for my Toshiba
>> Tecra A7.
>>
>> On a comment on the Archlinux forum above one user suggested to use
>> the e1000e driver from 2.6.33.6 but I don't think that's the right
>> thing to do.
> 
> you're right, it should work fine with 2.6.34.  Can you also please try 
> doing a full power off, and then boot the kernel?  Does that make any 
> difference?

nope. Still no eth0 ..

>  
>> This is the error I get:
>>
>> e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
>> e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
>> e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> e1000e 0000:02:00.0: setting latency timer to 64
>> e1000e 0000:02:00.0: irq 31 for MSI/MSI-X
>> e1000e 0000:02:00.0: Disabling ASPM L0s
>> 0000:02:00.0: 0000:02:00.0: NVM Read Error while reading MAC address
>> 0000:02:00.0: 0000:02:00.0: Invalid MAC Address: 00:00:00:00:00:00
> 
> the 00:00... for a mac address is pretty strange.  usually we get ff:ff 
> when things go wrong.  Does arch linux enable CONFIG_ASPM?  We made some 
> other changes to upstream to fix some bugs with the ASPM L0s disabling 
> code.


You can check all the kernel options Archlinux sets at
http://repos.archlinux.org/wsvn/packages/kernel26/repos/core-x86_64/


>> e1000e 0000:02:00.0: PCI INT A disabled
>> e1000e: probe of 0000:02:00.0 failed with error -5
> 
> There were some issues with the runtime power management in one of the 
> previous kernel revisions, you might be running into.  See below.
> 
> 
>>
>> lspci -v:
>>
>> 02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
>> Controller
>>         Subsystem: Toshiba America Info Systems PRO/1000 PL
>>         Flags: fast devsel, IRQ 16
>>         Memory at f0600000 (32-bit, non-prefetchable) [size=128K]
>>         I/O ports at 3000 [size=32]
>>         Capabilities: [c8] Power Management version 2
>>         Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
>>         Capabilities: [e0] Express Endpoint, MSI 00
>>         Capabilities: [100] Advanced Error Reporting
>>         Capabilities: [140] Device Serial Number 00-a0-d1-ff-ff-79-cb-eb
>>         Kernel modules: e1000e
> 
> please send output of lspci -vvv
> 

There you go:

02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet
Controller
        Subsystem: Toshiba America Info Systems PRO/1000 PL
        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-
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f0600000 (32-bit, non-prefetchable) [size=128K]
        Region 2: I/O ports at 3000 [size=32]
        Capabilities: [c8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [e0] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, 
L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ 
Unsupported+
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ 
TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM unknown, Latency 
L0
<128ns, L1 <64us
                        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-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq+ ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
                AERCap: First Error Pointer: 14, GenCap- CGenEn- ChkCap- ChkEn-
        Capabilities: [140 v1] Device Serial Number 00-a0-d1-ff-ff-79-cb-eb
        Kernel modules: e1000e

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to