From: John Zielinski <john_ml@undead.cc>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: RTL 8139 stops RX after receiving a jumbo frame
Date: Sun, 26 Feb 2006 16:12:16 -0500 [thread overview]
Message-ID: <440219B0.6080301@undead.cc> (raw)
In-Reply-To: <1140957965.23286.9.camel@localhost.localdomain>
Alan Cox wrote:
> Should drop the packet, but it may be triggering a driver path with a
> bug. Is this repeatable and with multiple 8139 cards
>
I took the card out of my firewall and put it into my test box. The
test procedure was to ping a third machine from the text box and then
start pinging the test box from the second machine using large packets.
The rev K card would always stop receiving permanently until a
ifdown/ifup was done.
I tried three other cards and they only showed heavy packet loss from
the ping running on the test box. The packet loss went away when the
second machine stopped pinging it with the large packets.
Here's the list of cards:
Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
eth0: Identified 8139 chip type 'RTL-8139 rev K'
Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev 10)
Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter
eth0: Identified 8139 chip type 'RTL-8139B'
Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
Subsystem: D-Link System Inc DFE-538TX 10/100 Ethernet Adapter
eth0: Identified 8139 chip type 'RTL-8139C'
Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
eth0: Identified 8139 chip type 'RTL-8139C'
next prev parent reply other threads:[~2006-02-26 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 4:23 RTL 8139 stops RX after receiving a jumbo frame John Zielinski
2006-02-26 12:46 ` Alan Cox
2006-02-26 21:12 ` John Zielinski [this message]
2006-02-26 14:44 ` Francois Romieu
2006-02-26 21:13 ` John Zielinski
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=440219B0.6080301@undead.cc \
--to=john_ml@undead.cc \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).