On Fri, Nov 16, 2012 at 04:27:25PM -0800, Jesse Brandeburg wrote:
> On Fri, 16 Nov 2012 14:58:13 -0800 akepner <[email protected]> wrote:
> 
> > With e1000e (versions 1.2.20, and 2.1.4) we've noticed that the 
> > ethtool selftest fails with a miscompare when the interface is 
> > up, but succeeds when it's down: 
> 
> Which hardware are you using?
> # lspci -nn

[admin@oak-sh317 ~]# ethtool -i lan0_0
driver: e1000e
version: 2.1.4-NAPI
firmware-version: 2.1-0
bus-info: 0000:03:00.0

[admin@oak-sh317 ~]# lspci -nn -s 0000:03:00.0 
03:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network 
Connection [8086:10d3]


> 
> what shows from:
> # ethtool lan0_0 

[admin@oak-sh317 ~]# ethtool lan0_0
Settings for lan0_0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes


> 
> is the cable plugged in while doing this? 

Yes.

> ... any output from dmesg? 

Just this:

e1000e 0000:03:00.0: lan0_0: offline testing starting
e1000e 0000:03:00.0: lan0_0: testing unshared interrupt
e1000e 0000:03:00.0: irq 104 for MSI/MSI-X
e1000e 0000:03:00.0: irq 105 for MSI/MSI-X
e1000e 0000:03:00.0: irq 106 for MSI/MSI-X
ADDRCONF(NETDEV_UP): lan0_0: link is not ready
e1000e: e1000e: lan0_0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
ADDRCONF(NETDEV_CHANGE): lan0_0: link becomes ready
lan0_0: no IPv6 routers present


> 
> what about if you up the messagelvl?
> 
> # ethtool -s lan0_0 msglvl 0xffff
> # ethtool -t lan0_0

I didn't see any change to dmesg output with msglvl at 0xffff.

> 
> this may output too much info, not sure.
> 
> I just know that the maintainers of the driver will want this info.

-- 
Arthur


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
E1000-devel mailing list
[email protected]
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