mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@hockin.org>
To: slug@aeminium.org (Nuno Miguel Fernandes Sucena Almeida)
Cc: linux-kernel@vger.kernel.org
Subject: Re: natsemi.c (linux 2.4.9) - Something Wicked happened! 18000
Date: Fri, 31 Aug 2001 23:37:06 -0700 (PDT)	[thread overview]
Message-ID: <200109010637.f816b6A28284@www.hockin.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0109010708370.19262-100000@aeminium.aeminium.pt> from "Nuno Miguel Fernandes Sucena Almeida" at Sep 01, 2001 07:45:34 AM

> kernel: eth2: Setting full-duplex based on negotiated link capability.
> kernel: eth2: Something Wicked happened! 18000.
> 
> With tcpdump at the other computer i got all the echo send icmp packets
> but the NS NIC didn't seem to receive the echo reply packets!
> 
> I searched the linux kernel mailing list and found a post with this same
> error. Tried to override link negotiation with mii-diag but no luck.
> 
> They said that after an upgrade from 2.4.5 to 2.4.6 the error
> started to appear. So, i grabbed the natsemi.c source code from 2.4.5,
> compiled it and the system is now working fine, even with 100MbpsTx-FD,
> giving 10MByte/s.


aha!  So I'll check the diffs since 2.4.5 - thanks for the data point.  One
thing I did to make this error go away was increase the RX ring - I don't
have the code here, or I'd post a patch.  If you wait until tomorrow, I'll
pop into work and check out the diffs and post you an elementary patch, and
you can tell me if it goes away.


  reply	other threads:[~2001-09-01  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01  6:45 Nuno Miguel Fernandes Sucena Almeida
2001-09-01  6:37 ` Tim Hockin [this message]
2001-09-01 18:27 Manfred Spraul
2001-09-01 21:02 ` Nuno Miguel Fernandes Sucena Almeida
2001-09-01 20:58   ` 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=200109010637.f816b6A28284@www.hockin.org \
    --to=thockin@hockin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slug@aeminium.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

all inboxes | Powered by JetHome®