Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out
From: David Greaves <hidden>
Date: 2004-06-18 21:28:53
OK Thanks for the pointers and time Stephen, much appreciated :) Ganesh and Jens - you said you'd like to keep this on-list so Stephen let's ensure your reply is archived... David Stephen Hemminger wrote:
It will be up to Intel (Genesh et al) to look at this. On Fri, 18 Jun 2004 19:44:10 +0100 David Greaves [off-list ref] wrote:quoted
Stephen Hemminger wrote:quoted
To get to the root of these problems, could you: * Give full lspci -v output for the boards in question.ash: 00:07.0 Ethernet controller: Intel Corp.: Unknown device 1076 Subsystem: Intel Corp.: Unknown device 1176 Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11 Memory at e3020000 (32-bit, non-prefetchable) [size=128K] Memory at e3000000 (32-bit, non-prefetchable) [size=128K] I/O ports at b400 [size=64] Expansion ROM at <unassigned> [disabled] [size=128K] Capabilities: [dc] Power Management version 2 Capabilities: [e4] PCI-X non-bridge device. Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-quoted
Jun 18 19:38:18 ash kernel: eth0: may be hung last tx was 2457 ticksThis means the code that in the e1000 watchdog is seeing the stuck board. The driver then calls netif_stop_queue which seems odd.quoted
Jun 18 19:38:20 ash kernel: eth0: may be hung last tx was 4457 ticks Jun 18 19:38:22 ash kernel: eth0: may be hung last tx was 6457 ticks Jun 18 19:38:24 ash kernel: eth0: may be hung last tx was 8457 ticks Jun 18 19:38:26 ash kernel: NETDEV WATCHDOG: eth0: transmit timed out after 5000 j iffies Jun 18 19:38:26 ash kernel: eth0: transmit timeout from queuing Jun 18 19:38:26 ash kernel: eth0: may be hung last tx was 10457 ticks Jun 18 19:38:26 ash kernel: eth0: state=0x7 transmit ring size=4096 count=256 to_u se=66 to_clean=59The state bits show: XOFF - stopped (but that was done in e1000_watchdog) START - board is running PRESENT - board is present. That looks okay, but what was the state in the e1000 watchdog??