All of lore.kernel.org
 help / color / mirror / Atom feed
From: JG <jg@cms.ac>
To: Lincoln Dale <ltd@cisco.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: TG3: very high CPU usage
Date: Sat, 31 Jan 2004 10:15:51 +0100	[thread overview]
Message-ID: <20040131091559.8A026202D31@23.cms.ac> (raw)
In-Reply-To: <20040125123154.A8CA4202CAA@23.cms.ac>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

hi, 

i'm replying to my email.

> thank you for the info! i searched their site, but i only found a reference to BACS on their faq page and that this software should be on their driver cdrom (well, it is not on my netgear cdrom).
> but i'll test my cable with a fluke networks cable tester tomorrorw or on tuesday. i'll post the results if they are relevant.

well, i did a thorough cable test with a DSP-4100 fluke networks cable tester and i had some bad values. i've been using 3 cables (24m) with adapters, all single cables were fine, so the adapters seemed to cause the problem.
but i'm now using a longer x-over cable (30m) where i also get those speed problems. it is a *bit* better, i get about 1-2MB/s in both directions, but i'm also experiencing a very high error rate over the x-over cable...(~40-50 errors per second)

do you have this BACS software and is it possible to test the NIC itself with it? maybe one of my NICs is causing this.

thx,
JG


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-31  9:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19  3:35 TG3: very high CPU usage Mark Williams (MWP)
2004-01-20 12:33 ` JG
2004-01-20 23:13   ` Lincoln Dale
2004-01-21  3:19     ` Tom Sightler
2004-01-22  3:57       ` Lincoln Dale
2004-01-22 12:55         ` JG
2004-01-24 13:43           ` JG
2004-01-25  0:03             ` Lincoln Dale
2004-01-25 12:31               ` JG
2004-01-31  9:15                 ` JG [this message]
2004-02-01  0:20                   ` Lincoln Dale
2004-02-07 18:26                     ` JG
2004-02-08  0:00                       ` Lincoln Dale
2004-02-09 10:13                         ` JG
2004-01-22 16:06         ` Tom Sightler
     [not found] <fa.eu7l1gd.ekqe1j@ifi.uio.no>
2004-01-19 11:32 ` Andreas Hartmann
2004-01-20  3:54   ` Mark Williams (MWP)
     [not found] <fa.g9joqss.1nneajs@ifi.uio.no>
     [not found] ` <fa.e29fqcc.sick10@ifi.uio.no>
2004-01-20  9:17   ` Andreas Hartmann
2004-01-20  9:44     ` Lincoln Dale
2004-01-20 10:16       ` Mark Williams (MWP)
2004-01-20 12:09         ` Lincoln Dale

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=20040131091559.8A026202D31@23.cms.ac \
    --to=jg@cms.ac \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltd@cisco.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.