From: Tantilov, E. S <emi...@in...> - 2008-08-27 00:00:24
|
Leigh Sharpe wrote: > Hi All, > I'm having a problem with my e1000 cards intermittently shutting > down. This is happening across multiple cards, on multiple systems. I > get the following messages in the syslog at the time: > > Aug 26 22:58:36 ElizaQOS kernel: e1000: eth13: e1000_watchdog: NIC > Link is Down This message is from the driver and it means that the interface lost link for some reason. What is the link partner? > > ethtool and mii-tool both show a different status for the affected Use ethtool > leigh@ElizaQOS:~$ sudo ethtool eth13 > Settings for eth13: > 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: Unknown! (65535) > Duplex: Unknown! (255) > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: on > Supports Wake-on: umbg > Wake-on: d > Current message level: 0x00000007 (7) > Link detected: no > --- Ethtool output matches with the e1000 link down message. > > The port can be brought up by issuing this command: > > ethtool -s eth13 speed 100 duplex full autoneg on This command is actually incorrect. To force speed/duplex you need to use "autoneg off", but as John pointed out this will be invalid configuration if your link partner is set to auto. To reset the autonegotiation use ethtool -r instead. > which I assume simply restarts autonegotiation. Turning off autoneg > and setting the speed/duplex doesn't seem to help. > > This is on a Debian 2.6.18 kernel. lspci and lspci -t attached. What is the version of e1000? > Any ideas what might be happening? It's not obvious and I have not seen the link go down unless the cable was disconnected, or perhaps a problem with the link partner of some sort. Thanks, Emil |