linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bill Fincke <willy@synergymicro.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: GT64260 ethernet driver - long term stability?
Date: Thu, 30 May 2002 17:53:02 -0700	[thread overview]
Message-ID: <3CF6C96E.BD1DAA3A@synergymicro.com> (raw)
In-Reply-To: 200205100459.XAA27925@lists.linuxppc.org


Has anyone exercised the gt64260_eth.c driver (from the MontaVista
BK tree) for any length of time?  I ported it and have been using
it successfully for several weeks, but find that it can't sustain
continuous file transfers for more than a few hours.

I'm running a loop with ftp putting/getting a 24-MB file to a remote
Linux system, and find that after a few hours, the "put" times out.
It happens on any of the 3 ports, and to/from several different
systems (G4 Mac or PC).  I run the test on the same system through
a I82559 chip and it runs all weekend.

The only clue I have it that the driver reports a flurry of RX CRC
errors when the timeout occurs.  After ftp quits, I can ping the
remote system, but the RX packets seem to be mismatched with the
TX (ping reports once a second, but instead of ~100 usec transit
time, it reports 1.000 sec, or 2.000 sec, or 3.000 sec, as if it's
getting RX packets that are 1, 2, 3 seconds old).

Anyone else seen anything like this?

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-05-31  0:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200205100459.XAA27925@lists.linuxppc.org>
2002-05-10 17:13 ` "broken" GT64260 ethernet driver Bill Fincke
2002-05-10 17:24   ` mod+linuxppc-dev
2002-05-10 17:30     ` Mark A. Greer
2002-05-31  0:53 ` Bill Fincke [this message]
2002-05-31 11:21   ` GT64260 ethernet driver - long term stability? Geert Uytterhoeven
2002-05-31 21:52   ` Mark A. Greer

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=3CF6C96E.BD1DAA3A@synergymicro.com \
    --to=willy@synergymicro.com \
    --cc=linuxppc-dev@lists.linuxppc.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).