From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: John Zielinski <john_ml@undead.cc>
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 12:46:05 +0000 [thread overview]
Message-ID: <1140957965.23286.9.camel@localhost.localdomain> (raw)
In-Reply-To: <44012D53.30700@undead.cc>
On Sad, 2006-02-25 at 23:23 -0500, John Zielinski wrote:
> I'm surprised that the switch actually let the jumbo packet through onto
> a 100Mbit link. I'm going to see if I can find a non RTL 8139 card in
> my parts bin and see what that one does.
>
> What's the normal behavior for overruns on an interface?
Should drop the packet, but it may be triggering a driver path with a
bug. Is this repeatable and with multiple 8139 cards /
next prev parent reply other threads:[~2006-02-26 12:46 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 [this message]
2006-02-26 21:12 ` John Zielinski
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=1140957965.23286.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=john_ml@undead.cc \
--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).