On Thu, 2 Apr 2009, Chris Markle wrote:
> My system is a fc1 system (yeah I know... :( ): > > [r...@xxx root]# uname -a > Linux xxx 2.4.22-1.2174.nptlsmp #1 SMP Wed Feb 18 16:21:50 EST 2004 > i686 i686 i386 GNU/Linux > > running a pretty old (5.2.16) version of the e1000 driver: > > [r...@xxx root]# ethtool -i eth0 > driver: e1000 > version: 5.2.16 > firmware-version: N/A > bus-info: 01:01.0 > > I am seeing the eth0 device "flapping" (transitioning frequently from > link up to link down and back ala: > > Apr 2 12:03:35 delivery kernel: e1000: eth0 NIC Link is Down > Apr 2 12:03:37 delivery kernel: e1000: eth0 NIC Link is Up 1000 Mbps > Full Duplex > Apr 2 12:03:39 delivery kernel: e1000: eth0 NIC Link is Down > Apr 2 12:03:42 delivery kernel: e1000: eth0 NIC Link is Up 1000 Mbps > Full Duplex > [...] you failed to mention what hardware you have? > Ethtool shows our end in auto-negotiation mode and supposedly thw > switch is set teh same way: > > [r...@xxx root]# ethtool eth0 > Settings for eth0: > 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 auto-negotiation: Yes > Speed: 1000Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: on > Supports Wake-on: umbg > Wake-on: g > Link detected: yes > > I ran a ethtool diag test and got a FAIL result with the loopback test > showing a result of 13. > > [r...@delivery root]# ethtool -t eth0 offline > The test result is FAIL > The test extra info: > Register test (offline) 0 > Eeprom test (offline) 0 > Interrupt test (offline) 0 > Loopback test (offline) 13 > Link test (on/offline) 0 > > Curious as to what the 13 is telling me? Can someone also give me a > clue as to where in the current e1000 source code I should be looking > to see how self-test is done and if these result codes are documented > there in any way. (You know like "teach a man to fish..."). you're going to look in e1000_ethtool.c the function is e1000_diag_test, and from my quick look, code 13 from e1000_loopback_test is from a corrupt loopback test frame. This may indicate that your hardware is failing. you may want to try to download the e1000-8.0.9 or the latest e1000 driver from e1000.sourceforge.net, and just run that first to make sure that it wasn't a driver bug we fixed in the 4 or 5 years since the driver you're running was created :-) Jesse ------------------------------------------------------------------------------ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
