Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*2\.6\.6\s+e1000\s+NETDEV\s+WATCHDOG\:\s+eth0\:\s+transmit\s+timed\s+out\s*$/: 10 ]

Total 10 documents matching your query.

1. 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: xxxxxx>
Date: Mon, 14 Jun 2004 17:47:08 +0100
I have 2 machines with Intel/Pro 1000MT cards. One machine seems to work fine (AFAIK), the other has major problems. I've swapped the cards and the problem stays on the machine. I'm using version 5.
/archives/netdev/2004-06/msg00350.html (10,598 bytes)

2. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: Szepe <szepe@xxxxxxxxxxxxxxx>
Date: Wed, 16 Jun 2004 11:59:23 +0100
Stephen Hemminger wrote: How big is the transmit ring. Setting a bigger transmit ring fixed my problem modprobe e1000 TxDescriptors=1024 Also, there are lots of flavors of this chipset and board. One
/archives/netdev/2004-06/msg00416.html (12,952 bytes)

3. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: fuji@xxxxxxxxxxxxxx>
Date: Fri, 18 Jun 2004 11:11:24 -0700
To get to the root of these problems, could you: * Give full lspci -v output for the boards in question. * Are you using any special queuing or shaping (output of "tc qdisc ls") * You could try the f
/archives/netdev/2004-06/msg00549.html (12,514 bytes)

4. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: mminger@xxxxxxxx>
Date: Fri, 18 Jun 2004 19:44:10 +0100
Stephen Hemminger wrote: 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 Su
/archives/netdev/2004-06/msg00551.html (21,367 bytes)

5. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: x (Luis R. Rodriguez)
Date: Fri, 18 Jun 2004 22:28:53 +0100
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 wro
/archives/netdev/2004-06/msg00566.html (13,354 bytes)

6. 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: David Greaves <david@xxxxxxxxxxxx>
Date: Mon, 14 Jun 2004 17:47:08 +0100
Hi I have 2 machines with Intel/Pro 1000MT cards. One machine seems to work fine (AFAIK), the other has major problems. I've swapped the cards and the problem stays on the machine. I'm using version
/archives/netdev/2004-06/msg01234.html (10,392 bytes)

7. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: David Greaves <david@xxxxxxxxxxxx>
Date: Wed, 16 Jun 2004 11:59:23 +0100
How big is the transmit ring. Setting a bigger transmit ring fixed my problem modprobe e1000 TxDescriptors=1024 Also, there are lots of flavors of this chipset and board. One machine I was using had
/archives/netdev/2004-06/msg01300.html (13,270 bytes)

8. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Fri, 18 Jun 2004 11:11:24 -0700
To get to the root of these problems, could you: * Give full lspci -v output for the boards in question. * Are you using any special queuing or shaping (output of "tc qdisc ls") * You could try the f
/archives/netdev/2004-06/msg01433.html (12,757 bytes)

9. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: David Greaves <david@xxxxxxxxxxxx>
Date: Fri, 18 Jun 2004 19:44:10 +0100
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.: Un
/archives/netdev/2004-06/msg01435.html (23,971 bytes)

10. Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out (score: 1)
Author: David Greaves <david@xxxxxxxxxxxx>
Date: Fri, 18 Jun 2004 22:28:53 +0100
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 It will be up to In
/archives/netdev/2004-06/msg01450.html (13,687 bytes)


This search system is powered by Namazu