From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Tim Hockin <thockin@hockin.org>
Cc: Colin Paton <colin.paton@etvinteractive.com>,
linux-kernel@vger.kernel.org
Subject: Re: Natsemi ethernet 'cable magic' fix can cause problems
Date: Sat, 31 Jul 2004 11:51:13 -0300 [thread overview]
Message-ID: <20040731145113.GF6497@logos.cnet> (raw)
In-Reply-To: <20040513170358.GA19426@hockin.org>
On Thu, May 13, 2004 at 10:03:58AM -0700, Tim Hockin wrote:
> On Thu, May 13, 2004 at 11:35:03AM +0100, Colin Paton wrote:
> > The problem was strange - about 30% packet loss was experienced during
> > pings. Moving the box to a different ethernet wall outlet (but still
> > using the same port on the switch) cured the problem. The problem
> > therefore appeared to be cable dependant.
> >
> > It would appear that the call to 'do_cable_magic()' in
> > drivers/net/natsemi.c causes the problem to occur.
> >
> > It looks as though this was added in to actually *fix* such problems...
> > but in our case it made things worse.
>
> I'm the responsible party on that one. do_cable_magic() was a direct
> result of a significant amount of work with National's engineers to
> root-cause some major problems we had had.
>
> If I recall, the problem we experienced was when the cable was "short"
> (where short was < 30m, I think). What can you tell me about your cabling
> setup?
>
> Willing to test? Ping me back.
Hi Tim, Collin,
Did you made any progress on this issue?
next prev parent reply other threads:[~2004-07-31 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 10:35 Natsemi ethernet 'cable magic' fix can cause problems Colin Paton
2004-05-13 17:03 ` Tim Hockin
2004-07-31 14:51 ` Marcelo Tosatti [this message]
2004-07-31 18:11 ` Tim Hockin
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=20040731145113.GF6497@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=colin.paton@etvinteractive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.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