From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: David Greaves <david@dgreaves.com>
Cc: Jens Laas <jens.laas@data.slu.se>,
Stephen Hemminger <shemminger@osdl.org>,
netdev@oss.sgi.com, ganesh.venkatesan@intel.com
Subject: Re: 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler
Date: Mon, 21 Jun 2004 10:42:58 -0600 [thread overview]
Message-ID: <1087836178.20902.23.camel@tubarao> (raw)
In-Reply-To: <40D2B114.5020201@dgreaves.com>
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
next prev parent reply other threads:[~2004-06-21 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 16:47 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out David Greaves
[not found] ` <20040615155111.26d6b809@dell_ss3.pdx.osdl.net>
2004-06-16 10:59 ` David Greaves
2004-06-18 8:04 ` Jens Laas
2004-06-18 9:08 ` 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler David Greaves
2004-06-18 10:27 ` Jens Laas
2004-06-18 12:51 ` David Greaves
2004-06-21 16:42 ` Thayne Harbaugh [this message]
2004-06-21 17:29 ` David Greaves
2004-06-21 17:43 ` ganesh.venkatesan
2004-06-21 18:34 ` David Greaves
2004-06-18 18:11 ` 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out Stephen Hemminger
2004-06-18 18:44 ` David Greaves
[not found] ` <20040618141629.0edd9766@dell_ss3.pdx.osdl.net>
2004-06-18 21:28 ` David Greaves
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 14:40 2.6.6 e1000 NETDEV WATCHDOG: eth0: transmit timed out+ delay scheduler Venkatesan, Ganesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1087836178.20902.23.camel@tubarao \
--to=tharbaugh@lnxi.com \
--cc=david@dgreaves.com \
--cc=ganesh.venkatesan@intel.com \
--cc=jens.laas@data.slu.se \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).