| To: | David Greaves <david@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler |
| From: | Thayne Harbaugh <tharbaugh@xxxxxxxx> |
| Date: | Mon, 21 Jun 2004 10:42:58 -0600 |
| Cc: | Jens Laas <jens.laas@xxxxxxxxxxx>, Stephen Hemminger <shemminger@xxxxxxxx>, netdev@xxxxxxxxxxx, ganesh.venkatesan@xxxxxxxxx |
| In-reply-to: | <40D2B114.5020201@xxxxxxxxxxxx> |
| Organization: | Linux Networx |
| References: | <40CDD68C.8070509@xxxxxxxxxxxx> <20040615155111.26d6b809@xxxxxxxxxxxxxxxxxxxxx> <40D0280B.2030308@xxxxxxxxxxxx> <Pine.LNX.4.60.0406180953240.1089@xxxxxxxxxxxxxxxxxx> <40D2B114.5020201@xxxxxxxxxxxx> |
| Reply-to: | tharbaugh@xxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 2004-06-18 at 03:08, David Greaves wrote: > Jens Laas wrote: > > We have tried different versions of e1000 without luck. > > Me too, 3 cards. > (did I mention I have 2 machines with very similar specs (AMD/VIAKT600) > and the other one works - actually, to be accurate, hasn't yet failed > but hasn't yet run at full speed - and it has a higher CPU speed) What do you mean by, ". . . hasn't yet run at full speed - and it has a higher CPU speed . . ." ? Does this mean that you can't get the card to have a reasonable throughput (~900Mbps)? -- Thayne Harbaugh Linux Networx |
| Previous by Date: | Re: RFC: [1/2] PPP MPPE module, Matt Domsch |
|---|---|
| Next by Date: | [patch-kj] net/ipv4/fib_hash.c: check kmem_cache_create(), maximilian attems |
| Previous by Thread: | Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler, David Greaves |
| Next by Thread: | Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler, David Greaves |
| Indexes: | [Date] [Thread] [Top] [All Lists] |